how to deal with VRM System Time Offset Exceeds 1 Minute alarm on FusionCompute V1R5C00 version

2

The system checks its time every minute. This alarm is generated when the system detects that the time offset exceeds 1 minute
Handle the alarm.

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.
Click System Configuration on the System Management page, select Time Management, and obtain the IP address of the NTP server.
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


Check whether the NTP server is configured.

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

Have the administrator check whether the NTP server is available. If available, obtain the NTP server IP address of the NTP server and run the following command to check whether the heartbeat communication between the node and the upper-layer NTP server is normal:
ntpq -p NTP server IP address or domain name

Determine the NTP server status according to the command output and check whether Request timed out or ntpq: read: Connection refused is contained in the command output.

If yes, the heartbeat communication of the server is abnormal. Go to Step 8.

If no, the heartbeat communication of the server is normal. Go to Step 9.


Have the administrator check whether the node can properly communicate with the NTP server and whether the NTP server runs properly. After the heartbeat communication between the node and the NTP server is restored, go to Step 9.
Run the sh /usr/sbin/ntpdate NTP server IP address or domain name&& /sbin/hwclock -w -u command to synchronize time.
Check whether sntp: not enough valid responses received in time is contained in the command output.


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

Run the following command to restart all processes on the node:

sh /opt/galax/gms/common/config/restartPorcess.sh

NOTE:
The restart of all processes takes about 3 minutes. During the restart, you cannot log in to the FusionStack portal.


Check whether the following information is displayed:

restart all process success.

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

After 3 minutes, log in to the FusionCompute again, locate the row that contains the alarm to be cleared, click Manually clear, and clear this alarm. Check whether the alarm is cleared.

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

Contact technical support.
Handle the alarm impact.

The alarm generation and processing involve time adjustment. If the time is adjusted to the past time, some alarms cannot be cleared automatically. For example, if the time is adjusted from T1 09:00 a.m. to T2 08:00 a.m., some alarms generated from T0 08:00 a.m. (original 08:00 a.m.) to T1 cannot be cleared automatically. These alarms need to be cleared manually. After the time reaches T3 09:00 a.m., check whether the alarms generated from T2 to T3 on the Monitoring page are automatically cleared based on the online help information. If not, choose Monitoring > Alarms to manually clear the alarms.

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