NSX-T install / upgrade on ESXi fails on a vLCM enabled cluster
Article ID: 401260
Updated On:
Products
Issue/Introduction
- Preparation of the ESXi s NSX Host transport node fails.
- NSX upgrade fails with similar error.
- The issue occurs in a vLCM-enabled vSphere cluster.
- The image used for the ESXi host is different from the one used for the rest of the hosts in the cluster
- ESXi transport node preparation in NSX fails with the error shown in the screenshot below:
Failed to install software on host. Solution apply failed because the vSphere Lifecycle image contains either a new ESXi version or a new addons version or new components. Please proceed to the vSphere Client Lifecycle Manager to update ESXi or addons or components along with the solution 'com.vmware.nsxt' Solution apply failed on host: '<Hostname>'. The 'TSDM Daemon for VMware ESX' component version '19.16.0.2-1OEM.703.0.0.18644231' was deleted from vSphere Lifecycle image. Please proceed to the vSphere Client Lifecycle Manager to delete the component and update the solution 'com.vmware.nsxt'. Solution apply failed on host: '<Hostname>'.
Environment
VMware NSX
VMware vSphere ESXi
Cause
The issue occurs because the desired state in vLCM is not the same as the ESXi Host.
Resolution
- To resolve the issue, make sure to use the same image for all the ESXi hosts in the vSphere vLCM cluster and remediate the cluster successfully.
- Once completed, the host preparation can be initiated from the NSX, and vLCM will initiate the Apply NSX Solution task to install the NSX vibs on the host.
Note: The solution-apply operation only adds the solution vibs but does not update base ESXi or any additional components. If the base ESXi or any additional components are part of the vLCM image drift, the solution-apply operation will be rejected/failed. Hence it is imperative that all the hosts in the cluster are in compliant with the vLCM image before initiating the NSX installation or the upgrade.
Additional Information
Before applying TNP on the cluster, the host should already be compliant (ESX OS, other components, ovf tools, etc.)
Prepare an NSX Cluster with vSphere Lifecycle Manager
If the issue persists even after fixing the image, please open a support ticket with Broadcom Support team:
Feedback
