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

FusionCloud 6.3.1.1 Troubleshooting Guide 03

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).
NTP Service Fault

NTP Service Fault

Symptom

Cloud Configuration Service (CCS), Network Time Protocol (NTP), DMK, DNS-Internal, and Repo Server are deployed together on the OM-SRV01 and OM-SRV02 nodes. If the NTP service is faulty, the VM cannot synchronize time with the upper-level clock source.

Possible Causes

  • The network between the VM and the upper-level clock source is disconnected.
  • The NTP is abnormal.

Fault Diagnosis

Figure 24-8 shows the troubleshooting method of this fault.

Figure 24-8 Fault Diagnosis

Procedure

  1. Check whether you can log in to the VM where the NTP service is deployed.

    • If yes, go to 4.
    • If no, go to 2.

  2. Restore the VM. For details, see Cloud Service Management Plane Fault Diagnosis.
  3. Contact Technical Support to reinstall the NTP service. The task is complete.
  4. Use PuTTY to log in to an NTP service node.

    • Login address: Management IP addresses of the TDNS-TNTP-01 and TDNS-TNTP-02 nodes.
    • Username: untp
    • Default password: Huawei12#$

  5. Run the following command to disable logout on timeout:

    TMOUT=0

  6. Run the following command to check whether the VM can communicate with upper-level clock source.

    ping IP address of the upper-level clock source

    • If yes, go to 7.
    • If no, contact technical support for assistance.

  7. Run the following commands to check whether the ntpd process has been stopped accidentally.

    systemctl status ntpd

    • If yes, go to 8.
    • If no, contact technical support for assistance.

    If information similar to the following is displayed, the ntpd process stops accidentally:

  8. Run the following command to restart the ntpd process and check the command output:

    systemctl restart ntpd

    • If no command output is displayed, the ntpd process is restarted. Go to 9.
    • If the following information is displayed, the named process fails to be started. Go to 10:
      Job for ntpd.service failed because the control process exited with error code. See "systemctl status ntpd.service" and "journalctl -xe" for details.

  9. Run the following command to check the ntpd process status:

    systemctl status ntpd

    If information similar to the following is displayed, the ntpd process is normal and the task is complete.

  10. Run the following command to restore the ntpd process based on the error message:

    systemctl status ntpd

    journalctl -xe

    After the fault is rectified, restart the ntpd process. If the fault persists, Contact technical support for assistance.

Translation
Download
Updated: 2019-08-16

Document ID: EDOC1100063248

Views: 25078

Downloads: 39

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