Is there a known issue with OpenBGPD ignoring MED during its path
selection? Note that the first item listed is best below and it has a
MED of 12. The others are 10 which should be preferred over 12. I'm
guessing that it's then going to a later stage of path selection where
it's choosing hte lowest router ID of 77.171.0.2.
--- BEGIN ---
rr2# bgpctl show ip bgp detail 20.139.176.0
BGP routing table entry for 20.139.0.0/16
1239 3549
Nexthop 77.171.0.2 (via 77.171.7.136) from r02 (77.171.0.6)
Origin IGP, metric 12, localpref 80, internal, valid, best
Last update: 2d05h35m ago
Communities: 5150:180
Originator Id: 77.171.0.6
Cluster ID List: 77.171.0.17
BGP routing table entry for 20.139.0.0/16
3356 3549
Nexthop 77.171.0.13 (via 77.171.7.138) from r03 (77.171.0.13)
Origin IGP, metric 10, localpref 80, internal, valid
Last update: 2d05h14m ago
Communities: 5150:180
Originator Id: 77.171.0.13
Cluster ID List: 77.171.0.17
BGP routing table entry for 20.139.0.0/16
1239 3549
Nexthop 77.171.0.2 (via 77.171.7.136) from rr1 (77.171.0.16)
Origin IGP, metric 12, localpref 80, internal, valid
Last update: 2d05h25m ago
Communities: 5150:180
Originator Id: 77.171.0.6
Cluster ID List: 77.171.0.17 77.171.0.16
BGP routing table entry for 20.139.0.0/16
7018 3549
Nexthop 77.171.0.28 (via 77.171.7.130) from r03.crossroads (77.171.0.28)
Origin IGP, metric 10, localpref 80, internal, valid
Last update: 2d05h35m ago
Communities: 5150:180
Originator Id: 77.171.0.28
Cluster ID List: 77.171.0.17
--- END ---
This is running bgpd that came with 4.9, I haven't tested a -current
compiled bgpd yet.
OpenBSD rr2 4.9 GENERIC.MP#819 amd64
On a related note I put a few of these routers in over the weekend and
everything else is working incredibly well!
--Chris
