[j-nsp] SRX-OSPF problem
Gökhan Gümüş
ggumus at gmail.com
Mon Dec 27 11:45:50 EST 2010
Hi ,
Pls see my policies on both routers,
R1,
R1> show configuration policy-options
policy-statement static-direct-to-ospf {
term 10 {
from protocol [ static direct ];
then accept;
R2,
R2> show configuration policy-options
policy-statement static-direct-to-ospf {
term 10 {
from protocol [ static direct ];
then accept;
Thanks and regards,
Gokhan
2010/12/27 Cristian Frizziero <cristian.frizziero at iquall.net>
> Could you copy the detail of the policy you are applying?
>
> Thanks
>
> [image: Logo]
>
> Ing. Cristian Frizziero
> Honorio Pueyrredon 1475
> Buenos Aires - Argentina
>
> Tel. +54.11.4855.6041 (Ext. 517)
> Cel. +54.11.6811.7562
>
> [image: dd] cristian.frizziero
>
> [image: m] Mail cristian.frizziero at iquall.net
> Web www.iquall.net
>
>
>
>
>
>
> El 27/12/2010 13:15, Smith W. Stacy escribió:
>
> Thanks, but we need the 'show ospf database exensive' output as well.
>
> --Stacy
>
>
> On Dec 27, 2010, at 9:11 AM, Gökhan Gümüş wrote:
>
>
> Hi all,
>
> Also please see the show ospf route detail output from boh routers,
>
> R1,
> thewiz at dcn.lon10.uk> show ospf route detail
> Topology default Route Table:
>
> Prefix Path Route NH Metric NextHop Nexthop
> Type Type Type Interface Address/LSP10.100.9.16/32 Intra Network IP 0 lo0.0
> area 0.0.0.0, origin 10.100.9.16, priority low
>
>
> R2,
>
> R2> show ospf route detail
> Topology default Route Table:
>
> Prefix Path Route NH Metric NextHop Nexthop
> Type Type Type Interface Address/LSP
> 10.100.9.1 Intra AS BR IP 1 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, optional-capability 0x2
> 10.100.9.2 Intra AS BR IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.2, optional-capability 0x2
> 10.100.9.4 Intra AS BR IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.4, optional-capability 0x2
> 10.100.9.5 Intra AS BR IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.5, optional-capability 0x2
> 10.100.9.13 Intra AS BR IP 1 ge-0/0/0.55 10.100.0.35
> area 0.0.0.0, origin 10.100.9.13, optional-capability 0x2
> 10.100.9.18 Intra AS BR IP 1 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, optional-capability 0x2
> 10.100.9.20 Intra AS BR IP 1 ge-0/0/0.55 10.100.0.42
> area 0.0.0.0, origin 10.100.9.20, optional-capability 0x2
> 10.100.9.25 Intra AS BR IP 1 ge-0/0/0.55 10.100.0.47
> area 0.0.0.0, origin 10.100.9.25, optional-capability 0x2
> 10.100.9.39 Intra Router IP 1 ge-0/0/0.50 10.100.0.245
> area 0.0.0.0, origin 10.100.9.39, optional-capability 0x0
> 10.100.9.41 Intra AS BR IP 1 ge-0/0/0.50 10.100.0.246
> area 0.0.0.0, origin 10.100.9.41, optional-capability 0x20.0.0.0/0 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium10.100.0.0/27 Intra Network IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.5, priority medium10.100.0.32/27 Intra Network IP 1 ge-0/0/0.55
> area 0.0.0.0, origin 10.100.9.25, priority low10.100.0.128/27 Intra Network IP 2 ge-0/0/0.50 10.100.0.245
> area 0.0.0.0, origin 10.100.9.39, priority medium10.100.0.160/27 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.246
> area 0.0.0.0, origin 10.100.9.41, priority medium10.100.0.240/28 Intra Network IP 1 ge-0/0/0.50
> area 0.0.0.0, origin 10.100.9.1, priority low10.100.1.0/28 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.4, priority medium10.100.1.16/28 Intra Network IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium10.100.1.32/28 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.2, priority medium10.100.1.64/28 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.5, priority medium10.100.1.176/28 Intra Network IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium10.100.2.16/28 Intra Network IP 2 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium10.100.2.19/32 Ext2 Network IP 0 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium10.100.2.32/28 Intra Network IP 2 ge-0/0/0.55 10.100.0.47
> area 0.0.0.0, origin 10.100.9.25, priority medium10.100.2.48/28 Intra Network IP 2 ge-0/0/0.55 10.100.0.42
> area 0.0.0.0, origin 10.100.9.20, priority medium10.100.2.55/32 Ext2 Network IP 0 ge-0/0/0.55 10.100.0.42
> area 0.0.0.0, origin 10.100.9.20, priority medium10.100.2.56/32 Ext2 Network IP 0 ge-0/0/0.55 10.100.0.42
> area 0.0.0.0, origin 10.100.9.20, priority medium10.100.2.80/28 Intra Network IP 2 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium10.100.2.87/32 Ext2 Network IP 0 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium10.100.2.128/28 Intra Network IP 2 ge-0/0/0.55 10.100.0.35
> area 0.0.0.0, origin 10.100.9.13, priority medium10.100.5.0/28 Intra Network IP 2 ge-0/0/0.50 10.100.0.245
> area 0.0.0.0, origin 10.100.9.39, priority medium10.100.6.0/28 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.246
> area 0.0.0.0, origin 10.100.9.41, priority medium10.100.9.1/32 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium10.100.9.2/32 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.2, priority medium10.100.9.4/32 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.4, priority medium10.100.9.5/32 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.5, priority medium10.100.9.13/32 Intra Network IP 1 ge-0/0/0.55 10.100.0.35
> area 0.0.0.0, origin 10.100.9.13, priority medium10.100.9.18/32 Intra Network IP 1 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium10.100.9.20/32 Intra Network IP 1 ge-0/0/0.55 10.100.0.42
> area 0.0.0.0, origin 10.100.9.20, priority medium10.100.9.25/32 Intra Network IP 1 ge-0/0/0.55 10.100.0.47
> area 0.0.0.0, origin 10.100.9.25, priority medium10.100.9.39/32 Intra Network IP 1 ge-0/0/0.50 10.100.0.245
> area 0.0.0.0, origin 10.100.9.39, priority medium10.100.9.41/32 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.246
> area 0.0.0.0, origin 10.100.9.41, priority medium10.111.1.0/30 Ext2 Network IP 0 ge-0/0/0.55 10.100.0.40
> area 0.0.0.0, origin 10.100.9.18, priority medium82.98.222.32/27 Intra Network IP 2 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium192.168.0.24/30 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium192.168.0.28/30 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.241
> area 0.0.0.0, origin 10.100.9.1, priority medium192.168.1.0/24 Ext2 Network IP 0 ge-0/0/0.50 10.100.0.246
> area 0.0.0.0, origin 10.100.9.41, priority medium
>
>
> Thanks,
> Gokhan
>
> On Mon, Dec 27, 2010 at 5:00 PM, Smith W. Stacy <stacy at acm.org> <stacy at acm.org> wrote:
> Can you provide the output of 'show ospf database extensive' and 'show ospf route detail' from both routers?
>
> --Stacy
>
>
> On Dec 27, 2010, at 8:48 AM, Gökhan Gümüş wrote:
>
>
> 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.5510.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.010.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.nethttps://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
More information about the juniper-nsp
mailing list