Active Timer: This timer is used to monitor the active router. This timer starts any time an active router receives a hello packet. This timer expires in accordance with the hold time value that is set in the related field of the HSRP hello message.
Can someone verify my assumptions are correct and answer my question
I believe a router within the HSRP group (such as a listening router) would start its Active timer each time it recieved a hello packet from the active router, and start its standby timer each time it recieved a hello from the standby timer.. is this correct?.. and if so my question is if multiple listening routers exist how do they know which one becomes the new standby (should the existing standby fail) is an election forced? and if so is the election just between the existing listening routers?
I believe a router within the HSRP group (such as a listening router) would start its Active timer each time it recieved a hello packet from the active router, and start its standby timer each time it recieved a hello from the standby timer.. is this correct?
From initializing HSRP to the final state (Active, Standby, Listen) there are several events which (re-)start the Active- or Standby-timers and the expiration of those timers also trigger actions. You can see those events and actions in the HSRP state machine:
It takes some time to get used to this kind of presentation, therefore I attached a (very small) partial flowchard to give you a basic idea.
If you have more than two HSRP-enabled routers on a segement, one active and one standby router will be elected and the others will stay in Listen state until the active or standby router fail or parameters are changed (e.g. priorities when preemtion is enabled). There is a special message type called "Resign", which the active router sends when HSRP is disabled on an interface. As a last resort, the other routers will realize the loss of active or standby router based on the timers (absence of hellos).
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...