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 Troubleshooting Guide 02

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 Faults

NTP Service Faults

The System Time Inconsistent with the NTP Time

Symptom

The time of the server OS is different from that of the NTP clock source. As a result, the server cannot synchronize time with the NTP clock source.

Prerequisites

You have obtained the IP address of the NTP clock source.

Operation Instructions

During time synchronization, node services must be restarted. Perform the following operations during off-peak hours.

Procedure

The time zone and time can be forcibly synchronized in two modes: GUI mode and manual mode. In GUI mode, the system slowly adjusts the time and no sudden time change occurs. In manual mode, the system forcibly synchronizes the time immediately and sudden time change occurs. Sudden time change affects functions that have high requirements on time accuracy, for example, the backup and restore function. Select a time zone and time synchronization mode as required.

  • Using the GUI
    1. Use a browser to log in to ManageOne Deployment Portal.

      URL: https://Floating IP address of ManageOne Deployment Portal:31945, for example, https://192.168.0.1:31945

      Default account: admin; default password: Huawei12#$

    2. On the main menu, choose Application > Service Management > System Monitoring.
    3. In the upper left corner of the System Monitoring page, click to switch to the ManageOne product to be stopped. Click Stop and select Stop All from the drop-down list.
    4. In the displayed Warning dialog box, click OK.
    5. Click Task Information List in the Prompt dialog box to check progress of the task in the Task Progress column. When the task progress reaches 100%, check whether the status of the task is successful in the Task Status column.
      • If yes, go to 6.
      • If no, contact technical support for assistance.
    6. On the main menu of Deployment Portal, choose Maintenance > Time Management > Configure Date and Time
    7. On the Configure Date and Time page, click Forcibly Synchronize.
    8. In the displayed dialog box indicating that the synchronization is complete, click OK. If the forcible synchronization fails, you can view the execution status in the Task Information List. For details, contact technical support for assistance.
    9. On the main menu, choose Application > Service Management > System Monitoring.
    10. In the upper left corner of the System Monitoring page, click to switch to the ManageOne product to be started. Click Start and select Start All from the drop-down list.
    11. In the displayed Warning dialog box, click OK.
    12. Click Task Information List in the Prompt dialog box to check progress of the task in the Task Progress column. When the task progress reaches 100%, check whether the status of the task is successful in the Task Status column.
      • If yes, go to 13.
      • If no, contact technical support for assistance.
    13. After the time zone and time are forcibly synchronized, wait about 1 to 15 minutes and perform 13.a through 13.c to check whether the time zone and time of the server OS are the same as those of the NTP clock source.
      1. Log in to a node as the sopuser user. For details about how to obtain the IP address of a node, see Querying the IP Address of a Node.

        The default password is D4I$awOD7k.

      1. Run the following command to switch to the root user:

        sudo su root

        The default password is Changeme_123.

      1. Run the following command. If the value of offset in the command output is less than or equal to 100.000, in milliseconds, the time zone and time of the server OS are the same as those of the NTP clock source.

        ntpq -p

             remote           refid      st t when poll reach   delay   offset  jitter
        ==============================================================================
        *192.168.33.78   192.682.34.41    9 u  221 1024  377    0.181    0.021   0.123
        +192.168.33.79   192.168.34.41    9 u  805 1024  377    0.270    0.223   0.137
      • If yes, the fault is rectified.
      • If no, contact technical support for assistance.
  • Manual mode
    1. Use PuTTY to log in to the target node as the sopuser user in SSH mode.

      The default password is D4I$awOD7k.

    2. Run the following command to switch to the root user:

      sudo su root

      The default password is Changeme_123.

    3. Run the following command to stop the NTP service on the node with time zone and time to be synchronized:

      service ntpd stop

      If the following information is displayed, the stop operation is successful:

      Redirecting to /bin/systemctl stop  ntpd.service
    4. Run the following commands to synchronize the system time with the NTP clock source:

      ntpdate IP address of the clock source

      The operation succeeds if information similar to the following is displayed:

       22 Dec 11:47:23 ntpdate[11672]: adjust time server 192.168.25.55 offset -0.002394 sec

      hwclock --systohc

      NOTE:

      Change IP address of the clock source in the command to the actual IP address. If the server whose time zone and time are to be synchronized is a Deploy node, change the IP address to that of the NTP server. If the server is a product node, change the IP address to that of the active Deploy node. For details about how to query the Deploy nodes, see Querying the IP Address of a Node. For details about how to determine the active and standby nodes, see Determining the Active and Standby Nodes of the Deployment System.

    5. Run the following command. If the value of offset in the command output is less than or equal to 100.000, in milliseconds, the time zone and time of the server are the same as those of the NTP clock source.

      ntpq -p

           remote           refid      st t when poll reach   delay   offset  jitter
      ==============================================================================
      *192.168.33.78   192.168.34.41    9 u  221 1024  377    0.181    0.021   0.123
      +192.168.33.79   192.168.34.41    9 u  805 1024  377    0.270    0.223   0.137
      • If the server whose time zone and time are to be synchronized is a Deploy node, the time of the server must be the same as that of the NTP clock source.
      • If the server whose time zone and time are to be synchronized is a product node, the time of the server must be the same as that of the Deploy node.

        If the time is accurate and consistent, perform 6. Otherwise, contact technical support for assistance.

    6. Run the following command to start the NTP service on the node with the time zone and time to be modified:

      service ntpd start

      If the following information is displayed, the start operation is successful:

      Redirecting to /bin/systemctl start ntpd.service

Restoring the NTP Server Status

Symptom

On the main menu of Deployment Portal, choose Maintenance > Time Management > Configure NTP. On the Configure NTP page, add NTP servers. In the NTP server list, the Time Sync Status of the NTP server is Abnormal.

Procedure
  1. Check whether the network connectivity between the Deploy node and the upper-level NTP server is normal.

    1. Use PuTTY to log in to each Deploy node as the sopuser user in SSH mode.
      The default password is D4I$awOD7k.
      NOTE:
      • For details about how to query the IP address of the Deploy node, see Querying the IP Address of a Node.
      • If Deploy nodes are deployed in cluster mode, log in to the regionAlias-ManageOne-Deploy01 node and perform corresponding operations. Then, log in to the regionAlias-ManageOne-Deploy02 node and perform related operations.
    2. Run the following command to switch to the root user:

      sudo su root

      The default password is Changeme_123.

    3. Run the following command to check whether the network connectivity between the Deploy node and the upper-level NTP server is normal:

      ntpq -p

      remote           refid      st t when poll reach   delay   offset  jitter
      ==============================================================================
      *LOCAL(0)        .LOCL.      5 l   57   64  0    0.000    0.000   0.000
      • If the values of reach, delay, offset, and jitter are not 0 in the command output, the network connectivity between the Deploy node and its upper-level NTP server is normal.
      • If the values of reach, delay, offset, and jitter are 0 in the command output, the network connectivity between the Deploy node and its upper-level NTP server is abnormal. Check whether the NTP service of the Deploy node is normal. For details, see 3.

  2. Contact the NTP server vendor to check whether the NTP service of the upper-level NTP server is normal.

    • If yes, go to 3.
    • If no, replace the NTP server.

  3. Check whether the NTP service of the Deploy node is normal.

    1. Use PuTTY to log in to each Deploy node as the sopuser user in SSH mode.

      The default password is D4I$awOD7k.

      NOTE:
      • For details about how to query the IP address of the Deploy node, see Querying the IP Address of a Node.
      • If Deploy nodes are deployed in cluster mode, log in to the regionAlias-ManageOne-Deploy01 node and perform corresponding operations. Then, log in to the regionAlias-ManageOne-Deploy02 node and perform related operations.
    2. Run the following command to switch to the ossadm user:

      su - ossadm

      The default password is Changeme_123.

    3. Run the following command to check whether the NTP service is started:

      service ntpd status

      • If the command output contains "active (running)", the NTP service has been started on the Deploy node.
      • If the command output contains "inactive (dead)", the NTP service is not started on the Deploy node. In this case, run the following commands to start the NTP service:

        sudo su root

        The default password is Changeme_123.

        service ntpd start

        If the following information is displayed, the NTP service is started successfully:

        Redirecting to /bin/systemctl start ntpd.service

  4. If the preceding check items are normal but the NTP server is still in the Abnormal state, perform the following operations:

    1. On the main menu of Deployment Portal, choose Application > Service Management > System Monitoring.
    2. In the upper left corner of the System Monitoring page, click to switch to the ManageOne product to be stopped. Click Stop and select Stop All from the drop-down list.
    3. In the displayed Warning dialog box, click OK.
    4. Click Task Information List in the Prompt dialog box to check progress of the task in the Task Progress column. When the task progress reaches 100%, check whether the status of the task is successful in the Task Status column.

      If yes, go to 4.e.

      If no, contact technical support for assistance.

    5. On the main menu of Deployment Portal, choose Maintenance > Time Management > Configure NTP. In the Configure NTP dialog box, click Reconfigure.
    6. In the displayed Warning dialog box, click OK.
    7. On the main menu of Deployment Portal, choose Maintenance > Time Management > Configure Date and Time. On the Configure Date and Time page, click Forcibly Synchronize. 15 minutes later, check the NTP server status.
    8. On the main menu, choose Application > Service Management > System Monitoring.
    9. In the upper left corner of the System Monitoring page, click to switch to the ManageOne product to be started. Click Start and select Start All from the drop-down list.
    10. In the displayed Warning dialog box, click OK.
    11. Click Task Information List in the Prompt dialog box to check progress of the task in the Task Progress column. When the task progress reaches 100%, check whether the status of the task is successful in the Task Status column.
      • If yes, the start is successful.
      • If no, contact technical support for assistance.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1748

Downloads: 12

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