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-34001 NTP Synchronization Status Is Abnormal

ALM-34001 NTP Synchronization Status Is Abnormal

Description

This alarm is reported when ICAgent detects that the NTP synchronization status is abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

34001

Critical

Time domain alarm

Parameters

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 the NTP synchronization status is abnormal.

System Actions

None

Possible Causes

  • The NTP service is disabled.
  • The NTP server is incorrectly configured.
  • The NTP process is abnormal.
  • The NTP time changes between 60–1000s.
    NOTE:

    During the time hopping verification by the NTP algorithm, the NTP client identifies the time hopping to be inaccurate and will not synchronize the time. In this case, the alarm is reported when ICAgent detects that the NTP synchronization status is abnormal. After the verification is complete, the NTP client automatically synchronizes the time and then the alarm is cleared.

Procedure

  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. 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.

    Check whether this alarm is generated on all nodes listed in the fault location information on the Alarm List page.

    • If this alarm is generated on all nodes, go to Step 11.
    • If this alarm is not generated on all nodes, go to Step 12.

  11. Check whether the NTP network is normal.

    1. Run the following command on any node where the alarm is generated to query the server node where NTP resides:

      vi /var/paas/bootstrap/knowledge/fusionstage_LiteCoreBase.yaml

      clock:        
          ip: 10.10.29.188         
          tenant-ip: 10.10.31.80         
          timezone: Asia/Shanghai  iaas:    
      cloud_provider: fusionsphere        
          fs_host_ip: 10.118.22.3        
          hicloud_app_env: default         
          hicloud_app_userid: default      
          hicloud_appid: default        
          hicloud_biz_type: default       
          hicloud_ebs_base_uri: default       
          hicloud_ec2_base_uri: default       
          hicloud_iam_auth_host_ip: default      
          hicloud_scope: internal        
          hicloud_system_env: pro         
          hicloud_vpc_base_uri: default    
    2. Run the following command to check whether the node where the alarm is generated can communicate with the NTP server node:

      ping{IP}

      • If the node where the alarm is generated can communicate with the NTP server node, run the service ntpd status command on the server node to check whether the status of the server node is running.
        • If the status of the server node is running, go to Step 13.
        • If the status of the server node is not running, contact technical support to check the NTP server faults.
      • If the node where the alarm is generated cannot communicate with the NTP server node, go to Step 17.
        NOTE:

        IP indicates the IP address of the server node where NTP resides obtained in Step 11.a.

  12. On the node where this alarm is generated, run the following command to check whether the NTP service is enabled:

    service ntpd statu

    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
    • If active (running) is displayed next to Active in the fourth row of the command output, the NTP service is enabled and running. Go to Step 14.
    • If inactive (dead) is displayed next to Active in the fourth row of the command output, the NTP service is not enabled. Go to Step 13.

  13. Run the following command to enable the NTP service:

    service ntpd start

    Perform Step 12 to check whether the NTP service is successfully enabled.

    • If the NTP service is enabled, go to Step 14.
    • If the NTP service is not enabled, go to Step 17.

  14. Run the following command to check whether the NTP synchronization status is normal:

    ntpq -p

    If information similar to the following is displayed, the NTP synchronization status is normal (the value of offset less than 100). This alarm will be automatically cleared in one minute.

    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    
    • If the NTP synchronization status is normal, the alarm will be automatically cleared.
    • If the NTP synchronization status is not normal, go to Step 15.

  15. Run the following command to check the NTP process status. If the process status is Ss, go to Step 16.

    ps aux |grep ntpd|grep -v grep

    If the process status is not Ss, run the following commands to manually delete the process and restart the NTP service:

    Kill -9 {NTP process ID}

    service ntpd restart

  16. For details, see the command and command output in Step 14 and Step 15. This alarm will be automatically cleared in one minute. Otherwise, go to Step 17.
  17. Copy the /etc/ntp.conf file from the faulty node and 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: 34913

Downloads: 31

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