What to read next Host Fails to Install as Transport Node Accessing the NSX CLI Terminal Transport Node Installation Failure Due To Pending Reboot Unable to Reach Transport Node Due to Incorrect Credentials As Host is in Orphaned State Transport node profile Fails to Prepare Transport Nodes Due to Stale Objects Transport Node Creation is in Partial Success State Due to Logical Switch or Segment Full-sync Realization Error Transport Node status is degraded when its interface is down Transport Node status is Disconnected or Unknown Transport Node is Down as Agent Service is Down Transport Node Connectivity to Controller is Down Unable to power on VMs or vMotion VMs on Transport Node Transport Node Tunnels Down Installation Fails Due to Insufficient Space in Bootbank on ESXi HostNSX installation might fail if there is insufficient space in the bootbank or in the alt-bootbank on an ESXi host. NSX Agent on ESXi Transport Nodes Times Out Communicating with NSX ManagerIn a large-scale environment with many transport nodes and VMs on ESXi hosts, NSX agents, which run on ESXi hosts, might time out when communicating with NSX Manager. Parent topic: Troubleshooting Installation Issues