Error on virtual service : Virtual service needs 2 service engine for High Availability.

Products

• VMware Avi Load Balancer

Issue/Introduction

Fault/Alert observed on the virtual service.

Virtual Service Fault

Virtual Service (vip_id 1) needs 2 Services Engines for High Availability. Currently only 1 Service Engine(s) available. Reason:Reached configured maximum limit of 1 Service Engines in Service Engine group

 

Virtual Service Fault

Virtual Service (vip_id 1) needs 4 Services Engines for High Availability. Currently only 2 Service Engine(s) available. Reason:Insufficient licensable resources available to create Service

Cause

1) The above virtual service fault can be observed when the virtual service scale out is set to greater than 1 and the desired number of service engine is not available, which can happen due to multiple reasons eg No license available to create service engine, max number of service engine reached in SE group setting etc.

2) In some scenario it is observed even if the min_scale_per_vs is set to 1, we observe this error.

3) This can happen if the customer has manually scaled out the VS or changed the min_scale_per_vs to greater than 1, disable/enable the virtual service and then reverted the changes on the SE group settings.

4) Reverting scale out changes does not scale in the virtual services from the existing service engines.

Resolution

1) In order to place the virtual service on the desired number of service engine we need to set the max_scale_per_vs to same as min_scale_per_vs.

2) In the above virtual service fault if we set the min_scale_per_vs and min_scale_per_vs to 1 and disable/enable the virtual service, the fault will disappear.

3) This will place the virtual service on 1 service engine.

4) Once the virtual service fault has disappeared, we can change the settings to default settings or required settings.

eg: