Before you can start the migration process, you must add the VMware vCenter that is associated with NSX-V as a compute manager in NSX.

Prerequisites

Log into the NSX-V NSX Manager web interface to retrieve the settings used for VMware vCenter registration. You must use the same settings. For example, if an IP address is specified, use the IP address and not the FQDN. Note that the FQDN of the VMware vCenter is case-sensitive. If you enter the FQDN in the procedure below, be sure that it matches the VMware vCenter's FQDN exactly.

Procedure

  1. From a browser, log in with admin privileges to NSX Manager at https://<nsx-manager-ip-address>.
  2. Select System > Fabric > Compute Managers > Add Compute Manager.
  3. Complete the compute manager details.
    Option Description
    Name and Description Type the name to identify the VMware vCenter.

    You can optionally describe any special details such as, the number of clusters in the VMware vCenter.

    Type The default compute manager type is set to VMware vCenter.
    Multi NSX

    Starting with NSX 3.2.2, you can register the same vCenter Server with multiple NSX Managers.

    Enable this field if you want to allow multiple NSX instances to manage a single VMware vCenter. This functionality is supported from VMware vCenter 7.0 or later versions.
    Note: Cannot be enabled on a Workload Control Plane (WCP) cluster or vSphere Lifecycle Manager (vLCM) cluster.
    FQDN or IP Address Type the FQDN or IP address of the VMware vCenter.
    HTTPS Port of Reverse Proxy The default port is 443. If you use another port, verify that the port is open on all the NSX Manager appliances.

    Set the reverse proxy port to register the compute manager in NSX.

    Username and Password Type the VMware vCenter login credentials.
    SHA-256 Thumbprint Type the VMware vCenter SHA-256 thumbprint algorithm value. If you configured the VMware vCenter WCP (Workload Control Plane) feature, using the SHA256 setting results in communication issues between the WCP component in VMware vCenter and NSX Manager. In such cases, use the SHA1 algorithm instead.
    Create Service Account Enable this field for features such as vSphere Lifecycle Manager that need to authenticate with NSX APIs. Log in with the administrator@vsphere.local credential to register a compute manager. After registration, the compute manager creates a service account.
    Note: Service account creation is not supported on a global NSX Manager.

    If service account creation fails, the compute manager's registration status is set to Registered with errors. The compute manager is successfully registered. However, vSphere Lifecycle Manager cannot be enabled on NSX clusters.

    If a VMware vCenter admin deletes the service account after it was successfully created, vSphere Lifecycle Manager tries to authenticate the NSX APIs and the compute manager's registration status is set to Registered with errors.

    Enable Trust

    Enable this field to establish trust between NSX and compute manager, so that services running in vCenter Server can establish trusted communication with NSX. For example, for vSphere Lifecycle Manager to be enabled on NSX clusters, you must enable this field.

    Supported only on VMware vCenter 7.0 and later versions.

    Access Level Enable one of the options based on your requirement:
    • Full Access to NSX: Is selected by default. This access level gives the compute manager complete access to NSX. Full access ensures vSphere for Kubernetes and vSphere Lifecycle Manager can communicate with NSX. The VMware vCenter user's role must be set to an Enterprise Admin.
    • Limited Access to NSX: This access level ensures vSphere Lifecycle Manager can communicate with NSX. The VMware vCenter user's role must be set to Limited vSphere Admin.
    If you left the thumbprint value blank, you are prompted to accept the server provided thumbprint.

    After you accept the thumbprint, it takes a few seconds for NSX to discover and register the VMware vCenter resources.

    Note: If the FQDN, IP, or thumbprint of the compute manager changes after registration, edit the computer manager and enter the new values.
  4. If the progress icon changes from In progress to Not registered, perform the following steps to resolve the error.
    1. Select the error message and click Resolve. One possible error message is the following:
      Extension already registered at CM <vCenter Server name> with id <extension ID>
    2. Enter the VMware vCenter credentials and click Resolve.
      If an existing registration exists, it will be replaced.

Results

It takes some time to register the compute manager with VMware vCenter and for the connection status to appear as UP.

You can click the compute manager's name to view the details, edit the compute manager, or to manage tags that apply to the compute manager.

After the VMware vCenter is successfully registered, do not power off and delete the NSX Manager VM without deleting the compute manager first. Otherwise, when you deploy a new NSX Manager, you will not be able to register the same VMware vCenter again. You will get the error that the VMware vCenter is already registered with another NSX Manager.

Note: After a vCenter Server (VC) compute manager is successfully added, it cannot be removed if you successfully performed any of the following actions:
  • Transport nodes are prepared using VDS that is dependent on the VC.
  • Service VMs deployed on a host or a cluster in the VC using NSX service insertion.
  • You use the NSX Manager UI to deploy Edge VMs or NSX Manager nodes on a host or a cluster in the VC.

If you try to perform any of these actions and you encounter an error (for example, installation failed), you can remove the VC if you have not successfully performed any of the actions listed above.

If you have successfully prepared any transport node using VDS that is dependent on the VC or deployed any VM, you can remove the VC after you have done the following:
  • Unprepare all transport nodes. If uninstalling a transport node fails, you must force delete the transport node.
  • Undeploy all service VMs, all NSX Edge VMs, and all NSX Manager nodes. The undeployment must be successful or in a failed state.
  • If an NSX Manager cluster consists of nodes deployed from the VC (manual method) and nodes deployed from the NSX Manager UI, and you had to undeploy the manually deployed nodes, then you cannot remove the VC. To successfully remove the VC, ensure that you re-deploy an NSX Manager node from the VC.

This restriction applies to a fresh installation of NSX as well as an upgrade.