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.


FusionAccess-vLB-vLB service malfunction because of the port limitation of vLB and WI.

Publication Date:  2017-08-04 Views:  107 Downloads:  0
Issue Description

vLB service malfunction while vAG service on the same server is normal. Execute “service HAProxy start” on the vLB server and then check the service status, vLB service status is “stopped”.

Handling Process

The vLB start mechanism: check WI status before start, if all WIs’ service status are abnormal, vLB will stop its service.
1. Check vLB server memory and CPU, make sure it meets the suggested standard, and deploy separately from WI server.
2. Check the vLB run log under /var/log/haproxy, find the WI status is down.
3. If failed to login to all the WI, please fix the WI sever issue first. If succeed to login any of the WI, then go to step 4.
4. Login the vLB through putty, run the command of ssh -v WI ip -p 80/443 to confirm that the 443 and 80 port is allowed between vLB and WI in the firewall. For example, ssh -v -p 80, let the customer reconfigure the firewall if it is not accessible.


Checkt he firewall configuration and reconfigure the firewall to allow 443/80 port of the WI server.


If firewall exists on the platform network, confirm that all need ports are allowed on the firewall.