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-34002 Time Hopping Occurs During NTP Synchronization

ALM-34002 Time Hopping Occurs During NTP Synchronization

Description

This alarm is reported when ICAgent detects that the NTP synchronization status is normal but the time offset between the NTP client and server is greater than 60s. If the time offset reaches 1,000s, the NTP service will terminate.

Attribute

Alarm ID

Alarm Severity

Alarm Type

34002

Critical

Time domain violation

Parameters

Parameter Name

Parameter Description

hostName

Indicates the host name.

hostIP

Indicates the host IP address.

ntpServerIP

Indicates the NTP server IP address.

Impact on the System

Partial service functions become abnormal because time hopping occurs during NTP synchronization.

System Actions

None

Possible Causes

The NTP service has just started.

Procedure

Check the start time of the NTP service.

  1. Check the location information of the alarm.

    1. Use a browser to log in to the FusionStage OM zone console.
      1. Log in to ManageOne Maintenance Portal.
        • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
        • The default username is admin, and the default password is Huawei12#$.
      2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
    2. Choose Application Operations > Application Operations from the main menu.
    3. In the navigation pane on the left, choose Alarm Center > Alarm List and query the alarm by setting query criteria.
    4. Click to expand the alarm information. Record the values of hostIP and hostName.

  2. Use PuTTY to log in to the manage_lb1_ip node. Run the following command to ping the IP address of the hostIP and check where the network is normal:

    The default username is paas, and the default password is QAZ2wsx@123!.

    ping hostIP

    • If the network is normal, go to 9.
    • If the network is abnormal, go to 3~8.

  3. Use PuTTY to log in to the manage_lb1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

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

    su - root

    Default password: QAZ2wsx@123!

  5. Run the following command to check whether the node corresponding to the queried hostIP is a management zone node:

    kubectl get node hostName -oyaml | grep 'com.huawei.project/name'

    labels:      
     com.huawei.project/name: fst-manage

    Check whether the value of com.huawei.project/name is fst-manage.

    • If yes, the node is a management zone node. Go to 6.a.
    • If no, the node is a data zone node. Go to 6.b

  6. Query the IP address for logging in to the node.

    1. Run the following command to query InternalIP of the node:

      kubectl get node hostName -oyaml | grep -B 2 InternalIP

    2. Run the following command to query ExternalIP of the node:

      kubectl get node hostName -oyaml | grep ExternalIP

  7. Run the following command switch to the paas user:

    su - paas

  8. Run the following command to go to the node using the IP address queried in 6:

    ssh IP

  9. Use PuTTY to log in to the faulty node based on the value of the hostIP parameter.

    Default username: paas. Default password: QAZ2wsx@123!

  10. Run the following command to check the start time of the NTP service:

    service ntpd status

    Information similar to the following is displayed:

    Redirecting to /bin/systemctl status  ntpd.service
    ● ntpd.service - Network Time Service
       Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled)
       Active: active (running) since Thu 2018-01-04 23:06:56 CST; 3 days ago
     Main PID: 12931 (ntpd)
       Memory: 1.4M
       CGroup: /system.slice/ntpd.service
               └─12931 /usr/sbin/ntpd -u ntp:ntp -g -x

    In the command output, the time after since is the start time of the NTP service. Check whether this alarm is reported within one minute after the start time.

    • If yes, the NTP service has just started. Go to 11.
    • If no, go to step 12.

  11. Run the following command to check whether the NTP hopping is cleared:

    ntpq -p

    Information similar to the following is displayed:

      remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
    *10.186.55.92    LOCAL(0)        11 u   98  128  377    0.820    0.963   0.249  

    Check whether the value of offset in the command output is less than 100 (ms).

    • If yes, the time hopping is cleared and this alarm will be automatically cleared.
    • If no, go to 11. If the offset value does not decrease, go to 12.

  12. Contact technical support for assistance.

Alarm Clearing

After ICAgent detects that the NTP synchronization status is normal, the system automatically clears the alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35968

Downloads: 31

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