k-melton wrote:
Jon
I read the article entitled "Reliable Static Routing Backup Using Object Tracking" that you had sent the link for. Here is the config I have so far based on what it said to do:
ip sla monitor 1
type echo protocol ipIcmpEcho 209.145.88.29
frequency 30
ip sla monitor schedule 1 life forever start-time now
track 123 rtr 1 reachability
ip local policy route-map ipsla
access-list 150 permit icmp host 209.145.88.30 host 209.145.88.29
access-list 150 deny icmp any any
route-map ipsla permit 150
match ip address 150
set interface GigabitEthernet0/1
ip route 0.0.0.0 0.0.0.0 209.XXX.88.XX track 123
ip route 0.0.0.0 0.0.0.0 123.456.789.123 254
Here is the output from the sho ip route track table command:
bhigw2#sho ip route track-tab
ip route 0.0.0.0 0.0.0.0 209.xxx.88.xx track 123 state is [up]
bhigw2#
I am hoping this may be all we need. If you can look this over and tell me what you think.
Have a splendid weekend!
Kevin
Kevin
Had a spare half hour Sunday evening so did a quick lab. Apologies for this but reliable static routing with object tracking is actually overkill for what we need. All you actually need to do is track the route so full config -
ip sla monitor 1
type echo protocol ipIcmpEcho 209.145.88.29
frequency 30
track 123 rtr 1 reachability
ip route 0.0.0.0 0.0.0.0 209.145.88.29 track 123
and that's all you need to add. I tested this by shutting down the ethernet interface on the upstream router ie. the 209.145.88.29 router and once the IP SLA failed on bhigw2 the static route was removed. Once removed it was no longer being redistributed into EIGRP and so was not passed back down the line to the 4500. The 4500 then used it's floating static route pointing to the other gateway. Note, i think i have already mentioned this but make your floating static AD 200 or above.
Once i brought the interface back up and the IP SLA succeeded the route was reinstalled on bhigw2 and then redistributed all the way back to the 4500.
So i think we are there. Let me know if you have any other queries.
Jon
