NSX LCP Bundle Missing or Cluster Preparation Failure in vLCM
search cancel

NSX LCP Bundle Missing or Cluster Preparation Failure in vLCM

book

Article ID: 418166

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

  • When attempting to enable VMware NSX on a vSphere Lifecycle Manager (vLCM) enabled cluster, the NSX LCP (Life Cycle Plugin) bundle may be missing, or the cluster status may report a preparation failure. This occurs when the required communication trust and service account configurations between the NSX Manager and the vCenter Server (Compute Manager) have not been established or have become out of sync.
  • In the vSphere Client, hosts report as Out of Compliance.
  • The NSX LCP Bundle is missing or displayed as "None" in the vLCM Image settings.
  • In the NSX Manager UI (System > Fabric > Nodes > Host Transport Nodes), the cluster shows a Preparation failed state.
  • The following error string is logged:
    26198: Error occurred during operation on cluster: [Cluster-ID]. Error: NSX cannot be enabled on vLCM enabled cluster as required configurations are not created on Compute Manager. Please perform edit action on Compute Manager to enable trust and create service account.
  • The cluster status indicates: The cluster is not in sync. Click 'Resolve' to initiate sync between the NSX Manager and vLCM on vCenter.

Environment

VMware vCenter Server

VMware NSX

Cause

This issue occurs because the vCenter Server, registered as a Compute Manager in NSX, does not have the mandatory Enable Trust and Create Service Account settings activated. These settings are required for NSX to push its component bundles into the vLCM image depot on vCenter.

Resolution

Step 1: Configure Compute Manager

  1. Log in to the NSX Manager UI.
  2. Navigate to System > Fabric > Compute Managers.
  3. Select the target vCenter Server and click Edit.
  4. Ensure both Enable Trust and Create Service Account are set to Enabled.
    • Note: If these are already enabled, toggle them OFF, click Save, then Edit again and toggle them ON to force a refresh of the trust configuration.
  5. Click Save and verify the status shows as Registered.

Step 2: Force NSX to Push the Component Bundle

If the NSX LCP Bundle still does not appear in vCenter after enabling trust, follow these steps to force the push:

  1. In the NSX Manager UI, navigate to System > Fabric > Nodes > Host Transport Nodes.
  2. Locate the cluster reporting the failure or missing bundle.
  3. Click the Resolve button on the error message. This triggers NSX to attempt a push of the LCP bundle to the vCenter depot.
  4. If the button is not visible, navigate to System > Fabric > Compute Managers, select the vCenter, and click Refresh. This re-triggers the synchronization of available NSX versions to the vCenter Image Depot.

Step 3: Verify in vCenter

  1. Return to the vSphere Client.
  2. Navigate to the cluster Updates tab > Image.
  3. Click Edit on the Image and check if the NSX LCP Bundle is now available in the components list.

Additional Information

Prepare an NSX Cluster with vSphere Lifecycle Manager

Resetting the VMware Update Manager Database