NSX VIBs are specific to the version of ESXi that is installed on the host. If you upgrade ESXi, you must install new NSX VIBs appropriate for the new ESXi version.
Before you begin
Check the VMware Product Interoperability Matrix to verify which versions of vSphere and ESXi are compatible with your NSX installation. See http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Read the appropriate version of the vSphere documentation for detailed instructions on upgrading vSphere, including the vSphere Upgrade Guide and the Installing and Administering VMware vSphere Update Manager Guide.
Verify Platform Services Controller and vCenter Server systems are upgraded to the new vSphere version.
Make sure the fully qualified domain names (FQDNs) of all of your hosts can be resolved.
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, navigate to Enable rule.. Edit the rule and deselect
About this task
You must ensure the host stays in maintenance mode throughout the upgrade process to avoid DRS or vMotion moving VMs to the host before the upgrade is complete.
- Put the host into maintenance mode.
If the cluster has DRS enabled, DRS will attempt to move VMs to other hosts. If DRS fails for any reason, you may need to move the VMs manually and then put the host into maintenance mode.
- Upgrade ESXi on the host.
Reboot the host after the ESXi upgrade is complete.
- If the host has status Not connected after the reboot, connect the host. Right click the host and select .
- Navigate to .
- Select the host on which you upgraded ESXi. The Installation Status displays Not Ready.
complete the NSX VIB update.
NSX VIBs are updated on the host, and the host is rebooted.
- Once the host has completed the reboot, exit from maintenance mode.
You can verify that the VIBs are updated by connecting to the host command line and issuing the esxcli software vib list | grep esx-v command. The first part of the VIB version displays the version of ESXi for the VIB. For example, before upgrade from ESXi 5.5 to ESXi 6.0.
[root@host-1:~] esxcli software vib list | grep esx-v esx-vsip 5.5.0-0.0.XXXXXXX VMware VMwareCertified 2017-01-23 esx-vxlan 5.5.0-0.0.XXXXXXX VMware VMwareCertified 2017-01-23
After upgrade to ESXi 6.0:
[root@host-1:~] esxcli software vib list | grep esx-v esx-vsip 6.0.0-0.0.XXXXXXX VMware VMwareCertified 2017-01-23 esx-vxlan 6.0.0-0.0.XXXXXXX VMware VMwareCertified 2017-01-23