[nsp] BGP best path

Oliver Boehmer (oboehmer) oboehmer at cisco.com
Mon May 17 06:17:20 EDT 2004


> I might be overlooking something here, but how can this be? In my view
> the first route should be preferred...
> 
> rtr#sh ip bgp vp rd xxxx:666 1.2.3.4
> BGP routing table entry for xxxx:666:1.2.3.4/32, version 39464
> Bestpath Modifiers: deterministic-med
> Paths: (2 available, best #2, no table)
>   Advertised to update-groups:
>      1          2          3          4
>   Local, (Received from a RR-client)
>     x.y.64.1 (metric 8) from x.y.64.1 (x.y.73.1)
>       Origin incomplete, metric 146944, localpref 110, valid, internal
>       Extended Community: RT:xxxx:666 RT:xxxx:9999 0x8800:32768:0
>         0x8801:10:130048 0x8802:65281:16896 0x8803:65319:1514
>   Local
>     x.y.108.6 (metric 16) from x.y.108.9 (x.y.108.9)
>       Origin incomplete, metric 25753600, localpref 100, valid,
>       internal, best Extended Community: RT:xxxx:666 RT:xxxx:9999
>         Cost:pre-bestpath:128:25753600 (default-2121730047)
>         0x8800:32768:0 0x8801:10:25728000 0x8802:65281:25600
>       0x8803:65285:1500 Originator: x.y.108.6, Cluster list: x.y.108.9

You're using BGP cost community with POI "pre-bestpath", which
influences the path selection at the top of the decision algorithm (see
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_
guide09186a00801eff5f.html). When a route doesn't carry a cost
community, the default value (2147483647) is assumed, so the second path
wins as its cost is lower.

	oli



More information about the cisco-nsp mailing list