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-9905 Heartbeat Communication Between the Third-party Arbitration Node and the OpenStack OM Interrupted

ALM-9905 Heartbeat Communication Between the Third-party Arbitration Node and the OpenStack OM Interrupted

Description

The system checks whether the third-party arbitration IP address can be pinged from the active or standby FusionSphere OpenStack OM node at a specified interval. This alarm is generated when the heartbeat communication between the third-party arbitration node and the active or standby FusionSphere OpenStack OM node fails.

Attribute

Alarm ID

Alarm Severity

Auto Clear

9905

Major

Yes

Parameters

Name

Meaning

Fault Location Info

Heartbeat Communication Between the Third-party Arbitration Node and the OpenStack OM Interrupted

Additional Info

Heartbeat Communication Between the Third-party Arbitration Node and the OpenStack OM Interrupted

Impact on the System

After the heartbeat communication between the third-party arbitration node and Service OM is interrupted, the following results might occur:

  • If the heartbeat communication between the active and standby Service OM nodes are interrupted, the active node will also work as the standby node, resulting in Service OM service interruption.
  • If the OS of the active Service OM node is faulty, the switchover from the standby node to the active node cannot be triggered, resulting in Service OM service interruption.

Possible Causes

The network is faulty.

Procedure

  1. Use PuTTY to log in to the Service OM node. Ensure that the management floating IP address and user galaxmanager are used to establish the connection.

    Default username: galaxmanager ; default password: IaaS@OS-CLOUD9!

    NOTE:

    Log in to the FusionSphere OpenStack web client. For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode). Choose Cloud Service > FusionSphere OpenStack OM and view VM List to obtain the management floating IP address.

  2. Run the following command and enter the password of user root to switch to user root:

    su - root

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

    TMOUT=0

  4. Run the following command to obtain the names and IP addresses of the active and standby nodes:

    QueryHaState om

    Information similar to the following is displayed:

    LOCAL_HOST=allinonefm0
    LOCAL_STATE=standby
    LOCAL_IP=192.168.61.138
    
    REMOTE_HOST=allinonefm1
    REMOTE_STATE=active
    REMOTE_IP=192.168.61.165

    In this example command output, the current node is allinonefm0 and the physical IP address is 192.168.61.138; and the peer node is allinonefm1 and the physical IP address is 192.168.61.165.

  5. Use PuTTY to log in to the Service OM node.

    Ensure that username galaxmanager and the physical IP address of the node for which this alarm is generated are used to establish the connection.

  6. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password is IaaS@OS-CLOUD8!.

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

    TMOUT=0

  8. Run the following command to obtain the third-party arbitration IP address:

    grep "^haArbitrateIP=" /opt/goku/services/ha/conf/runtime/gmn.cfg | awk -F= '{print $2}'

  9. Ping the third-party arbitration IP address and check whether the third-party arbitration node can be pinged.

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

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

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

  11. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47856

Downloads: 33

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