VMware Networking Community
DineshReddy1205
Contributor
Contributor

NSX-T Upgrade 3.0 to 3.1.3

Planning to upgrade NSX-T 3.0 to 3.1.3

 

For Host Transport Node Upgrade - which mode  is recommend  for Production Environment 

1. Maintenance mode or 2. In-place mode

please suggest which is better  method for production environment and what is the major difference

Labels (1)
Tags (1)
Reply
0 Kudos
1 Reply
sunvmware1
Enthusiast
Enthusiast

Hi,

Before you place your ESXi host in maintenance mode, power off any NSX Edge VMs that may be residing on the host and ensure that the NSX Edge VMs continue to reside on the same host

For ESXi host, for an in-place upgrade you do not need to power off the tenant VMs and placing a host into maintenance mode
before the upgrade

Limitations on In-Place Upgrade
For NSX-T Data Center, in-place upgrade of a host is not supported in the following scenarios:
More than one N-VDS switch is configured on the host.
More than 100 vNICs are configured on the host N-VDS switch.
ENS is configured on the host N-VDS switch.
CPU use for the hostd, nsxa, or the config-agent service is high.
vSAN(with LACP) is configured on the host N-VDS switch.
Layer 7 firewall rules or Identity Firewall rules are enabled.
VMkernel interface is configured on the overlay network.
NSX-T Data Center Upgrade Guide
VMware, Inc. 8
Service Insertion has been configured to redirect north-south traffic or east-west traffic.
A VProbe-based packet capture is in progress.
For ESXi hosts with version 7.0 and later, when upgrading from NSX-T 3.1 or later, in-place
upgrade is not supported in the following scenarios:
More than 1000 vNICs are configured on the host N-VDS or the VDS switch.
CPU use for the hostd, nsxa, or the config-agent service is high.
Layer 7 firewall rules or Identity Firewall rules are enabled.
Service Insertion has been configured to redirect north-south traffic or east-west traffic.
A VProbe-based packet capture is in progress.
The nsx-cfgagent service is not running on the host.

refer step-by-process document

 

Reply
0 Kudos