Upgrade to vSphere 7 NSX-T Host Transport Nodes > ProVirtualzone

Upgrade to vSphere 7 NSX-T Host Transport Nodes is another blog post about upgrading your environment to vSphere 7. When we upgrade our vCenter and vSphere and using NSX-T, we also need to upgrade our NSX-T Host Transport Nodes vib agents in the ESXi hosts.

After we upgrade our vCenter and vSphere to v7, we have in NSX-T in the Host Transport Nodes with errors.

Most of the time this type of error we click on it and then click Resolve or Configure NSX, and NSX-T will automatically fix the issue. But not in this case, since vib agents installed in the ESXi host is still from vSphere 6.7. As we can see in the other column, OS Type (already some have v7.02 since some agents were already upgraded).

How to upgrade vib agents?

We can do this in two ways. One if through Lifecycle Manager or manually install in each ESXi host using command esxcli software vib install -d vib path/vib_name.

If it is for the first option or the second option, we need first to download vib from VMware. Select NSX Kernel Module for VMware ESXi 7.0, and we can download it from HERE.

Using Lifecycle Manager.

After you download the zip file, you need to import it into your Lifecycle Manager.

Next, create a Baseline extension.

After Baseline is created, just to the Cluster where the ESXi hosts with NSX-T agents are and remediate.

After reboot ESXi hosts.

Install in ESXi hosts manually.

Upload the vib file nsx-lcp-3.0.1.0.0.16404614-esx70.zip to ESXi (with WinSCP, for example) and run the vib install command.


[root@ESXi-01:~] esxcli software vib install -d /tmp/nsx-lcp-3.1.1.0.0.17483060-esx70.zip -f
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_nsx-adf_3.1.1.0.0-7.0.17483060, VMware_bootbank_nsx-cfgagent_3.1.1.0.0-7.0.17483060, VMware_bootbank_nsx-context-mux_3.1.1.0.0-7.0.17483060...
VIBs Removed: VMware_bootbank_nsx-adf_3.1.2.0.0-6.7.17883598, VMware_bootbank_nsx-cfgagent_3.1.2.0.0-6.7.17883598, VMware_bootbank_nsx-context-mux_3.1.2.0.0-6.7.17883598...
VIBs Skipped: VMware_bootbank_nsx-python-gevent_1.1.0-15366959, VMware_bootbank_nsx-python-greenlet_0.4.14-16723199, VMware_bootbank_nsx-python-protobuf_2.6.1-16723197
[root@ESXi-01:~]

[root@ESXi-01:~] esxcli software vib install -d /tmp/nsx-lcp-3.1.1.0.0.17483060-esx70.zip -f

Installation Result

Message: Operation finished successfully.

Reboot Required: false

VIBs Installed: VMware_bootbank_nsx-adf_3.1.1.0.0-7.0.17483060, VMware_bootbank_nsx-cfgagent_3.1.1.0.0-7.0.17483060, VMware_bootbank_nsx-context-mux_3.1.1.0.0-7.0.17483060...

VIBs Removed: VMware_bootbank_nsx-adf_3.1.2.0.0-6.7.17883598, VMware_bootbank_nsx-cfgagent_3.1.2.0.0-6.7.17883598, VMware_bootbank_nsx-context-mux_3.1.2.0.0-6.7.17883598...

VIBs Skipped: VMware_bootbank_nsx-python-gevent_1.1.0-15366959, VMware_bootbank_nsx-python-greenlet_0.4.14-16723199, VMware_bootbank_nsx-python-protobuf_2.6.1-16723197

[root@ESXi-01:~]

Even if it states that reboot is not required, NSX-T could not fix and set the new version until I reboot the ESXi host.

Note: This manual install needs to be done in all ESXi hosts that are in the Host Transport Nodes.

After new NSX-T vib agents are installed, and ESXi hosts rebooted, return to NSX-T and resolve each one to fix and recognize the new version.

Click in the error and next click Resolve 2 times.

As we can see in the next image, after a couple of minutes, NSX-T did fix the issue and assumed the new vib agent version and displays Success.

After all ESXi hosts fix, we have a fully functional NSX-T with all the Host Transport Nodes Green.

I hope this simple tip in this Upgrade to vSphere 7 NSX-T Host Transport Nodes blog post will help you to fix and upgrade NSX-T Host Transport Nodes.

If you need help with how to upgrade your NSX-T, please check my other article, How to upgrade NSX-T 2.4.x or 2.5.x to NSX-T 3.0

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