NSX preparation failed on ESXi host due to associated stale logical ports to the host
Article ID: 424917
Updated On:
Products
VMware NSX
Issue/Introduction
- NSX preparation fails on an ESXi host due to validation error.
- The error code shows validation error 26210 indicating that the same ip already exists
Error: Node example-esxi.local with same ip <IP address of host example-esxi.local> already exists. Check the state of existing transport node. If it is a failure in deletion then use force option to delete previous transport node and retry the operation. If the host is part of a cluster having transport node profile applied then move the host into datacenter before deletion. Refer KB article number 319975 for more details. (Error code: 26210) - Searching for the transport node ID/name in the NSX UI global search displays logical ports associated with the host.
- In NSX manager UI, policy view, the related segment ports show as Admin Status Up and Status Success.
- In NSX manager UI, manager view the related logical ports show, Admin Status is Up, but Operational Status is Down.
- This can also be applied as a search filter as shown below by switching to Manager View > Network > Logical Switches > Ports
Environment
VMware NSX
Cause
Stale logical ports created dependencies that prevented the host from being completely deleted from the NSX database.
Resolution
- Manually remove the stale logical ports from the NSX manager to resolve the conflict.
- Refer to Broadcom knowledge base article 319115 for steps to remove stale logical ports.
- Post cleanup of the stale logical ports try to force delete the ESXi transport node to ensure the entry is cleaned up from NSX database.
- Prepare the host for NSX.
If the issue remains unresolved or requires direct database manipulation, please open a Broadcom Technical support case.
Please refer to Creating and managing Broadcom support cases for process details.
Additional Information
Feedback
Yes
No
Powered by
