BGP Load Balancing - Gateway Unreachable

Hello!

I’m testing in my LAB a load-balancing configuration between Cisco and Mikrotik RouterBoard1000 V6.10.

I followed the instruction in this link:
http://wiki.mikrotik.com/wiki/Manual:BGP_Load_Balancing_with_two_interfaces

A summary about the scenario:
#I created BGP Session on Cisco (65535) and Mikrotik (65530)
#I created Loopback Interf. on Cisco (10.10.10.1/24) and Mikrotik (10.0.0.2/24)
#Add static route on both route to reach the Loopback

Cisco

ip route 10.0.0.0 255.255.255.0 5.172.2.4 50
ip route 10.0.0.0 255.255.255.0 109.238.3.4 50

Mikrotik

0 ADC dst-address=5.172.2.0/29 pref-src=5.172.2.4 gateway=ether1 gateway-status=ether1 reachable distance=0 scope=10
1 Db dst-address=7.7.7.0/24 gateway=10.10.10.1 gateway-status=10.10.10.1 unreachable distance=20 scope=40 target-scope=255 bgp-as-path=“65535” bgp-med=0 bgp-origin=igp received-from=peer1
2 ADC dst-address=9.9.9.0/24 pref-src=9.9.9.1 gateway=Loopback9 gateway-status=Loopback9 reachable distance=0 scope=10
3 ADC dst-address=10.0.0.0/24 pref-src=10.0.0.2 gateway=Loopback100 gateway-status=Loopback100 reachable distance=0 scope=10
4 A S dst-address=10.10.10.0/24 gateway=ether1,ether2 gateway-status=ether1 reachable,ether2 reachable distance=50 scope=10 target-scope=30
5 ADC dst-address=109.238.3.0/29 pref-src=109.238.3.4 gateway=ether2 gateway-status=ether2 reachable distance=0 scope=10

#Enable BGP Session on Cisco with neighbor IP 10.0.0.2 and announced subnet 7.7.7.0/24

router bgp 65535
no synchronization
bgp router-id 1.1.1.1
bgp log-neighbor-changes
network 7.7.7.0 mask 255.255.255.0
neighbor 10.0.0.2 remote-as 65530
neighbor 10.0.0.2 ebgp-multihop 255
neighbor 10.0.0.2 update-source Loopback100
no auto-summary

#Enable BGP Session on Mikrotik with neighbor IP 10.10.10.1 and announced subnet 9.9.9.0/24

/routing bgp instance
set default router-id=2.2.2.2
/routing bgp network
add network=9.9.9.0/24 synchronize=no
/routing bgp peer
add in-filter=bgp-in multihop=yes name=peer1 remote-address=10.10.10.1 remote-as=65535 ttl=default update-source=Loopback100

And now…the problem!

The session are UP and I can ping 9.9.9.1 from Cisco to Mikrotik

BGP neighbor is 10.0.0.2, remote AS 65530, external link
BGP version 4, remote router ID 2.2.2.2
BGP state = Established, up for 00:32:54
Last read 00:00:45, hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received(old & new)
Address family IPv4 Unicast: advertised and received
Message statistics:
InQ depth is 0
OutQ depth is 0

Connections established 13; dropped 12
Last reset 00:33:40, due to User reset
External BGP neighbor may be up to 255 hops away.
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 10.10.10.1, Local port: 11068
Foreign host: 10.0.0.2, Foreign port: 179


2651#ping 9.9.9.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 9.9.9.1, timeout is 2 seconds:
!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

But on mikrotik i can’t ping the subent 7.7.7.0/24 because the gateway is unreachable (see the attachement)
I tried ti change the SCOPE and applied a filter but i have the same situation.

Help please! :slight_smile:
Immagine.jpg

something wired about Your 10.10.10.0/24 subnet. ITS reacheble on two Interfaces. ITs seems like mikrotik cant do a ping/arp to 10.10.10.1 (but it should work, since bgp is established?)

If you put the route 7.x.x.x manualy. does it get reachible?

Most likely that if you manage to solve that 10.10.10.0/24 connected route problem (bug?) than you’re good. Have tried a reboot on MT?