2025-01-28T15:06:47.382Z: [netCorrelator] 8492350294662us: [esx.problem.net.vmknic.ip.duplicate] Duplicate IP address detected for 172.###.###.226 on interface vmk3, current owner being 00:50:##:##:21:d2.
2025-01-28T15:06:47.675Z: [netCorrelator] 8492323880740us: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for 172.###.###.228 on interface vmk4. The current owner is 00:50:##:##:58:bb.
2025-01-28T15:59:42.701Z: [netCorrelator] 8495366153398us: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for 172.##.##.232 on interface vmk3. The current owner is 00:50:##:##:ce:05.
2025-01-28T15:59:42.939Z: [netCorrelator] 8495366391665us: [vob.net.vmknic.ip.duplicate] A duplicate IP address was detected for 172.##.##.235 on interface vmk4. The current owner is 00:50:##:##:3f:ea.
VMware NSX 3.2.1 and below.
When creating or updating a Transport Node (preparing NSX), if the operation fails, the Transport Node may release its TEP IP address, even though it is still in use. This IP address could then be reassigned to another Transport Node in the future, leading to potential duplicate TEP IP issues.
This issue is resolved in NSX 3.2.2, 3.2.3 and 4.0.1 and above, available at Broadcom downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB
Workaround:
To resolve the issue of non-allocated IPs within an IP pool, follow the steps below:
1. Identify Non-Allocated IPs
Use the following API to retrieve the IP allocations within the specified IP pool:
GET https://<nsx-mgr-ip>/policy/api/v1/pools/ip-pools/<mp-pool-id>/allocations
Sample output
{
"results": [
{
"allocation_id": "192.168.141.11",
"_protection": "NOT_PROTECTED"
},
{
"allocation_id": "192.168.141.14",
"_protection": "NOT_PROTECTED"
},
{
"allocation_id": "192.168.141.12",
"_protection": "NOT_PROTECTED"
}
],
"result_count": 3
}
Review the response to identify IP addresses that have not been allocated (non-allocated IPs)
2. Manually Allocate IPs
Once you have identified the non-allocated IP addresses, you can manually allocate them to the required IP Pool. Use the following API to allocate the IP:
https://<nsx-mgr-ip>/api/v1/pools/ip-pools/<mp-pool-id>?action=ALLOCATE
Request Body:
{
"allocation_id": "<ip-from-step-1>"
}
3. Verify Allocation
After manually allocating the IP addresses, use the same API from Step 1 to verify that the allocation has been successfully applied. This ensures that the IP has been correctly assigned and is no longer in the non-allocated state.
By following these steps, you should be able to resolve any issues related to unassigned IP addresses in the IP pool.
If you are contacting Broadcom support about this issue, please provide the following:
Handling Log Bundles for offline review with Broadcom support.