VMware vSphere Installation

VMware Nuances

Verify the following VMware nuances:

  • Ensure to use Version 6.0 and higher.
  • Verify that you have sufficient shared storage between hosts.
  • You must have privileges to launch a VM and access the selected DC/Datastore.
  • Your datacenter must exist at the root level.

    Be aware that CloudCenter Suite does not support folders at the root level.

  • Network Time Protocol (NTP) must be configured – this is important as the CloudCenter Suite installation can fail, if NTP is not configured or if it is wrongly configured.

    If you setup CloudCenter Suite in offline mode, you must provide valid NTP server details before you save your configuration.

  • In CloudCenter Suite 5.1 and earlier, if your environment has strict URL rules that redirects (for example, using a shorter URL that redirects to https://storage.googleapis.com) the configured URL, you may not be able to complete the installation as these kind of redirects may not be allowed if you have installed the repository in an offline cluster. As the offline solution is not completely air gapped in CloudCenter Suite 5.0 and 5.1, you must added these URLs to your allowed lists behind the firewall so you can access these sites.

    The installation process assumes internet connectivity to certain domains.  When installing CloudCenter Suite into environments residing behind a proxy, please ensure the following domains are entirely accessible.  Remember the proxy information - this will be used during the installation of CloudCenter Suite.

    Note: The Installer VM supports HTTP and HTTPS proxies, with or without username and password.  The proxy must support TLS 1.2.

    Warning: Several of the following links might perform redirects.  Please ensure your proxy and firewall are configured to allow redirects of the following URLs. 

    Proxy URLDescription





    Repository for Cisco CloudCenter Suite Docker Charts



    Repository for Cisco CloudCenter Suite Helm Charts



    Repository for Cisco CloudCenter Suite Tiller Image
    OtherThe Suite Installer may require additional connections to the installation environment (for example, vCenter, Hyperflex Data Platform, AWS Console, and so forth)  Please ensure your cloud target is reachable via the proxy!
  • For CloudCenter Suite to use a particular user account in VMware, that account must have the permissions identified in the table below.

    vCenter ObjectRequired PermissionReason
    NetworkAssign NetworkIf the default network in a template/snapshot must be changed

    Allocate space

    For persistent disk operation

    Browse datastore
    Low level file operations
    Remove file
    FolderCreate folderFor user folder creation

    Apply recommendation

    For datastore cluster support
    Assign VM to resource poolFor resource pool selection

    Create task

    For VM operation

    Update task
    Virtual MachineAll permissions
    Global RoleSet Custom AttributesTo add custom attributes on virtual machines
    Manage Custom Attributes
  • Additionally, refer to your module documentation for module-specific dependencies:

    Workload ManagerCloud Overview
    Action OrchestratorAdd Cloud Account
    Cost OptimizerCloud Overview

Installation Process

To install the CloudCenter Suite on a new vSphere cluster, perform the following procedure. 

  1. Verify that you have prepared your environment as listed in the VMware Nuances section above.
  2. Navigate to the Suite Installer Dashboard.

  3. Click Get Started in the New Kubernetes Cluster tile to create a new Kubernetes cluster and install the Suite Admin on it.
  4. Click vSphere and enter your vSphere credentials and click Connect.

    vCenter DetailsDescription
    vCenter HostThe IP address or hostname of the vSphere setup
    vCenter UsernameThe username to be used for the vSphere setup
    vCenter PasswordThe password to be used for the vSphere setup

  5. Once the connection is validated, click Next.

  6. To specify the placement properties, enter the following details.

    vCenter DetailsDescription
    ClusterThe cluster to deploy the node in the above datacenter.
    Resource PoolThe resource pool used to deploy the node.
    DatastoreThe datastore cluster to associate with the node.
    NetworkThe network cluster to associate with the node.
    FolderThe folder from which the cluster node is selected.
    Node PrefixAny user-defined prefix.
    Virtual Appliance Template FolderThe folder containing the template to launch the Kubernetes cluster nodes.
    Virtual Appliance Template Name

    The name of the installer VM Template that you created earlier and from where you launched the Suite Installer – use this same template to create worker VMs.

    See VMware vSphere Appliance Setup for dependent details on creating the Suite Installer Virtual Appliance.

    IP Allocation ModeThis switch allows you to select the mode:
    • DHCP: This strategy allows the IP to be allocated by the DHCP server to the instance on server boot up. This IP address is not known prior to server boot up.

    • Static IP: This strategy allows the customer to provide the IP address. As this IP address may or may not be available to the server (based on the availability), you must perform adequate checks to ensure IP availability before using this strategy.

    Instance TypeSelect the minimum Hardware Requirements based on your setup requirements. Based on your selection, the system automatically calculates the required instance type.

  7. Specify the NTP Configuration details:

    If you setup CloudCenter Suite in offline mode, you must provide valid NTP server details before you save your configuration.

    NTP detailsDescription
    NTP ServersThe list of IP addresses or FQDNs of your NTP server(s) – to be used to sync VM clocks.
    NTP PoolsThe list of IP addresses or FQDNs of your NTP pools.

  8. Conditional if using Static IP. 

    1. The Start IP and End IP for the Static IP Pool range should be large enough to cover the following VMs:

      1. 3 primary servers

      2. 1 Load Balancer

      3. Number of Worker VMs used in your environment

        The Number of Worker VMs depends on the selected instance type. For example:

        • If the instance type is large (8 CPU, 32GB memory), then 4 workers are created and the total static IPs required for this environment are 8 IPs (4 worker VMs, 3 primary servers, and 1 load balancer).

        • If the instance type is large (8 CPU, 24GB memory), then 5 workers are created and the total static IPs required for this environment are 9 IPs (5 worker VMs, 3 primary servers, and 1 load balancer).

        • If the instance type is large (8 CPU, 16GB memory), then 7 workers are created and the total static IPs required for this environment are 10 IPs (6 worker VMs, 3 primary servers, and 1 load balancer).

        • If the instance type is smaller (4 CPU, 16GB memory), then 8 workers are created, so the static IPs required for this environment are 12 IPs (8 worker VMs, 3 primary servers, and 1 load balancer).

        Accordingly, select the IP range by taking into consideration the Number of Worker VMs that will be created based on instance type.

        This is just an example, be aware that different datacenters will have different instance types configurations and dependencies.

        To determine the number of workers select the instance type in the CloudCenter Suite installer, the Number of Worker VMs are calculated and displayed at the bottom of the instance field as displayed in the following screenshot.

    2. If you need to scale up nodes after setting up the Suite Admin, then you must ensure a wider range:

      1. If you plan to scale up by one node and you have already selected the instance type such that 8 worker VMs are created, then the valid static IP range must be to (or higher, depending on the scale up number).

      2. In this example:

        1. The worker VMs will consume 8 IPs, the primary server VMs will consume 3 IPs, and the load balancer will consume 1 IP.

        2. Additionally, you need to scale up by one node which will consume 1 more IP, making taking the total to 13 IPs.

        3. These IPs should be available for allocation – they should not have been allocated to any other VM or resource.

  9. Click InstallThe installation progress is visible on screen. 

  10. Once successful, you see the following message.

  11. You have the following options at this point:

    1. Click Take Me To Suite Admin to launch and set up the Suite Admin.
    2. Click Install Another Cluster to start another installation and go back to the homepage (Installer Dashboard).

    3. Download Kubeconfig file to connect to the launched cluster using the kubectl tool.

    4. Download SSH private key to SSH into your cluster node on private clouds – each time you launch a new cluster using the installer, the CloudCenter Suite generates a new key-pair for that cluster. 

      For private clouds, the download link for the SSH private key is available on the last page of the installer UI as displayed in the following screenshot.

  12. Be sure to switch off the installer VM. You can reuse this VM for any other purpose, for example, as an Offline Repository.
Terms & Conditions Privacy Statement Cookies Trademarks