We have redistribute connected, static and other BGP turned on for all routers. All routers are running Mikrotik 2.9.30 & 2.9.31. Same AS between three routers.
The middle router sees the route from one peer but isn’t advertising it to the other:
/ip route print from [find gateway=6.2.52.89]
46 ADb 6.2.53.0/24 r 6.2.52.89 200 ether1
/routing bgp advertisements print 6.2.216.221
<Route isn’t listed>
Any idea what is causing this behavior?
Is it an active route on the middle router?
Sam
karyal
October 7, 2006, 7:42pm
3
believewireless:
We have redistribute connected, static and other BGP turned on for all routers. All routers are running Mikrotik 2.9.30 & 2.9.31. Same AS between three routers.
The middle router sees the route from one peer but isn’t advertising it to the other:
/ip route print from [find gateway=6.2.52.89]
46 ADb 6.2.53.0/24 r 6.2.52.89 200 ether1
/routing bgp advertisements print 6.2.216.221
<Route isn’t listed>
Any idea what is causing this behavior?
Did you try setting nexthop-choice=force-self on the peers configuration?
Bye,
Ricky
force-self is on every peer. We have the following:
ISP1 → MT 1 → MT 2 → MT3 → ISP2
We are trying to get the route on MT1 to be announced by MT3 to ISP2. It’s in /routing bgp network on MT1 and seen by MT2 but not announced to MT3.
All filters have been removed and it’s still not being seen. Any ideas?
repeat … is it an active route on the middle router?
Sam
Yes, I already showed that in the first post:
/ip route print from [find gateway=6.2.52.89]
46 ADb 6.2.53.0/24 r 6.2.52.89 200 ether1
Eugene
October 13, 2006, 1:21pm
7
issue /routing bgp peer resend-all command and see if the route is being advertised afterwards. If it is not, send support output file to support@mikrotik.com
Eugene
It looks like the resend fixed it. Thanks.
I did notice a route today where that didn’t fix it. I had to disable the peer and re-enable it for it to work.
Eugene
October 20, 2006, 11:07am
9
You have to report such cases accompanied by support-output files to support@mikrotik.com
Eugene