Adding an NSX-T Data Center to CloudControl

CloudControl learns about your NSX-T environment when you add a NSX-T Data Center.

  1. From the Home tab, select Inventory > NSX-T.

  2. On the NSX-T page, select Actions > Add NSX-T Data Center.

    Note: If there are no NSX-T Data Centers in your system, you can also click the Add NSX-T Data Center link on the NSX-T page.

  3. On the About page, complete the following: 

    Field

    Value
    IP/FQDN Enter the NSX-T Data Center address or FQDN.

    Port

    Enter the port used for the NSX-T Data Center, or accept the default.

  4. Select Service Account or Managed Credentials Account.

    For a Service Account: 

    Field

    Value

    Service Account

    The NSX-T Data Center service account to be used for CloudControl. The same account must be used across all NSX-T Managers, and it must have administrator privileges.
    Service Account Password

    The password for the NSX-T Data Center service account.

    For a Managed Credentials Account

    Field

    Value

    Account

    Select the managed credentials account that you want to use. If you have not yet created a managed credentials account, see Creating a Credential Management Account.
    Secret Name

    For Secrets Vault, this is the secret name to be used to access the secret in the format box:secret that be found in the KeyControl webGUI. Where 'box' is the name of the box that contains the secret, and 'secret' is the name of the secret. For example, box1:secret1.

    For CyberArk, this is the secret ID.

  5. Complete the following: 

    Field

    Value
    Published IP/FQDN The IP address or FQDN to use to route all traffic to this NSX-T Data Center.

    Published Netmask

    The subnet mask to use to route all traffic to this NSX-T Data Center.
  6. Click Continue. 
  7. Review the Certificate Details and click Approve.
  8. On the Details page, you can monitor the process as all of your NSX-T information is collected.
  9. Click Continue to view the dashboard for the newly added vCenters.

What to Do Next