NSX-T with vSphere Lifecycle Manager Scenarios

Installation and uninstallation scenarios to consider when you work with vSphere Lifecycle Manager (vLCM) for NSX-T clusters.

Scenario	Result
You try to enable vSphere Lifecycle Manager on a cluster where transport node profile is not applied, but some hosts are individually prepared as host transport nodes.	vSphere Lifecycle Manager cannot be enabled on the cluster because a transport node profile was not applied to the cluster.
You try to enable vSphere Lifecycle Manager on a cluster using a transport node profile configured to apply N-VDS host switch.	vCenter Server checks for cluster eligibility so that the cluster can be converted to a vSphere Lifecycle Manager cluster. As N-VDS host switch type is not supported, apply a transport node profile that is configured to use a VDS host switch.
You move an unprepared host from a non-vSphere Lifecycle Manager cluster to a vSphere Lifecycle Manager cluster.	If the vSphere Lifecycle Manager cluster is prepared with a transport node profile, the unprepared host is prepared as an NSX-T transport node by vSphere Lifecycle Manager. If the vSphere Lifecycle Manager cluster is not prepared with a transport node profile, the host remains in unprepared state.
You move a transport node from a vSphere Lifecycle Manager cluster to a non-vSphere Lifecycle Manager cluster that is not prepared for NSX-T.	The NSX-T VIBs are deleted from the host, but the NSX Solution-related data (set by vSphere Lifecycle Manager) is not deleted. Now, if you try to enable vSphere Lifecycle Manager cluster on the cluster, NSX Manager notifies that NSX Solution will be removed from the host. This notfication is misleading because NSX-T VIBs were already removed on the host.
After you perform the Remove NSX operation on a Sphere Lifecycle Manager cluster, if vSphere Lifecycle Manager is unable to delete NSX-T from the desired state, all nodes go into Uninstall Failed state. Now, you try to remove NSX-T on individual transport nodes.	If you remove NSX-T on each individual transport node, then even though NSX-T VIBs are removed on the host, the cluster continues to have NSX as the desired state in vSphere Lifecycle Manager. This state shows up as drift in host compliance in vCenter Server. So, you must perform Remove NSX on the cluster to remove NSX from the vSphere Lifecycle Manager configuration.
vCenter Server is added as a compute manager with Multi NSX flag enabled. Apply TNP on another existing vLCM cluster.	NSX-T does not allow preparation of the existing vLCM cluster if it is part of the same vCenter Server.
vCenter Server is added as a compute manager with Multi NSX flag enabled. Then try to change the already prepared cluster to a vLCM cluster.	NSX-T does not allow preparation of the existing vLCM cluster.
vCenter Server is added as a compute manager with Multi NSX flag enabled. Then try creating a new vLCM cluster.	NSX-T allows preparation of the existing vLCM cluster.
vCenter Server already contains a vLCM cluster and you try to add the vCenter Server as a compute manager with Multi NSX flag enabled.	NSX-T fails this operation because the vCenter Server already contains a vLCM cluster.