I am currently trying to lab a dual-homed internet scenario using HSRP object tracking that it will cut over in the event of a route learnt from the internet is no longer accessible.
We recently had a real life failure where standard HSRP was configured and it did not cut over because it was only tracking the status of the WAN interface rather than whether the BGP peering dropped. So interface was still up but no routes were being given to us via ISP. The result was that the HSRP did not cut over.
After some investigation it seemed that object tracking would solve this. But in the lab environment I cannot get this to work using just BGP. The message I get is
IP route 126.96.36.199 255.255.255.255 reachability
Reachability is Down (unsupported)
9 changes, last change 00:01:08
First-hop interface is unknown
HSRP Vlan20 0
It is reachable when I get this message. The only way I found round this was to implement a static route to the far end device but this still does not work because even when the route is gone it still believes it is alive and well because of the static route. So even this would not cut over. My belief is that HSRP object tracking is not working with BGP as a routing protocol. A lot of documents do not mention using BGP but do not explicitly say that it is not supported.
To summarize I need a mechanism to ensure that HSRP cuts over in the event of pure BGP peer failure. The current solution we have is textbook with prepending and I-BGP in place.
Does anybody have any ideas?