Workaround for NSX-T Host Upgrade Failure using Manual VIB Installation

VMware NSX

Upgrading an NSX-T Host Transport Node from the NSX Manager UI fails.
The host status displays as "NSX Install Failed", "Disconnected", or "Not Available" in the System > Fabric > Nodes view.
Clicking the "Resolve" button in the NSX UI does not correct the issue.
Rebooting the ESXi host does not resolve the upgrade failure.
In some cases, the error message [LockingError] Another process is updating the ESX image may be observed during the initial attempt.

The NSX Manager automated agent is unable to successfully push or install the required kernel modules (VIBs) to the ESXi host. This can be caused by:

The ESXi esxupdate process is locked by a previous failed attempt or a third-party agent (e.g., HA/FDM).
The NSX Manager cannot reliably transfer the installation bundle to the host due to intermittent network connectivity on the management plane.
The host believes it is in a "pending" upgrade state that prevents new automated workflows from triggering.

To resolve this issue, manually install the NSX Kernel Modules (VIBs) directly on the ESXi host using the Command Line Interface (CLI).

Prerequisites:

Ensure the ESXi host is in Maintenance Mode.
Obtain the NSX Offline Bundle (ZIP) that matches your target NSX version (e.g., nsx-lcp-bundle-4.2.****-esx80.zip). This can be downloaded from the Broadcom Support Portal or extracted from the NSX Manager repository.

Steps:

Upload the Bundle: Use a tool like WinSCP or the vSphere Datastore Browser to upload the NSX offline bundle ZIP file to the ESXi host.
- You can place it in /tmp/ or on a persistent datastore path (e.g., /vmfs/volumes/datastore1/).
SSH to Host: Log in to the ESXi host as root via SSH.
Verify Location: Navigate to the directory where you uploaded the file to confirm the path.
```
ls -l /path/to/your/bundle.zip
```
Install VIBs: Run the following command to install the VIBs manually. (Note: Use the full path to your zip file).
```
esxcli software vib install -d /path/to/nsx-lcp-bundle-4.2.3.1.x-esx80.zip
```
(Note: If you are reinstalling over an existing corrupt install, you can append --no-live-install if required, though a standard install usually suffices).
Reboot: Once the command returns "Message: The update completed successfully," reboot the host.
```
reboot
```
Verify Installation: After the host comes back online, log in via SSH and verify the NSX VIBs are present.
```
esxcli software vib list | grep nsx
```
Sync NSX Manager: Log in to the NSX Manager UI. Navigate to System > Fabric > Nodes > Host Transport Nodes. If the host is not yet green, select the host and click Resolve or Sync to establish the management plane connection.

Documentation Reference: For further details on manual installation switches and requirements, refer to the Broadcom documentation: Manually Install NSX-T Data Center Kernel Modules on ESXi Hypervisors.
Logs: If the manual esxcli command fails, check the ESXi update logs at /var/log/esxupdate.log for specific locking or dependency errors.