Deleted segment continues to be advertised to the BGP peer due to stale route redistribution.

Products

• VMware NSX

Issue/Introduction

• Segment deletion is stuck in "In Progress" state.
  
  
• Below API was executed , which returns success and the segment gets deleted.
  DELETE https://<NSX-Manager>/policy/api/v1/infra/segments/<segment-ID>
  
  
• Deleted segment is still being redistributed by Tier-0 router over to the BGP peer.
  
  
• Investigation from the Edge CLI (using get interfaces within the relevant VRF) confirms that a Tier-1/Tier-0 router port associated with the IP address of the deleted segment still exists on the Edge node. This indicates a stale interface that was previously displayed in Manager mode.

Environment

VMware NSX

VMware NSX-T datacenter

Cause

The primary cause of this issue is the persistence of a stale router port on the Edge node. Even after the segment is logically deleted from the NSX Manager, the corresponding router port associated with the segment's IP address remains on the Edge node. This stale port causes the Edge router to continue redistributing the associated network information to BGP peers, despite the segment no longer existing in the NSX policy configuration.

Resolution

To resolve this issue, the stale router port(s) associated with the deleted segment must be manually identified and removed. This typically requires assistance from Broadcom Support.

Steps to Identify Stale Logical Router Port(s):

1. Identify VRF ID:

   • Log in to the Edge node CLI.
   • Execute the command get logical-router to list all logical routers.
   • Identify the VRF ID of the corresponding Tier-0 or Tier-1 logical router where the deleted segment was previously attached.

2. Identify Stale Interface(s):

   • Switch to the identified VRF context: vrf <VRF-ID>
   • Execute the command get interfaces to list all interfaces within that VRF.
   • Carefully review the output to identify the specific router port ID(s) that correspond to the IP address(es) of the deleted segment.

3. Search in NSX UI (Optional, for verification):

   • If possible, search for the identified router port ID in the NSX UI (e.g., under Tier-0 or Tier-1 gateway interfaces) to confirm it is indeed stale and not associated with any active segment.

Open a support case with Broadcom Support to delete these entries.

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

 

 

Additional Information

The segment deletion issue is fixed in NSX 4.2

Reference:Deleting a segment in NSX-T fails with stuck in "In Progress"