During the upgrade process, a new Edge virtual appliance is deployed alongside the existing one.

When the new Edge is ready, the old Edge's vNICs are disconnected and the new Edge's vNICs are connected. The new Edge then sends gratuitous ARP (GARP) packets to update the ARP cache of connected switches. When HA is deployed, the upgrade process is performed two times.

This process can temporarily affect packet forwarding. You can minimizing the impact by configuring the Edge to work in ECMP mode.

OSPF adjacencies are withdrawn during upgrade if graceful restart is not enabled.

Verify that NSX Manager has been upgraded.

Verify that the NSX Controller cluster and host preparation have been upgraded before upgrading logical routers.

Verify that there is a local segment ID pool, even if you have no plans to create NSX logical switches.

Verify the hosts have enough resources to deploy additional NSX Edge Services Gateway appliances during the upgrade, particularly if you are upgrading multiple NSX Edge appliances in parallel. See the System Requirements for NSX for the resources required for each NSX Edge size.

For a single NSX Edge instance, there are two NSX Edge appliances of the appropriate size in the poweredOn state during upgrade.

For an NSX Edge instance with high availability, both replacement appliances are deployed before replacing the old appliances. This means there are four NSX Edge appliances of the appropriate size in the poweredOn state during upgrade of a given NSX Edge. Once the NSX Edge instance is upgraded, either of the HA appliances could become active.

Verify that the host clusters listed in the configured location and live location for the NSX Edge appliance are prepared for NSX and that their messaging infrastructure status is GREEN. If the configured location is not available, for example, because the cluster has been removed since the NSX Edge appliance was created, then verify the live location only.

Find the ID of the original configured location (configuredResourcePool > id) and the current live location (resourcePoolId) with the GET https://NSX-Manager-IP-Address/api/4.0/edges/{edgeId}/appliances API request.

Find the host preparation status and the messaging infrastructure status for those clusters with the GET https://NSX-Manager-IP-Address/api/2.0/nwfabric/status?resource={resourceId} API request, where resourceId is the ID of the configured and live location of the NSX Edge appliances found previously.

Look for the status corresponding to the featureId of com.vmware.vshield.vsm.nwfabric.hostPrep in the response body. The status must be GREEN.


Look for the status corresponding to the featureId of com.vmware.vshield.vsm.messagingInfra in the response body. The status must be GREEN.


Understand the operational impact of the NSX Edge upgrade while the upgrade is in progress. See Operational Impacts of NSX Upgrades in the NSX Upgrade Guide.

If you are upgrading from NSX 6.0.x and you have L2 VPN enabled on an NSX Edge you must delete the L2 VPN configuration before you upgrade. Once you have upgraded, you can reconfigure L2 VPN. See "L2 VPN Overview" in the NSX Installation Guide.


In the vSphere Web Client, select Networking & Security > NSX Edges.


For each NSX Edge instance, select Upgrade Version from the Actions () menu.

If the upgrade fails with the error message "Failed to deploy edge appliance," make sure that the host on which the NSX edge appliance is deployed is connected and not in maintenance mode.

After the NSX Edge is upgraded successfully, the Status is Deployed, and the Version column displays the new NSX version.

If an Edge fails to upgrade and does not rollback to the old version, click the Redeploy NSX Edge icon and then retry the upgrade.

After you upgrade your 6.2.4 or earlier NSX Edges to 6.2.5 or later, you must turn off vSphere Virtual Machine Startup for each NSX Edge in a cluster where vSphere HA is enabled and Edges are deployed. To do this, open the vSphere web client and find the ESXi host where NSX Edge virtual machine resides. Click Manage > Settings and under Virtual Machines, select VM Startup/Shutdown, click Edit, and make sure that the virtual machine is in Manual mode (that is, make sure it is not added to the Automatic Startup/Shutdown list).