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-6022 Heartbeat Communication Between the Host and the NTP Server Interrupted

ALM-6022 Heartbeat Communication Between the Host and the NTP Server Interrupted

Description

The NTP client periodically (default interval: 2 minutes) checks the connection between the current node and the node where the active NTP server is located. This alarm is generated when the connection fails or the active NTP server is faulty for more than 30 minutes. This alarm is cleared when the network fault between nodes is rectified or the fault of the active NTP server is rectified.

Attribute

Alarm ID

Alarm Severity

Auto Clear

6022

Major

Yes

Parameters

Name

Meaning

Fault Location Info

host_id: specifies the ID of the host for which the alarm is generated.

Additional Info

  • host_id: specifies the ID of the host for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.
  • Local_Address: specifies the management IP address of the host.
  • Peer_address: specifies the floating IP address of the NTP server.

Impact on the System

  • If the NTP client is disconnected from the node where the active NTP server is deployed or the active NTP server is faulty, the node where the NTP client is deployed cannot synchronize time with the internal active NTP server.
  • A valid token cannot be used within its validity period, or an expired token can be still used.
  • Services on the node may be unavailable due to time asynchronization.
  • System data sampling may be incorrect.
  • Data may be lost.

Possible Causes

  • The floating IP address of the active NTP server is not configured or has been deleted.
  • The active ntp-server process is faulty.
  • The internal network is faulty.

Procedure

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

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

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

    TMOUT=0

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

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

    Default account format: DCname_admin; default password: FusionSphere123.

  1. Run the following command to query NTP server deployment information:

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

    Information similar to the following is displayed:

      +------------+-------------------------------+--------+--------------------------------------+ 
      | instanceid | componenttype                 | status | runsonhost                           | 
      +------------+-------------------------------+--------+--------------------------------------+ 
      | 1          | ntp-server-1.0.0-1.x86_64.rpm | active | 00259E83-0048-0000-1000-1DD24170FFFF | 
      | 0          | ntp-server-1.0.0-1.x86_64.rpm | standby| CCCC8175-8F78-0000-1000-1DD200005020 | 
      +------------+-------------------------------+--------+--------------------------------------+
    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.

  2. Log in to the FusionSphere OpenStack web client.

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

  3. On the Summary page, obtain the management IP address of the host in the OM IP Address column based on the host ID or host name in the alarm additional information.
  4. 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 1 and 2.
  5. Run the following command on the node:

    ip addr show |grep brcps:ntp

    Information similar to the following is displayed:

    inet 172.28.1.37/16 scope global secondary brcps:ntp-s

    Check whether the floating IP address is configured.

    • If yes, go to 11.
    • If no, go to 12.

  6. Run the following command on the node where the active ntp-server service is deployed to check the active ntp-server process status:

    ps -ef|grep ntp |grep -v grep

    Information similar to the following is displayed:

    root      5832     1  0 Aug03 ?        00:00:27 /usr/bin/python /usr/local/bin/ntp-client/ntp_client/ntpclient.py -s 172.31.9.37
    root     22843     1  0 01:33 ?        00:00:00 /usr/sbin/ntpd -4 -c /usr/local/bin/ntp-server/conf/ntp.conf 
    cps      22851     1  0 01:33 ?        00:00:10 python /usr/local/bin/ntp-server/ntp_server/ntpserver.py     

    Check whether the process exists.

    • If yes, go to 15.
    • If no, go to 12.

  7. Perform the following operations to stop the active ntp-server process.

    1. Run the following command to enter the secure operation mode:

      cpssafe

      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) 
        please choose:[1|2|3]
    2. Enter 1 to enable Keystone V3 authentication.

      Information similar to the following is displayed:

      Input command:
    3. Run the following command to stop the active ntp-server process:

      cps host-template-instance-operate --service ntp --action stop ntp-server --host NTP host ID

      Information similar to the following is displayed:

      +------------+--------------------------------------+---------+ 
      | template   | runsonhost                           | result  | 
      +------------+--------------------------------------+---------+ 
      | ntp-server | CCCC8175-8F78-0000-1000-1DD200005020 | success | 
      +------------+--------------------------------------+---------+     

      Check whether the process is successfully stopped.

    • If yes, go to 13.
    • If no, go to 15.
    NOTE:

    --host in the preceding command indicates the ID of the node where the active ntp-server service is deployed.

  8. Perform the following operations to start the active ntp-server process:

    1. Run the following command to enter the secure operation mode:

      cpssafe

      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) 
        please choose:[1|2|3]
    2. Enter 1 to enable Keystone V3 authentication.

      Information similar to the following is displayed:

      Input command:
    3. Run the following command to start the active ntp-server process:

      cps host-template-instance-operate --service ntp --action start ntp-server --host NTP host ID

      Information similar to the following is displayed:

      +------------+--------------------------------------+---------+ 
      | template   | runsonhost                           | result  | 
      +------------+--------------------------------------+---------+ 
      | ntp-server | CCCC8175-8F78-0000-1000-1DD200005020 | success | 
      +------------+--------------------------------------+---------+     

      Check whether the process is successfully started.

    • If yes, go to 14.
    • If no, go to 15.
    NOTE:

    --host in the preceding command indicates the ID of the node where the active ntp-server service is deployed.

  9. After 5 to 10 minutes, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 15.

  10. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37543

Downloads: 31

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