VCP-IaaS Study Notes: Section 1.2

This is Section 1.2 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

  • Identify components of vCloud Connector
  • vCloud Connector UI
  • vCloud Connector Server
  • vCloud Connector Nodes

  • Describe cross-cloud vApp flow
  1. Customer requests transfer using vCC UI.
  2. vCC Server tells Node to transfer vApp.
  3. Node tells vCenter Server to “export” using VIM API.
  4. Content is moved from datastores to source Node cache via vmkernel network.
  5. Content is transferred from source to destination Node via multipart using checkpoint-restart.
  6. Destination Node tells vCD to do an “import” using vCloud API.
  7. Content transfers from destination Node cache to vCD transfer server storage.
  8. vCD commands the appropriate vCenter import.
  9. Content transfers from vCD transfer server storage to destination datastore via vmkernel network and is made available through the vCD catalog.

  • Identify VM state (shutdown/power down)
    • Click workloads in the vCloud Connector GUI.
    • Select the appropriate entry
    • If you are changing the state of a vApp with multiple VMs, the status of the child VMs will not reflect their new state automatically. To see the updated status, refresh the screen.
  • Differentiate between functionality of components of vCloud Connector
    • vCloud Connector UI
      • vCloud Connector UI is the user interface that vCloud Connector Server produces. It can be surfaced in vSphere Client or at If you decide to display your UI via, and your vCC Server is behind a firewall, only browsers also behind the firewall can see the UI. You decide where to display the UI during the configuration process.
    • vCloud Connector Server
      • vCloud Connnector Server is a virtual appliance that coordinates the activity of vCloud Connector, controls vCloud Connector Nodes, and produces the vCloud Connector UI. Only one vCloud Connector Server is needed.
    • vCloud Connector Nodes
      • vCloud Connector Nodes are virtual appliances that handle transferring content from one cloud to another. Transfers between clouds that are interrupted, for example because of network problems, can be resumed at the point that they were interrupted. A vCloud Connector Node must be installed in every vSphere or vCloud cloud that vCloud Connector oversees.
  • Explain the relationship between the components of vCloud Connector
    • vCloud Connector Server is installed at local vSphere environment
      • Only one Connection Server is needed.
    • A vCloud Node is the installed in the local vSphere environment or the local private vCloud.
    • Another vCloud node is installed at a public vCloud.
    • The GUI is either accessible through the vSphere client or
      • There you manage your vCloud connections and do your copy tasks between vClouds.
  • Determine and implement required network and security settings
    • These ports need to be open in NAT connection in the vCloud
      • Port 8443: For communication between vCC Server and Node and between Nodes.
      • Port 5480: For communication with the Web admin interface for the appliance, for example during the registration process.
    • You can change the password, adjust log levle and manage SSL certificates in the Connector Server
    • You will need to replace the self signed SSL certificates before production use.
  • Determine storage requirements and add storage for use by a vCC node
    • Copy operations rely on staging storage when you copy resources between clouds. To successfully copy resources, make sure you have enough storage in your vSphere and vCloud Director clouds. Default storage on Nodes is 40 GB. You may need to increase this if you will be copying large VMs or templates or if you will be copying many items simultaneously.
    • Pre-req
      • Take a snapshot of the appliance
    • In vSphere
      • Add a second hard drive to the VM
      • Go to console and run: sudo /opt/vmware/hcagent/scripts/
    • In vCloud
      • Turn off VM in vApp
      • Select properties ->Hardware->Add->Disk.
      • Power on VM – Open console
      • Logon – admin/vmware
      • Name the new disk, command: ls /dev/sd*
      • Add the new disk, command: sudo /opt/vmware/hcagent/scripts/ <diskname>
  • Register vCloud Connector with vCenter Server
    • In the vCloud Connector GUI click the vSphere Client button
    • Fill in the information
      • IP and name og vCC server and vCenter, user and pw for vCenter.
    • If you previously registered a vSphere client you can choose: Overwrite existing registration
    • Click register.

About larushjartar
VMware Specialist and IBM Technician.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: