The duration for the NSX-T Data Center upgrade process depends on the number of components you have to upgrade in your infrastructure. It is important to understand the operational state of NSX-T Data Center components during an upgrade, such as when some hosts have been upgraded, or when NSX Edge nodes have not been upgraded.

The upgrade process is as follows:

Hosts > NSX Edge cluster > Management plane.

Check NSX-T Data Center Components

You can perform an automated pre-check to verify whether the NSX-T Data Center components are ready for upgrade. The pre-check process scans for the component activity, version compatibility, component status of the hosts, NSX Edge, and management plane. Resolve any warning notifications to avoid problems during the upgrade.

Before you upgrade, you must verify that your existing NSX-T Data Center 2.3 NSX Manager meets the vCPU and RAM limits in the vSphere Client and make necessary changes.

NSX-T Data Center 2.3 Appliance

Memory

vCPU

NSX-T Data Center 2.4 Appliance

Memory

vCPU

N/A

N/A

N/A

NSX Manager Extra Small VM

8 GB

2

NSX Manager Small VM

8 GB

2

NSX Manager Small VM

16 GB

4

NSX Manager Medium VM

16 GB

4

NSX Manager Medium VM

24 GB

6

NSX Manager Large VM

35 GB

8

NSX Manager Large VM

48 GB

12

The NSX Manager must have 200 GB disk space available for the upgrade.

Hosts Upgrade

During Upgrade

After Upgrade

  • For standalone ESXi hosts or ESXi hosts that are part of a disabled DRS cluster, place hosts in maintenance mode.

    For ESXi hosts that are part of a fully enabled DRS cluster, if the host is not in maintenance mode, the upgrade coordinator requests the host to be put in maintenance mode. The vSphere DRS tool migrates the hosts to another host in the same cluster during the upgrade and places the host in maintenance mode.

  • For ESXi host, for an in-place upgrade you do not need to power off the tenant VMs.

  • For KVM host or bare metal server, for an in-place upgrade you do not need to power off the host. For a maintenance mode upgrade, power off the host.

  • Configuration changes are allowed on NSX Manager.

  • Power on or return the tenant VMs of standalone ESXi hosts or ESXi hosts that are part of a disabled DRS cluster that were powered off before the upgrade.

  • Upgraded hosts are compatible with non-upgraded hosts, NSX Edge cluster and Management plane.

  • New features introduced in the upgrade are not configurable until the NSX Edge cluster and Management plane are upgraded.

  • Run post checks to make sure that the upgraded hosts and NSX-T Data Center do not have any problems.

NSX Edge Cluster Upgrade

During Upgrade

After Upgrade

  • During the NSX Edge upgrade, you might experience the following traffic interruption:

    • North-south datapath is affected if the NSX Edge is part of the datapath.

    • East-west traffic between tier-1 routers using NSX Edge firewall, NAT, or load balancing.

    • Temporary Layer 2 and Layer 3 interruption.

  • Configuration changes are not blocked on NSX Manager but might be delayed.

  • Configuration changes are allowed.

  • Upgraded NSX Edge cluster is compatible with the upgraded hosts and older versions of the Management plane.

  • New features introduced in the upgrade are not configurable until the Management plane is upgraded.

NSX Controller Cluster Upgrade

Note:

In the NSX-T Data Center 2.4 release, the NSX Controller is merged with the NSX Manager during upgrade.

Management Plane Upgrade

Note:

Before you configure your NSX-T Data Center 2.3 NSX Manager for upgrade, you must backup the NSX Manager. See the NSX-T Data Center Administration Guide.

During Upgrade

After Upgrade

  • Configuration changes are not blocked on the Management plane. Do not to make any changes during the Management plane upgrade.

  • API service is available.

  • User interface is unavailable for a short period.

  • Configuration changes are allowed.

  • New features introduced in the upgrade are configurable.