NSX-T IP Pool deletion cannot complete due to "Realization Errors" with stale IP entries

Products

• VMware NSX

Issue/Introduction

• When Service VMs, Host Transport Nodes, or NSX edges are removed
• Their IP addresses from an IP pool may not be released
• The IP Pool was marked for deletion
• This action can cause the realization of IP Pool deletion to fail due to stale IP entries still seen as allocated in NSX-T
• A error message similar to "Received error cannot delete Partition 0 as it has allocated Ids deleting resource: <UUID> from NSX for <UUID>" in IP Address Pools page. 

Environment

VMware NSX-T 3.x and VMware NSX versions before 4.1.2

Cause

This issue is caused by a software defect in VMware NSX-T. 

 

Resolution

This issue is fixed in VMware NSX 4.1.2, please upgrade to this version to prevent the deletion of IP Pools before the allocation is released. 

Workaround:

Please check the IP Pool allocation before deleting it. The allocation information can be found under "Networking", "IP Management", "IP Address Pool", and then under the "Allocation" column of the IP Pool. 

If there are IPs still shown in the allocation, please reconfigure the perspective service/host/edges to not use an IP from this pool.

 

If the object has already been deleted and the IP become stale, you can run the following API calls to get it released:

POST https://NSX-Manager-IP/api/v1/pools/ip-pools/<pool-UUID>?action=RELEASE

with the following inside the body of the POST request:

{

"allocation_id":"IP-Address",

"allocation_id":"IP-Address"

}

Please consult the NSX-T API guide: https://dp-downloads.broadcom.com/api-content/apis/API_NTDCRA_001/3.2.1/html/api_includes/method_AllocateOrReleaseFromIpPool.html