Adding a Host

We recommend that you first add a vCenter Server as a host. When vCenter Server is added, CloudControl automatically imports all vCenter Server virtualized resources and managed ESXi hosts.

  1. Select Compliance > Hosts.

  2. On the Hosts page, click Add.

  3. In the Add Host Wizard dialog box, select the type of host that you want to add and click Next.

    • vCenter, vSphere Web Client Server, and VMware NSX—Adds a vCenter Server host, a vSphere Web Client Server host, and NSX Manager.

    • vSphere Web Client Server Only—Adds only a Web Client Server host.

      Note: For vSphere 6.0 and above, you cannot add only a Web Client Server (WCS) host. You can either add WCS with a vCenter host, or select Other Hosts.
      CloudControl automatically protects WCS for each vCenter added.

    • Other Hosts—Select this to add a host of any other type, such as unmanaged ESXi, or an ESXi host newly added to a protected vCenter.

  4. On the Host Login page, enter the following information: 

    • The fully qualified hostname or IP address of the host.

    • The service account name and password to be used for CloudControl. The service account must have admin privileges.

      Note: Passwords for hosts can contain either the left angle bracket (<) or the right angle bracket (>) characters, but not both.

  5. Optionally, expand the Advanced Properties section to view the VI SDK, HTTP, and HTTPS port settings. We recommend that you maintain the default settings.

    Note: Ports to communicate with vSphere 6.0 components through the firewall are:

    • CloudControl <-> WCS - 443 instead of 9443.
    • 443 is the preferred port though 9443 continues to be valid.
    • CloudControl <-> PSC - 444.
  6. Click Next.

    CloudControl attempts to automatically detect the host type. Supported host types are vCenter Server, ESXi, NSX and WCS.

  7. On the Host Details page, enter the following and click Next.

    • Friendly Name—A unique name to identify the vCenter Server, or the specified ESXi host, in the list of CloudControl hosts.

      This does not have to be the same name as used in DNS. Spaces and special characters are allowed, but the name should not exceed 64 characters.

    • Description—A description for the host.

    • Protected—Select this checkbox to have CloudControl protect both the vCenter Server, and the ESXi hosts it manages. This choice is selected by default.

  8. Click Next.

  9. On the Published IP (PIP) page, enter the following and click Next.

    • Published Hostname/IP—The hostname/IP address to use to route all traffic to this host.

    • Published IP Mask—The subnet mask to use to route all traffic to this host.

  10. If applicable, on the vSphere Web Client Server Configuration page enter the following and click Next.

    Field

    Description

    vSphere Web Client Server Hostname/IP

    The hostname/IP address of the Web Client server.

    User ID

    The service account to be used for CloudControl. The same account must be used across all vCenter Servers connected to the Web Client Server.

    Important: If you plan to use the NSX proxy in CloudControl, this account must be the same as the Service Account used to map NSX with vCenter at the infrastructure level.

    Password

    The CloudControl Service Account password.

    Https Service Port

    The Web Client Server HTTPS port number.

    Published vSphere Web Client Server Hostname/IP

    The published hostname/IP address for the Web Client Server. This should be the same as the PIP for vCenter.

    Published Netmask

    The published subnet mask for the Web Client Server.

  11. On the Authentication Mode Configuration page, enter the following and click Next.

    • Use CloudControl Service Account (default)—Select this to use the CloudControl Service Account for authentication when establishing sessions from CloudControl to vCenter Server. This is the default mode, and only one administrative account is required on vCenter Server.

    • Use Pass through without CloudControl Service Account—Select this to use the user’s account for authentication when establishing sessions from CloudControl to vCenter Server. In this mode, a vCenter Server account must be configured for each user.

    • Use Pass through with CloudControl Service Account—Select this to use the user’s account for initial authentication but use the CloudControl Service Account for all other operations. Select this mode if using Smart Card for authentication. Refer to the Smart Card Authentication section in the Administration Guide for HyTrust CloudControl for more information on Smart Card support.

  12. On the Complete Host Add page, click Finish.

Once you have successfully added a vCenter Server, it is displayed on the Hosts page along with any managed hosts. Protected hosts are shown with a gold shield () icon. Managed-hosts that require additional configuration before they can be protected are indicated by the blocked () icon. For more information, see Configuring Managed Hosts.

Note: In larger environments, the add host process can take several minutes, so it may take some time before all hosts are displayed on the Hosts page.