VCD Hands-on Lab

This Hands-on Lab is designed to quickly enable you to setup a sandbox environment with no network segregation and DHCP. This will allow you to deploy the product and exercise the functionality. The intention is to effectively understand the value HDM has to offer for migration.

Lab Setup

Set up the Lab without any network segregation, with DHCP and connectivity to the target VCD cloud, as shown in figure 1.

Figure 1: Lab Connectivity Lab layout

  1. Set up the source environment.
    1. Set up a Single Network with DHCP service with IPs in 192.168.1.0/24
    2. Provision two servers with at least 96 GB RAM each.
    3. Deploy and configure the two ESXi (6.5U2+ or 6.7) with Management on the single network
    4. Deploy vCenter Server (6.5 or 6.7) and configure it over the single network.
    5. Add ESXi to vCenter.
    6. Provision shared datastore with at least 1 TB storage.
    7. Configure the two ESXi into a cluster
    8. Add the shared storage to the two ESXi within the cluster.

The on-premises configuration is now complete. To configure the target cloud:

  1. Set up networking on the target VCD
    1. In the next step you will create the required networks on the cloud target and set up an IPSec tunnel. If your VCD is within the Lab you can skip the IPSec tunnel configuration in the step below. Please make sure subnets on cloud side are not same as on-premises WAN subnet, use different network.
    2. Please follow the step in ORG VDC System and Network Configuration
    3. After the ORG VDC setup is complete, the networks will be configured on the target cloud and an IPSec tunnel will be connected to it.
    4. Set up a DHCP service on the UPLINK_WAN_NETWORK and the HDM_INTERNAL_NETWORK which was setup in step 1 with IPs in step#1.

Test the connectivity.

  1. Test to ensure that the VCD tenant portal can be accessed from the source environment.
  2. Deploy a TestVM(linux or windows) on the premises and cloud side, attach the respective WAN Network configured earlier.
  3. Test connection to the tenant portal from the TestVM.
  4. Try connection from premises VM to Cloud VM and reverse.
  5. If you are able to successfully connect, the setup is operational.

Download PrimaryIO HDM

To obtain your license and download link for HDM, visit https://www.primaryio.com/ibm/

You will receive an email with the following:

  • A link to download the PrimaryIO HDM software
  • A link to training videos
  • A license key for the software

Before proceeding with the installation, watch the training videos (https://www.primaryio.com/training/) and use this guide.

Deploy the HDM Appliance

  • Make sure you have at least 10GB of free space to download the appliance
  • Unzip the product zip file from the download link
  • Deploy the appliance using the vCenter UI
alt_text
  • Perform the step as directed by the UI.
  • Select Single Network created during lab setup.
  • Select IP Allocation as DHCP.
alt_text
  • Skip the Customize template.
  • Complete OVF deployment.
  • Power on the appliance.

Validate the Network Configuration

alt_text
  • All ESXi servers in vCenter should be connected
alt_text
  • The ESXi server must be able to communicate with vCenter. Test this using the ping command from the ESXi server to the vCenter FQDN (or IP)
  • Check to ensure the appliance is powered on

On-premises Deployment

Add on-premise vCenter

  • Locate the IP address of the appliance
  • Enter https://<appliance-ip> in the appliance web interface
  • Log into the appliance web UI using default password: 2Hdm$aK!N@h!
  • After login, select alt_text
alt_text
  • Select Add vCenter
alt_text
  • Enter the vCenter credentials
  • Select Add
alt_text Register the vCenter plugin by selecting Register

vCenter configuration is now complete. Log into the newly-configured vCenter.

Note: For the plugin to be visible within vCenter, you will need to logout and log back into vCenter at least twice.

Configure the License

Navigate to the Licensing page on the HDM vCenter Plugin

alt_text
  • The HDM plugin can be accessed directly via the Menu
  • It can take approximately five minutes to load HDM the first time it is accessed
  • On the Licensing tab, select Add License
  • Add the license key you received by email

Deploy HDM on-premises

alt_text
  • Select Administration, then Configuration
  • Choose the cluster where you want to install vCenter
  • Select Install
alt_text
  • For vCD, choose:
    • Resource: Ultra-Lite
    • Deployment: Cluster or Standalone
  • Only choose these options (this guide is only tailored to this configuration)
alt_text
  • Complete all steps to begin the deployment
  • Choose shared storage created during lab setup
  • Choose DHCP in all network configurations.
  • This step will take a few minutes to complete. Progress will be shown on the vCenter task bar.

Cloud Deployment

Configure Cloud vCenter

alt_text
  • Select Clouds, then Add Cloud
  • The cloud configuration wizard will pop-up automatically
alt_text
  • Choose vCloud Director
  • Enter vCD credentials
  • Select Add
  • Please note, it will take approximately five minutes to configure vCD and move to the next screen
alt_text
  • Choose vApp to deploy HDM cloud components
  • Choose the highest performance for rapid transfer
alt_text
  • For Parts 1 and 2, choose DHCP

WAN Routing Configuration

alt_text
  • Set the WAN subnet for the on-premises and cloud environments.
  • Set the gateway for both sides of the WAN.
  • DON'T Skip this step.
alt_text
  • Map the on-premises single network to UPLINK_WAN_NETWORK.
  • Depending on the chosen configuration and uplink speed, this step may require up to an hour to complete
alt_text
  • To ensure the deployment has been successful, select HDM from the Menu, followed by the Administration, HDM Health, and Component Health tabs
  • Check the status. If it is green, it is ready to begin migration.

Perform a Cold Migration

During cold migration, the VM being migrated is powered off. After the migration has been completed on the cloud, the VM can be powered back on.

NOTES:
Migrations will be successful for VMs where network and disk interfaces are accessible to HDM via VMware APIs.
If network or disk interfaces are added dynamically, the virtual machine will need to be powered down to allow 
the newly added network and disk interface information to become available to HDM via VMware APIs.
Before migration is triggered, ensure that the health of all HDM components is green.
alt_text
  • Right-click on the VM
  • Select Migrate
  • The migration wizard will pop-up automatically
alt_text
  • Complete all steps
alt_text
  • The migration status will be displayed in the wizard, as well as in vCenter Tasks
  • Following successful migration, the VM will be ready for use in the cloud
  • To migrate multiple VMs and the HDM dashboard, please refer to the HDM 2.2.1 Admin Guide