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>Search

Reminder

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

upgrade
Knowledge Base

Two VRRP Master ME60s Existed Because They Applied VRRP of Different Versions

Publication Date:  2013-10-28  |   Views:  267  |   Downloads:  1  |   Author:  00183405  |   Document ID:  ETC0001504022

Contents

Issue Description

Version information:
ME60: V6R2C02SPC700+SPH038

Network topology:



Fault symptoms:
The S7806 connected to two ME60s. In normal cases, the VRRP heartbeat packets between the two ME60s were forwarded by the S7806. After a technician enabled the two ME60s' subinterfaces, the VRRP state was Master on both the ME60s.

Handling Process

To address the issue, Huawei performed the following problems and observed the following information:

1. Checked configurations on the ME60s and S7806.

No error was found.

2. On the S7806, enabled vlanif 1911, configured an IP address on the same network segment, and pinged the IP address.

The pinging operation was successful.

3. Debugged VRRP packets on the two ME60s (for details, see the attachment).

ME60-1 successfully received and sent VRRP packets. The debugging information is as follows:

<ME60-1>
Apr 27 2013 14:00:29.690.1+08:00 YL-YY-LJ-BAS-1.MAN.ME60 VRRP/7/DebugPacket:
 Eth-Trunk2.1911 | Virtual Router 225 :receiving from 10.96.124.253, priority = 100,timer = 100, auth type is no, SysUptime: (11,924250442)
 
Apr 27 2013 14:00:29.690.2+08:00 YL-YY-LJ-BAS-1.MAN.ME60 VRRP/7/DebugPacket:
 Eth-Trunk2.1911 | Virtual Router 225 :sending from 10.96.124.254, priority = 105,timer = 100, auth type is no, SysUptime: (11,924250442)
 
On ME60-2, only sent VRRP packets were captured. The debugging information is as follows:

<ME60-2>
Apr 27 2013 14:00:28.890.1+08:00 YL-YY-XS-BAS-1.MAN.ME60 VRRP/7/DebugPacket:
 Eth-Trunk2.1911 | Virtual Router 225: sending from 10.96.124.253, priority = 100,timer = 1, auth type is no, SysUptime: (11,1355329634)
 
Apr 27 2013 14:00:29.890.1+08:00 YL-YY-XS-BAS-1.MAN.ME60 VRRP/7/DebugPacket:
 Eth-Trunk2.1911 | Virtual Router 225: sending from 10.96.124.253, priority = 100,timer = 1, auth type is no, SysUptime: (11,1355330634)
4. Captured outgoing packets at a port of the switch that interconnected with ME60-2.

VRRP packets sent by ME60-1 were captured, indicating that the L2 network normally forwarded the VRRP packets but the VRRP packets did not arrive at ME60-2 or were discarded.

5. Checked the VRRP version on the two ME60s.

The VRRP version on ME60-1 was V3, whereas that on ME60-2 was V2. As a result, ME60-2 could not identify VRRP packets sent by ME60-1.

The VRRP version information is as follows:

[ME60-1] dis vrrp protocol-information
VRRP protocol information is shown as below:
VRRP protocol version : V3
Send advertisement packet mode : send v3 only

<ME60-2>disp vrrp protocol-information                                                                              
 VRRP protocol information is shown as below:                                                                                      
    VRRP protocol version : V2                                                                                                     
    Send advertisement packet mode : send v2 only

Root Cause

The VRRP version on ME60-1 was V3, whereas that on ME60-2 was V2.

Solution

Change the VRRP version on either ME60 to ensure that both the ME60s apply the same VRRP version.

Suggestions

It is recommended that the VRRP version not be changed, unless otherwise specified, and the default version (V2) be used.