how to deal with Failed to Back up or Upload Key Data on the VRM Node alarm on FusionCompute V1R5C00 version

1

This alarm is generated when the system detects that key data fails to be backed up or uploaded from the Virtualization Resource Management (VRM) node to the File Transfer Protocol (FTP) server.

The number of key data copies saved on the FTP server exceeds 7 and the deletion of the earliest key data copies fails.
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 for which the alarm is generated.
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 df -h command to check whether the value in the Avail column of the /var/backup directory is greater than the sum of the values in the Used columns of the /opt/gaussdb directory and the /etc/galax directory.

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/xvda1 10317828 1848936 7944776 19% /
devtmpfs 2469080 152 2468928 1% /dev
tmpfs 2469080 0 2469080 0% /dev/shm
/dev/xvda6 1027768 17936 957624 2% /etc/galax
/dev/mapper/vg_vrm-lv_extend
63461 5402 54783 9% /extend
/dev/xvda8 1106800 34188 1016388 4% /opt/galax/upgrade
/dev/mapper/vg_vrm-lv_gaussdb
39736736 867952 36853808 3% /opt/gaussdb
/dev/xvda5 18572112 453124 17175576 3% /var
/dev/mapper/vg_vrm-lv_backup
73409792 397488 69283820 1% /var/backupIf yes, go to Step 6.
If no, go to Step 14.

On FusionCompute, choose System > System Configuration. In the navigation tree on the left, choose Service and Management Node, locate the row that contains VRM service in Service list, click Operation, and select Configure Management Data Backup. In the displayed dialog box, check whether the system is configured to upload key data to the FTP server..

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

Check whether key data is uploaded to the FTP server.

If yes, go to Step 8.
If no, go to Step 9.

Check whether the deletion permission for the client is configured on the FTP server.

If yes, go to Step 14.
If no, configure the deletion permission for the client on the FTP server and then go to Step 12.

Check whether the FTP server is correctly configured, and ensure its availability.
Run the ping ftp server IP address command to check whether the network connection between the local PC and the FTP server is normal. If no, check the network configuration and cable connection, and recover the network connection.
On FusionCompute, choose System > System Configuration. In the navigation tree on the left, choose Service and Management Node, locate the row that contains VRM service in Service list, click Operation, and select Configure Management Data Backup. In the displayed dialog box, check whether the current FTP server configuration is correct. If not, configure the FTP server on the current page.
Manually clear this alarm.
Run the cronBackupUpload command to back up data timely, and check whether this alarm is generated again

Other related questions:
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 Communication Between a VRM and Other VRMs in the VRM Domain Interrupted alarm on FusionCompute V1R5C00 version
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

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

how to deal with Clock Synchronization Process on the VRM Is Abnormal alarm on FusionCompute V1R5C00 version
This alarm is generated when the system detects that the clock synchronization process on the Virtualization Resource Management (VRM) node has stopped or is abnormal. This alarm is cleared when the clock synchronization process on the VRM node becomes normal. Restart the clock synchronization 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 ntp restart Run the following command to check the process status: service ntp status Check whether the command output is as follows: remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 19 64 377 0.000 0.000 0.001 Checking for network time protocol daemon (NTPD): 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 process status: service ntp status Check whether the following information is displayed, containing Checking for network time protocol daemon (NTPD): running remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 19 64 377 0.000 0.000 0.001 Checking for network time protocol daemon (NTPD): running

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