Based on the analysis of the message, according to the code to realize, the problem is caused by the number members of the active/standby VGMP is not consistent. but in the prompt information, the master display the slave tips, and slave display the master tips. At the same time, this problem will not happen, only changes a little configuration in the master, and then save configuration, the problem may appear.
In the slave open VGMP debugging debugging VRRP - group all, find on the extranet port, slave receive VGMP hello message sent by itself:
Find in the debugging that the slave receive the VGMP hello message sent by himself, this is the direct cause of prompting. slave receive the VGMP hello message sent by itself, after resolve find the message status is salve, when take message the corresponding state is master, compared the VGMP number of members between message and master. Because the slave status is salve, the members number in master state is 0, find the number is inconsistent, displaying that the active/standby configuration is not consistent.
Why slave receive the VGMP hello message sent by itself, through ping test can find, this link appeared on the layer 2 loop (TTL = 255 UDP message), to this phenomenon, need to find out the cause of the loop.