I am sure the "older route wins" selection takes place here. We should probably dig deeper on Cisco's site to find specifics on route selection in this case, but evidence points to it.
Take a look, I will make comments in-line. To test, try removing the route in 1000:3, wait few minutes and reactivate it. See if the same selection takes place. If not, this is indeed the case. If the same route is chosen, we need to look even deeper (debug). > BGP routing table entry for 1000:2:123.123.123.123/32, version 8 <--- note > version > Paths: (1 available, best #1, no table) > Not advertised to any peer > 200 1000 > 200.254.254.2 (metric 1) from 100.254.254.9 (100.254.254.9) > Origin IGP, metric 0, localpref 100, valid, internal, best > Extended Community: RT:1000:1000, > mpls labels in/out nolabel/214 > BGP routing table entry for 1000:3:123.123.123.123/32, version 5 <--- note > version > Paths: (1 available, best #1, no table) > Not advertised to any peer > 200 1000 > 200.254.254.3 (metric 1) from 100.254.254.9 (100.254.254.9) > Origin IGP, metric 0, localpref 100, valid, internal, best > Extended Community: RT:1000:1000, > mpls labels in/out nolabel/306 > BGP routing table entry for 1000:8:123.123.123.123/32, version 9 > Paths: (2 available, best #1, table sp1000) <--- Older route is chosen > Advertised to update-groups: > 1 > 200 1000, imported path from 1000:3:123.123.123.123/32 > 200.254.254.3 (metric 1) from 100.254.254.9 (100.254.254.9) > Origin IGP, metric 0, localpref 100, valid, internal, best > Extended Community: RT:1000:1000, > mpls labels in/out 816/306 > 200 1000, imported path from 1000:2:123.123.123.123/32 > 200.254.254.2 (metric 1) from 100.254.254.9 (100.254.254.9) > Origin IGP, metric 0, localpref 100, valid, internal > Extended Community: RT:1000:1000, > mpls labels in/out 816/214 -- Marko CCIE #18427 (SP) My network blog: http://cisco.markom.info/ _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
