GSLB DNS VS down with error "Vip oper state not available from ServiceEngine.Vip is not active on ServiceEngine"

Products

• VMware Avi Load Balancer

Issue/Introduction

GSLB DNS VS gets stuck in placement and is not coming up. The VS status on the UI shows "Vip oper state not available from ServiceEngine.Vip is not active on ServiceEngine"

Cause

- The issue happens because of stale vsgs objects in the system.
- Each GSLB service is mapped to a DNS VS using a vsgs object.
- As part of the DNS VS placement, the SE first downloads all the GSLB services mapped to that VS through these vsgs objects.
- When there are stale entries, the SE getting the DNS VS, tries to download the config for a GSLB service that does not exist.
- Because of this, the DNS VS download on the SE fails and the VS placement gets stuck.

Resolution

- To fix this, we will need to delete the stale vsgs entries.
- Please follow the steps below:
-- Create a dummy DNS VS on the controller.
-- Note down the uuids of the DNS VS and dummy DNS VS. You could use the command below for each of the VSs:

[admin:<cntlr-ip>]: > show virtualservice <dns-vs-name> | grep uuid
| uuid                               | virtualservice-xxxxxxxxxxxx | 
[admin:<cntlr-ip>]: > 

-- Replace the DNS VS from the GSLB site config on the GSLB leader with the dummy DNS VS.
-- From controller CLI on the site where the placement is stuck, verify that all the vsgs entries have been replaced with the new dummy DNS VS uuid. You could use the command below to list the vsgs mappings:

[admin:<cntlr-ip>]: > show vsgs
+------------------------------------------------------------------------------------------------------+-------------------------------------------+
| name                                                                                                 | uuid                                      |
+------------------------------------------------------------------------------------------------------+-------------------------------------------+
| virtualservice-xxxxxxxxxxx:gslbservice-xxxxxxxxxxx | vsgs-xxxxxxxxxxx |
+------------------------------------------------------------------------------------------------------+-------------------------------------------+

-- Once we have confirmed that all old DNS VS UUID is NOT present in the vsgs mapping objects, we can edit the GSLB site config from the GSLB leader to re-add the original DNS VS back.
-- Post this, the DNS should be placed successfully.
-- Also delete the dummy DNS VS that was created.