Unknown
'.Unknown
' status, shows the status of the policy or rule for the relevant hosts. You observe a duplicate entry (one host is listed twice), one has a status of 'Success
' and the other has a status of 'Unknown
':As admin, run the following command on the NSX-T Manager to list all the transport nodes, you can see the same host listed twice with different UUID's:
> get nodes UUID Type Display Name <Transport-Node-UUID-1> esx esx-01.example.com <Transport-Node-UUID-2> esx esx-01.example.com
Up
and one with status Unknown
:# curl -k -u 'admin' -H "Content-Type: application/xml" -X GET https://localhost/api/v1/transport-nodes/<Transport-Node-UUID>/status
"node_uuid" : "<Transport-Node-UUID-1>", "node_display_name" : "esx-01.example.com", "status" : "UP", ... "status" : "UP", ...
"node_uuid" : "<Transport-Node-UUID-2>", "node_display_name" : "esx-01.example.com", "status" : "UNKNOWN", ... "status" : "UNKNOWN", ...
# curl -k -u 'admin' -H "Content-Type: application/xml" -X DELETE https://localhost/api/v1/transport-nodes/<Transport-Node-UUID>
"httpStatus" : "BAD_REQUEST", "error_code" : 9411, "module_name" : "NsxSwitching service", "error_message" : "Cannot delete a transport node <Transport-Node-UUID> which is part of Auto-TN compute collection f9412a40-####-####-####-d63d21c9d0e0:domain-c##. Please use the object name or UUID in Global Search to find all linked objects."
2023-03-09T10:52:16.138+01:00 nsxmanager01 NSX 6075 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="16a63b47-####-####-####-28938ab21484" subcomp="manager" username="####@example.com"] MPA on <Inactive-Transport-Node-UUID> is not connected. ... 2023-03-09T10:52:16.143+01:00 nsxmanager01 NSX 6075 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" reqId="16a63b47-####-####-####-28938ab21484" subcomp="manager" username="####@example.com"] Got deployment status HOST_DISCONNECTED for node <Inactive-Transport-Node-UUID>
Workaround:
IMPORTANT
The below workaround is not applicable if the cluster where the 'duplicate host' resides is prepared using vSphere Lifecycle Management (vLCM) or has service insertion deployed in it or is an NSX-T Security Only installed cluster. It is not possible to detach the transport node profile (TNP) from such clusters.
If your NSX configuration is not compatible with the below workaround please contact VMware Technical Support and reference this KB article (91869).
# curl -k -u 'admin' -H "Content-Type: application/xml" -X DELETE https://localhost/api/v1/transport-nodes/<Transport-Node-UUID>