NSX cannot be enabled on vLCM enabled cluster as required configurations are not created on compute manager
Article ID: 407958
Updated On:
Products
Issue/Introduction
- The cluster is prepared for NSX
- You accidently set image on the non vLCM cluster in the vCenter and made it a vLCM cluster
- All the hosts in the cluster are reporting as out of compliance in the vCenter
- In the NSX manager, you see the cluster in Preparation failed state and the error looks similar to the below
26198: Error occurred during operation on cluster:###################:domain-## 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 ####### is not in sync. Click 'Resolve' to initiate sync between the NSX manager and vLCM on vCenter.
Environment
NSX 4.1.2.5
Cause
This issue occurs if the image is set on a non vLCM NSX prepared cluster and the compute manager is not registered with the mandatory settings for vLCM
Resolution
To resolve the issue, follow the below steps.
1. Edit the Compute Manager on NSX and make sure enable trust and create service account options are enabled as per Prepare an NSX Cluster with vSphere Lifecycle Manager.
2. Once done, click on the RESOLVE button on the error in NSX so that the cluster syncs.
Note: Disabling vLCM on the vSphere cluster is not a supported operation in vCenter.
Additional Information
Also refer to: Switching from using Baselines to Images (vLCM) may result in drift and report VIB/Component Removal Notifications
If the steps outlined in this KB do not resolve the issue, please raise a support ticket with Broadcom Support, selecting NSX as the product.
Handling Log Bundles for offline review with Broadcom support.
Feedback
