ESXi host preparation in NSX fails with Error 600: The requested object : ########-####-####-####-############ could not be found. Object identifiers are case sensitive.
Article ID: 430064
Updated On:
Products
Issue/Introduction
When attempting to add multiple ESXi hosts to NSX for host preparation, the process fails during the validation phase. The following error is displayed in the NSX Manager UI.
This error typically occurs across multiple hosts, all referencing the same missing UUID.
Environment
VMware NSX
Cause
The failure is caused by stale or orphaned references to a deleted Transport Zone Profile (TZP). The Corfu DB retains metadata for these deleted profiles; during host preparation validation, the system attempts to locate the non-existent UUID, leading to the "object could not be found" error.
Resolution
To resolve this issue, we must have the stale entries removed from the NSX database.
Open a ticket with the Broadcom NSX team to clean up the stale entry.
As a workaround:
Create a new Transport Node Profile with the same setting as existing one and apply the new TNP.
Additional Information
You can also refer to this KB NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors"
Feedback
