No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

VRRP Heartbeat Packets Are Interrupted After the display interface Command Is Executed on the NE80E

Publication Date:  2013-09-03 Views:  37 Downloads:  0
Issue Description
Networking:
NE80E-1------NE80E-2
     |                    |
     |___BSC__|

VRRP heartbeat packets are transmitted along the trunk between NE80E-1 and NE80E-2.
When collecting information on NE80E devices using the display interface | include GigabitEthernet|Line protocol|Description|Last 300 seconds|CRC|Overrun|Lost command, the VRRP status switchover fails.

Every time a VRRP status switchover occurs, and alarm similar to the following is displayed:
Virtual Router state BACKUP changed to MASTER, because of protocol timer expired. (Interface=Vlanif1005, VrId=4)
Every time information is collected, the exception in heartbeat logs is recorded in logs as follows:
heart timer is accumulate!system is busy!new time low :d4b425fc,new time high :00000005,old time low :d4b425fc,old time high :00000005; 
heart info in busy system: spi[0].count =1,spi[0].send =25043234,spi[0].receive =25043231,spi[1].count =1,spi[1].send =25043234,spi[1].receive =25043231;
Handling Process
The display interface | include GigabitEthernet|Line protocol|Description|Last 300 seconds|CRC|Overrun|Lost command traverses all interfaces on an NE80E, making LPUs busy collecting information. Therefore, LPUs fail to send VRRP heartbeat packets to the main control board in a timely manner, leading to a VRRP status switchover.
Root Cause
The display interface | include GigabitEthernet|Line protocol|Description|Last 300 seconds|CRC|Overrun|Lost command traverses all interfaces on an NE80E, making LPUs busy collecting information. Therefore, LPUs fail to send VRRP heartbeat packets to the main control board in a timely manner, leading to a VRRP status switchover.
Solution
1. Fault location based on collected information: When the problem occurs, the interval at which the SOCK task is scheduled is about 2s. If LPUs have not sent all packets in the second scheduling, the VRRP heartbeat packets time out when the third scheduling is performed because the timeout period of VRRP heartbeat packets is 3s.
2. Fault location based on logs: If the backup end does not receive VRRP heartbeat packets from the master end within the specified period (3s), a VRRP status switchover is triggered.
Suggestions
1. Fault location based on collected information: When the problem occurs, the interval at which the SOCK task is scheduled is about 2s. If LPUs have not sent all packets in the second scheduling, the VRRP heartbeat packets time out when the third scheduling is performed because the timeout period of VRRP heartbeat packets is 3s.
2. Fault location based on logs: If the backup end does not receive VRRP heartbeat packets from the master end within the specified period (3s), a VRRP status switchover is triggered.

END