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

The different member quantity of VRRP-Group caused VRRP Group has two master

Publication Date:  2012-07-27 Views:  34 Downloads:  0
Issue Description

Current Version is NE40E V300R003C02B697
Topology as following:
R_01------eth-trunk 3----R_02, and configure two VRRP-Group on both R_01 and R_02 respectively.

FSE feedback VRRP group 1 is normal,  but VRRP group 2 had two master after configuring VRRP Group on both R_01 and R_02 respectively.

Alarm Information
NULL
Handling Process
Assign the VRRP which should belong to VRRP Group 2 to VRRP Group 2 on R_01, to ensure the member quantity of VRRP Group 2.
and then the problem was solved.
Root Cause

分别查看两台设备上的VRRP Group1与VRRP Group2的信息 

Check the configuration about VRRP Group 1 and VRRP Group 2 on both two NE40E respectively

R_01:

[TW_R_01-vrrp-group-1]disp vrrp-group 1 verbose
 vrrp-group 1
                 state: master     <<<<------for VRRP-Group 1, R_01 is master.
                enable: yes
           description: for_wiom_vrrp
       priority config: 100
   using vrrp priority: yes
          priority run: 120
               preempt: yes, delay time: 10000
                 timer: 1000
            group-send: no
           peer status: offline
           create time: 02:19:16
      last change time: 02:11:56
           vrrp number: 20     <<<<<<<---------There are 20 members of VRRP Group 1 on R_01

[TW_R_01-vrrp-group-1]disp vrrp-group 2 verbose
 vrrp-group 2
                 state: master    <<<<------for VRRP-Group 2 R_01 is master 
                enable: yes
           description: for_wir6_vrrp
       priority config: 100
   using vrrp priority: yes
          priority run: 120
               preempt: yes, delay time: 0
                 timer: 1000
            group-send: no
           peer status: offline
           create time: 01:47:08
      last change time: 00:58:06
           vrrp number: 7      <<<<<<<---------There are only 7 members of VRRP Group 2 on R_01

 

R_02:

<TW_R_02>disp vrrp-group 1 ver
 vrrp-group 1
                 state: slave        <<<<------for VRRP-Group 1, R_02 is slave. 
                enable: yes
           description: for_wiom_vrrp
       priority config: 100
   using vrrp priority: yes
          priority run: 100
               preempt: no
                 timer: 1000
            group-send: no
           peer status: online
           create time: 01:42:50
      last change time: 00:00:02
           vrrp number: 20      <<<<<<<---------There are 20 members of VRRP Group 1 on R_02

<TW_R_02>disp vrrp-group 2 ver
 vrrp-group 2
                 state: master             <<<<------For VRRP-Group 2, R_02 is Master as well, have two master. 
                enable: yes
           description: for_wir6_vrrp
       priority config: 100
   using vrrp priority: yes
          priority run: 100
               preempt: no
                 timer: 1000
            group-send: no
           peer status: offline
           create time: 01:44:32
      last change time: 01:12:28
           vrrp number: 20      <<<<<<<---------There are 20 members of VRRP Group 2 on R_02, which is different from R_01

For this problem, it is due to the different member quantity of VRRP Group 2 on R_01 and R_02,(R_01 has 7 members, but R_02 has 20 members.). and VRRP Group 1 is normal, because the member quantity of VRRP Group 1 is same on both R_01 and R_02 (Both are 20 members.)
By default, NE40E will check the code which is created according to the member quantity of VRRP Group and VRID. so for VRRP Group 2. it  had different member quantity to lead the check code is not accordance. so the VRRP Group can't be normal.

Suggestions
During configuring VRRP Group, please ensure the member quantity of VRRP Group must be same on both two end Routers.

END