/NSX Host Transport Nodes Install Failed

NSX Host Transport Nodes Install Failed

This quick tip about NSX Host Transport Nodes Install Failed, when you get Install Failed, I will explain a simple fix that fixes this problem in most cases.

This is a similar problem that I already wrote a blog post about it, but that was during an ESXi host upgrade Upgrade to vSphere 7 NSX-T Host Transport Nodes. In that case, it needed some extra ESXi shell commands and a VIBs download. In this one, we are only focusing on fixing the problem simply (also discussed in the previous post).

After a new NSX 3.2 install, I try to automatically create the Host Transport Nodes(install NSX agents in ESXi hosts) and always get NSX Install Failed.

It was impossible to install the NSX agent(VIB driver) in all of the ESXi hosts, and the error was a time-out.

I tested the communication from vCenter / ESXi to NSX, and no issues were found. All IP and fully-qualified domain name (FQDN) could be resolved in vCenter, ESXi, and NSX.

So the quick solution is to install them one by one by using the option in the NSX ( I think it has existed since v3.0) called Resolve. This Resolve button is in almost issues that we can find in the NSX, and it will try to fix the error manually.

In this case, NSX will retry to install the NSX agent in the ESXi host, but I will do it one by one.

Click on the error(in this case, NSX Install Failefollowingnext click Resolve tree times. One in the task event, one in the error description, and the last one to confirm the Resolve option.

Next, most of the time NSX agent driver will start installing in the ESXi host, mainly if the problem is time out with the ESXi host.

Somehow when NSX tries to install all agents simultaneously, it gets some time-outs, and we see this error. That is why performing this simple manual install using resolve is a good option.

And that is it. No need for many troubleshooting or shell commands. This is enough to install Host Transport Nodes. And as I said in this quick tip, it only takes a few clicks to fix the problem.

Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.

©2022 ProVirtualzone. All Rights Reserved
By | 2022-09-30T12:30:55+02:00 September 26th, 2022|NSX, VMware Posts, vSphere|0 Comments

About the Author:

I am over 20 years’ experience in the IT industry. Working with Virtualization for more than 10 years (mainly VMware). I am an MCP, VCP6.5-DCV, VMware vSAN Specialist, Veeam Vanguard 2018/2019, vExpert vSAN 2018/2019 and vExpert for the last 4 years. Specialties are Virtualization, Storage, and Virtual Backups. I am working for Elits a Swedish consulting company and allocated to a Swedish multinational networking and telecommunications company as a Teach Lead and acting as a Senior ICT Infrastructure Engineer. I am a blogger and owner of the blog ProVirtualzone.com

Leave A Comment