NSX LCP Bundle is missing or displayed as "None" in vLCM Image
search cancel

NSX LCP Bundle is missing or displayed as "None" in vLCM Image

book

Article ID: 418166

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

  • When running "Check Compliance" from the vLCM image compliance screen, the cluster is reported as non-compliant.

  • In the vLCM image details, the NSX LCP Bundle is listed with "None" in the version column, indicating it is missing from the image.

Environment

VMware vCenter Server

Cause

This issue occurs because the Create Service Account setting was not enabled in NSX Manager for the vCenter Server (registered as a Compute Manager).

This setting is mandatory for NSX to properly push its component depot, including the LCP bundle, to the vCenter Server's vLCM repository. If this setting is disabled, the bundle is never added to the vLCM image, leading to the compliance failure.

Resolution

The resolution involves two stages: first, enabling the "Create Service Account" setting, and second, forcing NSX to re-upload its component depot to vCenter Server by configuring NSX on a temporary empty cluster.

Part 1: Enable "Create Service Account" in NSX Manager

  1. Log in to the NSX Manager user interface.

  2. Navigate to System > Fabric > Compute Managers.

  3. Locate the target vCenter Server in the list and click EDIT.

  4. Click the toggle switch to activate the Create Service Account setting.

  5. Click SAVE to apply the changes.


Part 2: Force NSX to Push the Component Bundle

You must force NSX to re-upload its depot to vCenter Server. The simplest way to trigger this is by creating a new, temporary cluster and configuring NSX on it.

2-1. Create a New Empty vLCM Cluster

  1. Log in to the vSphere Client.

  2. Right-click the Datacenter object that contains your problematic cluster.

  3. Click New Cluster.

  4. In the new cluster wizard, select Import image from existing host to simplify setup and ensure it's a vLCM-managed cluster. You do not need to add any hosts to this cluster; it can remain empty.

2-2. Configure NSX on the Empty Cluster

  1. Log back into the NSX Manager UI.

  2. Navigate to System > Fabric > Hosts.

  3. Find the new empty cluster you just created.

  4. Select the checkbox next to the new cluster and click Configure NSX at the top.

  5. Select any available Transport Node Profile to apply.

    • Note: Since the cluster is empty, this action will not affect any hosts. Its purpose is to trigger the NSX depot upload to the linked vCenter Server.

  6. Monitor the task in vCenter Server. Once the related "Configure NSX" tasks show as "Completed," the NSX components have been successfully pushed to the vLCM depot.

2-3. Cleanup and Verification

  1. You can now delete the temporary empty cluster from vCenter Server.

  2. Navigate back to your original cluster's Host > Image screen in vLCM.

  3. The NSX LCP Bundle should now appear correctly in the image. If necessary, run Check Compliance again.

Additional Information

Prepare an NSX Cluster with vSphere Lifecycle Manager

Resetting the VMware Update Manager Database

Powered by Wolken Software