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


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


MM910s master and slave failover failed

Publication Date:  2015-01-14 Views:  143 Downloads:  0
Issue Description

Server: E9000 MM910
Version: (U54)2.20
The data of the active and standby MM910 cannot be synchronized, and the active/standby failover command cannot be executed successfully.
Alarm description: LAN heartbeat lost

Alarm Information
 LAN heartbeat lost
Handling Process

1.   In HMM portal alarm center, Check whether the blade value in the alarm location parameter is SMM1

2.         Run the ifconfig command on the command-line interfaces (CLIs) for the active MM910 to check whether the eth1 network port exists.If the following command output is displayed, the eth1 network port exists (eth1 is included in the left column).

3.   Check eth1 inet addr: if it is not 172.31.XXX.XXX , please go to HMM Chassis setting –MM to edit the Network Segment of the Management Plane into 172.31.XXX.XXX mask and Save

4.   Repeat step2 and step 3 on slave MM910.

5.   Run the reboot command on the CLI for the standby MM910.

On master MM910 ping 172.31.XXX.XXX  if can ping then log in HMM to check that alarm is gone. And MM910s can play failover.


From HMM web configures MM910s IP address, edit Network Segment of the Management Plane to 172.31.XXX.XXX


Suggest: when configure the IP address of MM910sNetwork Segment of the Management Plane should use the default IP for MM910s heartbeat.