Description

After an external clock source is configured, the NTP server periodically (default interval: 2 minutes) checks the time difference between the external clock source and the node where the active ntp-server service is deployed. If multiple external clock sources are configured, the system checks the time difference between the NTP server and each external clock source. This alarm is generated when any of the time differences exceeds the threshold.

Attribute

Parameters

Impact on the System

If the time difference between the external clock source and the local node where the active ntp-server service is deployed exceeds the threshold, the node does not synchronize time with the external clock source.

Possible Causes

• The system time of the node where the local active ntp-server service is deployed is changed.
• The system time of the external clock source changed.
• The time of the node was not forcibly synchronized when the node connected to the external clock source for the first time.
• Multiple external clock sources are configured, and the time difference between the NTP server and an external clock source exceeds the threshold.

Procedure

1. Log in to the FusionSphere OpenStack web client.

   For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode).

2. Choose O&M > Routine Maintenance.
3. After 2 minutes, check the system time status in the Time Synchronization area, in which Querying the system status changes into system time error, as shown in the following figure. View the details as prompted to obtain the time difference for the host where the alarm is generated.

4. Choose Configuration > System. Click NTP and view information about the configured external clock source, as shown in the following figure.

5. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

   The default user name is fsp. The default password is Huawei@CLOUD8.

   The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

   NOTE:

   To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:

   • Region Type I scenario:

     Cascading system: Cascading-ExternalOM-Reverse-Proxy

     Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

   • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

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

   su - root

   The default password of user root is Huawei@CLOUD8!.

7. Run the following command to disable user logout upon system timeout:

   TMOUT=0

8. Run the following command to import environment variables:

   source set_env

   Information similar to the following is displayed:

     please choose environment variable which you want to import: 
     (1) openstack environment variable (keystone v3) 
     (2) cps environment variable 
     (3) openstack environment variable legacy (keystone v2) 
     (4) openstack environment variable of cloud_admin (keystone v3) 
     please choose:[1|2|3|4] 

9. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

   Default account format: DCname_admin; default password: FusionSphere123.

10. Run the following command to query ntp-server deployment information (node ID information and the runsonhost value in the command output):

    cps template-instance-list --service ntp ntp-server

    Information similar to the following is displayed:

     +------------+----------------+--------+------------+----------------+
     | instanceid | componenttype  | status |runsonhost  |omip            |
     +------------+----------------+--------+------------+----------------+
     | 1          | ntp-server     | active | Mgmt1      |10.38.82.84     |
     | 0          | ntp-server     | standby| Mgmt3      |10.38.82.136    |
     +------------+----------------+--------+------------+----------------+

    NOTE:

    The number of command outputs is determined by the ntp-server deployment mode. The record whose value of status is active indicates that the host functions as the active ntp-server node.

11. Log in to the node where the active ntp-server service is deployed using the management IP address. For details about the username and password, see 5 to 6.
12. Run the following command to check whether check whether all system time differences are less than the threshold:

    ntpdate -d IP address of the external clock source

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

13. Check whether any inaccurate clock source exists.
    • If yes, remove inaccurate clock sources and go to 14.
    • If no, contact technical support for assistance.

14. Perform 3 again to check whether the prompt information changes from Querying the system status to The system time is normal.
    • If yes, go to 15.
    • If no, contact technical support for assistance.

15. After 5 to 10 minutes, check whether the alarm is cleared.
    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None