Segments in NSX-T Policy UI reflecting less ports than Manager
book
Article ID: 312637
calendar_today
Updated On:
Products
VMware NSX
Issue/Introduction
Symptoms:
You have NSX-T 3.1.x deployed.
Segments in Policy UI view are not reflecting the same number of ports as the Manager UI .i.e. the Policy UI showing less ports / virtual machines connected than there actually is.
Environment
VMware NSX-T Data Center 3.x VMware NSX-T Data Center VMware NSX-T
Cause
The Policy segment port API and the Manager logical switch port API are fetching information from different DB tables, in the case of NSX-T 3.1.x we have two different services, one for MP (Manager) and the other for Policy.
When the VM is attached to the segment/logical switch, it will be detected by Manager and a corresponding port is created on Manager related DB table.
The Policy service will periodically check if there are any new logical ports and create the same in the Policy related DB table.
Due to this architecture, it is possible to encounter a discrepancy between Policy port API and Manager port API.
Resolution
This issue is resolved in NSX-T 3.2, available at VMware Downloads
Note: Any impacted ports will not be updated if an upgrade is performed, but it will prevent the issue from reoccurring for any newly created ports .
Workaround:
Check which are the logical ports missing from the Policy UI by comparing to Manager UI.
Fetch the logical port information using the api below :
GET https://<nsx-mgr-ip>/api/v1/logical-ports/<port-id>
Update the logical port information using the api below with the body as the output of the GET api:
PUT https://<nsx-mgr-ip>/api/v1/logical-ports/<port-id>
Note : AllowOverwrite should be set to true to be able to to run PUT api as below .