After upgrading NSX Manager and NSX Controllers, you can update the appropriate clusters in your environment.

About this task

Upgrading the host clusters upgrades the NSX VIBs.

If you are upgrading from NSX 6.2.x or earlier, or if you are upgrading from NSX 6.3.0 or later with ESXi 5.5, hosts must be rebooted to complete the upgrade.

  • If the cluster has DRS enabled, when you click Resolve all DRS attempts to reboot the hosts in a controlled fashion that allows the VMs to continue running. VMs are moved to other hosts in the cluster and the hosts enter maintenance mode and are rebooted.

  • If the cluster does not have DRS enabled, you must power off or vMotion the VMs manually before beginning the upgrade. When you click Resolve all the hosts enter maintenance mode and are rebooted.

If you are upgrading from NSX 6.3.0 or later with ESXi 6.0 or later, the hosts must enter maintenance mode to complete the upgrade. Rebooting is not required.

  • If the cluster has DRS enabled, when you click Resolve all DRS attempts to put the hosts into maintenance mode in a controlled fashion that allows the VMs to continue running. VMs are moved to other hosts in the cluster and the hosts enter maintenance mode.

  • If the cluster does not have DRS enabled, you must power off or vMotion the VMs manually before beginning the upgrade. You must manually put the hosts into maintenance mode to complete the upgrade.

Prerequisites

  • 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.

  • 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 Hosts and Clusters > Cluster > Manage > Settings > VM/Host Rules. Edit the rule and deselect Enable rule.

  • Log into one of the hosts in the cluster and run the esxcli software vib list command.

    The VIBs present will depend on the ESXi and NSX versions, and therefore might change as part of the upgrade. Note the current version of the installed VIBs:

    ESXi version

    NSX version

    VIBs installed

    5.5

    6.1.x, 6.2.x or 6.3.x

    • esx-vsip

    • esx-vxlan

    6.0 or later

    6.3.2 or earlier

    • esx-vsip

    • esx-vxlan

    6.0 or later

    6.3.3 or later

    • esx-nsxv

    Note:

    Some versions of NSX have additional VIBs which will be removed during the upgrade.

    • If you are upgrading from a version of NSX earlier than NSX 6.2, prepared hosts have an additional VIB, esx-dvfilter-switch-security.

    • If you are upgrading from NSX 6.2.x where the version is NSX 6.2.4 or later, prepared hosts have an additional VIB, esx-vdpi.

Procedure

  1. In the vSphere Web Client, navigate to Home > Networking & Security > Installation, select the Host Preparation tab.
  2. For each cluster that you want to upgrade, click Upgrade available.

    The Installation Status displays Installing.

  3. The cluster Installation Status displays Not Ready. Click Not Ready to display more information. Click Resolve all to attempt to complete the VIB installation.

    The hosts are put in maintenance mode, and rebooted if required, to complete the upgrade.

    The Installation Status column displays Installing. Once the upgrade is complete the Installation Status column displays a green check mark and the upgraded NSX version.

  4. If the Resolve action fails when DRS is enabled, the hosts might 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 again. Click Not Ready to display more information. 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.

    The Installation Status column displays Installing. Once the upgrade is complete the Installation Status column displays a green check mark and the upgraded NSX version.

  5. If the Resolve action fails when DRS is disabled and you are upgrading from NSX 6.3.0 or later with ESXi 6.0 or later, you must manually put the hosts into maintenance mode to complete the upgrade.
    1. Place the evacuated hosts in maintenance mode.
    2. Navigate to Networking & Security > Installation > Host Preparation.

      The upgrade automatically starts when the hosts enter maintenance mode. The Installation Status column displays Installing. If you do not see the Installing status, refresh the page.

      Once the upgrade is complete the Installation Status column displays a green check mark and the upgraded NSX version.

    3. Remove the hosts from maintenance mode.

Results

To confirm the host update, log into one of the hosts in the cluster and run the esxcli software vib list command. Make sure that the appropriate VIBs have been updated to the expected version.

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.

See Host Preparation in the NSX Troubleshooting Guide for more troubleshooting steps.

What to do next

Upgrade NSX Edge