A complete uninstall of NSX removes host VIBs, the NSX Manager, controllers, all VXLAN configuration, logical switches, logical routers, NSX firewall, Guest Introspection, and the vCenter NSX plug in. Make sure to follow the steps for all hosts in the cluster. VMware recommends that you uninstall the network virtualization components from a cluster before removing the NSX plug-in from vCenter Server.
About this task
Do not remove appliances that were created by NSX from vCenter directly, for example, NSX Edge appliances. Always manage and remove these appliances using the Networking and Security tab of the vSphere Web Client.
You must have been assigned the Enterprise Administrator or NSX Administrator role.
Remove any registered partner solutions, as well as endpoint services before reversing host preparation so that service VMs in the cluster are removed gracefully.
Delete all NSX Edges. See Uninstall an NSX Edge Services Gateway or a Distributed Logical Router.
Detach virtual machines in the transport zone from the logical switches, and delete the logical switches. See Uninstall a Logical Switch.
Uninstall NSX from host clusters. See Uninstall NSX from Host Clusters.
- Delete the transport zone.
- Delete the NSX Manager appliance and all NSX controller appliance VMs from the disk.
- Remove any leftover VTEP vmkernel interfaces.
Generally, the VTEP vmkernel interfaces are already deleted as a result of earlier uninstall operations.
- Remove any leftover dvPortgroups used for VTEPs.
Generally, the dvPortgroups used for VTEPs are already deleted as a result of earlier uninstall operations.
- If you removed VTEP vmkernel interfaces or dvPortgroups, reboot the hosts.
- For the vCenter on which you want to remove the NSX Manager plug-in, log in to the managed object browser at https://your_vc_server/mob.
- Click Content.
- Click ExtensionManager.
- Click UnregisterExtension.
- Enter the string com.vmware.vShieldManager and click on Invoke Method.
- If you are running the vSphere 6 vCenter Appliance, launch the console and enable the BASH shell under Troubleshooting Mode Options.
Another way to enable the BASH shell is to log in as root and run the shell.set --enabled true command.
- Delete the vSphere Web Client directories for NSX and then restart the Web Client service.
The vSphere Web Client directories for NSX are called com.vmware.vShieldManager.** and are located as follows:
vCenter Server 5.x
Windows 2003 – %ALLUSERSPROFILE%\Application Data\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\
Windows 2008/2012 – %ALLUSERSPROFILE%\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\
VMware vCenter Server Appliance – /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
vCenter Server 6.0.x
Windows 2008/2012 – C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\
VMware vCenter Server Appliance – /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
For vCenter Server Appliance, run the service vsphere-client restart command in the appliance shell.
For Windows-based vCenter, run services.msc, right-click vSphere Web Client, and click Start.
The NSX Manager plug-in is removed from vCenter. To confirm, log out of vCenter and log back in.
The NSX Manager plug-in Networking & Security icon no longer appears on the Home screen in the vCenter Web Client.
Go to Administration > Client Plug-Ins and verify that the list of plug-ins does not include NSX User Interface plugin.