Troubleshooting NSX Host Upgrade Failures
Article ID: 378906
Updated On:
Products
VMware NSX
Issue/Introduction
- ESXi Hosts are upgraded as part of Upgrade Unit Groups.
- By default hosts in the same vSphere clusters map to the same Upgrade Unit Group.
- In non-VSAN clusters, new Upgrade Unit Groups can be created to control how hosts are upgraded.
- The maximum limit for a simultaneous upgrade is five host upgrade unit groups and ten hosts per group.
- Host upgrade can be performed using maintenance mode or in-place. In-place is faster but can have a small impact on datapath traffic.
Environment
VMware NSX
VMware NSX-T
Resolution
Host VIB status via ESX cli:
esxcli software vib list | egrep "nsx|vsipfwlib"esxcli software profile get | less
Host logs:
- VIB install logs on Non VLCM cluster: /var/run/log/esxupadate.log
- VIB install logs on VLCM cluster: /var/run/log/lifecycle.log
- ESXi main kernel log: /var/run/log/vmkernel.log
Known Issues:
- ESXi hosts reboot during an NSX host upgrade
- NSX Upgrade State Shows Previous Upgrade Still in Progress, During Host Upgrade Phase.
- Host Upgrade pauses with "Cannot continue upgrade. Upgrade coordinator backend is busy in sync operation. Please try again after some time"
- Recovering from an NSX-T In-place Upgrade Failure
- After NSX 4.x install/upgrade, ESXi Hosts are in a "Not Responding" state in vCenter and VMs cannot connect to their network
- ESXi host lost management connectivity during maintenance mode VMware NSX upgrade
- ESXi hosts in Failed state following upgrade to NSX 3.2.2 or 4.0.1.1
- During NSX-T upgrade, ESXi host may experience a PSOD
- ESXi Transport Node upgrade fails in NSX-T
- Upgrading VMware NSX ESXi transport node(s) fails with "out of memory" error
- SDDC Manager shows NSX upgrade on vLCM domains as successful after failed retry
Additional Information
Feedback
Yes
No
Powered by
