BGP routes won't get installed on CCR1072

RouterOS Forwarding Protocols
1

Hello all,

Can someone help me identify why my Mikrotik won't utilize the BGP learned routes? I have a CCR1072 that runs iBGP with a Juniper QFX5100. The CCR1072 receives all the required routes from the Juniper, but it doesn't install them inside the routing table. I currently have static routes for those networks until the BGP issue is resolved.

[atetu@emp-cle.edge-fw01.ccr1072] > ip route print where received-from=iBGP-Core-QFX5100
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

DST-ADDRESS PREF-SRC GATEWAY DISTANCE

0 Db 10.0.99.40/30 64.85.172.5 200
1 Db 10.10.100.0/24 64.85.172.5 200
2 Db 10.50.104.0/24 172.20.103.2 200
3 Db 10.50.106.0/24 172.20.106.2 200
4 Db 10.50.109.0/24 172.20.109.2 200
5 Db 10.60.104.0/24 172.20.103.2 200
6 Db 10.103.0.0/22 172.20.103.2 200
7 Db 10.104.0.0/22 172.20.103.2 200
8 Db 10.106.0.0/22 172.20.106.2 200
9 Db 10.109.0.0/22 172.20.109.2 200
10 Db 10.224.0.0/22 172.20.103.2 200
11 Db 10.250.103.0/24 172.20.103.2 200
12 ADb 172.20.101.0/30 64.85.172.5 200
13 ADb 172.20.102.0/30 64.85.172.5 200
14 ADb 172.20.103.0/30 64.85.172.5 200
15 ADb 172.20.105.0/30 64.85.172.5 200
16 ADb 172.20.106.0/30 64.85.172.5 200
17 ADb 172.20.107.0/30 64.85.172.5 200
18 ADb 172.20.108.0/30 64.85.172.5 200
19 ADb 172.20.109.0/30 64.85.172.5 200
20 Db 172.25.103.0/24 172.20.103.2 200


bgp unreachable.JPG
bgp unreachable.JPG641×305 61.7 KB

2

It looks like you have added static routes to each network, via 10.0.99.42. These are being used as active routes because they have the lowest cost (1)

Your BGP routes (ibgp) are not being installed into the routing table because the same destination (for example 10.103.0.0/22) is already available at a lower cost.

If you disable the static routes, you should see the BGP routes becoming active.

3

Hi pwuk,

I have identified the issue. The Juniper runs eBGP to my tower networks and iBGP to the edge-CCR1072. I forgot to enable “next-hop self” on the Juniper peering towards the CCR1072. The routes are now propagating as expected after I made that change.

-AT