NSX managed VPCs and Subnets appear greyed out or cannot be modified in vCenter
Article ID: 422153
Updated On:
Products
Issue/Introduction
When managing Virtual Private Clouds (VPCs) that were provisioned and deployed through VMware NSX, users observe that the option to create a new subnet under an NSX-managed VPC is greyed out in the vCenter Server (VC) interface
Environment
VMware NSX
VMware Cloud Foundation
Cause
This behavior is working as designed, as it is rooted in the fundamental architecture that dictates NSX (the NSX Manager UI/API) is the exclusive authority (control plane) for all VPCs created through its interface, requiring the vCenter UI to be intentionally restricted from making modifications to these NSX-owned objects, thereby ensuring that all network changes are properly validated by the NSX control plane to maintain VPC network topology stability and integrity.
Resolution
To manage NSX-created VPCs, all modifications, including creation, editing, deletion of subnets, and project movement, must be performed directly using the NSX Manager user interface or the NSX API, as this is the authoritative NSX management plane.
Feedback
