ROSv6 BGP Best Path Selection Algorithm problem

RouterOS Forwarding Protocols
1

Hi, I’m having trouble selecting the active default route learned by iBGP. If I understand the following document correctly (https://wiki.mikrotik.com/wiki/Manual:BGP_Best_Path_Selection_Algorithm), the chosen route will be determined in the first instance by the weight assigned to that prefix. However, I’m not being able to select the preferred route using this parameter:


/ip route print detail where routing-mark=INET
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 
 0 ADb  dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 recursive via 192.168.100.100 ether1 distance=200 scope=20 target-scope=10 
        routing-mark=INET bgp-weight=0 bgp-local-pref=100 bgp-med=0 bgp-origin=incomplete bgp-ext-communities="RT:65000:10,RT:65000:110" 

 1  Db  dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 recursive via 192.168.100.100 ether1 distance=200 scope=20 target-scope=10 
        routing-mark=INET bgp-as-path="65010,65011" bgp-weight=1 bgp-local-pref=100 bgp-med=0 bgp-origin=igp bgp-ext-communities="RT:65000:20,RT:65000:120"

It can be seen that the active route has a lower weight than the other route present. Is there an error in my interpretation of the route selection process?

2

Have you tried to reverse the weight between the two routes? BGP in RouterOS 6 is sometimes just broken. For example: We found that the MED value behavior is reversed. Not the route with the lowest MED is selected but that with the highest MED. Although per RFC and also per Mikrotik documentation the route with the lowest MED should be selectet when everything else in the rules further up the decision tree is the same. Very annoying. So check if behavior is also reversed for weight. May be the devs just mixed up those two parameters.

3

@netzwerghh, thanks for the reply.
I tried your suggestion, but the result is the same. It seems like weight is not taken into account in route selection.

4

both routes are received from peers belonging to the same instance?

5

Hi @mrz, both routes are learned from a route reflector, and are filtered using route-targets.

6

hi,

any update? we are also interested on this

7

it’s a bad habit that mikrotik support ask some question then leave the customer without answer