NSX Compute Manager Disconnected During Upgrade Due to Unresponsive VIP Node
Article ID: 444940
Updated On:
Products
Issue/Introduction
VMware NSX upgrade halts because the Compute Manager is disconnected or down. The system reports the exact error: "FQDNs are not configured for nodes." Additionally, the NSX Manager node holding the VIP is unresponsive, preventing UI and API access. Subsequent attempts to resume the upgrade directly in the NSX UI within a VMware Cloud Foundation (VCF) deployment result in skipped steps and explicit system messages indicating the environment is managed by SDDC.
Environment
VMware NSX 4.2.1.3
VMware Cloud Foundation (VCF)
Cause
The primary issue preventing Compute Manager connectivity is caused by the NSX Manager node currently holding the Virtual IP (VIP) becoming unresponsive.
Resolution
Identify the unresponsive NSX Manager node that currently holds the VIP.
Reboot the unresponsive NSX Manager node to force a VIP failover to a healthy manager node in the cluster.
- Monitor the Appliances page of the GUI or run the "get cluster status" in the CLI to confirm the cluster is stable before proceeding.
Verify that the Compute Manager connection is restored and the FQDN error clears.
Abort the out-of-band NSX upgrade attempt from the NSX UI.
Execute the NSX upgrade workflow exclusively through the SDDC Manager interface to maintain Bill of Materials (BOM) compliance and state synchronization.
Additional Information
Feedback
