Newly created segments, do not show up in the vCenter inventory

Products

• VMware NSX

Issue/Introduction

• Newly created segments are displayed in NSX UI, but do not appear in the vCenter inventory.
  
  
• The following log messages are seen in the NSX-T manager log var/log/proton/nsxapi.log:                                                                                                                                                                                              

WARN L2HostConfigTaskExecutor1 TransportNodeAsyncServiceImpl 5101 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Host configuration failed. Detailed error message :  NSX Ownership Validation: NSX ownership validation failed. [TN = xxxxx-xxxx-xxxx-xxxx-xxxxxxxx]. Reason: Cannot find the HostSwitch [xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx] of type VDS.
1731631:  value: " NSX Ownership Validation: NSX ownership validation failed. [TN = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx]. Reason: Cannot find the HostSwitch [xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx] of type VDS.

host_config_status: CONFIG_STATUS_FAILED
failure_code: 8804
failure_message {
  value: " NSX Ownership Validation: NSX ownership validation failed. [TN =  xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx]. Reason: Cannot find the HostSwitch [xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx] of type VDS."
}

INFO L2HostConfigTaskExecutor1 TransportNodeStateServiceImpl 5101 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated TransportNodeState [TransportNodeState [transportNodeId=TransportNode/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx, hostId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx, fabricNodeType=HOST_NODE, transportNodeRevision=2, hostConfigStatus=FAILED, failureCode=8804, failureMessage= NSX Ownership Validation: NSX ownership validation failed. [TN = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx]. Reason: Cannot find the HostSwitch [[xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx] of type VDS., errorParams=[12, 2024-Sep-23 03.21.38 AM, 2024-Sep-23 03.24.38 AM], appInitSucceed=false, logicalSwitchFullSyncSucceed=true, transportZoneIds=[TransportZoneEndpoint/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx, TransportZoneEndpoint/xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx], hostSwitchStates=[HostSwitchState [switchId = xx xx xx xx xx xx xx xx-xx xx xx xx xx xx xx xx], switchName = XXXX-XXX-XX, teamingPolicyType = LOADBALANCE_SRCID

Environment

VMware NSX

Cause

The error message indicates that the NSX Manager was unable to confirm ownership of the transport node due to its inability to locate the specified HostSwitch of type VDS (Virtual Distributed Switch).
This usually implies that the HostSwitch is either misconfigured, absent from the vCenter, and that the NSX Manager does not have the required permissions or connectivity to access it.

Resolution

• Verify that the HostSwitch (DVS), mentioned in the logs, is available in the vCenter's networking and check the vDS host tab, to ensure the connection status of the hosts is good.
  
  
• Inspect any hosts (Transport Nodes) that NSX was removed from, they may appear as standalone hosts, especially if moved from clusters in vCenter.
  If any transport nodes are still listed as standalone hosts, ensure NSX-T is completely removed from these hosts.
  
  
• This issue has been seen, when a transport node was moved out of an NSX-T prepared cluster, to remove NSX-T, so they were in the standalone tab and had errors, where NSX-T was not completely removed.