Troubleshooting NSX Edge Upgrade Failures
Article ID: 379032
Updated On:
Products
VMware NSX
Issue/Introduction
- Edges are upgraded as part of Edge Upgrade Unit Groups
- There is a 1:1 mapping of Edge clusters to Edge Upgrade Unit Groups
- New Edge Upgrade Unit Groups cannot be created and Edges cannot be moved from one Upgrade Unit to another
- Edge upgrade is expected to result in some datapath and service disruption as any active Gateways will need to failover to another Edge in the cluster.
Environment
VMware NSX
VMware NSX-T
Resolution
Admin cli to check upgrade status:
get upgrade progress-status
Logs:
- On the Edge /var/log/syslog can be reviewed for errors
- On the Manager /var/log/upgrade-coordinator/upgrade-coordinator.log is the main upgrade log
- To RCA an Edge upgrade failure logs from both Manager and Edge should be collected. If unavailable through the UI, Edge logs can also be collected from admin cli using
get support-bundle file <filename.tgz>
Known issues:
- NSX Edge Upgrade Failed
- VMware NSX Upgrade fails in NSX Edges Upgrade step
- VMware NSX Edge upgrade fails on power on step post-upgrade due to the edge vnics getting disconnected on Edge virtual machine.
- NSX Edge upgrade fails as appliance configuration is invalid
- Edge upgrade or new deployment is in a Failed state
- Prepare NSX Edge Upgrade Bundle Failed due to certificate error
- NSX-T Edge Pre-check Errors and Stuck Upgrade at switch_os Step on Edge Nodes
- NSX edge upgrade is failing with error 'Download and verify bundle failed with msg: Closing connection 0' in UI.
- Edge Upgrade/redeployment failure due to resource pool path issue
- NSX Edge upgrade or new deployment fails on 4.1.1 when the upgrade or installation is attempted on older CPUs
- VMware NSX Edge upgrades fail due to mount exception: <mount point> already mounted or mount point busy
- Upgrading or deploying an VMware NSX Edge node or Manager appliance from NSX manager UI fails. Errors related to "curl_wrapper"
- NSX-T Edge Node upgrade can not be started with error "The value VERSION_UNKNOWN for version format is invalid"
- NSX-T Edge Node Upgrade from 3.1.3 to 3.2 fails with "NSX Edge configuration has failed. 1G hugepage support required"
- NSX Edge node upgrade fails with an error
- False alert of Edge upgrade failed with error: Unexpected error while upgrading upgrade unit:null
- After NSX Edge VM Upgrade to 4.2 The service dispatcher and dataplane continually changed from STARTED to STOPPED when edge VM is on a host with Intel Ivy Bridge or Sandy Bridge CPUs
- Edge node deployment or redeployment fails during VMware NSX-T data center upgrade: 'Host did not have any virtual network defined'
- NSX Edge fails to connect to the broker after upgrade
- In NSX-T 3.2.4, if there are more than 100 EdgeTransportNodes in the system while upgrading NSX Manager, the upgrade can fail
Additional Information
Feedback
Yes
No
Powered by
