[j-nsp] SRX-OSPF problem

Stefan Fouant sfouant at shortestpathfirst.net
Mon Dec 27 10:59:54 EST 2010


Instead of simply doing a 'show route', can you show us the result of a
'show ospf database extensive'.

Stefan Fouant, CISSP, JNCIEx2
GPG Key ID: 0xB4C956EC

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Gökhan Gümüs
> Sent: Monday, December 27, 2010 10:48 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] SRX-OSPF problem
> 
> Hi all,
> 
> I have two Juniper SRX 210 router which are connected via VPLS.
> VPLS is up and running.
> I am using 10.1R1.8 version on both boxes.
> My question is even if OSPF is up and running, routes are not being
> exchanged each other.
> I am accepting all OSPF traffic on security zones.
> 
> R1> show configuration protocols ospf
> 
> export static-direct-to-ospf;
> area 0.0.0.0 {
>     interface ge-0/0/0.55;
>     interface lo0.0;
> 
> R1> show configuration interfaces ge-0/0/0.55
> vlan-id 55;
> family inet {
>     address 10.100.0.38/27;
> }
> 
> R1> show configuration interfaces lo0
> unit 0 {
>     family inet {
>         address 10.100.9.16/32;
> 
> 
> -----------------------------------------------------------------------
> -
> 
> R2> show configuration protocols ospf
> 
> export static-direct-to-ospf;
> area 0.0.0.0 {
>     interface ge-0/0/0.50 {
>         priority 128;
>     }
>     interface ge-0/0/0.55 {
>         priority 255;
> 
> R2> show configuration interfaces ge-0/0/0.55
> description "[DCN-UK]";
> vlan-id 55;
> family inet {
>     address 10.100.0.34/27;
> }
> 
> R2> show configuration interfaces lo0
> unit 0 {
>     family inet {
>         address 10.100.9.12/32 {
>             primary;
>             preferred;
>         }
>         address 127.0.0.1/32;
> 
> R1> show ospf neighbor
> Address          Interface              State     ID               Pri
> Dead
> 10.100.0.34      ge-0/0/0.55            Full      10.100.9.12      255
> 36
> 
> R1> show route
> 
> inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
> + = Active Route, - = Last Active, * = Both
> 
> 10.100.0.32/27     *[Direct/0] 16:20:03
>                     > via ge-0/0/0.55
> 10.100.0.38/32     *[Local/0] 16:20:08
>                       Local via ge-0/0/0.55
> 10.100.2.96/28     *[Direct/0] 16:18:41
>                     > via vlan.0
> 10.100.2.110/32    *[Local/0] 16:21:05
>                       Local via vlan.0
> 10.100.9.16/32     *[Direct/0] 16:21:20
>                     > via lo0.0
> 224.0.0.5/32       *[OSPF/10] 16:21:21, metric 1
>                       MultiRecv
> 
> 
> ------------------------------------------------
> 
> R2> show ospf neighbor
> Address          Interface              State     ID               Pri
> Dead
> 10.100.0.38      ge-0/0/0.55            Full      10.100.9.16      128
> 31
> 
> R2> show route
> 
> 10.100.2.19/32     *[OSPF/150] 16:30:39, metric 0, tag 0
>                     > to 10.100.0.40 via ge-0/0/0.55
> 10.100.2.32/28     *[OSPF/10] 16:30:39, metric 2
>                     > to 10.100.0.47 via ge-0/0/0.55
> 10.100.2.48/28     *[OSPF/10] 16:17:38, metric 2
>                     > to 10.100.0.42 via ge-0/0/0.55
> 10.100.2.55/32     *[OSPF/150] 16:17:38, metric 0, tag 0
>                     > to 10.100.0.42 via ge-0/0/0.55
> 
> Is there anyone who might explain that strange behaviour?
> 
> Thanks,
> Gokhan
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp




More information about the juniper-nsp mailing list