Resolving Server Not Accessible Fault for Virtual Service

Server Not Accessible virtual service fault on Avi Load Balancer UI can indicate non-availability of servers from a specific SE while being available to all other SEs. This topic shows how to resolve this fault in virtual service.

The virtual service fault http-vs-pool: Server rm-cli-2 not accessible from Service Engine(s) se-vwpvi is observed when navigated to the Virtual Services tab of Avi Load Balancer UI.

The error message http-vs-pool: Server rm-cli-2 not accessible from Service Engine(s) se-vwpvi indicates that the specific server rm-cli-2 is not reachable from only one specific Service Engine se-vwpvi, but it is accessible from the other Service Engines. Health monitors do not mark this particular server down because the server is still reachable from other SEs in the Service Engine group. The virtual service, with which this server is communicating has scaled out to the other SEs, and therefore there is no occurrence of any state change for the server or the virtual service.

Server on Avi Load Balancer goes to down state only when none of the SEs can reach the server, and therefore the associated virtual service is also marked down by health monitors.