How the order of PATHS in bgp table is governed ? is it on first come basis or based on preference ??
for example in below output , path 3 will prefer path 2 but is listed as path 3 .... Any views here ......
sh bgp vrf ONE97-H2 172.21.214.161
Mon Jan 28 05:30:17.777 IST
BGP routing table entry for 172.21.214.0/24, Route Distinguisher: 9730:22790
Versions:
Process bRIB/RIB SendTblVer
Speaker 2971637905 2971637905
Last Modified: Jul 18 01:05:27.680 for 27w5d
Paths: (3 available, best #1)
Advertised to CE peers (in unique update groups):
172.37.141.98
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
172.37.141.98
64520
172.37.141.214 from 172.37.141.214 (172.37.138.54)
Origin incomplete, metric 0, localpref 100, valid, external, best, group-best, import-candidate, imported
Received Path ID 0, Local Path ID 0, version 2971637905
Extended community: RT:9730:22774
Source AFI: VPNv4 Unicast, Source VRF: ONE97-S4, Source Route Distinguisher: 9730:22990
Path #2: Received by speaker 0
Not advertised to any peer
64520 64520 64520
x.x.37.49 (metric 322) from x.x..37.10 (x.x..37.49)
Received Label 27022
Origin incomplete, metric 0, localpref 100, valid, internal, imported
Received Path ID 0, Local Path ID 0, version 0
Extended community: RT:9730:22774
Originator: x.x.37.49, Cluster list: 0.0.0.22, 0.0.38.2, 0.0.0.80
Source AFI: VPNv4 Unicast, Source VRF: default, Source Route Distinguisher: 9730:22774
Path #3: Received by speaker 0
Not advertised to any peer
64520 64520
x.x.x.x.220 (metric 2) from x.x.x.10 (x.x.x..220)
Received Label 4579
Origin incomplete, metric 0, localpref 100, valid, internal, imported
Received Path ID 0, Local Path ID 0, version 0
Extended community: RT:9730:22774
Originator: x.x.x..220, Cluster list: 0.0.0.22
Source AFI: VPNv4 Unicast, Source VRF: default, Source Route Distinguisher: 9730:22775
