How to deal with Communication Between a VRM and Other VRMs in the VRM Domain Interrupted alarm on FusionCompute V1R5C00 version

6

This alarm is generated when the communication between a Virtualization Resource Management (VRM) node and other VRM nodes in the VRM domain is interrupted.

This alarm is cleared when the communication resumes.
Query the IP address of the VRM node for which the alarm is generated.

On the FusionCompute portal, choose System > System Configuration, and choose Site Cascading in the navigation tree on the left.
The Cascading page is displayed.

Make a note of the management plane floating IP address of the faulty VRM node.
Check the network.

Use PuTTY to log in to a VRM.
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


On the VRM node, ping the management plane floating IP address of the faulty VRM node and check whether it can be pinged.

If yes, go to Step 6.
If no, have technical support rectify the network fault.

Check the VRM process.

Use PuTTY to log in to the faulty VRM.
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 following command to check the process status:
service vrmd status

Check whether the following information is displayed:

Checking for service vrm running

If yes, contact technical support.
If no, go to Step 10.

Run the following command to restart the VRM process:
service vrmd restart

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 12.

Log in to the VRM node.
For details, see Step 3.

On the VRM node, ping the management plane floating IP address of the faulty VRM node and check whether it can be pinged.

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

Log in to the faulty VRM node.
For details, see Step 6.

Run the following command to check the process status:
service vrmd status

Check whether the following information is displayed:

Checking for service vrm running

Other related questions:
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.

how to deal with Heartbeat Communication Between the VRM and the NTP Server Interrupted alarm on FusionCompute V1R5C00 version
Refer to the Link: http://support.huawei.com/ehedex/pages/DOC100006992931188002/04/DOC100006992931188002/04/resources/05_fc/alarm/cn_58_42_15.1007009.html

How to deal with Inconsistent Data in VRM Internal Modules alarm on FusionCompute V1R5C00 version
This alarm is generated when inconsistent data is detected in the internal modules of the Virtualization Resource Management (VRM) node. This alarm is cleared after the VRM is restarted. 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 the user root: su - root Run the following command to disable logout on timeout: TMOUT=0 Run the following command to restart the VRM process: service vrmd restart NOTICE: Restarting the VRM process may interrupt running services. For example, the current operation may fail. 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 6. Log in to the faulty VRM node. For details, see Step 1. Run the following command to check the process status: service vrmd status Check whether the following information is displayed: Checking for service vrm running

how to deal with NTP Clock Source Is Not Configured for a VRM alarm on FusionCompute V1R5C00 version
This alarm is generated when the system detects that the Network Time Protocol (NTP) clock source is not configured for a Virtualization Resource Management (VRM) node. This alarm is cleared when the NTP clock source is configured for the VRM On FusionCompute, choose System > System Configuration. The System Configuration page is displayed. In the navigation tree on the left, choose Time Management. On the Time Management page displayed, check whether the NTP clock source is configured for the site. If yes, go to Step 5. If no, go to Step 3. On the Time Management page, set an address for the NTP server, set Synchronization intervals (s), and click save. In the dialog box that is displayed, click OK. NOTE: You are advised to configure an external NTP clock source first. If no external NTP clock source exists, configure the clock source as the VRM host when the VRM is deployed on a VM or the VRM which is deployed on a server. After 5 or 6 minutes, check whether the alarm is cleared.

how to deal with System Timing Service Process on the VRM Is Abnormal alarm on FusionCompute V1R5C00 version
This alarm is generated when the system detects that the system timing service process on the Virtualization Resource Management (VRM) node has stopped or is abnormal. The alarm is cleared when the system timing service process of the VRM becomes normal. Restart the system timing service process. On FusionCompute, choose Monitoring > Alarm. On the Alarm page, click the alarm object name. The Service and Management Node page is displayed. On the Service and Management Node page, view the management node information and obtain the management IP address of the alarm object viewed in Step 1. Use PuTTY to log in to the 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 restart the process: service cron restart Run the following command to check the process status: service cron status Check whether the command output is as follows: Checking for Cron: running If yes, go to Step 8. If no, go to Step 11. After 2 or 3 minutes, check whether the alarm is cleared. If yes, no further action is required. If no, go to Step 9. Run the following command to check the status of the system timing service process: service cron status Check whether the following information is displayed: Checking for Cron: running

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top