You can upgrade VMware NSX-T Data Center to 3.2.2 using the upgrade coordinator. The upgrade coordinator resides in the NSX Manager and orchestrates the upgrade process of ESXi hosts, NSX-T Data Center Edge cluster, and NSX-T Data Center management plane. The upgrade process involves upgrading the components in the following sequence: VMware NSX-T Data Center Edges, ESXi Hosts, and NSX-T Data Center management plane.
Perform the Pre-Upgrade Tasks.
Review the NSX-T Data Center Upgrade Checklist to track your work on the NSX-T Data Center upgrade process.
Prepare your infrastructure for the NSX-T Data Center upgrade.
Back up the NSX Manager of version 184.108.40.206 or 3.2.1.
NSX-T Data Center 3.2.2 supports skip-level upgrades from the following versions:
NSX-T Data Center 220.127.116.11 as part of Telco Cloud Platform 2.2
NSX-T Data Center 3.2.1 as part of Telco Cloud Platform 2.5
- ♦Upgrade NSX-T Data Center to 3.2.1.
- Upgrade the Upgrade Coordinator component.
- Upgrade NSX edges.
- Upgrade ESXi hosts.
In case of SR-IOV enabled worker nodes or if the worker nodes cannot be migrated to another ESXi host, manually power OFF the worker node VMs to move the host into the maintenance mode.
Drain the pods from the worker nodes:
kubectl drain <worker_node_name> --ignore-daemonsets --delete-local-data --force
Power OFF the worker nodes.
- Upgrade NSX manager.
What to do next
Perform the post-upgrade tasks to verify that the NSX-T Data Center upgrade is successful.
After the NSX-T Data Center upgrade is successful, verify that the clusters prepared for NSX-T Data Center are in the Success state:
Log in to NSX-T manager using Virtual IP (VIP) address.
Navigate to System > Fabric > Node > Host Transport Nodes.
Verify that all the clusters prepared for NSX-T Data Center are in Success state without any error.
If there is an error on the ESXi hosts in the cluster, reconfigure the transport node by selecting the CONFIGURE NSX option on the cluster using the existing transport node profile. If there is any other upgrade issue, see Troubleshooting Upgrade Failures.