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-6015 NTP Server Failed to Connect to the External Clock Source or the External Clock Source Failed

ALM-6015 NTP Server Failed to Connect to the External Clock Source or the External Clock Source Failed

Description

After an external clock source is configured, the NTP server periodically (2 minutes) checks the connection between the external clock sources and the active ntp-server node. This alarm is generated when the connection between the NTP server and all external clock sources becomes abnormal or external clock sources fail for more than 30 minutes. This alarm is cleared when the connection between the NTP server and any of the external clock sources or an external clock source is restored.

Attribute

Alarm ID

Alarm Severity

Auto Clear

6015

Major

Yes

Parameters

Name

Meaning

Fault Location Info

Region: specifies the name of the region for which the alarm is generated.

Object: specifies the service 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 IP address of the NTP client.
  • Peer_address: specifies the IP address of the external clock source.

Impact on the System

The node where the local active ntp-server service is deployed will not synchronize time with the external clock source.

Possible Causes

  • The network between the local NTP server and the external clock source fails.
  • The external clock source is not started or fails.
  • The firewall on the node where the external clock source is deployed blocks access from the ntpd service.
  • When you configure an external clock source, the external clock source and the selected network plane are on different network segments and the NTP gateway is not configured.
NOTE:

If multiple ALM-6015 alarms with the same alarm object and object ID but different object types exist on the alarm page, manually clear the alarms whose object type is host.

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 the IP address of the external clock source (server value in the command output) and the outbound port (network value in the command output):

    cps template-params-show --service ntp ntp-server

    Information similar to the following is displayed:

    +-----------------------+------------------------------------------+ 
      | Property              | Value                                    | 
      +-----------------------+------------------------------------------+ 
      | active_ip             | 192.168.0.2/24                             | 
      | admin_user            | cps                                      | 
      | auth_host             | identity.az1.dc1.domainname.com          | 
      | auth_mode             | False                                    | 
      | auth_port             | 443                                      | 
      | auth_protocol         | https                                    | 
      | ca_certfile           | N8296FGj0gDK1OA8******                   | 
      | certfile              |                                          | 
      | cps_password          | N8296FGj0gDK1OA8djBQ50u/7CZvJ+RfE2qNhiGI | 
      |                       | CE8=                                     | 
      | gateway               |                                          | 
      | keystone_offline_time | 86400                                    | 
      | maxdist               | 30                                       | 
      | network               | external_api                             | 
      | os_auth_url           | https://identity.az1.dc1.domainname.com: | 
      |                       | 443/identity-admin/v3                    | 
      | period                | 64                                       | 
      | private_key           | N8296FGj0gDK1OA8******                   | 
      | server                | 192.168.0.1                                | 
      | standby_ip            | 192.168.0.3/24                             | 
      | use_ssl               | True                                     | 
      +-----------------------+------------------------------------------+
    NOTE:

    If multiple external clock sources are deployed, their IP addresses are separated using commas (,) in the server field in the command output.

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

  3. Log in to the FusionSphere OpenStack web client.

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

  4. 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.
  5. 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 to 2.
  6. Run the following command to check whether the network communication between the external clock source and the node where the active ntp-server service is deployed is normal:

    ping External clock source IP address -I Outbound port

    For example, run the ping 192.168.0.1 -I external_api command.

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

    If multiple external clock sources are deployed, check the network communication for the external clock sources one by one. Ensure that the NTP server can communicate with at least one external clock source.

  7. Run the service ntpd status command to check whether the external clock source is normal.

    • If yes, go to 13.
    • If no, run the service ntpd start command to start the external ntpd server. Rectify the fault of the external clock source or configure another external clock source. Then, go to 16.

  8. Check whether the firewall on the node where the external clock source is deployed allows access from the ntpd and ntpdate ports.

    • If yes, go to 17.
    • If no, modify the firewall settings and go to 16.
    NOTE:

    The ntpd service uses port 123, and the ntpdate service uses port 124.

  9. On the FusionSphere OpenStack web client, choose Configuration > System > NTP and check whether NTP Gateway and External NTP (IP/Domain) are in the same network segment.

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

  10. Reconfigure NTP Gateway, NTP Client IP Address, and NTP Subnet Mask, and click Submit. Run the command in 11 to check whether the network communication between the external clock source and the active ntp-server node is normal:

    • If yes, go to 16.
    • If no, go to 17.

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

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

  12. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34650

Downloads: 31

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