HSRP tracking via IP

Unanswered Question
Jul 31st, 2007
User Badges:

There's a way of tracking a remote IP via icmp with HSRP. If this IP is not reachable then it will force the failover. I believe the the way it works is once the remote IP is unreachable the timer starts, the service provider is stating that the timer is when the IP address is checked. which is it please?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
mohammedmahmoud Tue, 07/31/2007 - 06:42
User Badges:
  • Green, 3000 points or more


You can track the reachability of the IP in the routing table.

track 100 ip route reachability


interface Ethernet0/0

ip address x.x.x.x

standby 1 preempt

standby 1 ip y.y.y.y

standby 1 priority 110

standby 1 track 100 decrement 20


Mohammed Mahmoud.

Edison Ortiz Tue, 07/31/2007 - 06:48
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

Yes, you can track a remote IP with HSRP and it doesn't have to be via ICMP. You can use the track feature within IOS.

Let's say you have this route in your RIB (

Then you configure the track with:

track 1 ip route reachability

And your HSRP with:

interface [module/port]

ip address

standby ip

standby preempt

standby priority 105

standby track 1 decrement 10

As soon as the route is no longer in the routing table, the HSRP priority will be 95 and the other HSRP router will take over.

jtrumbell Thu, 08/02/2007 - 10:12
User Badges:

Isn't there a way where a IP is selected and is checked via icmp. Once it becomes unreachable then a timer begins and the failover occurs. I thought I saw it as a HSRP tracking option, it could have been a VRRP tracking option? thanks

Edison Ortiz Thu, 08/02/2007 - 10:20
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

You can use IP SLA for ICMP checks, however this may create unnecessary traffic in your network. It's best to track interfaces/routes based on their current state.

jtrumbell Thu, 08/02/2007 - 10:38
User Badges:

Yes, but in this situation we want router A to failover immediatly when anything occurs with or beyond Router B. We dont want to wait for the routing update, if the client base notices a pause or a timeout they call into the helpdesk. So whenever possible we want any failovers to be invisible to the client base. Waiting for the routers to converge will likely cause some session timeouts.

Edison Ortiz Thu, 08/02/2007 - 10:41
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

When the connection is lost the routing update will be triggered and it will react as quick or even faster than a ping response.

Please try in a Lab before implementing and you will see what I'm referring.


This Discussion