No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-9201 OpenStack OM Failed to Synchronize Time with Upper-Layer Network Server

ALM-9201 OpenStack OM Failed to Synchronize Time with Upper-Layer Network Server

Description

The time management module detects the running status of the upper-layer server at the specified synchronization interval. This alarm is generated when the time management module detects that the upper-layer server is unavailable for 30 minutes.

Attribute

Alarm ID

Alarm Severity

Auto Clear

9201

Major

Yes

Parameters

Name

Meaning

Fault Location Info

None

Additional Info

  • Local_Address: specifies the local IP address.
  • Peer_Address: specifies the peer IP address.

Impact on the System

Service OM cannot use the upper-layer server as its time server. As a result, the time on the system is inaccurate.

Possible Causes

  • Time difference between Service OM and the upper-layer server is more than one minute.
  • The network communication between Service OM and the upper-layer server is abnormal.
  • The time synchronization service on the upper-layer server is abnormal.

Procedure

  1. Log in to the Service OM web client.

    For details, see Logging In to and Logging Out of Service OM.

  2. On the Service OM page, choose Services > Service OM > Centralized O&M > System > Time Management.
  3. Check the IP address of time server 1, that is, the IP address of the upper-layer server.
  4. Use PuTTY to log in to Service OM.

    Ensure that the Service OM management floating IP address and username galaxmanager are used to establish the connection.

    Default username: galaxmanager ; default password: IaaS@OS-CLOUD9!

    NOTE:

    Log in to the FusionSphere OpenStack web client. For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode). Choose Cloud Service > FusionSphere OpenStack OM and view VM List to obtain the management floating IP address.

  5. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password is IaaS@OS-CLOUD8!.

  6. Run the following command to check the communication status:

    pingIP address of the upper-layer time server, for example, ping 172.28.9.37

    The network communication is normal if the following information is displayed:

    ping 172.28.9.37 (172.28.9.37) 56(84) bytes of data. 
    64 bytes from 172.28.9.37: icmp_seq=1 ttl=64 time=0.035 ms 
    64 bytes from 172.28.9.37: icmp_seq=2 ttl=64 time=0.028 ms 
    64 bytes from 172.28.9.37: icmp_seq=3 ttl=64 time=0.025 ms     

  7. Check whether the communication is normal.

    • If yes, go to 8.
    • If no, check the network connection and ensure that the network communication is normal.

  8. Run the following command to check whether the time synchronization service on the upper-layer server is available.

    ntpdate -d IP address of the upper-layer server, for example, ntpdate -d 172.28.9.37

    If information similar to the following is displayed, the service is normal:

    allinonefm:/opt # ntpdate -d 172.28.9.37 
    6 Sep 12:13:23 ntpdate[14344]: ntpdate 4.2.8p9@1.3265-o Tue Nov 29 09:18:51 UTC 2016 (1) 
    Looking for host 172.28.9.37 and service ntp 
    host found : 172.28.9.37 
    transmit(172.28.9.37) 
    receive(172.28.9.37) 
    transmit(172.28.9.37) 
    receive(172.28.9.37) 
    transmit(172.28.9.37) 
    receive(172.28.9.37) 
    transmit(172.28.9.37) 
    receive(172.28.9.37) 
    server 172.28.9.37, port 123 
    stratum 11, precision -24, leap 00, trust 000 
    refid [172.28.9.37], delay 0.02594, dispersion 0.00002 
    transmitted 4, in filter 4 
    reference time:    dd59f464.9d65b276  Wed, Sep  6 2017 12:13:24.614 
    originate timestamp: dd59f469.8bc9aecc  Wed, Sep  6 2017 12:13:29.546 
    transmit timestamp:  dd59f469.8bb6a04c  Wed, Sep  6 2017 12:13:29.545 
    filter delay:  0.02594  0.02594  0.02600  0.02603  
             0.00000  0.00000  0.00000  0.00000  
    filter offset: 0.000017 0.000002 -0.00004 -0.00003 
             0.000000 0.000000 0.000000 0.000000 
    delay 0.02594, dispersion 0.00002 
    offset 0.000017 
    6 Sep 12:13:29 ntpdate[14344]: adjust time server 172.28.9.37 offset 0.000017 sec     

  9. Check whether the time synchronization service on the upper-layer server is available.

    • If yes, go to 11.
    • If no, go to 10.

  10. Restore the upper-layer server and ensure that the time synchronization service is normal.
  11. Check whether the time difference between the upper-layer server and Service OM is less than one minute.

    • If yes, go to 17.
    • If no, go to 12.

  12. On the System page, click Time Management.

    The Time Management page is displayed.

  13. On the Time Management page, click Synchronize Time Forcibly.

    System services will be restarted during forcibly time synchronization, which takes about 20 minutes.

  14. Wait for about 20 minutes, log in to Service OM, and check whether the time synchronization is successful on the Time Management page.

    • If yes, go to 15.
    • If no, go to 18.

  15. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 16.

  16. Handle the time error by performing operations provided in "System Time Faults" in the HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide.
  17. After 10 to 15 time synchronization intervals, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 18.

  18. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45433

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next