A complete uninstall of NSX removes host VIBs, the NSX Manager, controllers, all VXLAN configuration, logical switches, logical routers, NSX firewall, 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
Removing NSX completely requires two host reboots. The first reboot is required after uninstalling the NSX VIBs. The second reboot is required after removing the host VTEPs and dvPortgroups used for VTEPs.
Do not remove NSX appliances from vCenter directly. Always manage and remove NSX appliances using the Networking and Security tab of the vSphere Web Client.
If you want to remove NSX from individual hosts (instead of from the entire the entire cluster), see Remove a Host from an NSX Prepared Cluster.
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.
- Remove the cluster from its transport zone.
Go to Logical Network Preparation > Transport Zones and disconnect the cluster from the transport zone.
If the cluster is grayed out and you cannot disconnect it from the transport zone, this might be because 1) a host in the cluster is disconnected or is not powered on, or 2) the cluster might contain one or more virtual machines or appliances that are attached to the transport zone. For example, if the host is in a management cluster and has NSX controllers installed on it, first remove or move the controllers.
- Delete the transport zone.
- Unconfigure VXLAN on the cluster.
- Reverse host preparation by uninstalling the NSX VIBs.
Select one of the following methods for uninstalling NSX VIBs. The first two options uninstall NSX VIBs on all hosts in a cluster. The last two options uninstall the VIBs on one host at a time.
In the vCenter Web Client, go to Networking & Security > Installation > Host Preparation, and click Uninstall.
In the vCenter Web Client, go to Administration > vCenter Server Extensions > vSphere ESX Agent Manager. On the Management tab, right-click the VCNS agency and select Delete Agency.
Move the host from the prepared cluster to an unprepared cluster.
On the host, run the following commands:
esxcli software vib remove --vibname=esx-vxlan
esxcli software vib remove --vibname=esx-vsip
- Reboot the hosts.
Removing VIBs from a host requires a host reboot. The required reboot does not happen automatically. When a host needs to be rebooted, the (reboot required) tag appears in the Hosts and Clusters view. For example:
Use one of the following procedures to reboot the hosts.
Reboot the host manually.
Select the cluster and click the Resolve action. This action reboots all hosts in the cluster. If the cluster has DRS enabled, DRS will attempt to reboot the hosts in a controlled fashion that allows the VMs to continue running. If DRS fails for any reason, the Resolve action halts. In this case, you may need to move the VMs manually and then retry the Resolve action or reboot the hosts manually.
- 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.
- 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.