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-73209 ZooKeeper Health Check Alarm

ALM-73209 ZooKeeper Health Check Alarm

Description

FusionSphere OpenStack periodically (default interval: 24 hours) checks data consistency among ZooKeeper nodes. This alarm is generated when inconsistent data exists.

Attribute

Alarm ID

Alarm Severity

Auto Clear

73209

Major

Yes

Parameters

Name

Meaning

Fault Location Info

zookeeper: specifies the name of the component for which the alarm is generated.

Additional Info

  • The first parameter lists IP addresses of ZooKeeper for which the alarm is generated.
  • Second parameter:
    • XX has diff data with leader XX: specifies that ZooKeeper data is inconsistent.
    • XX has diff path with leader XX: specifies that ZooKeeper path is inconsistent.

Impact on the System

The configuration data that takes affect is inconsistent with the expected data.

Possible Causes

The network at the active site is isolated in active-active DR scenarios.

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. Import environment variables and choose the CPS authentication. For details, see Importing 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] 

  1. Run the cps zookeeper-data-check command to check the command output.

    • Information similar to the following is displayed:
      +------------+--------------------------+
      | result     | data                     |
      +------------+--------------------------+
      | consistent | diff_data:{},            |
      |            | diff_path:{},            |
      |            | leader:[u'172.28.8.123'] |
      +------------+--------------------------+

    Check whether the command output contains consistent.

    • If yes, the ZooKeeper data is consistent. You can manually clear the alarm. Alternatively, you can wait for the next alarm check period, and the alarm is automatically cleared.
    • If no, go to 6.

  2. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35732

Downloads: 31

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