In FusionManager V100R005,what's the possible reason of the alram "ALM-ServiceCenter.9201 Failure to Synchronize Time by the ServiceCenter from the Upper-Layer Time Server"

1

Time difference between ServiceCenter and the upper-layer NTP server is more than one minute.
The network communication between ServiceCenter and the upper-layer NTP server is abnormal.
The time synchronization service on the upper-layer NTP server is unavailable.

Other related questions:
In FusionManager V100R005,what's the impact of the alarm"ALM-ServiceCenter.9201 Failure to Synchronize Time by the ServiceCenter from the Upper-Layer Time Server"
ServiceCenter cannot use the upper-layer NTP server as its time server As a result, the time displayed on the system is inaccurate.

In FusionManager V100R005,what's the mean of the alarm "ALM-ServiceCenter.9201 Failure to Synchronize Time by the ServiceCenter from the Upper-Layer Time Server"
The time management module detects the status of the upper layer time server at the preset synchronization interval. This alarm is generated when the time management module detects that the upper-layer NTP server is unavailable for 10 consecutive times. This alarm is cleared when the time management module detects that the upper-layer NTP server becomes available.

In FusionManager V100R005,how to troubleshoot the alarm "ALM-ServiceCenter.9201 Failure to Synchronize Time by the ServiceCenter from the Upper-Layer Time Server"
Click System. The System page is displayed. On the System page, choose System Configuration > Time Management. The Time Management page is displayed. Check the IP address of time server 1, that is, the IP address of the upper-layer NTP server. Use PuTTY to log in to ServiceCenter as user galaxmanager. Ensure that the ServiceCenter management IP address is used to establish the connection. Run the following command to check the communication status: ping IP address of the upper-layer time server, for example, ping 192.168.41.10. The communication between ServiceCenter and the upper-layer NTP server is normal if the following information is displayed: ping 192.168.41.10 (192.168.41.10) 56(84) bytes of data. 64 bytes from 192.168.41.10: icmp_seq=1 ttl=64 time=0.035 ms 64 bytes from 192.168.41.10: icmp_seq=2 ttl=64 time=0.028 ms 64 bytes from 192.168.41.10: icmp_seq=3 ttl=64 time=0.025 ms Check whether the communication between ServiceCenter and the upper-layer NTP server is normal. If yes, go to Step 7. If no, check the network connection and ensure that the network communication is normal. Run the following command to check whether the time synchronization service on the upper-layer NTP server is available: ntpq -p IP address of the upper-layer NTP server For example, run the ntpq -p 192.168.41.10 command. The time synchronization service is running properly if information similar to the following is displayed: GMN01:~ # ntpq -p 192.168.41.10 remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 11 l 410 64 377 0.000 0.000 0.004 Check whether the time synchronization service on the upper-layer NTP server is available. If yes, go to Step 10. If no, go to Step 9. Troubleshoot the upper-layer NTP server and ensure that it provides the time synchronization service properly. Check whether the time difference between the upper-layer NTP server and ServiceCenter is less than 1 minute. If yes, go to Step 16. If no, go to Step 11. On the System page, click 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 14. If no, go to Step 17. Check whether the alarm is cleared. If yes, no further action is required. If no, go to Step 15. Handle the time error by following instructions provided in System Time Errors in Troubleshooting in the product documentation. After 10 to 15 time synchronization intervals, check whether the alarm is automatically cleared. If yes, no further action is required. If no, go to Step 17. Contact technical support.

In FusionManager V100R005,what's the mean of the alarm's parameters "ALM-ServiceCenter.9201 Failure to Synchronize Time by the ServiceCenter from the Upper-Layer Time Server"
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 Failure to Synchronize Time with the Upper-Layer NTP Server 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.9207 License Is About to Expire"
The license is about to expire in less than 30 days.

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