Recently, I had this come up where I had to remove the vCloud Availability 3.0 (vCAv) plugin from my lab vCenter. Today, there is not a way to do this through the vCAv on-premises appliance UI – it must be done directly on the vCenter. Therefore, after speaking with a colleague (Bill Leck), I received the steps on removing it from the vCenter instance.
Here are the high-level steps:
- SSH to the vCenter
- Remove packages
- Remove endpoints from the lookup service
- Restart vCenter UI services
This is a very easy and straight forward process. I’ve documented the step by step directions below.
First, I see my vCloud Availability plugin on vCenter instance –
Let’s SSH to my vCenter…
UI packages are under the /etc/vmware/vsphere-ui/cm-service-packages folder. We need to remove the specific vCAv packages from this folder. Below is the two packages to remove:
rm -rf /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.h4.vsphere.client-3.0.0 /etc/vmware/vsphere-ui/cm-service-packages/com.vmware.cis.vsphereclient.plugin/com.vmware.h4.ngc.client-3.0.0
Next, we need to remove the vCAv entity from the lookupservice SDK. First, we need to get the ID of the vCAV endpoint, and then unregister it. Below are the two commands we will utilize. Note the space between the URL and the 2>/dev/null.
/usr/lib/vmidentity/tools/scripts/lstool.py list --ep-type com.vmware.vcav.endpoint --url http://localhost:7080/lookupservice/sdk 2>/dev/null
/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --user ‘<SSO User>’ --password ‘<SSO User password>’ --id <ID of vCAv service identified by the above command> 2>/dev/null
In my environment, we can see the following when I run the first command:
I’ve also highlighted the service ID as we will need that for the next command.
Now, inputting in the second command and copying the service ID, it successfully removes the endpoint –
Last of all, when attempting to hit the lookup service for it, nothing is listed for ‘vcav’ anymore –
Last of all, we will want to restart the vSphere UI services. 6.5 and 6.7 operate a little differently, so the syntax is listed below.
vSphere 6.5 - execute “service-control --stop vsphere-ui”, followed by “service-control --start vsphere-ui”
vSphere 6.7 - execute “vmon-cli -r vsphere-ui”
I am running 6.5, so let me go ahead and stop and start the UI services.
Logging into my vCenter instance, the vCAv plugin is now removed from the Menu and shortcuts window.
Very easy process on removal. If you need to re-install the plugin, please do so through the vCAv on-premises appliance registration. Big thanks to Bill Leck for his guidance.