I am trying to troubleshoot our IP SLA configuration. It is setup to determine availability of a route through site A and if that route is not available, then the traffic would be redirected to a route in site B. I have the IP SLA configuration below:
IP SLA Config on Site A:
ip sla monitor 1
type echo protocol ipIcmpEcho 10.50.50.1 source-interface FastEthernet0/0.10
ip sla monitor schedule 1 life forever start-time now
track 1 rtr 1 reachability
ip route 10.20.1.0 255.255.255.0 10.20.102.125 track 1
ip route 10.20.1.0 255.255.255.0 10.20.128.16 4
ip route 10.50.50.1 255.255.255.255 10.20.102.125 permanent
The issue we're having is that all traffic appears to be going out the route at Site B and returning through Site A.
IP SLA Config on Site B:
ip sla monitor 1
type echo protocol ipIcmpEcho 10.50.50.1 source-interface FastEthernet0/0
ip sla monitor schedule 1 life forever start-time now
!
track 1 rtr 1 reachability
ip route 10.20.1.0 255.255.255.0 10.20.102.125 track 1
ip route 10.20.1.0 255.255.255.0 10.20.128.16 4
ip route 10.50.50.1 255.255.255.255 10.20.102.125 permanent
You will see that this is just a duplicate of the Site A config and we're planning on removing this after we get everything working on the sites that point to either of these locations.
The other locations have the following routes:
ip route 10.20.1.0 255.255.255.0 10.20.102.125 track 1
ip route 10.20.1.0 255.255.255.0 10.20.128.16 4
ip route 10.50.50.1 255.255.255.255 10.20.102.125 permanent
I've configured BGP on the router in Site A with 10.20.1.0/24 as a network and running sh ip bgp properly shows that the next hop for that network should be 10.20.102.125. With this said, I should be able to remove the routing statements mentioned above on the remote sites routers and the statements on Site B and the intended traffic should be able to find its way (once BGP propagates) to Site A, right?
Thanks for your help,
Chris
