Configuring the Silent Period to Avoid Alarms Due to Delay in Receiving VRRP Advertisement Packets
The silent period starts when the interface state is changed from down to up. During this period, the Primary Down Event is ignored. Configure the silent period interval to avoid alarms caused by the delay or interruption of the incoming VRRP advertisement packets during the interface startup phase.
To configure the silent period interval that the Primary
Down Event timer ignores, include the startup-silent-period statement at the [edit protocols vrrp] hierarchy level:
[edit protocols vrrp] startup-silent-period seconds;
During the silent startup period, the show vrrp detail command output shows a value of 0 for Master priority and your IP address for Master router. These values indicate
that the Primary selection is not completed yet, and these values
can be ignored.
When you have configured startup-silent-period, the Primary Down Event is ignored until the startup-silent-period expires.
For example, configure a VRRP group, vrrp-group1, with an advertise interval of 1 second, startup silent period of 10 seconds, and an interface interface1 with a priority less than 255.
When interface1 transitions from down to up:
The vrrp-group1 group moves to the backup state, and starts the Primary Down Event timer (3 seconds; three times the value of the advertise interval, which is 1 second in this case).
If no VRRP PDU is received during the 3-second period, the startup-silent-period (10 seconds in this case) is checked, and if the startup silent period has not expired, the Primary Down Event timer is restarted. This is repeated until the startup-silent-period expires. In this example, the Primary Down Event timer runs four times (12 seconds) by the time the 10-second startup silent period expires.
If no VRRP PDU is received by the end of the fourth 3-second cycle, vrrp-group1 takes over the primary role.