NSX Federation Error received when attempting to delete a segment from the Global Manager: "The API deleteInfraSegmentMonitoringBinding is invalid on the global manager. (Error code: 500518)"

Products

• VMware NSX

Issue/Introduction

• Deleting a segment in the Global Manager fails with the error "The API deleteInfraSegmentMonitoringBinding is invalid on the global manager. (Error code: 500518)"
• There are no port mirroring profiles configured for the segment.
• In the global manager logfile /var/log/syslog you may see entries similar to the following

2025-01-23T11:45:11.862Z ######.#####.com NSX 5056 POLICY [nsx@6876 comp="global-manager" errorCode="PM500518" level="ERROR" reqId="########-####-####-####-########af00" subcomp="global-manager" username="######"] The API deleteInfraSegmentMonitoringBinding is invalid on the global manager.

2025-01-23T11:45:11.863Z ######.#####.com NSX 5056 - [nsx@6876 audit="true" comp="global-manager" entId="<segmentprofilebindmap-id>" level="INFO" reqId="########-####-####-####-########af00" subcomp="global-manager" update="true" username="######"] UserName="######", Src="######.#####.com", ModuleName="PolicyMonitoringProfileBinding", Operation="DeleteInfraSegmentMonitoringBinding", Operation status="failure", New value=["<segment-id>" "<segmentprofilebindmap-id>"]

2025-01-17T08:02:20.580Z ######.#####.com NSX 5056 - [nsx@6876 audit="true" comp="global-manager" level="INFO" reqId="########-####-####-####-########b09e" subcomp="global-manager" update="true"] UserName="######", Src="######.#####.com", ModuleName="Policy", Operation="PatchInfra", Operation status="failure", New value=[{"enforce_revision_check":true} {"resource_type":"Infra","children":[{"Segment":{"type":"DISCONNECTED","vlan_ids":["####"],"transport_zone_path":"/global-infra/sites/<site_name>/enforcement-points/default/transport-zones/<transportzone-id>","advanced_config":{"hybrid":false,"multicast":true,"inter_router":false,"local_egress":false,"urpf_mode":"STRICT","connectivity":"ON"},"federation_config":{"global_overlay_id":######},"admin_state":"UP","replication_mode":"MTEP","resource_type":"Segment","id":"<segment-id>","display_name":"<segment-name>","path":"/global-infra/segments/<segment-id>","relative_path":"<segment-id>","parent_path":"/global-infra","unique_id":"########-####-####-####-########01b6","owner_id":"########-####-####-####-########e416","marked_for_delete":false,"overridden":false,"_create_time":1565357414032,"_create_user":"#####","_last_modified_time":1718695853535,"_last_modified_user":"######","_system_owned":false,"_revision":6},"resource_type":"ChildSegment","marked_for_delete":true,"mark_for_override":false}],"marked_for_delete":false,"overridden":false,"_revision":-1}]

• In the global manager logfile /var/log/gmanager/gmanager.log you may see entries similar to the following

2025-01-23T11:45:11.862Z  INFO http-nio-127.0.0.1-64440-exec-879 PolicyHierarchicalAPIUtils 5056 POLICY [nsx@6876 comp="global-manager" level="INFO" reqId="########-####-####-####-########af00" subcomp="global-manager" username="######"] Added to deletion list:SegmentMonitoringProfileBindingMapDto{portMirroringProfilePath='', ipfixL2ProfilePath='', super{MonitoringProfileBindingMapDto{super{PolicyConfigResourceDto{children='null', markedForDelete='false', overridden='false', super{PolicyResourceDto{path='/global-infra/segments/<segment-id>/segment-monitoring-profile-binding-maps/<segmentprofilebindmap-id>', relativePath='<segmentprofilebindmap-id>', parentPath='/global-infra/segments/<segment-id>', remotePath='', uniqueId='########-####-####-####-########1640', realizationId='null', ownerId='########-####-####-####-########e416', originSiteId='null', super{ManagedResource{resourceType='SegmentMonitoringProfileBindingMap', aCreateUser='#####', aCreateTime='1574357807120', aLastModifiedUser='system', aLastModifiedTime='1605355142222', aSystemOwned='false', aProtection='null', id='<segmentprofilebindmap-id>', displayName='<segmentprofilebindmap-id>', description='null', tags='[Tag{scope='lm_path', tag='/infra/segments/########-####-####-####-########0ab1/segment-monitoring-profile-binding-maps/<segmentprofilebindmap-id>'}]', super{RevisionedResource{aRevision='1', super{Resource{aSelf='null', aLinks='null', aSchema='null'}}}}}}}}}}}}}

Environment

VMware NSX
VMware NSX-T Data Center

Cause

When deleting a port mirroring profile, under certain conditions, it may lead to a stale entry in the NSX manager database. This stale entry may still be attached to a segment preventing the removal of the segment.

Resolution

This is a known issue impacting VMware NSX.

Workaround:

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

Additional Information

Deleting port mirroring sessions fails in NSX
https://knowledge.broadcom.com/external/article?articleNumber=322483