Name mismatch between vCenter port groups and NSX Logical Switches/Segments

Products

• VMware NSX

Issue/Introduction

• You are running NSX 4.2.0 or higher.
  Note: Prior to NSX 4.2.0, there might be stale NSX port groups on vCenter. For more information, please see: Stale NSX port groups observed on vCenter, though the Segments have been deleted from NSX
• The vCenter displays a port group name created by NSX, but you are unable to find it on NSX Manager (under Policy) "No matching records found".
• From Networking, Under Manager, Connectivity -> Logical Switches, the port group is also not found:
  
• The same behavior can occur in an opposite scenario, where there is a logical switch (LS) with a specific name, but you are unable to find it from vCenter.

Environment

VMware NSX 4.2.0 or higher

Cause

There may be a display name mismatch between NSX Manager and vCenter, where the name of the logical switch or segment is different from what is displayed on vCenter (or vice-versa), leading you to not find the port group.

Resolution

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Workaround:

1. Ensure the Compute Manager is connected/up.
2. Reboot the vCenter Server.
   Note: When the vCenter server is rebooted and the connection is restored, NSX triggers a full sync to vCenter, in which NSX retrieves all NSX DVPGs from vCenter, compares them to the logical switch/segment/subnet, and then makes the corresponding create/update/delete.
3. If after rebooting vCenter, you are still unable to find the logical switch/segment/subnet, please open a support request.

Additional Information

If you are contacting Broadcom support about this issue, please provide the following:

• NSX Manager support bundles.
• vCenter log bundle.
• vCenter output for the command:
  /opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres
select * from VPX_DVPORTGROUP;
• NSX Manager Corfu tables (SSH to one NSX Manager as root) and provide the following outputs:
  corfu_tool_runner.py -n nsx -t LogicalSwitchState -o showTable
corfu_tool_runner.py -n nsx -t LogicalSwitch -o showTable
corfu_tool_runner.py -n nsx -t Segment -o showTable
corfu_tool_runner.py -n nsx -t HostTransportNode -o showTable
corfu_tool_runner.py -n nsx -t DistributedVirtualSwitchMsg -o showTable
  
  

Handling Log Bundles for offline review with Broadcom support:

• Collect Support Bundles for Troubleshooting VMware NSX
• Uploading files to cases on the Broadcom Support Portal
• Creating and managing Broadcom support cases