NSX configuration for a host fails when vSphere Lifecycle Manager image contains a HPE Customization for HPE Servers addon.

Products

• VMware NSX

Issue/Introduction

• When attempting a fresh install of VMware NSX components on hosts within a vSphere Lifecycle Manager (vLCM) cluster, the installation fails on all the hosts in the cluster. The host's NSX installation state is reported as Failed.
  
  
• The configuration fails with below error reported in the NSX UI:
  
  

  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: 'xxxxxxxxxx.xxxxxxxx.com'. The vSphere Lifecycle Manager image contains a new "HPE Customization for HPE Servers' addon version "803.0.0.12.2.0-9'.
  Please proceed to the vSphere Client Lifecycle Manager to update the addon and the solution 'com.vmware nsxt'Solution apply failed on host:'xxxxxxxx.xxxxxxxxxx.com'

Environment

VMware NSX

Cause

This operation fails because the vLCM image contains a newer version of an existing component (specifically, a hardware vendor-specific addon) that conflicts with the intended state or the NSX installation workflow.

This conflict prevents the NSX VIBs  from being successfully staged and applied to the hosts, resulting in an installation failure.

 

Resolution

Resolution

This is a condition that may occur in a VMware NSX environment when  installing NSX components in a vLCM-managed cluster for the first time alongside certain hardware vendor addons.

The recommended resolution is to ensure the vLCM image is fully compliant with the NSX solution and other components before re-attempting the installation task.

Workaround

The following steps can be used to resolve the conflict and allow the NSX installation to complete successfully:

1. Remove NSX from the Hosts:

From NSX UI , select the cluster and click on remove NSX from all hosts in the affected cluster.

Ensure all hosts return to a Non-Configured state for NSX.

2. Verify vLCM Image Compliance:

In vSphere Client, navigate to vSphere Lifecycle Manager for the cluster.

Ensure the vLCM image is compliant and includes all necessary components, including the hardware vendor addon that originally triggered the conflict (e.g., 'HPE Customization for HPE Servers').

3. Prepare the Hosts (Reinstall NSX):

Install NSX for the hosts in the cluster again from the NSX UI. 

The hosts will be prepared successfully, and the NSX installation task will complete. 

4. Confirm Compliance and Connectivity:

Verify that the hosts are reported as compliant with the vLCM Image.

Confirm that the hosts are correctly configured as NSX Transport Nodes and have connectivity to the NSX Manager/Controller cluster.

Additional Information

If you are contacting Broadcom support about this issue, please provide the following:

• NSX Manager support bundles.
• ESXi host support bundles for hosts that are failing to configure as transport nodes.
• Text of any error messages seen in NSX GUI or command lines pertinent to the investigation.
  
  
  Handling Log Bundles for offline review with Broadcom support:

Collect Support Bundles for Troubleshooting VMware NSX
Uploading files to cases on the Broadcom Support Portal
Creating and managing Broadcom support cases