[c-nsp] route-target import on non-leaking PEs

Jason Lixfeld jason at lixfeld.ca
Thu Dec 13 14:42:24 EST 2012


On 2012-12-13, at 10:28 AM, Jason Lixfeld <jason at lixfeld.ca> wrote:

> rrc-3600#sh ip bgp vpnv4 vrf Inetv4 0.0.0.0
> BGP routing table entry for 1:4:0.0.0.0/0, version 20719
> Paths: (2 available, best #1, table Inetv4, not advertised to EBGP peer)
> Multipath: iBGP
>  Not advertised to any peer
>  Refresh Epoch 1
>  Local
>    1.1.1.11 (metric 30) from 1.1.1.11 (1.1.1.11)
>      Origin IGP, metric 0, localpref 100, valid, internal, best
>      Community: 1:65535 no-export
>      Extended Community: RT:1:4
>      mpls labels in/out nolabel/16000
>      rx pathid: 0, tx pathid: 0x0
>  Refresh Epoch 1
>  Local
>    1.1.1.10 (metric 40) from 1.1.1.10 (1.1.1.10)
>      Origin IGP, metric 0, localpref 100, valid, internal
>      Community: 1:65535 no-export
>      Extended Community: RT:1:4
>      mpls labels in/out nolabel/289985
>      rx pathid: 0, tx pathid: 0
> rrc-3600#sh ip cef vrf Inetv4 0.0.0.0/0 detail
> 0.0.0.0/0, epoch 0, flags rib defined all labels, default route
>  recursive via 1.1.1.11 label 16000
>    nexthop 1.1.1.197 TenGigabitEthernet0/2 label 36
> rrc-3600#
> 
>> But yes, my original email should have been more specific: unless you have add-paths, unique RD is required for multipath.
> 
> So... looks like I do need to do a different RD on my other default-route-sourcing PE.  If I'm reading the output of those two commands correctly, add path seems to be there on the 7600s (albeit in an undocumented manner) but not at all on the ME3600s.

So after thinking about this a little more, I realized that my ME3600 example was incorrect.   The reference device wasn't actually sitting equidistant between the two PEs sourcing the default routes.  When I check the routing table and the cef table for the default route, the results lead me to believe that multi-path is actually working, meaning that add path is doing what it's supposed to.  Am I wrong?

rrc-3600#sh ip bgp vpnv4 vrf Inetv4 0.0.0.0/0
BGP routing table entry for 1:4:0.0.0.0/0, version 347497
Paths: (2 available, best #2, table Inetv4, not advertised to EBGP peer)
Multipath: iBGP
  Not advertised to any peer
  Local
    1.1.1.11 (metric 50) from 1.1.1.11 (1.1.1.11)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath
      Community: 1:65535 no-export
      Extended Community: RT:1:4
      mpls labels in/out nolabel/16000
  Local
    1.1.1.10 (metric 50) from 1.1.1.10 (1.1.1.10)
      Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
      Community: 1:65535 no-export
      Extended Community: RT:1:4
      mpls labels in/out nolabel/289985
rrc-3600#sh ip cef vrf Inetv4 0.0.0.0/0 detail 
0.0.0.0/0, epoch 0, flags rib defined all labels, per-destination sharing
  recursive via 1.1.1.10 label 289985
    nexthop 72.15.51.42 TenGigabitEthernet0/1 label 100
  recursive via 1.1.1.11 label 16000
    nexthop 72.15.51.87 TenGigabitEthernet0/2 label 94
rrc-3600#




More information about the cisco-nsp mailing list