NSX-T Manager IP Pools Cannot Be Deleted Due to Allocated IDs

Products

• VMware NSX

Issue/Introduction

• IP pools may remain in a "greyed out" or "In Progress" state in the User Interface and fail to be deleted following a previous installation or reconfiguration.
  
  
• Attempts to remove the stale IP pool result in errors indicating that the range is still in use despite no apparent active consumers.
  
  
• VMware Kubernetes System (VKS) was removed, leaving behind orphaned network resources.

• IP Pools in the NSX Manager UI are greyed out or stuck in "In Progress" status.

• Syslog or NSX Manager logs contain the following error codes and messages:

  • errorCode="MP5015": IP Pool Id <UUID> cannot be deleted: range is in use

  • errorCode="PM500016": Range [{0}-{1}] cannot be deleted because it has allocated IDs.

• NSX Alarms report: Received error Range [{0}-{1}] cannot be deleted because it has allocated IDs. deleting resource <UUID>.

Environment

VMware NSX 4.x

Cause

The IP pool contains stale allocation entries in the Management Plane database that prevent the Policy Plane from executing the deletion.

Resolution

To resolve this issue, the specific allocations must be manually identified and removed via the NSX API before the pool itself can be deleted.

1. Identify the stale allocations within the problematic IP pool using the following API call (replace <IP-Pool-ID> with the actual UUID from the error message): curl -k -u admin -X GET https://localhost/api/v1/pools/ip-pools/<IP-Pool-ID>/allocations


   {
  "results" : [ {
    "allocation_id" : "10.##.##.50",
    "_protection" : "NOT_PROTECTED"
  } ],
  "result_count" : 1

2. Verify the output for the allocation_id (e.g., 10.##.##.50)


3. Delete the specific allocation using the ID identified in the previous step: curl -k -u admin -X DELETE https://localhost/api/v1/pools/ip-pools/<IP-Pool-ID>/allocations/<Allocation-ID>

4. Delete the stale IP pool from the Policy API once all allocations are cleared: curl -k -u admin -X DELETE https://localhost/policy/api/v1/infra/ip-pools/<IP-Pool-ID>

Note: If the issue persists, open support case with Broadcom. See Creating and managing Broadcom cases for information on how to open and manage cases.