Unable to upgrade NSX local manager
search cancel

Unable to upgrade NSX local manager

book

Article ID: 416125

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • When attempting to upgrade NSX Local Managers in a federated environment from version 3.1.1 to 3.2.3, the upgrade interface in the NSX UI on the local manager nodes fails to load.
  • The upgrade page (System > Upgrade) accessed via the local manager's UI displays no data or a blank state after the upgrade process is initiated.
  • The status monitored from the Global Manager UI correctly shows the local manager's upgrade status as "Not Started".
  • The lack of UI data prevents the administrator from confirming readiness, running pre-checks, and starting the component upgrades (Edge, Hosts, Management Plane).

Environment

NSX-T Data Center (Federated Environment)

Cause

This behavior is expected (but often misunderstood) behavior related to the NSX Upgrade Coordinator service's startup process following the upload of the upgrade bundle.

The Upgrade Coordinator is an internal service that takes time to fully initialize and populate all relevant environment data, including the components ready for upgrade, particularly in a complex Federated setup. If the UI is accessed immediately after selecting the upgrade, the data synchronization is often incomplete.

Resolution

The resolution is to wait for the NSX Upgrade Coordinator service to fully start and populate the data before accessing the upgrade screens. It may also be necessary to identify the orchestrator node (the manager currently handling the install-upgrade service) to ensure the UI is accessed correctly.

  1. Identify the Orchestrator Node: Use the NSX Manager CLI to determine which node in the cluster is running the install-upgrade service, as this node is coordinating the upgrade.

    get service install-upgrade

    The output will specify the IP or FQDN of the manager node that currently has the service enabled (e.g., Enabled on: <Manager_IP>).

  2. Wait for Data Population: After uploading the upgrade bundle, you must wait for the Upgrade Coordinator service to complete its initialization and data collection process, which can take 10 to 15 minutes or sometimes longer, depending on the environment size and complexity.

    • The UI may remain blank or display an incomplete state during this period.
    • Do not attempt to refresh the page constantly or restart services prematurely.

  3. Access UI via Orchestrator: Log in directly to the NSX Manager UI using the IP of the orchestrator node identified in Step 1.

  4. Confirm Readiness: Once sufficient time has passed (10-15 minutes), navigate to System > Upgrade in the local manager UI. The upgrade screen should now be fully populated, allowing you to run pre-checks and proceed with the upgrade steps.

Note: The Global Manager (GM) view shows the status as "Not Started" because the upgrade of the local components has not yet been initiated on the Local Manager (LM) UI. The GM only reflects the overall upgrade status across locations.
Powered by Wolken Software