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.


FusionCloud 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).
Health Check Exception

Health Check Exception


A listener fails to conduct the health check.

Possible Causes

Abnormal communication with backend ECSs, incorrect port configuration and health check parameters, or slow backend ECS response may cause the health check exception.


  1. Check whether a backend ECS can assess applications.

    • If the backend ECS can access applications, go to step 2 to eliminate other faults.
    • If the backend ECS cannot access applications, handle faulty backend ECSs.

  2. Log in to the backend ECS and verify that the backend ECS port is working properly.

    Since the network between layer-7 (HTTP) services and the backend ECS is a private network, you need to log in to the backend ECS to verify that the backend ECS port is working properly to ensure normal communication between the load balancer system and backend ECSs.

  3. Check whether the backend ECS has the port enabled.

    The port must be the same as that configured for the listener.

    For layer-4 load balancing, log in to the elb_lvs node and use telnet { Inner EIP plane}:{Backend listening port} for testing. For layer-7 load balancing, the HTTP status code must be 200 or other codes that indicate a normal status. The check methods are as follows:

    • If the backend ECS runs Windows, enter the internal network address in the browser address bar of the backend ECS. For example, you can enter http://{VM fip}:{backend listening port}.
    • If the backend ECS runs Linux, you can run the curl -I command to check whether the status is HTTP/1.1 200 OK. For example, you can run command curl -I {VM fip}:{backend listening port}
    • If no port is enabled, enable the port on the backend ECS.

  4. Check whether the backend ECS has a firewall or other security software.

    The IP address of the load balancer system is easily shielded by this type of software, causing the failure to communicate with backend ECSs.

    You can disable the firewall and perform the health check again. If the backend ECS status becomes normal after the firewall is disabled, the backend ECS private network firewall shields the IP address of the load balancer system.

    The following commands can be used to disable the firewall:

    • Windows: firewall.cpl
    • Linux: /etc/init.d/iptables stop

    If the fault persists, continue to perform follow-up operations.

  5. Check whether health check parameters are correctly configured.

    It is recommended that you set the parameters to their default values. After the health check takes effect, check whether the fault is rectified. If the fault persists, continue to perform follow-up operations.

  6. Use a static page to perform the health check and specify the page URL in the health check configuration if the health check page you use is not the home page of the backend ECS.

    It is recommended that the health check test file is a simple HTML page which is only used to display the returned result, rather than a dynamic scripting language, such as PHP.

  7. Check whether the backend ECS has a heavy load, which causes the ECS to respond slowly.

    • If yes, rectify the backend ECS fault.
    • If no, contact technical support for assistance.

Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22703

Downloads: 37

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