NSX Edge node deployment fails due to IP pool exhaustion and no alarm triggered.

Products

• VMware NSX

Issue/Introduction

Issue symptoms:

• Edge node deployment fails and status shows pending.
• Controller connection will be down with failed reason "OTHER_ERROR".
• No alarm triggered for IP pool usage high in NSX.
• You may find logs similar to the following in the edge node

/edge/controller-connections

 "ip": {
           "ipv4": ##########
        },
        "server_port": 1235,
        "fqdn": "",
        "state": "DISCONNECTED",
        "master": true,
        "failure_reason": "OTHER_ERROR" <<<<<<<<<
    },

var/log/syslog

2025-07-15T02:13:29.057Z WARN L2HostConfigTaskExecutor4 IPAMServiceImpl 5140 POOL-MGMT [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Allocation failed for subnet string_id: "########-b45a-4b2f-####-############"
. Retrying from next subnet
2025-07-15T02:13:29.057Z ERROR L2HostConfigTaskExecutor4 IPAMServiceImpl 5140 POOL-MGMT [nsx@6876 comp="nsx-manager" errorCode="MP5109" level="ERROR" subcomp="manager"] Insufficient Resource Exception : no free IP found to allocate from the pool IpPool/########-62b5-####-bf3d-############.
2025-07-15T02:13:29.057Z ERROR L2HostConfigTaskExecutor4 IPAMUtils 5140 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8212" level="ERROR" subcomp="manager"] Failed to get a valid IP from IpPool IpPool/########-62b5-####-bf3d-############ with cidr null, {}.
com.vmware.nsx.management.common.exceptions.InsufficientResourcesException: null
        at com.vmware.nsx.management.idas.ipam.service.IPAMServiceImpl.allocate(IPAMServiceImpl.java:105) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.IPAMUtils.ufoAllocateIpFromPool(IPAMUtils.java:63) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.VtepPopulator.allocateResourcesToNewVteps(VtepPopulator.java:436) ~[?:?]

 

Environment

VMware NSX-T Datacenter

VMware NSX

Cause

This is due to TEP IP pool exhausted during an edge node deployment. IPAM IP Pool Usage High alarm is raised only for Policy flows.

In Edge-TNP flows , all IP allocations from pool are done on Internal side and there won't be any alarm raised.

Resolution

Review the IP pool usage and you can resolve it by following any of the below-mentioned steps:

• Add a new subnet in the IP pool, this will extend the available range of IPs for allocations.
• Create a new IP pool and use it for allocation.
• Release the unused IP allocations from the IP pool. Contact VMware support for this process. For more details refer: Creating and managing Broadcom support cases.