Upgrade NSX
search cancel

Upgrade NSX

book

Article ID: 402584

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Upgrade prechecks should be run at least 10 days in advance of a scheduled upgrade window to allow time to address any issues found.
  • Ignoring this advice and performing prechecks at the start of an upgrade window may require an upgrade reschedule if blocking issues are found. 
  • See Troubleshooting NSX Precheck Upgrade failures.
  • For precheck errors that cannot be resolved, please open a support case with Broadcom to get further assistance. Note, precheck failures do not qualify as Severity 1.
  • Review the NSX Alarm dashboard on the NSX UI, Home -> Alarms. Action and resolve any open High or Critical Alarms.
  • An NSX upgrade cannot proceed if expired certificates exist in the environment. Perform a Certificate sanity check using Certificate Analyzer, Results and Recovery (CARR) Script to fix certificate related issues in NSX.
  • Read the target version Release Notes and be aware of Known Issues.
  • Confirm the target NSX version is compatible with other products in the environment, see Interoperability.
  • Confirm the NSX upgrade path is supported, see Upgrade Path.
  • Validate NSX backup and restore functionality and ensure the passphrase is known.
  • Ensure ports required for the upgrade are open e.g. 443/8080 see VMware Ports & Protocols.
  • If a bespoke Upgrade runbook is being followed ensure it is aligned with the official Upgrade Guide.
  • For 4.x upgrades, Broadcom recommends upgrading to 4.2.3.1, see Release Notes.
  • Environments using DFW should not upgrade to 4.2.2.0 due to a known PSOD issue, see KB.
  • DFW customers should be aware of this Product Advisory.
  • Upgrades to NSX 9.x are only supported as part of a VCF upgrade. Non-VCF NSX solutions are not supported beyond 4.x.
  • Broadcom strongly recommends a rolling reboot of the NSX Managers prior to starting an upgrade due to a JDK issue impacting 4.2.0.x and 4.2.1.x, see NSX is impacted by JDK-8330017: ForkJoinPool stops executing tasks due to ctl field Release Count (RC) overflow

Note: End of Service
NSX 3.0.x and 3.1.x are end of service as of 7th April 2025.
NSX 3.2.x is end of service as of 2nd October 2025.

Environment

VMware NSX 4.x

Resolution

After completing the steps in the article introduction, the environment is ready for upgrade.

Additional Information

Powered by Wolken Software