eBGP routes not being advertised to iBGP peer - Recursive Routing - Mikrotik

Hi everyone,

​

I am seeking some help with what I believe is a recursive routing issue. I have checked with my Upstream IP Transit provider and they seem to think everything looks good on their end.

​

I am receiving a Full BGP table from my Upstream IP Transit provider on Router-01 fine. This Router-01 I am receiving the Full BGP table on is an iBGP peer with my other Router-02. The iBGP Router-02 peer is NOT receiving the Full BGP table from Router-01.

​

If I look at the Mikrotik Routing table for Router-01 I can see the Full BGP table (800k+). The issue is that all of the eBGP routes are marked as 'gateway-status=103.xxx.xxx.94 unreachable'. This doesn't make sense to me since I am able to ICMP/ARP ping the 103.xxx.xxx.94 fine and I can see a Directly Connected route for 103.xxx.xxx.94 via sfp-sfpplus3 in the routing table. There is also an entry in the ARP table for 103.xxx.xxx.94. The sfp-sfpplus3 interface is meant to be directly connected to 103.xxx.xxx.94 via a cross-connect. sfp-sfpplus3 is configured as 103.xxx.xxx.95/31, as you can see it is in the same subnet as the 103.xxx.xxx.94 gateway.

​

Here is where it gets even more strange. I have a default route to an alternative Internet path (this is how I am currently able to manage my equipment).

0 A S dst-address=0.0.0.0/0 gateway=221.xxx.xxx.201 gateway-status=221.xxx.xxx.201 reachable via ether1 distance=240 scope=30 target-scope=10 

If I enable BGP multihop with this eBGP peer I start to learn the 103.xxx.xxx.94 gateway recursively via 221.xxx.xxx.201. The strange thing is 103.xxx.xxx.94 is meant to be directly connected via sfp-sfpplus3 so this doesn't make any sense to me...

17 ADb dst-address=1.0.133.0/24 gateway=103.xxx.xxx.94 gateway-status=103.xxx.xxx.94 recursive via 221.xxx.xxx.201 ether1 distance=20 scope=40 target-scope=30 bgp-as-path="x,38040,23969" bgp-origin=incomplete bgp-communities=19996:19996,x:3,x:104,x:1400,x:11000,x:11001 received-from=x-eBGP-peer 18 ADb dst-address=1.0.134.0/24 gateway=103.xxx.xxx.94 gateway-status=103.xxx.xxx.94 recursive via 221.xxx.xxx.201 ether1 distance=20 scope=40 target-scope=30 bgp-as-path="x,38040,23969" bgp-origin=incomplete bgp-communities=19996:19996,x:3,x:104,x:1400,x:11000,x:11001 received-from=x-eBGP-peer 

I'll be the first to admit I have a lot to learn when it comes to eBGP/iBGP. I tried adding all static routes I could think of with no luck. I also changed BGP settings (removed filters, Nexthop Choice, Multihop, Update Source) with no luck. The last things I can think of which requires me to visit the Data Centre is that I am not 100% certain the cross-connect sfp-sfpplus3 is plugged into is the correct one. We also purchased Layer 2 Aggregation from them and sfp-sfpplus3 potentially could be plugged into the Layer 2 Aggregation cross-connect. Maybe when I do the ICMP/ARP Ping to 103.xxx.xxx.94 it has been going via my alternative Internet route? The last thing is either the TX/RX need to be swapped around, but if this needed to be done I am not sure how the eBGP session is working fine over it. Also, we confirmed MAC addresses with the Upstream IP Transit provider so I think it should be the correct cross-connect.

​

If someone could help point me in the right direction that would be great.