"Unable to create transport node collection" when transitioning to vLCM images from baselines in SDDC Manager
search cancel

"Unable to create transport node collection" when transitioning to vLCM images from baselines in SDDC Manager

book

Article ID: 440430

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer VMware NSX

Issue/Introduction

During or immediately after following the steps within Transition to vSphere Lifecycle Manager Images Using the PowerShell Script Command-Line Interface to transition from vLCM baselines to images the following errors may be observed:

  • In the SDDC task details, the following error may be displayed:

Unable to create transport node collection with profile <Profile ID> on compute collection <UUID>:domain-c<X> through nsxmanager

  • In NSX, the cluster shows a status of "Preparation failed" on the host page with the following error displayed when clicking the failed state:

    600: The requested object : <UUID> could not be found. Object identifiers are case sensitive.

 

Environment

  • SDDC Manager
  • VMware NSX 

Cause

This issue occurs because the SDDC task attempts to re-apply the Transport Node Profile (TNP) to the hosts using a stale Transport Zone Profile. The presence of this stale profile causes the object lookup failure and cluster preparation failure in NSX. The use of the SDDC script simply triggers the workflow that highlights the issue within NSX.

Resolution

To resolve this issue, you must clean up the stale Transport Zone Profile so the TNP can be successfully applied. Please review Knowledge Article 324194 - NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors" to obtain assistance with this issue.