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-73208 External Arbitration Service Connection Fault

ALM-73208 External Arbitration Service Connection Fault

Description

This alarm is generated when the arbitration service in the active-active DR configuration of the management plane becomes faulty.

Attribute

Alarm ID

Alarm Severity

Auto Clear

73208

Major

Yes

Parameters

Name

Meaning

Fault Location Info

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

Additional Info

  • params_error: specifies that the arbitration service parameters are incorrect.
  • etcd_lost_connection: specifies that the IP address of the server is invalid.

Impact on the System

The arbitration service becomes unavailable, and the ZooKeeper process of the site will automatically stop. If the ZooKeeper processes on other nodes become faulty, the ZooKeeper connection drops. As a result, all services will become unavailable.

Possible Causes

  • The arbitration service parameter configuration is incorrect. The value of Additional Info is params_error.
  • Half or more than half of the arbitration servers are unreachable. Server IP addresses in the additional information are invalid.

Procedure

  1. Check whether the arbitration server parameter configuration is normal.

    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 commands to import environment variables: For details, see Importing Environment Variables. Choose the CPS authentication.

      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. Run the following command to obtain the rule group name of the arbitration server:

      cps hostcfg-list --type site

    6. Run the following command to obtain parameters of the arbitration server and check whether the parameter configuration is the same as the planned:

      cps hostcfg-show --type site site_rule_name

      site_rule_name indicates the name obtained in 1.e.

      • If yes, go to 3.
      • If no, interconnect FusionSphere OpenStack with the arbitration service again.

  2. Check whether the following alarms are generated. If they are reported, check the following alarms:

    1. ALM-2000266 System Time Offset Exceeds One Minute
    2. ALM-2001106 ETCD Service Status Is Abnormal
    3. ALM-2002101 Monitor Process Is Abnormal
    4. ALM-2002302 Monitor Cannot Communicate with the Peer Site
    5. ALM-2002501 Site Network Status Is Abnormal
    6. ALM-2001107 The Site Service Status Is Abnormal

  3. Check whether the arbitration service is invalid.

    • Log in to the arbitration service VM and check whether the arbitration service is normal.
      1. Log in to the arbitration service node of the cloud platform based on the IP address used by FusionSphere OpenStack to connect to the arbitration service in 1.f.

        Ensure that user arbiter is used to establish the connection.

        Run the following command and enter the password of user root as instructed to switch to the root user:

        sudo su - root

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

        TMOUT=0

      2. Check whether the arbitration service is normal.

        The command is as follows:

        systemctl status arbitration-etcd

        If information similar to the following is displayed, the service is normal. Otherwise, go to 5.

        [arbiter@ASVM01 ~]$ systemctl status arbitration-etcd
        arbitration-etcd.service - ArbitrationService etcd daemon
        Loaded: loaded (/usr/lib/systemd/system/arbitration-etcd.service; enabled)
        Active: active (running) since Fri 2018-04-13 21:47:40 CST; 3 days ago
        Process: 6791 ExecStop=/bin/sh /opt/arbitration-etcd/script/service.sh stop (code=exited, status=0/SUCCESS)
        Process: 6850 ExecStart=/bin/sh /opt/arbitration-etcd/script/service.sh start (code=exited, status=0/SUCCESS)
        Main PID: 6985 (etcd)
        CGroup: /system.slice/arbitration-etcd.service
         6985 /opt/arbitration-etcd/foss/2.2.4/etcd -name arbitration-etcd1 -data-dir /opt/arbitration-etcd/arbitration-etcd1 -cert-file=/opt/arbitration-etcd/keystore/server.crt -key-file=/opt/arbitr...

    • Log in to the first FusionSphere OpenStack node and check the connection between the alarm host and the arbitration service VM.
      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 commands to import environment variables: For details, see Importing Environment Variables. Choose the CPS authentication.

        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. Run the following command to check the connection between the host for which the alarm is generated and the arbitration service VM:

        cps-etcdCheck

        If information similar to the following is displayed, the connection is normal. Otherwise, go to 5.

        slot4:/opt/arbitration-etcd/foss/2.2.4 # cps-etcdCheck
        ============   read etcd configuer   ============
        total etcd servers is 1
        ip is: 172.28.0.2
        ============ 1. checking etcd health ============
        result: healthy etcd server num is 1
        check healthy passed!
        ============2. checking read value ============
        result: read from etcd succ!
        dc001 = ok
        dc002 = ok
        all status = ok	read value passed!
        ====================================
        all tests passed!

  4. Check whether the alarm is cleared.

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

  5. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 46652

Downloads: 33

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