NSX Segments stuck in 'Marked for Delete' state

Products

• VMware NSX

Issue/Introduction

• Deleted Segments are stuck (grayed out) in the NSX 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

Cause

NSX segments or policy objects may become stuck in a "Marked for Delete" or "Deleting" state when the system is unable to complete the deletion due to underlying dependencies or stale references. 

Resolution

• Referential Integrity Errors: The deletion is held in a "Marked for Delete" state because Enforcement Points (Local Managers) fail to realize the deletion due to local dependencies, such as group memberships
  • Reference (KB 431704) Deleted network segment stuck in "In Progress" state in NSX Federation
    
    
• Stale Logical Ports: A segment may fail to delete if a logical port is still associated with it, even if the port is stale. This is often indicated by error code 8402 or 600 in logs.
  • Reference (KB 401089) Deleting a segment in NSX-T fails with stuck in "In Progress" and (KB 431704) Deleted network segment stuck in "In Progress" state in NSX Federation
    
    
• Grouping Workflow Exceptions: Creation or deletion of ports can stall indefinitely due to a ConcurrentModificationException in the Grouping workflow, preventing the parent segment from completing its deletion cycle.
  • Reference (KB 414164) NSX segment ports stuck as "in progress"
    
    
• If Virtual Machines are still attached to a VLAN or Overlay Segment that has gone into a deletion in progress state, VM traffic may continue to run for some time across those networks, but it is not safe to remain in that state. The segment will need to be re-created and VMs migrated over to the new one.
  
  • Reference (KB 439273) Virtual Machines lose network connectivity on NSX Segments in "Marked for Delete" state
    
    

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

NSX API Guide