After upgrading NSX Manager and NSX Controllers to version 6.2.x, you can update the appropriate clusters in your environment. During this process, each host in the cluster receives a software update and is then rebooted.
Before you begin
Make sure the fully qualified domain names (FQDNs) of all of your hosts can be resolved.
Log into one of the hosts in the cluster and run the esxcli software vib list command. Note the current version of the following VIBs:
esx-dvfilter-switch-security - if you are upgrading a version of NSX prior to 6.2
Upgrade NSX Manager and the NSX Controller cluster.
Make sure that you understand the operational impact of a host cluster upgrade while the upgrade is in progress. See Operational Impacts of NSX Upgrades.
If DRS is disabled, power off or vMotion the VMs manually before beginning the upgrade.
If DRS is enabled, the running VMs are moved automatically during the host cluster upgrade. Before beginning the upgrade, make sure that DRS can work in your environment.
Make sure that DRS is enabled on the host clusters.
Make sure that vMotion functions correctly.
Check the host connection state with vCenter.
Check that you have a minimum three ESXi hosts in each host cluster. During an NSX upgrade, a host cluster with only one or two hosts is more likely to have issues with DRS admission control. For a successful NSX upgrade, VMware recommends that each host cluster have at least three hosts. If a cluster contains fewer than three hosts, the recommendation is to manually evacuate the hosts.
In a small cluster with only two or three hosts, if you have created anti-affinity rules stating that certain VMs must reside on separate hosts, these rules might prevent DRS from moving the VMs during the upgrade. Either add additional hosts to the cluster or disable the anti-affinity rules during the upgrade and reenable them after the upgrade is complete. To disable an anti-affinity rule, uncheck Enable rule.
About this task
When you are upgrading stateful ESXi along with NSX, there is upgrade order that needs to be followed:
Upgrade NSX Manager.
Upgrade NSX Controller cluster.
Manually place the ESXi hosts into maintenance mode.
Update NSX VIBs (this procedure).
Reboot the hosts (to get the 5.5 VIBs).
Upgrade ESXi hosts to version 6.0.
Reboot the ESXi hosts again (to get 6.0 VIBs).
Manually remove the ESXi hosts from maintenance mode.
Keep the hosts in maintenance mode during this process. Do not allow them to come out of maintenance mode too early.
- In the vSphere Web Client, navigate to Home > Networking & Security > Installation, select the Host Preparation tab.
- For each cluster that you want to upgrade, click Upgrade available.
The host upgrade initiates a host scan. The old VIBs are removed (though they are not completely deleted until after the reboot). New VIBs are installed on the altboot partition. To view the new VIBs on a host that has not yet rebooted, you can run the esxcli software vib list --rebooting-image | grep esx command.
If the cluster has DRS enabled, DRS attempts to reboot the hosts in a controlled fashion that allows the VMs to continue running. vMotion moves the running VMs to other hosts in the cluster and places the host into maintenance mode. If hosts require manual intervention to enter maintenance mode (for example, due to HA requirements or DRS rules), the upgrade process stops and the cluster Installation Status displays Not Ready. Click to display the errors.
After manually evacuating the hosts, select the cluster and click the Resolve action. The Resolve action attempts to complete the upgrade and reboot all hosts in the cluster. If the host reboot fails for any reason, the Resolve action halts. Check the hosts in the Hosts and Clusters view, make sure the hosts are powered on, connected, and contain no running VMs. Then retry the Resolve action.
When the cluster is updated, the Installation Status column displays the software version that you have updated to.
To confirm the host update, log into one of the hosts in the cluster and run the esxcli software vib list | grep esx command. Make sure that the following VIBs have been updated to the expected version.
In NSX 6.2 and later, the esx-dvfilter-switch-security VIB is included within the esx-vxlan VIB.
If a host fails to upgrade, perform the following troubleshooting steps:
Check the ESX Agent Manager on vCenter, and look for alerts and errors.
Log in to the host, check the /var/log/esxupdate.log log file, and look for recent alerts and errors.
Ensure that DNS and NTP are configured on the host.