Failed to add host to Cluster in SDDC Manager at "Prepare Transport Node Collection"
search cancel

Failed to add host to Cluster in SDDC Manager at "Prepare Transport Node Collection"

book

Article ID: 418946

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • When attempting to add a host to a cluster in VMware Cloud Foundation (VCF) SDDC Manager, the workflow fails at the "Prepare Transport Node Collection" subtask.
  • Within the SDDC Manager UI, the subtask failure displays the following messages:

    Description: Prepare Transport Node Collection

    Progress Messages: Unable to create transport node collection with profile ########-####-####-#-###-######## on compute collection ########-####-####-#-###-########:domain-cxx through nsxmanager NSX Manager FQDN

    Error Message: Unable to create transport node collection with profile xxxxxxxx-xxxx-xxxx-x-xxx-xxxxxxxxxxx on compute collection yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy:domain-cxx through nsxmanager NSX Manager FQDN

    Cause: Failed to realize transport node. Please refer logs.
  • In the SDDC Manager logs (/var/log/vmware/vcf/domainmanager/domainmanager.log), you observe the following timeout and failure sequence:

    yyyy-mm-ddThh:mm:ss.zzz+0000 DEBUG [vcf_dm,###############################,bf4b] [c.v.e.s.o.c.ProcessingTaskSubscriber,dm-exec-11]  Invoking task CreateTransportNodeCollectionAction. Description: Prepare Transport Node Collection, Plugin: NsxtPlugin, ParamBuilder null, Input map: {wldDmClusterName=NsxtPolicyAddHosts____23__clusterName, isVlcmCluster=vlcmEnabledCluster, wldClusterMoid=NsxtPolicyAddHosts____23__clusterMoid, vcenter=NsxtPolicyAddHosts____23__vcenter, transportNodeProfileId=NsxtPolicyAddHosts____23__ConfigureNsxWithTnpAttached____3__transportNodeProfileId, services={'TransportNodeCollectionService':'PolicyTransportNodeCollectionServiceImpl'}, nsxtManager=NsxtPolicyAddHosts____23__nsxtManagerVip}, Id: zzzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz ...

    yyyy-mm-ddThh:mm:ss.zzz+0000 DEBUG [vcf_dm,###############################,bf4b] [c.v.v.c.f.p.n.h.NsxtCommonOperations,dm-exec-11]  Waiting 2700000 ms for NSX cluster prepartion to be completed

    yyyy-mm-ddThh:mm:ss.zzz+0000 ERROR [vcf_dm,###############################,bf4b] [c.v.v.c.f.p.n.p.a.CreateTransportNodeCollectionAction,dm-exec-11]  Exception occured while creating transport node collection using profile xxxxxxxx-xxxx-xxxx-x-xxx-xxxxxxxxxxx on the cluster(with compute collection) yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy:domain-cxx

    java.lang.RuntimeException: Failed to realize transport node. Please refer logs.
  • Subtask "Prepare Transport Node Collection" failed because waiting preparation on NSX Manager.

  • In the NSX Manager syslog, you observe the exact reason for the transport node failure:

    yyyy-mm-ddThh:mm:ss.zzzZ NSX FQDN NSX 77662 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Created TransportNodeDesiredStateError object [TransportNodeDesiredStateError [id =TransportNodeDesiredStateError/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy:host-xxxx,computeCollectionId = yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy:domain-cxx,desiredStateErrorMessage = 26164: Transport Node cannot be created or updated because host is not attached to every VDS specified in Transport Node Profile.]]

Environment

SDDC Manager
VMware Cloud Foundation

Cause

This issue occurs if the target ESXi host you are attempting to add to the cluster is not attached to the vSphere Distributed Switch (VDS) specified in the NSX Transport Node Profile (TNP). Because the expected VDS is missing from the host, NSX Manager rejects the creation of the transport node, which subsequently causes the SDDC Manager workflow to fail.

Resolution

To resolve this issue, perform the following steps:

  1. Attach the VDS specified in the Transport Node Profile to the target ESXi host.

  2. Confirm that the host is successfully prepared as a transport node within the NSX Manager UI.

  3. Once the host preparation is confirmed in NSX, retry the failed host addition task in the SDDC Manager UI.