[j-nsp] L3VPN routes seem unresolvable
Jeff S Wheeler
jsw at inconcepts.biz
Sun May 1 00:24:04 EDT 2005
Dear list,
I am having a great deal of trouble with L3VPN configured per Juniper
examples in a simple topology. JUNOS is 7.2R1.7 with no E-FPCs
available.
In particular, I can find no documentation to shed light on the
`Indirect next-hop: 2 no-forward` condition reported on my VPN routes.
I would expect the routes to be hidden in this condition, but in fact
they are active and installed into the PFE as discard routes. I presume
the discard next-hop is being installed because a valid next-hop cannot
be computed by rpd.
In the below `show route ...` output, a default route is advertised by
PE1 to PE2. VPN label information seems to be correctly signalled, and
a route to PE1's loopback interface is present in PE2's inet.3 table.
PE1 is connected directly to PE2 via ATM (at-2/2/0.33 on PE1 to
at-0/3/0.33 on PE2); PE1's lo0.0 is numbered 1.2.3.4, PE2 1.2.3.5, for
the purposes of the below example output.
Any suggestions would be appreciated.
Kind regards,
--
Jeff Wheeler <jsw at inconcepts.biz>
pe2>
inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
1.2.3.4/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP Preference: 7
Next-hop reference count: 33
Next hop: via at-0/3/0.33 weight 1, selected
Label-switched-path pe2-pe1
State: <Active Int>
Local AS: 55555
Age: 2:55:48 Metric: 11
Task: RSVP
Announcement bits (2): 2-Resolve tree 1 3-Resolve tree
2
AS path: I
bgp.l3vpn.0: 25 destinations, 25 routes (25 active, 0 holddown, 0
hidden)
Restart Complete
1.2.3.4:999:0.0.0.0/0 (1 entry, 0 announced)
*BGP Preference: 170/-101
Route Distinguisher: 1.2.3.4:999
Next-hop reference count: 7
Source: 1.2.3.4
Protocol next hop: 1.2.3.4
Push 100256
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS: 55555 Peer AS: 55555
Age: 5:36:38 Metric2: 11
Task: BGP_55555.1.2.3.4+179
AS path: I
Communities: 55555:19 target:999:0
VPN Label: 100256
Localpref: 100
Router ID: 1.2.3.4
Secondary Tables: vpna.inet.0
Indirect next hops: 1
Protocol next hop: 1.2.3.4 Metric: 11
Push 100256
Indirect next hop: 2 no-forward
Indirect path forwarding next hops: 1
Next hop: via at-0/3/0.33 weight 1
1.2.3.4/32 Originating RIB: inet.3
Metric: 11 Node path
count: 1
Forwarding nexthops: 1
Nexthop: via at-0/3/0.33
vpna.inet.0: 34 destinations, 34 routes (34 active, 0 holddown, 0
hidden)
Restart Complete
0.0.0.0/0 (1 entry, 1 announced)
TSI:
KRT in-kernel 0.0.0.0/0 -> {indirect(no-forward)}
*BGP Preference: 170/-101
Route Distinguisher: 1.2.3.4:999
Next-hop reference count: 7
Source: 1.2.3.4
Protocol next hop: 1.2.3.4
Push 100256
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS: 55555 Peer AS: 55555
Age: 1:21:01 Metric2: 11
Task: BGP_55555.1.2.3.4+179
Announcement bits (1): 0-KRT
AS path: I
Communities: 55555:19 target:999:0
VPN Label: 100256
Localpref: 100
Router ID: 1.2.3.4
Primary Routing Table bgp.l3vpn.0
pe1> show route advertising-protocol bgp 1.2.3.5 table vpna.inet.0
0.0.0.0/0 exact extensive
vpna.inet.0: 74 destinations, 77 routes (73 active, 0 holddown, 1
hidden)
Restart Complete
* 0.0.0.0/0 (1 entry, 1 announced)
BGP group iBGP type Internal
Route Distinguisher: 1.2.3.4:999
VPN Label: 100256
Nexthop: Self
Localpref: 100
AS path: I
Communities: 55555:19 target:999:0
More information about the juniper-nsp
mailing list