Expected Behavior After Reconnecting Compute Manager to VMware NSX Manager
Article ID: 440966
Updated On:
Products
Issue/Introduction
A registered Compute Manager (vCenter Server) within a VMware NSX environment transitions to a disconnected or unavailable status. This article establishes the definitive operational impact, control-plane synchronization mechanics, and data-plane ramification guidelines when executing a manual reconnection operation via the NSX management interface.
Environment
VMware NSX 4.x
Cause
The explicit root cause of a Compute Manager status disconnection is environment-specific and outside the scope of this document. This knowledge base article functions strictly to define the behavior and safety boundaries of the remediation synchronization process.
Resolution
To re-establish the connection to the Compute Manager and complete inventory reconciliation, execute the following actions:
Log in to the NSX Manager UI with administrative privileges.
Navigate to System > Fabric > Compute Managers.
Locate the disconnected Compute Manager entry, select the ellipsis/options menu, and re-enter the vCenter credentials (e.g. [email protected]), then click Save
Expected Technical Behavior Post-Reconnection:
Inventory Discovery & Delta Resync: NSX Manager automatically initiates an active discovery thread to pull inventory updates from the vCenter Server database. This aligns object mapping models including Clusters, Host Transport Nodes (ESXi), Distributed Virtual Switches (vDS), and Virtual Machine Managed Object IDs (MoIDs).
Data Plane Continuity: Active workload data paths remain decoupled from this management-plane synchronization event. Active Distributed Firewall (DFW) enforcement states, overlay transport paths, edge routing configurations, and active Layer 2/3 traffic processing continue to execute without disruption on the ESXi host layer.
Additional Information
Feedback
