Thank you for the response, I really appreciate it.
I am able to ICMP ping the 103.xxx.xxx.94 gateway fine. I am able to ARP ping the 103.xxx.xxx.94 gateway fine. I am NOT able to MAC Ping the 3C:8A:B0:xx:xx:xx gateway. I am NOT able to MAC ARP ping the 3C:8A:B0:xx:xx:xx gateway.
sfp-sfpplus3 is the cross-connect interface to the Upstream IP Transit. The sfp-sfpplus3 interface is configured as 103.xxx.xxx.95/31. 103.xxx.xxx.94 is the eBGP peers remote address, which is meant to be directly connected. As you can see 103.xxx.xxx.94 & 103.xxx.xxx.95 are in the same /31 subnet.
add address=103.xxx.xxx.95/31 interface=sfp-sfpplus3 network=103.xxx.xxx.94
I spent the past few hours troubleshooting this with no success sadly. I even checked with my Upstream IP Transit provider and they seem to think everything looks good on their end.
I noticed some very strange behavior that doesn't make any sense to me. I have an alternative Internet path setup as a default route with a distance of 240.
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
When I configured the eBGP peer for multihop, the 103.xxx.xxx.94 gateway was recursive via the alternative Internet path 221.xxx.xxx.201.
17 ADb dst-address=18.104.22.168/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
18 ADb dst-address=22.214.171.124/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
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.
Everything is working as expected (Receiving Full BGP table, Advertising my Public subnet) except the gateway-status being unreachable. It doesn't make sense to me why the BGP routes say the gateway-status is unreachable when there is an ARP entry for 103.xxx.xxx.94 and a Directly Connected route for 103.xxx.xxx.94 via sfp-sfpplus3 in the routing table.
You do not have the required permissions to view the files attached to this post.