Troubleshooting Vrrp - H3C S5600 SERIES Operation Manual

[Sysname] interface Vlan-interface 2
[Sysname-Vlan-interface2] ip address 202.38.160.1 255.255.255.0
[Sysname-Vlan-interface2] quit
# Create a VRRP group.
[Sysname] interface Vlan-interface 2
[Sysname-Vlan-interface2] vrrp vrid 1 virtual-ip 202.38.160.111
# Enter GigabitEthernet 1/0/1 port view and enable the VRRP tracking function.
[Sysname] interface GigabitEthernet1/0/1
[Sysname-GigabitEthernet1/0/1] vrrp Vlan-interface 2 vrid 1 track reduced 50

Troubleshooting VRRP

You can locate VRRP problems through the configuration and debugging information. Here are some
possible symptoms you might meet and the corresponding troubleshooting methods.
Symptom 1: Frequent prompts of configuration errors on the console
This indicates that incorrect VRRP packets are received. It may be because of the inconsistent
configuration of the switches within the VRRP group, or the attempt of other devices sending illegal
VRRP packets.
The first possible fault can be solved through modifying the configuration.
The second possibility is caused by the malicious attempt of some devices; non-technical
measures should be taken to solve the problem.
Symptom 2: More than one master existing within a VRRP group
There are also 2 reasons. One is short coexistence of many masters, which is normal and needs no
manual intervention. Another is long coexistence of many masters, which may be caused because the
original master and other member switches in a VRRP group cannot receive VRRP packets from each
other, or receive some illegal packets.
To solve such a problem:
An attempt should be made to ping among these masters.
If such an attempt fails, check the connectivity between related devices.
If they can be pinged, check VRRP configuration.
For the configuration of a VRRP group, complete consistency for the number of virtual IP
addresses, each virtual IP address, timer interval and authentication type configured on each
member switch must be guaranteed.
Symptom 3: VRRP state of a switch changing repeatedly
Such problems occur when the VRRP group timer interval is too short. They can be solved through
prolonging the interval or configuring the preemption delay period.
1-18