MP2P Migration Fails With IpAddressBlock Does Not Have Spare Capacity Error

Products

• VMware NSX

Issue/Introduction

• During Management Plane to Policy (MP2P) migration, or when allocating new subnets via the Policy API, the operation fails and the migration is blocked.
• Users will observe the following error message in /var/log/migration-coordinator/migration-coordinator.log or /var/log/proton/nsxapi.log:

IpAddressBlock [path] does not have spare capacity to satisfy new block subnet [path] of size [size]

• Additionally, if a user previously attempted to delete the affected IP block while MP subnets still existed, the IP block may become stuck in an IN_PROGRESS or ERROR realization state with markedForDelete=true, placing it in an unmanageable state.

Environment

• VMware NSX-T 3.2.x

• VMware NSX 4.0.x

• VMware NSX 4.1.x

• VMware NSX 4.2.x

Cause

Legacy IP Blocks originally created prior to NSX 3.2.1 may have a maxBlockSize of 0 (or null) stored in the database. This missing or zeroed value causes capacity validation failures when the system attempts to promote MP subnets to Policy or allocate new capacity.

Resolution

This Issue will be fix in a future version of NSX  

Workaround:

Contact VMware by Broadcom support for further assistance: Creating and managing Broadcom support cases.

Additional Information

Migrating TAS Foundation to Policy