In FusionManager V100R005,how to troubleshoot the alarm "ALM-ServiceCenter.9203 ServiceCenter Server Time Changed"

1

Click System.
The System page is displayed.

Choose System Configuration > Time Management.
The Time Management page is displayed.

On the Time Management page, click Synchronize Time Forcibly.
System services will be restarted during forcibly time synchronization, which takes about 20 minutes.

Log in to ServiceCenter again after about 20 minutes, and go to the Time Management page to check whether the forcibly time synchronization is successful.

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

Check whether the alarm is cleared.

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

Handle the time error by following instructions provided in System Time Errors in Troubleshooting in the product documentation.
Contact technical support.

Other related questions:
In FusionManager V100R005,what's the mean of the alarm "ALM-ServiceCenter.9203 ServiceCenter Server Time Changed"
This alarm is generated when the ServiceCenter time is adjusted beyond the time adjustment threshold (60 seconds) of the system. The alarm can be automatically cleared after the handling operations are performed successfully.

In FusionManager V100R005,what's the impact of the alarm"ALM-ServiceCenter.9203 ServiceCenter Server Time Changed"
Served as the time server of the entire system, the abnormal time in ServiceCenter will affect the time of the system. Consequently, functions of many components, for example, the timing service on ServiceCenter are affected. In addition, ALM-9204 will be generated if the upper-layer NTP server is configured available for ServiceCenter.

In FusionManager V100R005,what's the mean of the alarm's parameters "ALM-ServiceCenter.9203 ServiceCenter Server Time Changed"
Additional information Provides supplementary information about the alarm. SN Specifies the number assigned to an alarm based on the sequence that the alarm is generated. Alarm name ServiceCenter Server Time Changed Object type Time Management Alarm object Time Management Component Specifies the component that reports the alarm. Type Specifies the type of the component that reports the alarm. Generated at Specifies the time when the alarm is generated. Cleared at Specifies the time when the alarm is cleared. Clearance type Specifies whether an alarm is manually or automatically cleared. This alarm can be automatically cleared. Cleared by Specifies the name of the operator who clears the alarm. Alarm Clearance User ID Specifies the ID of the user who clears the alarm. Alarm Cleared At Specifies the tenant view or administrator view in which the alarm is manually cleared.

In FusionManager V100R005,what's the possible reason of the alram "ALM-ServiceCenter.9203 ServiceCenter Server Time Changed"
The ServiceCenter time is changed manually.

In FusionManager V100R005,how to troubleshoot the alarm "ALM-ServiceCenter.9202 NTP Service Startup Failure"
Use PuTTY to log in to the ServiceCenter as user galaxmanager. Ensure that the management IP address of the ServiceCenter is used to establish the connection. Run the following command to disable PuTTY logout on timeout: TMOUT=0 Run the following command to check the process status: ntp status. The process is normal if the following information is displayed: remote refid st t when poll reach delay offset jitter ================================================================================ *LOCAL(0) .LOCL. 5 1 1 64 377 0.000 0.000 0.001 Checking for network time protocol daemon (NTPD): running Check whether the process is running properly. If yes, go to Step 11. If no, go to Step 5. Run the ntp restart command. Run the following command to check the process status: ntp status. The process is normal if the following information is displayed: remote refid st t when poll reach delay offset jitter ================================================================================ *LOCAL(0) .LOCL. 5 1 1 64 377 0.000 0.000 0.001 Checking for network time protocol daemon (NTPD): running Check whether the process is running properly. If yes, go to Step 8. If no, go to Step 9. Two or three minutes later, check whether the alarm is cleared. If yes, no further action is required. If no, go to Step 11 Run command ps -efww | grep -v grep | grep ntpd check the process ID. Run command kill -9 processID, check whether the result is successful? If yes, go to Step 5 If no, go toStep 11 Contact technical support.

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