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 Troubleshooting Guide 02

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).
Failure to Add or Remove a Backend Cloud Server

Failure to Add or Remove a Backend Cloud Server

Symptom

Users cannot add or delete a backend Cloud Server on the listener page.

Possible Causes

A Nginx process exception occurs in the LVS or Nginx cluster, the communication is abnormal, fault occurs or the traffic control function is configured in the configuration file.

Troubleshooting Process

Locate the fault based on the returned error code and error information.

  • If Issue configuration file failed is displayed, a Nginx process exception occurred in the LVS or Nginx cluster, or the communication between elb_api nodes and elb_lvs or elb_nginx nodes is abnormal.

    Rectify the LVS and Nginx VM fault by following instructions in section LVS Cluster Fault and elb_nginx Node Fault. If the issue persists, restore the communication between elb_api nodes and elb_lvs or elb_nginx nodes by following instructions in section Failure to Add or Remove a Backend Cloud Server.

  • If Uploading conf is overload is displayed and the error code is 503, traffic control is issued.

    Lower the frequency of adding or deleting a backend Cloud Server.

Procedure

  1. Use PuTTY to log in to the netcluster_elb_api_vm_1_01 node.

    The default username is elb and the default password is cnp200@HW.

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

    sudo su - root

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

    TMOUT=0

  4. Check whether the communication between elb_api nodes and elb_lvs or elb_nginx nodes is normal.

    Assume that the management plane IP address of an elb_lvs or elb_nginx node is 10.1.1.45, run the following command:

    ping 10.1.1.45

    If the IP address can be pinged, the communication is normal.

    • If yes, go to 5.
    • If no, contact technical support for assistance.

  5. Use PuTTY to log in to the elb_lvs node or elb_nginx node on the data plane using the IP address.

    The default username is elb and the default password is cnp200@HW.

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

    sudo su - root

  7. Run the following command to check whether the elb_lvs or elb_nginx node has the firewall enabled:

    iptables -L

    • If yes, the following information is displayed. Go to 8.

    • If no, ELB is still abnormal. Contact technical support for assistance.

  8. Run the following commands to clear related settings and save the firewall configuration to disable the firewall.

    iptables-F

    service iptables save

  9. Log in to the netcluster_elb_api_vm_1_02 node and repeat 1 to 8.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1801

Downloads: 12

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