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-14108 Abnormal LoadBalance Link

ALM-14108 Abnormal LoadBalance Link


This alarm is generated when the LVS node process is abnormal, the process on the backend management node connected to the LVS node is abnormal, or the link between the LVS node and backend management node is abnormal.


Alarm ID

Alarm Severity

Alarm Type



Communications alarm

Alarm Parameters

Table 17-9 Parameters in location information




Specifies the alarm ID.


Specifies the alarm cause ID.


Specifies the service name (IP address of the host where the service resides).

Table 17-10 Parameters in additional information




Specifies the name of the host for which the alarm is generated.


Specifies the VIP of the LVS link.


Specifies the description of the alarm cause.

Impact on the System

  • If a single LVS node or a single Server node is faulty, the management plane can still run properly with reduced availability.
  • If two LVS nodes or two Server nodes are faulty, the management plane cannot run properly.

Possible Causes

  • The LVS node process is faulty.
  • The process on the backend management node connected to the LVS node is faulty.
  • The link between the LVS node and the back-end management node is abnormal.


  1. Check the alarm causes and obtain the information about the node for which the alarm is generated. That is, the cause and faultNode fields in Additional Information on the alarm page.

    The serverName field contains the name and the IP address of the node for which the alarm is generated, for example, dcs-server(

  2. Log in to the LVS node and handle the alarm.

    1. Use PuTTY to separately log in to the lvs1 and lvs2 nodes as the paas user. (Obtain the IP addresses of the lvs1 and lvs2 nodes from the common stack parameters.)

    2. Log in to the lvs1 and lvs2 nodes to check whether the Keepalived process is normal.

      ps -wwf -u paas| grep keepalived | grep -v grep

      • If the process is running properly as shown in the following figure, go to 2.d.

      • If no process is displayed, go to 2.c.
    3. Run the following command to start the Keepalived process:

      /etc/keepalived/keepalived start

      • If the alarm is cleared, no further action is required.
      • If the alarm is not cleared, go to 2.d.
    4. View the /var/log/messages and /opt/dcs/logs/keepalived.log files to locate the cause of the process failure.
      • If the alarm is cleared after the alarm cause is located and the fault is rectified, no further action is required.
      • If the issue persists, contact technical support.

Alarm Clearing

If the process or link becomes normal after the fault is rectified, the system automatically clears the alarm.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34024

Downloads: 31

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