Tracking is only for HSRP to detect some changes in the routing table. HSRP is not a real routing protocol it just provides a default gateway at Layer 2 and Layer 3.
Interface tracking allows you to specify another interface on the router for the HSRP process to monitor in order to alter the HSRP priority for a given group.
If the specified interface's line protocol goes down, the HSRP priority of this router is reduced, allowing another HSRP router with higher priority can become active (if it has preemption enabled).
To configure HSRP interface tracking, use the command:
standby [group] track interface [priority]
Eg: Router(config-if)#standby 1 track serial 0/0 25
HSRP will track the availability of interface serial 0/0. If serial 0/0 goes down, the priority of the router in group 1 will be decremented by 25.
The track argument does not assign a new priority if the tracked interface goes down. The track argument assigns a value that the priority will be decreased if the tracked interface goes down.
Therefore, if you are tracking serial 0/0 with a track value of 25—standby 1 track serial 0/0 25—and serial 0/0 goes down, the priority will be decreased by 25; assuming a default priority of 100, the new priority will now be 75.
The default value of the track argument is 10.
Tracking allows syncing the HSRP priority to the good state of one or more uplinks. So combining tracking and preemption HSRP Active role can be taken by the router with the best current connectivity to the core providing better performance.
In modern IOS we can track more than simple interface state. Interface tracking enables HSRP process to monitor additional interfaces, the status of which will dynamically change the HSRP priority (Active/Standby).
Imagine the following scenario:
If you have two serial links to two different ISPs(assume primary/backup Internet connections) connected via two different routers, it would be interesting to have the serial interface connecting to your primary ISP tracked in order to minimize service interruption to your local users. If this serial interface goes down, your backup router can take over the gateway functionality to your local network, while maintaining the connectivity to the secondary ISP (backup). Users would still be able to access Internet via the backup router (through Secondary ISP) thanks to the interface tracking functionality in HSRP.
You can consider interface tracking as part of the 'Normal' HSRP.
It is possible to track more than one thing at a time within the same HSRP group. We can do interface tracking as well as IP SLA tracking within one HSRP group. Each tracked object will produce a priority decrement if it fails. This helps in scenarios where you want the active router to change role only when multiple events happen or if you want to track multiple aspects.
The purpose of tracking an interface is so that you can decrease the priority of an interface running HSRP if some other interface goes down. If the interface running HSRP goes down you do not want to decrease its priority you want the other standby interface to take completely over.
Hi I am creating location groups and sub-groups in Cisco Prime 3.6. I would like to have an hierarchy like Campus > Areas > Buildings > Floors However, I see that in PI I can have only Campus > Building > Floor Does anyone kn...
We installed an ISR4321k9 in a colo today and the guy doing the physical install was informed we were given a redundant network connection, so clickclick, we're connected to two WAN ports!Trouble is, they only gave us a /28 subnet with addresses "172.8.0....
We are trying to get access to the Web Interface. According to documentation it should be as simple as plugging in a network cable to any one of the 24 non-management ports on the front and then just launch a browser to https://192.168.1.1. We've tried bo...
Hello,I was wondering if there is a way to monitor the packets going through specific ports or IPs on the Switch.MORE INFORMATION:We have a PTP GM200 clock setup broadcasting a PTP signal at 192.168.1.231, we are using an Emergent Camera at 192.168.1.110 ...
HiThis switch has 16 1/10 built in ports plus an 8 port uplink module.Can anyone please tell me the interface numbering convention here?ie te1/x (built in ports) and te2/x (module) or something else???ThanksSpecs:Catalyst 4500-X switch chassis with:16 1G ...