I'm currently evaluating RouterOS v7.6 using the CHR.
I'm probably overlooking something simple here but I don't know where else to go.
The BGP documentation (https://help.mikrotik.com/docs/display/ ... hSelection) for Best Path Selection states:
Prefer the path with the highest LOCAL_PREF.
This attribute is used only within an AS. A path without the LOCAL_PREF attribute has a value of 100 by default.
I cannot understand why a route with bgp-local-preference 80 is preferred over a route with bgp-local-preference 120.
Here is the output of "routing/route/print detail where bgp dst-address=220.127.116.11/8"
The inactive BGP route (local pref 120) next hop is reachable on the loopback of the iBGP peer through OSPF.
The active BGP route (local pref 80) next is reachable on the other side of a directly connected network.
NOTE: This is within a LAB environment as we are still evaluating, so happy to share full configs or any other output as required.
Code: Select all
[admin@UK-IX2-SOUTH] > routing/route/print detail where bgp dst-address=18.104.22.168/8 Flags: X - disabled, F - filtered, U - unreachable, A - active; c - connect, s - static, r - rip, b - bgp, o - ospf, d - dhcp, v - vpn, m - modem, a - ldp-address, l - ldp-mapping, y - copy; H - hw-offloaded; + - ecmp, B - blackhole b afi=ip4 contribution=best-candidate dst-address=22.214.171.124/8 routing-table=main gateway=10.255.255.1 immediate-gw=10.0.0.1%ether3 distance=200 scope=40 target-scope=30 belongs-to="bgp-IP-10.255.255.1" bgp.peer-cache-id=*B000003 .as-path="1264" .communities=1111:120 .local-pref=120 .atomic-aggregate=yes .origin=igp debug.fwp-ptr=0x20342360 Ab afi=ip4 contribution=active dst-address=126.96.36.199/8 routing-table=main gateway=188.8.131.52 immediate-gw=184.108.40.206%ether1 distance=20 scope=40 target-scope=10 belongs-to="bgp-IP-220.127.116.11" bgp.peer-cache-id=*B000001 .as-path="1264" .communities=1111:80 .local-pref=80 .atomic-aggregate=no .origin=igp debug.fwp-ptr=0x203422A0 [admin@UK-IX2-SOUTH] >