NSX deleted segments remain as orphaned portgroups in vCenter vDS

Products

• VMware NSX

Issue/Introduction

• Segments that has been removed from NSX still remain as portgroups in vCenter DVS.
• You can see the following messages in /var/log/syslog:

 NSX 3371055 SWITCHING [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Skipping NSX portgroup deletion from vdsId : ## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ## as can not find PGstate info : null in LSState : LogicalSwitchState [id =LogicalSwitchState/########-####-####-####-############, revision = 9149, logicalSwitchName = , stateStatus = FAILED, switchType = DEFAULT, logicalSwitchRevison = -1, portGroupStateRevision = -1, #vdsIdPortGroupStateMap = 0, nextRealizationTime = 0]

• The following messages keeps repeating in /var/log/syslog :

NSX 3371055 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] nsxpg Successfully deleted nsx portgroup for logicalSwitch: LogicalSwitch/########-####-####-####-############ on vds : ## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##

Cause

During the vc full sync operation between NSX Manager and vCnenter, it is identified that there are orphaned portgroups but automated cleanup is not implemented yet. Therefore, the orphaned portgroups are not being removed automatically.

Resolution

This issue is resolved in VMware NSX 4.2.2, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

For workaround, please follow the steps in Remove Stale NSX Segments from vCenter Network Inventory to remove the orphaned portgroups.

Additional Information

Stale NSX Distributed Port Groups (NSX segments) are observed in vCenter