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


To have a better experience, please upgrade your IE browser.


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-16016 ELB API Node Split-brain

ALM-16016 ELB API Node Split-brain


This alarm is generated when the arbitration center cannot detect two master management nodes.


Alarm ID

Alarm Severity

Alarm Type



Communications alarm

Parameters (for Alarm Locating)

Table 17-15 Parameters





Namespace to which the ELB service belongs.



Name of the service that generates the alarm.



Name of the microservice that generates the alarm.



List of management node IP addresses.,


IP address of the node triggering the alarm.

Impact on the System


Possible Causes

The keepalived heartbeat between two ELB management nodes is interrupted, but the arbitration center cannot detect heartbeat interruption.


Perform the following steps:

  1. Log in to the FusionStage tenant management zone console.

    The console address is https://Access address of the console home page, for example,

  2. Choose Console > Application > FusionStage from the main menu.
  3. Choose Application Operations> Application Operations
  4. Choose Alarm Center > Alarm List to query the following alarm information:

    Additional information: Split brain occurs on the ELB API node, which may result in the API registration unavailability.

  5. Use PuTTY to log in to the two ELB management nodes respectively.

    The default username is paas. The default password is QAZ2wsx@123!.

  6. Run the following command and enter the password QAZ2wsx@123! of the root user to switch to the root user:

    su - root

  7. Check the statuses of the two management nodes.

    Run the following command:

    cat /etc/keepalived/status

    Check whether both the management nodes are in the master state.

    • If they are, go to 8.
    • If the status of one management node is master and that of the other is backup, the network is restored and the alarm is cleared.

  8. Run the PING command to check whether the two nodes are connected.

    • If the network is disconnected, fix the network first.
    • If the network is connected but the problem persists, contact technical support.

Alarm Clearance

After the fault is rectified, the system automatically clears the alarm.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 33681

Downloads: 31

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