how to deal with Heartbeat Communication Between the Host and VRM Interrupted alarm on FusionCompute V1R5C00 version

This alarm is generated when the heartbeat communication between the Virtualization Resource Management (VRM) node and a Computing Node Agent (CNA) node is interrupted.

This alarm is cleared when the heartbeat communication between the VRM node and the CNA node recovers.
Identify the IP address of the object for which the alarm is generated.

On the FusionCompute, choose Monitoring > Alarm. On the Real-Time Alarms, locate the row that contains the alarm and click the host name in the Alarm Object column.
A page is displayed showing the detailed information about the host.

On the Summary page, view Host IP Address and BMC IP of the host.
Check the status of the CNA node.

Enter the baseboard management controller (BMC) IP address in the address box of Internet Explorer, and log in to the CNA node using the administrator username and password.
If the login fails, contact the system administrator.

Click System Information, and check whether Device Status on the System Status page is Power Off.

If yes, go to Step 5.
If no, go to Step 7.

Click Power Management, select Power On, and click OK.
After the host is powered on, check whether the alarm is cleared.

If yes, no further action is required.
If no, go to Step 7.

Check the network.

Obtain the management plane floating IP address of the VRM node from the system administrator.
Use PuTTY to log in to the active VRM node.
Ensure that the management plane floating IP address and username gandalf are used to establish the connection.

Run the following command and enter the password of user root to switch to user root:

su - root


Run the ping command on the VRM node to check whether the management IP address of the CNA node can be pinged.

If yes, go to Step 19.
If no, go to Step 11.

Check the management network port of the CNA node.

Use PuTTY to log in to the CNA node.
Ensure that the management IP address and username gandalf are used to establish the connection.

If the login fails, log in to the BMC system using the BMC IP address and then log in to the CNA node by enabling the BMC remote control function.

Run the following command and enter the password of user root to switch to user root:

su - root


Run the following command to check whether any information is displayed.
lspci -n -m | grep 184e

If yes, an intelligent network interface card (iNIC) is used.
If no, a common NIC is used.

Run ifconfig inic0 | grep RUNNING in the iNIC environment or ifconfig Mgnt-0 | grep RUNNING in the common NIC environment to check whether any information is displayed.

If yes, rectify other network faults.
If no, go to Step 15.

Run ifconfig inic0 up in the iNIC environment or ifconfig Mgnt-0 up in the common NIC environment.
Run ifconfig inic0 | grep RUNNING in the iNIC environment or ifconfig Mgnt-0 | grep RUNNING in the common NIC environment to check whether any information is displayed.

If yes, go to Step 17.
If no, go to Step 25.

Run the following command:
route add default gw 192.168.40.1

The gateway IP address in the command is only used as an example, and you need to enter a correct gateway IP address based on the current networking environment.

After 3 or 4 minutes, switch to the Alarm page and check whether the alarm is cleared.

If yes, no further action is required.
If no, go to Step 19.

Check the Network Computer (NC) process.

Use PuTTY to log in to the CNA node.
Ensure that the management IP address and username gandalf are used to establish the connection.

Run the following command and enter the password of user root to switch to user root:

su - root


Run the following command to check the NC process status:
service vnad status

Check whether the command output is as follows:

Checking for service vna running

If yes, go to Step 25.
If no, go to Step 23.

Run the following command to start the CNA process:
service vnad restart

After 3 or 4 minutes, switch to the Alarm page and check whether the alarm is cleared.

Scroll to top