Wrong priority for some routes in bgp

RouterOS Forwarding Protocols
1

Hi everyone.
I’ve just seen some routes are in wrong order in routing table. I’ve made some change in bgp peers setting and filters to correct order of all my egress traffic, but some routes are still wrong.
For example I’ve set filters as described bellow:

add action=accept chain=RETN_in protocol=bgp set-bgp-local-pref=200 set-bgp-weight=40
add action=accept chain=Severen_in protocol=bgp set-bgp-local-pref=100 set-bgp-weight=20

I’d like to set priority RETN ISP for outgoing traffic and I’ve used to do that two metrics (also I’ve tried to use set-bgp-prepend but it didn’t help me too).
I can see in routing table: some routes are ok, but some are wrong. Take a looking for a picture.
2018-11-21_18-29-16.png
My question is: Is (was) it a bug in mikrotik, or have I done something wrong? Thank you.

  routerboard: yes
  model: CCR1009-7G-1C-1S+
  firmware-type: tilegx
  factory-firmware: 3.41
  current-firmware: 6.41.3
  upgrade-firmware: 6.41.3
2

Instance for both peers is the same?

3

Hi, can you help us bu posting the filters for each prefix? and the peer configuration too?

4

In this case are different.

And tell me please, what means instance, I’ve read all docs on this site but don’t understand when I must use separated instance and when mustn’t?

5

Unique instance should be used per VRF or in other special cases.
For common BGP setups all peers must use the same instance. Reason is that BGP selection algorithm is not used between routes received from different instances.