Hosts must be rebooted for the installed NSX VIBs to take effect. You must disable hosts in vCloud Director before rebooting them. This prevents vCloud Director from attempting to use the hosts during the reboot.

About this task

Prerequisites

  • Verify that all hosts have a status of Not Ready.

  • Verify that each vSphere cluster has enough capacity to temporarily run without one host.

  • Verify that DRS is enabled and not set to Manual.

Procedure

  1. In vCloud Director, disable the host.
    1. Navigate to Manage & Monitor > Hosts..
    2. Right click on a host, and select Disable Host.
  2. In the vSphere Web Client, navigate to Home > Hosts and Clusters.
  3. Right click on the host you have disabled in vCloud Director and select Enter Maintenance Mode. In the Confirm Maintenance Mode dialog box, Select Move powered-off and suspended virtual machines to other hosts in the cluster and click OK.
  4. If all virtual machines are not moved to other hosts, manually move them.
  5. Once the host is in maintenance mode, right click the host and select Reboot. Enter a reason for the reboot, and click OK.
  6. Once the host is back up, right click the host and select Exit Maintenance Mode.
  7. In vCloud Director, enable the host.
    1. Navigate to Manage & Monitor > Hosts..
    2. Right click on the host, and select Enable Host.
  8. Once the host is enabled in vCloud Director, repeat these steps with the next host.

Results

All virtual wires from your 5.5 infrastructure are renamed to NSX logical switches, and the VXLAN column for the cluster says Enabled.

Enabled

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.

  • esx-vsip

  • esx-vxlan

Note:

In NSX 6.2, 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.

What to do next

If you have deployed an NSX Controller cluster, you can optionally change the control plane mode: Update Transport Zones and Logical Switches in a vCloud Director Environment.

Otherwise, Determine Whether to Upgrade vShield Edge in a vCloud Director Environment