Removing NSX Segments that are stuck in "Marked for Delete" state
search cancel

Removing NSX Segments that are stuck in "Marked for Delete" state

book

Article ID: 303323

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Deleted Segments are stuck grayed out in the NSX-T UI and cannot be modified.

  • The API request: GET https://{mgrIP}/policy/api/v1/infra/segments  may NOT list these segments, but they are listed with:

    GET https://{mgrIP}/policy/api/v1/infra/segments?include_mark_for_delete_objects=true

  • The API request: DELETE https://{mgrIP}/policy/api/v1/infra/segments/<segment-id> returns a 404 response code, and the segment is not deleted

Environment

VMware NSX

Resolution

Confirm the following

  1. There are no logical ports associated with this LS at both Policy/MP.
  2. The Logical switch at the MP is deleted already and we have only Policy Object of LS.
  3. When you run realization API, there is no realized object at MP for the intent path in question (LS in question)

If the issue persists, please open a support case with Broadcom Support and refer to this KB article.

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




Additional Information