Hol-2081-01-Hbd

HOL-2081-01-HBD
Table of Contents
Lab Overview - HOL-2081-01-HBD - VMware HCX - Getting Started with Cross-Cloud
Mobility ............................................................................................................................. 2
Lab Guidance .......................................................................................................... 3
Introducing VMware HCX....................................................................................... 10
Module 1 - Establishing a State of Hybridity (60 minutes) .............................................. 14
What is the 'State of Hybridity'?............................................................................ 15
HCX Walkthrough .................................................................................................. 17
HCX Site Pairing .................................................................................................... 32
Network Extension Setup ...................................................................................... 47
Conclusion............................................................................................................. 53
Module 2 - Bi-Directional Cloud Migration (30 minutes).................................................. 54
Enterprise Migration.............................................................................................. 55
Zero downtime migration (vMotion) between On-Premises to Cloud Instance ...... 58
Bulk Migration between Cloud Instance to On-Premises ....................................... 69
Zero downtime bi-directional migration without stretched layer 2 (Optional)....... 76
Conclusion............................................................................................................. 77
Module 3 - Hybrid Disaster Recovery (DR) (30 minutes)................................................. 78
Introduction .......................................................................................................... 79
Setup Disaster Recovery Protection for a VM ........................................................ 81
Introduction to Interactive Simulation: HCX for Disaster Recovery ....................... 95
Introduction to Interactive Simulation: SRM with HCX .......................................... 96
Conclusion............................................................................................................. 97
Module 4 - OS Assisted Migration (15 minutes) .............................................................. 98
OS Assisted Migration ........................................................................................... 99
Hand-On Labs Interactive Simulation: OS Assisted Migrations............................ 100
Module 5 - Day 2 – Monitoring and Operations with HCX (15 minutes)......................... 102
Introduction......................................................................................................... 103
Hands-on Labs Interactive Simulation: Day 2 – Monitoring and Operations with
HCX ..................................................................................................................... 104
HOL-2081-01-HBD Page 1
HOL-2081-01-HBD
Lab Overview -
HOL-2081-01-HBD -
VMware HCX - Getting
Started with Cross-Cloud
Mobility
HOL-2081-01-HBD
Lab Guidance
Note: It will take more than 90 minutes to complete this lab.
Review the Table of Contents for an overview of all the modules (in the upper
right-hand corner of the Lab Manual).
Lab Abstract: Datacenter migrations are complex elongated processes. Moving to a

datacenter across the WAN is even more complicated. VMware Hybrid Cloud Services
allow efficient datacenter migration beginning at datacenter setup & design through
migrations leveraging VMware technologies such as Cross-Cloud vMotion. Learn about
VMware's SD-WAN technologies with high throughput Layer-2 Network Extension,
Disaster Recovery, Low/No Downtime Migration & optimized datacenter-to-datacenter or
datacenter-to-cloud connectivity.
In this lab we will explore VMware HCX, this game changing new Product offers
vSphere administrators a seamless method for extending an on-premises data center
and vSphere environments into HCX enabled private or public vSphere Cloud. The
Hybrid Cloud Manager offers hybrid networking and bi-directional workload migration
capabilities, simplifying resource integration and management of workloads. The Hybrid
Networking Services aspect of the offering consists of software- defined WAN
technologies that significantly improve the connectivity, resilience and security of
"middle mile" networking.
This Hands On lab mimics a Hybrid Cloud Infrastructure with an On-Premise vSphere
environment and Cloud vSphere environment.
On-Premise vSphere Environment:
• VC 6.7 (x1) (Can be a 5.x environment)

• ESX Host 6.7 (x2) (Can be a 5.x environment)
• Network IP range - 192.168.110.XXX
• Storage Datastores - Region01
Cloud vSphere Environment:
• VC 6.7 (x1)
• ESX Host 6.7 (x2)
• Network IP Range - 192.168.210.XXX
• Storage Datastores - Region02
Lab Module List:
• Module 1 - Establishing a State of Hybridity (60 minutes) (Basic)

◦ Simple setup of a SaaS-based Service Offering.
HOL-2081-01-HBD
• Module 2 - Bi-Directional Cloud Migrations (30 minutes) (Intermediate)

◦ Configure live migration and bulk migration of VM(s) between 2 vSphere-
based Clouds over the WAN. This module also covers an iSim to showcase
OS Assisted Migrations (OSAM), where we can migrate non-vSphere
workloads to vSphere.
• Module 3 - Hybrid Disaster Recovery (DR) (30 minutes) (Intermediate)

◦ Configure replication and test failover of a VM between 2 vSphere-based
Clouds over the WAN.
• Module 4 - Day 2 Monitoring and Operations (15 minutes) (Intermediate)

◦ iSIMs to showcase vROPS integration and how-to guides around auditing,
monitoring and troubleshooting.
Lab Captains:
• Module 1 - Alex Fanous, Staff Solutions Engineer, USA

• Module 2 - Alex Fanous, Staff Solutions Engineer; Metrri Jain, Staff NSX
Solutions Engineer, USA
• Module 3 - Metrri Jain, Staff NSX Solutions Engineer, USA
• Module 4 - Alex Fanous, Staff Solutions Engineer, USA
This lab manual can be downloaded from the Hands-on Labs Document site found here:
http://docs.hol.vmware.com
This lab may be available in other languages. To set your language preference and have
a localized manual deployed with your lab, you may utilize this document to help guide
you through the process:
http://docs.hol.vmware.com/announcements/nee-default-language.pdf
HOL-2081-01-HBD
Location of the Main Console
1. The area in the RED box contains the Main Console. The Lab Manual is on the tab
to the Right of the Main Console.
2. A particular lab may have additional consoles found on separate tabs in the upper
left. You will be directed to open another specific console if needed.
3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All your
work must be done during the lab session. But you can click the EXTEND to
increase your time. If you are at a VMware event, you can extend your lab time
twice, for up to 30 minutes. Each click gives you an additional 15 minutes.
Outside of VMware events, you can extend your lab time up to 9 hours and 30
minutes. Each click gives you an additional hour.
Alternate Methods of Keyboard Data Entry
During this module, you will input text into the Main Console. Besides directly typing it
in, there are two very helpful methods of entering data which make it easier to enter
complex data.
HOL-2081-01-HBD
Click and Drag Lab Manual Content Into Console Active

Window
You can also click and drag text and Command Line Interface (CLI) commands directly
from the Lab Manual into the active window in the Main Console.
Accessing the Online International Keyboard
You can also use the Online International Keyboard found in the Main Console.
1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.
HOL-2081-01-HBD
Click once in active console window
In this example, you will use the Online Keyboard to enter the "@" sign used in email
addresses. The "@" sign is Shift-2 on US keyboard layouts.
1. Click once in the active console window.

2. Click on the Shift key.
Click on the @ key
1. Click on the "@ key".
Notice the @ sign entered in the active console window.
HOL-2081-01-HBD
Activation Prompt or Watermark
When you first start your lab, you may notice a watermark on the desktop indicating
that Windows is not activated.
One of the major benefits of virtualization is that virtual machines can be moved and
run on any platform. The Hands-on Labs utilizes this benefit and we are able to run the
labs out of multiple datacenters. However, these datacenters may not have identical
processors, which triggers a Microsoft activation check through the Internet.
Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft
licensing requirements. The lab that you are using is a self-contained pod and does not
have full access to the Internet, which is required for Windows to verify the activation.
Without full access to the Internet, this automated process fails and you see this
watermark.
This cosmetic issue has no effect on your lab.
Look at the lower right portion of the screen
HOL-2081-01-HBD
Please check to see that your lab is finished all the startup routines and is ready for you
to start. If you see anything other than "Ready", please wait a few minutes. If after 5
minutes your lab has not changed to "Ready", please ask for assistance.
HOL-2081-01-HBD
Introducing VMware HCX
Has your team faced these Issues?
1. Incompatible, non-interoperable stacks in application dependency mapping

and migration planning, accounting for complex application infrastructure
architectures.
2. Cross-site networking and security issues that hold back adoption of cloud.
3. Application Dependency Mapping Delay
4. Business Disruption that require maintaining a secure off-premises 'Active'
infrastructure, resulting in potential capacity/resource wastage.
Where we've provided a multitude of options for consistent infrastructure across clouds
and platforms to optimize it, that doesn't solve for populating those clouds with existing
applications. Migrating applications to the cloud can be difficult without the right tool.
Today these problems are solved by investing people, resources and time to consume a
new piece of technology.
We think there is a better way of doing this.
HOL-2081-01-HBD
VMware HCX Provides
VMware HCX is designed specifically to address the problems. HCX provides a platform
for automating many of the manual tasks that app migration and mobility can present.
Use Case 1: Application Migration: Common scenarios include datacenter closures

where customers need to rapidly move out of a DC or Cloud environment for cost
reasons or quick consolidation. HCX can facilitate the movement of workloads and if
needed even upgrade vSphere versions as needed. Because of the way HCX stretches
networks from stack to stack or site to site, it is also an enabler for adoption of NSX.
Use Case 2: Workload rebalancing: Migration is not a one time event! The promise of
hybrid cloud and multi-cloud scenarios is that you can move workloads at will for scale,
cost management, replatforming, etc. As customers truly adopt multi-cloud, the ability
to actively rebalance workloads is becoming critical.
Use Case 3: Disaster Recovery: Leveraging a hybrid interconnect doesn't only have to
be for migration / rebalancing. You've got a common infrastructure in two or more
places and a permanent and secure pathway between them, why not use it for DR. HCX
can be used to backup workloads on demand for planned DR or migrate large numbers
of workloads in bulk to avoid natural disasters.
Furthermore, Operational Benefits of HCX:
1. Modernize your application infrastructure with minimal operational overhead.

2. Simple service-driven installation without the need to retrofit or upgrade a legacy
environment. No additional hardware or software infrastructure purchase
required!
HOL-2081-01-HBD
3. No products or appliances to manage – pure service-driven model; user signals

intent by checking the boxes across the services they need - WAN optimization,
encryption, vMotion and network extension services.
4. Operational focus is on the Project Outcome vs Product Install.
5. IP addressing schemes between source and destination can overlap and there's
no need to renumber or complex NAT.
6. Security domains remain separated – no approval to open internal protocols
between datacenters over Internet or private WANs.
What is Cross-Cloud/Site Mobility?
Cross-Cloud/Site Mobility is the capability to pair any cloud infrastructure together

and expect each cloud to act as an extension to the other(s). The HCX platform
becomes the basis on which Cross-Cloud/Site Mobility is provided by leveraging
infrastructure services (Any-Any vSphere Zero downtime migration, seamless Disaster
Recovery, enabling Hybrid Architectures, etc.) to provide tangible business value.
Please note that here Cloud/Site can be a public or private cloud.
HCX: Advanced
HOL-2081-01-HBD
HCX: Enterprise
HOL-2081-01-HBD
Module 1 - Establishing a
State of Hybridity (60
minutes)
HOL-2081-01-HBD
What is the 'State of Hybridity'?

In this module, you will -
• Understand how establishing the state of hybridity is the foundation for Cross-
Cloud Mobility.
• Understand the different IT operational scenario's where HCX can be applied to
solve today's Infrastructure problems and introducing new solutions such as,
hybrid datacenter architectures.
Overview
HCX's state of hybridity is made up of 2 primary components -
1. HCX interconnect Service

◦ The interconnect service provides resilient access over the internet and
private lines to the target site while providing strong encryption, traffic
engineering and extending the datacenter. This service simplifies secure
pairing of site and management of HCX components.
◦ WAN Optimization
▪ Improves performance characteristics of the private lines or internet
paths by leveraging WAN optimization techniques like data de-
HOL-2081-01-HBD
duplication and line conditioning. This makes performance closer to

a LAN environment.
2. Network Extension Service

◦ High throughput Network Extension service with integrated Proximity
Routing which unlocks seamless mobility and simple disaster recovery
plans across sites.
The operational advantages that the state of hybridity provides are many. Below are a
few -
1. Explore New Hybrid Datacenter Architectures. For e.g. DB tier on-premises

while App and Web tier in the public cloud, allowing to take advantage of price
and performance.
2. Migrate VMs between a mix of vSphere-based clouds and that are over the
WAN. For e.g. On-Premises vSphere/vCF Private Cloud and a vSphere/vCF Public
Cloud.
3. Take advantage of Zero-Downtime migrations and no Application
Dependency Mapping (ADM). For e.g. Datacenter consolidations require large
ADM exercises, as Production Apps reside in the to-be-retired-Datacenters. With
HCX, this will no longer be a concern.
4. Establish a simplified and complete Disaster Recovery solution. For e.g. DR
site can be a public cloud or another private cloud across the WAN.
Day-To-Day IT Operations Applicability of the State of

Hybridity
Below are a few benefits gained just from setting up the state of hybridity:
• Extend Existing Application and Networking Architecture for Production Apps over
the WAN.
• Explore and Add agile architecture for Production Apps by extending to Cloud.
• Catalog/Template Sync across on-premises private cloud and public cloud.
HOL-2081-01-HBD
HCX Walkthrough
In this section, we will familiarize ourselves with On-premises and Cloud vSphere
Infrastructure specifics as well as explore the HCX plugin available within the On-
Premises vSphere Instance.
On-Premises and Cloud HCX Walkthrough
In this exercise, we will do 2 things -
1. Record the On-Premises and Cloud vSphere Infrastructure specifics.

2. Familiarize ourselves with both On-Premises and Cloud HCX interfaces.
We will first review the underlying vSphere instances for both Site A and Site B before
we do a HCX walkthrough.
HOL Console Screen
HOL-2081-01-HBD
1. Make sure the lab is in Ready state.

2. Double click on Google Chrome browser on the desktop.
Login to vCenter
1. Verify the address as : https://vcsa-01a.corp.local/ui/

2. Username: administrator@corp.local
3. Password: VMware1!
4. Click on Login
Note: For additional screen space, consider closing or pinning the Alarms, Work in
Progress and Recent Tasks window's.
HOL-2081-01-HBD
Verify vCenter version for Site A (On-Premises)
1. Go to Menu
2. Click on Hosts and Clusters
3. Highlight vcsa-01a.corp.local
4. In our lab you will see that vCenter is version 6.7, however the source side for
HCX supports versions back to 5.x.
Verify vCenter version for Site A continued
Under Summary tab, you will see the Version information.
HOL-2081-01-HBD
Verify ESX version for Site A (On-Premises)
1. Select host esx-01a.corp.local

2. Click on Summary
3. Expand Configuration to verify ESXi version is 6.7.0
Verify vSphere Instance on Site B (Cloud)
1. Open a new tab on the browser.

2. Click on RegionB | RegionB vSphere Client (HTML) from the bookmarks
toolbar.
HOL-2081-01-HBD
Verify vCenter version for Site B (Cloud)
1. Verify the address as : https://vcsa-01b.corp.local/ui/

4. Click on Login
HOL-2081-01-HBD
Verify vCenter version for Site B (Cloud)
1. Go to Menu > Hosts and Clusters

2. Go to Summary
3. Expand Version Information and verify vCenter is version 6.7.0
Verify ESX version for Site B (Cloud)
HOL-2081-01-HBD
1. Expand datacenter RegionB01

2. Expand cluster RegionB01-COMP01
3. Select host esx-01b.corp.local
4. Go to Summary
5. Verify ESXi Version is 6.7.0.
Access HCX Plugin
This lab comes with HCX pre-installed on both the On-Premises, as well as the Cloud
vSphere instances.
We are now exploring the HCX plugin available within the On-Premises vSphere
Instance.
HCX is delivered via SaaS. The reason we have a plugin for VC is to simplify the
workflows for customers without having to go to multiple sites to access various
functionalities.
To access the HCX plugin,
1. Go back to the Site-A vCenter tab in Chrome

2. Click on Menu
3. Click on HCX from the Home menu on the right.
HOL-2081-01-HBD
Dashboard
The Dashboard is your starting page. It provides a high-level of all HCX related activities
in one single page.
1. Click on the Dashboard tab. The above screenshot is for illustration purposes.
The actual Dashboard would be empty now.
2. Cloud Overview shows you -
◦ Total # of VMs Migrated,
◦ Migrations in Progress,
◦ Migrations Scheduled and
◦ # of Networks Extended.
3. Site Pairings
◦ # of Sites that have been paired.
◦ Starting place for new site pairing.
HOL-2081-01-HBD
Interconnect
1. Click on the Interconnect tab.

2. Click on the Service Mesh sub-tab. HCX Components will show up here once we
deploy the HCX Fleet Services.
Extended Networks
1. Click on the Network Extension on the left navigation. Extended Networks will
show up here once we stretch the network further in the module.
Learn more about Extending the network in the next module.
HOL-2081-01-HBD
Migration View
1. Click on Migration from the left navigation. This shows all migration tasks
completed and in-progress. Your screen will be empty, but as you do some
vMotion in Module 2, you will see the details here.
Disaster Recovery View
1. Click on Disaster Recovery from the left navigation. This shows all DR specific
tasks in-progress and completed. Your screen will be empty, but as you do some
Disaster Recovery in Module 3, you will see the details here.
HOL-2081-01-HBD
Administration
1. Click on Administration from the left navigation.

◦ All updates and patches are sent via web.
2. Click on the browser tab to create a new browser window and continue to the
next page for more instructions.
HOL-2081-01-HBD
HCX Cloud Service Walkthrough (Cloud Portal)
This lab comes with HCX pre-installed on both the On-Premises, as well as the Cloud
vSphere instances.
We are now exploring the HCX website available within the Cloud vSphere Instance.
HCX is delivered via SaaS. The reason we have a plugin for VC is to simplify the
workflows for customers without having to go to multiple sites to access various
functionalities.
1. Click on HCX-Cloud-01b from the bookmarks toolbar. If not found, enter

https://hcx-cloud-01b.corp.local
2. Enter the username: administrator@corp.local
3. Enter the password: VMware1!
4. Click the LOG IN button. NOTE: It may take a few seconds to load the first time,
please be patient.
HOL-2081-01-HBD
Dashboard
You are now looking at the HCX Cloud Dashboard.
Services - Compute
1. Select Compute under Services on the left navigation menu.
Here we can see the NSX that we are connected to.
HOL-2081-01-HBD
Services - Networking - Networks
1. Select Networking from the left navigation.

2. With the Network tab already selected, we see some predefined networks.
Administration
1. Select System Updates under Administration from the navigation on the left.
NOTE: You can leave this browser tab open if you want. We may come back to this
browser window later.
HOL-2081-01-HBD
Conclusion
As you noticed, on-premises and cloud site are running with VMware vSphere. We have
now established that we have HCX pre-installed on both sites.
This ends the HCX Walkthrough exercise. In the next exercise, we will pair these 2 Sites
to establish the state of hybridity.
HOL-2081-01-HBD
HCX Site Pairing

In this exercise, we will be pairing our On-Premises vSphere Instance with the Cloud
vSphere Instance.
We are going to deploy the HCX Components which establishes the platform necessary
to provide the application portability and disaster recovery features.
Before we configure site pairing, let's take a detailed look at HCX deployment
consideration and HCX components.
HCX Design Considerations
• HCX Enterprise Manager is typically placed in the same compute/network/storage

resource objects as the vCenter server, and other management Virtual Machines.
• The HCX Enterprise Manager VM should be placed in a network that can make
internet-bound HTTPs connections and route internal connections to the ESX
Management network (if not placed directly on that network). Typically HCX
Manager in the same network as the vCenter server and other management
components.
• The HCX Enterprise Manager is deployed as a one-to-one pair with each vCenter
Server. The HCX Cloud Manager (the target site HCX Manager) can attach to
multiple vCenter Servers that are within a single physical datacenter.
• To integrate vCenter Linked-Mode, deploy HCX Manager as one-to-one pair with
each vCenter where HCX is desired; in the HCX Manager’s SSO configuration, the
shared Platform Services Controller (PSC) should be specified. HCX-Enabled
Linked-mode vCenters will display objects from all linked vCenters during HCX
Operations.
HOL-2081-01-HBD
HCX WAN Interconnect Component
The HCX Interconnect (HCX-WAN-IX) component provides migration and cross-cloud

vMotion capabilities over the internet and private lines to the target site while providing
strong encryption, traffic engineering and virtual machine mobility.
The HCX Interconnect Service (HCX-WAN-IX) appliance is always in the path for
replication-based and vmotion-based operations. The Remote Site HCX Interconnect
(HCX-WAN-IX) appliance is created automatically when a local appliance is deployed.
HCX WAN Interconnect (CGW) Deployment Considerations
• The HCX WAN Interconnect service appliance should be deployed in a cluster

where the HCX appliance will not be CPU/Memory resource constrained.
• It is recommended to have 100 Mbit of WAN bandwidth available for the HCX
WAN Interconnect's migration services.
HOL-2081-01-HBD
HCX WAN Optimization Component
The HCX WAN Optimization (HCX-WAN-OPT) service improves performance

characteristics of the private lines or internet paths by leveraging WAN optimization
techniques like data deduplication and compression.
This makes performance closer to a LAN environment. It accelerates on-boarding to the

cloud using Internet/VPN-without waiting for Direct Connect/MPLS circuits.
The HCX-WAN-OPT appliance is deployed "at-the-hip" of the HCX Interconnect. When

deployed –the component is always in the path for virtual machine migrations.
HCX WAN Optimization Deployment Considerations
• The HCX WAN Optimization service appliance should be deployed to the compute
zone, or network services cluster (or in a cluster where the HCX appliance will not
be CPU/Memory resource constrained.
• The HCX WAN Optimization service appliance should be deployed in performance
tier storage to ensure deduplication and WAN conditioning services operate
optimally.
The HCX WAN Optimization appliance does not need an IP address; HCX will use an
internal addressing configuration & network to service chain the WAN-OPT
HOL-2081-01-HBD
HCX Network Extension Component
HCX Network Extension (HCX-NET-EXT) provides a High Performance (4-6Gbps) Layer 2

extension capability.
• Use Extension with Migration to keep Virtual Machine IP and MAC addresses
during migration.
• Extend VLANS from VMware’s vSphere Distributed Switch.
• Extend VXLANs (Requires NSX integration in the HCX Appliance Management
interface)
• Extend Cisco’s Nexus 1000v networks
Deploying the Network Extension Service appliance will allow networks to be extended
in the vSphere Web Client. The Remote HCX-NET-EXT appliance is created
automatically whenever a local appliance is deployed. The HCX-NET-EXT service
appliance is always deployed as a service.
Site Pairing Options
This module provides two ways to demonstrate site pairing: Option 1 is a simulated
environment, Option 2 provides a live configuration lab. Please pick either Option 1 or
Option 2.
Option 1. Interactive simulation. You can use the link below to run through an
interactive simulation. This interactive simulation also includes the network extension
that the manual will complete in the next module.
The interactive simulation will allow you to run through the steps in a controlled setting.
In this simulation, you can use the software interface as if you are interacting with a
live environment.
1. Click here to open the interactive simulation. It will open in a new browser
window or tab.
HOL-2081-01-HBD
2. When finished, click the Return to the lab link.

3. Go to Module 2
Option 2. Live configuration in the lab, go to the next page to continue with this.
Option 2. Live configuration in the lab. Login to Site A

vCenter
If you already have the vSphere Client up, you can skip this step. Go back to Site-A
vCenter tab.
1. Start the Chrome Browser from the desktop. Click on RegionA and Site-A
vCenter. Verify the address as : https://vcsa-01a.corp.local/vsphere-
client/?csp
2. Enter Username: administrator@corp.local
3. Enter Password: VMware1!
4. Click on Login
HOL-2081-01-HBD
Return to the HCX Dashboard
1. Click Menu
2. Click HCX
HOL-2081-01-HBD
Site Pairing
1. Select Interconnect from the left navigation menu.

2. Select Site Pairs
3. In the middle of the page click Connect to Remote Site.
Register new Connection
Before any migrations can be done you will need to register the Public Cloud instance
with the HCX Manager.
HOL-2081-01-HBD
1. For the Remote Site URL type in hcx-cloud-01b.corp.local

2. Enter the username administrator@corp.local
3. The password is VMware1!
4. Click Connect
Verify Remote Site Pairing
1. New Site pairing would show the Remote Site Connection now.
HOL-2081-01-HBD
Service Mesh
1. With Interconnect select from the left navigation.

2. Select Service Mesh in the sub tabs.
3. Click Create Service Mesh.
Select Sites
Verify the sites we want to connect.
1. Click Continue.
HOL-2081-01-HBD
Select Compute Profiles for Source
Select the Source Compute Profiles
1. Click the drop down menu for the Source Compute Profile
2. Check the box next to enterprise-compute
3. Click Close
HOL-2081-01-HBD
Select Compute Profile for Remote
1. Click the drop down menu for the Remote Compute Profile
2. Check the box next to cloud-compute
3. Click Close
4. Click Continue
Review the Services to be enabled.
For our example, we will have all services enabled except the WAN Optimization Service.
1. Click Continue
HOL-2081-01-HBD
Review Network Profiles
Network Extension Scale
Review the Network Extension Appliance Scale Out options. We'll leave the settings at
the default.
1. Click Continue.
Topology Review
HOL-2081-01-HBD
Naming
1. Enter a name for the Service Mesh, such as HOL-1 or Interconnect-1

2. Click Finish
It is normal for the deployment to take 5-9 minutes.
HOL-2081-01-HBD
Refresh page
1. Click on Tasks in the sub menu to see the list of ongoing tasks.
2. Click the arrow next to the Deploy task to expand the list
3. Click the arrow next to the Prepare Fleet Pools to expand the list and review.
4. Click the arrow next to the Appliance Deployment Job to expand the list and
review.
Please be patient. It will take few minutes before the components are deployed and
ready to use.
HOL-2081-01-HBD
Verify Components Deployed and Tunnel is Up
Let's go back and verify if the HCX components are deployed and ready to use.
1. Click the Refresh icon at the top of the page.

2. Review that the service was deployed successfully.
Congratulations! You have deployed the HCX Components and established a SD-WAN
tunnel. In the next exercise, we will stretch the On-Premise Network to the Cloud.
HOL-2081-01-HBD
Network Extension Setup

In this lesson, we will extend network to the Cloud.
Access Hybrid Cloud Services (HCX) Plugin
On Site-A vCenter, if you are not already in the HCX window, you can either:
1. Click HCX from the Home menu at the top.
HOL-2081-01-HBD
Extend Network
In the HCX section, we will:
1. Click on Network Extension from the left navigation.

2. Click on the Extend network option.
HOL-2081-01-HBD
Extend Network to the Cloud
In the popup screen, we will configure the extend/stretch network to the cloud:
1. From the Edge drop-down menu, select gateway1 if not already selected
2. Select the line with the VM-RegionA01-vDS-COMP network,
3. Enter the following ip information under Gateway /Prefix length with
192.168.120.1/24
4. Click the Extend button to complete the operation to stretch the network to
the cloud.
HOL-2081-01-HBD
Verify L2 Tunnel Status
1. Click on 'Refresh' until Status changes to

2. Extension complete.
3. View the Destination Network name.
It will take few minutes for network extension to complete, please be patient.
Go to vcsa-01b to verify Stretch Network
1. Open a new tab on the browser.

2. Click on RegionB RegionB vSphere Client (HTML) from the bookmarks
toolbar.
HOL-2081-01-HBD
Login to vCenter
1. Enter username as administrator@corp.local

2. Enter password as VMware1!
3. Click LOG IN
HOL-2081-01-HBD
View Stretch L2 Network
1. Click on esx-01b.corp.local from the left menu.

2. Click Networks from the sub menu at the top
3. Verify the network name we saw in the previous steps is there. It should be
similar to L2E_VM-RgionA01-vDS-COM-0-ec20aaaf1
HOL-2081-01-HBD
Conclusion
In this module, we walked through the HCX's Cross-Cloud Mobility Solution in its
entirety, learned HCX site pairing and Network Stretch.
You've finished Module 1
Congratulations on completing Module 1!!
If you are looking for additional information on HCX Cross-Cloud Mobility solution, please
reach out to your sales team.
Proceed to any module below which interests you most.
• Module 2 - Bi-Directional Cloud Migration (30 minutes) Zero downtime

migration between on-premises and Cloud
• Module 3 - Hybrid Disaster Recovery (DR) (30 minutes) Protect, Recover and
Reverse replicate VM from on-premises to Cloud and back
• Module 4 - Day 2 – Monitoring and Operations with HCX (15 minutes) iSIM
to showcase vROPS integration and how-to guides around auditing, monitoring
and troubleshooting.
In case you want to exit lab, please click on the END button at the top right corner.
HOL-2081-01-HBD
Module 2 - Bi-Directional
Cloud Migration (30
minutes)
HOL-2081-01-HBD
Enterprise Migration
IMPORTANT: There is a dependency on Module 1 for this module. If you have
not completed module 1, please execute the PowerShell script to setup site-
pairing.
Go to Programs on the windows desktop, click on Windows PowerShell. At the command

prompt, type: hol\HCX\DoModuleOne.ps1, hit enter and follow the instructions. The
script will take 5-8 minutes to complete.
In this module, you will learn how to -
• Establish bi-directional migrations.

• Establish these migrations over the WAN, Internet or VPN.
• Enable and use zero-downtime and bulk migrations.
• Explore the Replication Assisted vMotion and day-day applicability of these
features.
Workload Migration
Migration of VMs typically fall in the following (or a variation of) 3 Operational Buckets -
1. Datacenter Consolidation - Merger & Acquisition, Retiring of Datacenter space,

upgrade of hardware/software infrastructure platforms with HCI, etc.
2. Datacenter Replacement - Moving to a IaaS or modern Private Cloud.
3. Datacenter Extension - Adopting a Hybrid Architecture (moving workloads that
require and take advantage of elastic public clouds),
Traditionally, all of the above require complex set of processes, purchase of additional
technology and investment in people. Typically, App Migration face the following
challenges -
1. Mission Critical Apps require migration without downtime.

2. And when these apps are migrated without downtime, they typically suffer from
performance degradation.
3. Given that during these migration windows, WAN and LAN traffic are negatively
impacted, a maintenance window with reduced usage of infrastructure is typically
outlined.
4. Migration windows are over multiple months due to size, distance and network
latency/loss.
5. Requires re-architecting a new IP platform for smooth switchovers requiring the
purchase of additional hardware or software.
6. Application rollback can be complex.
As you can see and have probably experienced, migrations pose complex problems that
require complex solutions. And usually, Complex = Expensive.
HOL-2081-01-HBD
In Todays Enterprise IT world, 3 types of Migrations are often considered.
1. Cold Migration - VM is powered-off. VMs moved to the destination Site. Templates

are a good example of workloads that require Cold Migration.
2. Warm Migration - VM is powered-on. VMs are snapshotted and kept in sync with
source site. When Source site is down, VMs are powered-on in last known good
state. Tier-2 Apps are a good example of workloads, that use this type of
Migration.
3. Zero-Downtime Migration - VM needs to remain powered-on. RPO/RTO
requirements require zero downtime. Any data-loss is unaffordable. Mission
Critical Apps require this type of migration.
Migration With HCX
With HCX, we are not only looking to solve this problem, but hybridity in
general. Which is why -
1. HCX enables zero-downtime migration without having to worry about IP re-

architecting.
2. HCX enables Bulk Migration at Scale. Workflows exist for moving 100s VMs in
parallel.
3. HCX works across the WAN and LAN, thereby enabling a unique model of
Infrastructure with a mix of Private, Public and Hybrid, based on the workload
requirements.
◦ HCX includes all components required for Migration and beyond .
HOL-2081-01-HBD
4. Network Stretching, Proximity Routing, Wan-OPT, Suite-B encryption, Traffic

Engineering are included.
5. HCX requires No DNS and SSL certificate changes, no app reconfig, simpler
rollbacks, no need for strict application groupings that are caused by non-
optimized WAN environments.
6. HCX works across any vSphere versions (vSphere version 5.x+), thereby not
requiring to you to invest in bringing both sites up to parity and enabling you to
modernize your datacenters with full SDDC/vCF stack, managed service or IaaS.
7. HCX enables you to seamlessly extend your network and thus your IP space,
extensively reducing the complexity and ensuring your IP Addressing policies,
security policy violations and administrative boundaries are not broken.
8. HCX is delivered as a service, not a product bundle – download small plugin (via
OVA) into vSphere, signal the intent via service-driven deployment forms where
you select which functions you want to use between sites and tether the sites
together. Frequent upgrades, no appliances to manage, ease of install and ease
of support.
9. HCX enables you to combine on and off-premises networks into a single
organizational network, you can still isolate individual workloads on that network
via SD-firewalling, ensuring that there are no security gaps.
HOL-2081-01-HBD
Zero downtime migration (vMotion)

between On-Premises to Cloud
Instance
In this lesson we will migrate a VM from Inventory in Site A to Site B while powered on.
Migration Options
This module provides two options to continue, option 1 is a simulated environment,

option 2 provides a live configuration lab. Please pick one of the two options. You can
use the link below to run through an interactive simulation or continue on to the next
page to make the configuration live in the lab.
Option 1. The interactive simulation will allow you to run through the steps in a
controlled setting. If you proceed to do the lab version the steps may take 5-10 minutes
to complete. In this simulation, you can use the software interface as if you are
interacting with a live environment.
window or tab.
2. When finished, click the Return to the lab link to continue with this lab.
3. Go to Bulk Migration section.
Option 2. Live configuration in the lab, go to the next page to continue with this.
HOL-2081-01-HBD
Login to vCenter
We will begin by logging into the On-premise (Site A) VC.
1. Verify the address as : https://vcsa-01a.corp.local/vsphere-client/?csp

4. Click on Login
HOL-2081-01-HBD
To access the HCX plugin:
1. Click the Menu button

2. Click HCX
Verify Site Pairing
HOL-2081-01-HBD
Before we do a VM migration, we want to make sure we have paired the 2 sites from the
previous Module 1 and also have completed the Layer 2 Network Stretch. The
requirement for VM Migration at a minimum is to have Site Pairing.
L2 Network Stretch is optional.
1. Verify the Site Pairing already exists from our previous Module 1. You may need to
scroll a bit down to see the Site pairings. If you have not done the Site Pairing,
please go back to Module 1 Site pairing before you can do a VM migration.
2. Validate that you also have a single Network Extension defined. On the next
page, we will see more details about this Stretched Network.
Verify L2 Network Stretch
Now we will verify that we have completed the L2 Network Stretch:
1. From the left navigation, select the Network Extension item.

2. Expand the Port Group named HCX-Stretched-Network by clicking on the
triangle icon.
3. You will see the status Extension complete stating that we have successfully
extended the L2 Network Stretch from Module 1.
NOTE: L2 Network Stretch is optional for VM migration.
HOL-2081-01-HBD
Starting the Migration
1. Click on Migration from the left navigation.

2. Click on Migrate Virtual Machines.
HOL-2081-01-HBD
Migration Screen Options
This screen shows the options available when starting a migration. The next two pages
will go over the specific settings needed for the migration we will perform. On the
Migrate Virtual Machines to Remote Site window:
1. The Top left side shows the paired remote site.

2. The left side shows the Source inventory (local site where plugin is installed).
3. Top Right side shows the global values that you can set for all your migration
initiating from this site. Global Value options are:
◦ Specify Destination Folder - It is Datacenter
◦ Specify Destination Container - Can be a cluster, ESX host or folder.
◦ Select Storage - Datastores that are available on the Remote Site.
◦ Select Provisioning Type - 3 Options. Same format as source, Thick
Provision or Thin Provision.
◦ Select Migration Type - vMotion or Bulk Migration.
Please continue to the next page of this lab manual.
HOL-2081-01-HBD
Source Inventory
1. You should see a VM named core-A at the bottom.

2. If needed, select RegionA01 from the left inventory.
Choosing VM to Migrate
1. Check the checkbox for VM core-A
HOL-2081-01-HBD
2. Expand the triangle next to VM core-A

3. For Specify Destination Folder select Discovered virtual machine.
4. For Specify Destination Container select esx-01b.corp.local
5. From the dropdown menu for Select Storage, select HCX-DS-01b-1.
6. From the dropdown menu for Select Provisioning Type, select Same format
as source.
7. For HCX-Stretched-Network, confirm L2E_VM-RegionA01-vDS-
COM-0-ec20aaf1 is selected
8. From the dropdown menu for Select Migration Type, select vMotion.
9. Click Next to continue.
Validate Migration Request
Before migrating the VM, validation is done to ensure the inputted parameters are
correct and migration can actually be completed. This check is done dynamically and
talks to both sides of the migration to verify the settings. You can ignore any warnings
that may come up.
1. Select Finish to start the migration.
HOL-2081-01-HBD
Migration in Progress
1. Click Refresh to see updated progress.

2. Verify the Migration info is listed as 'vMotion'.
3. Click Finish
Migration is Complete
HOL-2081-01-HBD
1. Click on Refresh and wait until the migration completes.

2. View Migration completed status.
View migrated VM at Site-B
Now we are going to connect to the Site-B vCenter to locate the VM Core-A that we
have vMotioned from Site A.
1. Select to create a new browser tab.

2. From the Bookmarks toolbar, click on Site-B vCenter.
3. Enter the User name: administrator@corp.local
4. Enter the Password: VMware1!
5. Click on Login to continue.
HOL-2081-01-HBD
View migrated VM at Site-B
1. From the top, select the Home menu.

2. From the Home Menu, select Host and Clusters.
3. On the left navigation, expand out the arrows for vcsa-01b.corp.local,
RegionB01, and RegionB01-COMP01. Locate and click on the VM, core-A.
Note: This is the VM from RegionA via vMotion.
4. With the core-A VM selected, on the right window select the Summary tab. Here
we see some summary details about the core-A VM. Notice it is running on Host
esx-02b.corp.local where it was vMotioned.
Congratulations! You have vMotioned a VM from Site A to Site B successfully. In the next
exercise, we will bulk migrate VMs, via vMotion, from Site B to Site A.
HOL-2081-01-HBD
Bulk Migration between Cloud Instance

to On-Premises
We will now do a bulk migration of the VMs from Remote site to the Source Site.
This migration method uses the VMware vSphere Replication protocols to move the
virtual machines to a remote site.
• The Bulk migration option is designed for moving virtual machines in parallel.
• This migration type can set to complete on a pre-defined schedule.
• The virtual machine runs at the source site until the failover begins. The service
interruption with bulk migration is equivalent to a reboot.
Login to vCenter
HOL-2081-01-HBD
We will now go back to our vCenter for Site-A. If you still have your vSphere Web Client
connected to Site-A vCenter, you may skip this step. If not, please open a new Chrome
browser tab:
1. Go to the address: https://vcsa-01a.corp.local/vsphere-client/?csp or click

from the bookmarks toolbar on Site-A vCenter.
4. Click on Login
To access the HCX plugin:
1. Click Menu and then select HCX from the drop down.
HOL-2081-01-HBD
Starting the Migration
1. Click on the Migration tab.

2. Click on Migrate Virtual Machines.
Choose Reverse Migration
1. Check the Reverse Migration checkbox. We are now going to migrate VMs from
RegionB01 back to RegionA01.
HOL-2081-01-HBD
Start all migrations from the enterprise plug in at the source side. Even if we are doing
a reverse migration.
Choose the 2 VMs
1. Check the checkbox next to core-A VM to select it for vMotion.

2. Check the checkbox next to core-B VM to select it for vMotion.
3. At the top there are universal migration options, the selections you make it will
apply to all selected VMs. We will select RegionA01 as Destination Folder.
4. We will select esx-01a.corp.local as our host to vMotion to (Destination
Container).
5. For Storage, select HCX-DS01a.
6. For Provisioning Type, select Same format as source.
7. For Migration Type, select Bulk Migration.
8. For both VMs core-A and core-B, select RegionA01-vDS-COMP/VM-
RegionA01-vDS-COMP as the network to use.
9. We have 2 options to schedule. The default is ASAP. Alternatively you can
schedule the migration for some point in the future.
10. Click Next to continue.
HOL-2081-01-HBD
Validating the Migration
Migration process is now being validated for the parameters that were passed. Note: If
you happen to have some warning, you may safely ignore them and proceed.
1. Click on Finish to start the reverse bulk migration of VMs back to RegionA01.
Migration in Progress
The Migration screen now shows the bulk migration in progress.
HOL-2081-01-HBD
1. Click the Refresh button sporadically to see any updates to the process.
Direction and color of arrow show the type of migration. Reverse migration from Remote
to Local.
• 'Rev' denotes reverse migration.

• 'Bulk' denotes Bulk migration of VMs
• 'vMotion' as before denotes emotion as the migration type.
Migration is Complete
The Migration screen now shows the bulk migration in progress.
1. Click the Refresh button sporadically to see any updates to the process.
Direction and color of arrow show the type of migration. Reverse migration from Remote
to Local.
• 'Rev' denotes reverse migration.

• 'Bulk' denotes Bulk migration of VMs
• 'vMotion' as before denotes emotion as the migration type.
HOL-2081-01-HBD
Verification
From the Hosts and Clusters view, we will verify if VMs were successfully migrated over
from the Remote site.
1. On the left menu, expand the arrows for vcsa-01a.corp.local, RegionA01

Datacenter and RegionA01-COMP01.
2. Select the host esx-01a.corp.local. Note: Remember we reverse migrated the 2
VMs to this host.
3. On the right panel, select the tab VMs for this host.
4. Notice the 2 VMs, core-A and core-B are located on this host just as we expected.
Congratulations! You have successfully bulk migrated both VMs from Site B to Site A.
HOL-2081-01-HBD
Zero downtime bi-directional migration

without stretched layer 2 (Optional)
Consider doing this optional exercise.
• Login to vSphere Client.

• Unstretch Network
◦ Go to HCX plugin > Interconnect > Extended Networks > Expand the
Network Stretch and Click on 'unstretch'.
• vMotion VM
◦ Follow similar workflow from previous exercise to vMotion VM from Site A
to Site B.
• vMotion back
◦ Follow similar workflow from previous exercise to vMotion VM from Site A
to Site B.
• Stretch Network
◦ Follow similar workflow from previous exercise (from Module 1) to stretch
network.
• Please continue with Module 3.
HOL-2081-01-HBD
Conclusion
In this module, you learnt how to
• Establish bi-directional migrations.

• Establish these migrations over the WAN, Internet or VPN.
• Enable and use zero-downtime and bulk migrations.
• Explore the Replication assisted vMotion and day-day applicability of these
features.
Day-to-Day Applicability of this Module
1. Non-disruptive vSphere Upgrade (from vSphere 5.x to vSphere 6.x+) into newer
hardware or public cloud.
2. Migration of Production Apps without the need for Application Dependency
Mapping.
3. Moving VMs between various cloud infrastructures for various IT operations tasks
such as (hardware refresh, switch upgrades, software upgrades/patches, etc).
Congratulations on completing Module 2.
Proceed to any module below which interests you most.
• Module 3 - Hybrid Disaster Recovery (DR) (30 minutes) Protect, Recover and
Reverse replicate VM from on-premises to Cloud and back
HOL-2081-01-HBD
Module 3 - Hybrid
Disaster Recovery (DR)
(30 minutes)
HOL-2081-01-HBD
Introduction
IMPORTANT: There is a dependency on Module 1 for this module. If you have
not completed module 1 or module 2, please execute the PowerShell script to
setup site-pairing.
Go to Programs on the windows desktop, click on Windows PowerShell. At the command

prompt, type: hol\HCX\DoModuleOne.ps1, hit enter and follow the instructions. The
script will take 5-8 minutes to complete.
In this module, you will learn -
• Multiple benefits of the Disaster Recovery Solution.

• How to Protect VMs for Disaster Recovery.
• How to Test recover, Test Cleanup, Recover and Reverse Replicate the VMs from
on-premises to cloud and back.
What is Hybrid Disaster Recovery
4 Key weaknesses that Enterprises face today when dealing with a disaster
1. There is no DR plan or is an afterthought.

2. The DR plan is inadequate.
3. The DR plan has not been updated for newer infrastructure and associated
changes in processes.
4. The DR plan is not properly tested.
HCX's introduces a new architecture in solving the age old problem of Disaster Recovery.
With the state of hybridity established and network extended, the HCX platform can now
be used to provide Active-Active protection for either Partial Recovery or Full Recovery
of BOTH VM workloads and Infrastructure.
With HCX's Hybrid Disaster Recovery solution, the following is possible -
1. Protect VMs on the primary (local) site to a secondary (remote) site.

2. Protect VMs from the secondary (local) site to the primary (remote) site.
3. Deploy Test and Planned Recovery from the remote site.
4. Reverse replicated the recovered VM to the local site.
5. Reconfigure protected VMs - to change RPO, etc.
6. Pause, Resume protected VMs - to account for maintenance windows, etc.
By adding Data Center Designer into the architecture, replicating/mirroring even the
most complex networking topologies into a single virtual data center now is a reality,
simplifying disaster recovery to the cloud.
HOL-2081-01-HBD
Illustration of Proximity Routing
In a partial failover scenario, tromboning (When users extend their networks to the
cloud, Layer 2 connectivity is stretched onto the cloud. However, without route
optimization, Layer 3 communication requests must return to the on-premises network
origin to be routed.) is a real problem.
HCX includes Proximity Routing to solve this problem.
In the diagram above, the N*a components on the left reside in the on-premises data
center, and the N*b component on the right reside in the cloud.
R1 is the default gateway for N1-b, therefore, N1-b must return to R1 to route traffic
through R2. To prevent asymmetric routing, HCX injects host routes into the on-premises
network.
1. If the virtual machine was newly created in the cloud, the host route is injected
immediately.
2. If the virtual machine was transferred using vMotion, the route is not injected
until the virtual machine reboots. Waiting until after the reboot ensure that the
on-premises stateful devices continue to service the existing session until the
virtual machine reboots. After the reboot, the routing information is consistent,
both on-premises and in the cloud.
That is, R1 can use routing to reach a specific virtual machine through R2, rather than
using the locally connected extended Network. R2 fully owns the path for other
networks to reach virtual machines with Proximity Routing enabled.
HOL-2081-01-HBD
Setup Disaster Recovery Protection for

a VM
In this lesson, we will configure disaster recovery protection for a VM
Login to vSphere Web Client At Site A
1. Go to Chrome browser and click on RegionA, click on RegionA vSphere Client

(HTML),. Verify the address as : https://vcsa-01a.corp.local/vsphere-
client/?csp
4. Click on Login
HOL-2081-01-HBD
To access the Hybrid Cloud Services (HCX) plugin:
1. Click on Menu at the top.

2. Click on HCX.
HOL-2081-01-HBD
Verify Site Pairing
Before we do a VM protection, we want to make sure we have paired the 2 sites from
the previous Module 1 and also have completed the Layer 2 Network Stretch. The
requirement for VM Protection at a minimum is to have Site Pairing.
1. Verify the Site Pairing already exists from our previous Module 1. You may need to
scroll a bit down to see the Site pairings. If you have not done the Site Pairing,
please go back to Module 1 Site pairing before you can do a VM Protection.
2. Validate that you also have a single Network Extension defined. On the next
page, we will see more details about this Stretched Network.
HOL-2081-01-HBD
Verify L2 Network Stretch
Now we will verify that we have completed the L2 Network Stretch:
1. Click on Network Extension.

2. Click on the Port Group named RegionA01-vDS-COMP by clicking on the
triangle icon.
3. You will see the status Extension complete stating that we have successfully
extended the L2 Network Stretch from Module 1.
Hosts and Clusters
1. Click on Hosts and Clusters.
HOL-2081-01-HBD
Enable DR Protection on VM
1. Expand Datacenter RegionA01

2. Expand Cluster RegionA01-COMP01
3. Right Click on VM core-A
4. Expand HCX Actions
5. Click on Protect to HCX Target Site
HOL-2081-01-HBD
VM Replication Details
1. Check the checkbox for VM Name core-A

2. Expand the VM core-A
3. Select Destination Container as RegionB01-Comp01
4. Select Storage as HCX-DS-01b-1
5. Select RPO as 15 minutes. Recovery Point Objective (RPO) is the maximum
targeted period in which data might be lost from an IT service due to a major
incident. You can set the range between 5mins - 1 day.
6. Select Snapshots Interval as 1 hour. Here we establish multiple recovery
points. It can be configured between 1 hour - 7 days.
7. Select No. of Snapshots as 1 snapshot
8. Select HCX-Stretched-Network as L2E_VM-RegionA01-vDS-COM-0-ec20af1
9. Click on Next, you might need to scroll down to see next.
HOL-2081-01-HBD
Reviewing the configured replication policy for protected

VM
Verify the details and Click on Finish
Go To HCX Plugin
1. Click on Menu
2. Click on HCX
HOL-2081-01-HBD
Go to Disaster Recovery
1. Select tab Disaster Recovery

2. Local VMs show the following
1. Total # of VMs that are being protected out of the Total # of VMs in the
local site.
2. It also shows the # of these protected VMs that have been tested thus far.
3. Remote VMs show the following

1. The # of VMs that the local site is protecting for the Remote Site.
2. It also shows the # of these protected VMs that have been tested thus far.
4. Progress shows how many VMs are in the following state

1. Configuring
2. Syncing
3. Recovering
4. Testing
5. Cleaning
HOL-2081-01-HBD
DR Protection is Configuring
1. Currently the Status of the VM is Configuring
DR protection in Progress
This process might take a few minutes.
You will see Detailed Status first move to Not Available, to Protection Inactive, to
Synchronization (Full) and then finally to Active.
HOL-2081-01-HBD
DR Protection is Complete
1. VM is now in Active State - DR Protection is active for this particular VM. This is
represented by the green shield.
2. The yellow triangle means that this active VM has not been tested.
3. Green circle represents a powered-on VM.
4. Direction of the arrow shows the direction of protection. In this case the VM is
protected on the remote site.
HOL-2081-01-HBD
Verify DR Protection at Site A
1. Click on Recent Tasks at the bottom.

2. Verify "Enable replication of virtual machine" is Completed.
Lets look at Site B
1. Open a new tab on the browser

2. From the bookmarks menu click on RegionB, click on RegionB vSphere Client
(HTML)
HOL-2081-01-HBD
Login to Site B
1. Verify the address as : https://vcsa-01b.corp.local/vsphere-client/?csp

4. Click on Login
HOL-2081-01-HBD
Tasks on Site B
1. Click on Menu
2. Click on Tasks
Verify Protection on Site B
1. Verify the task "Create virtual disk" is Complete. Do NOT close Site B tab.
HOL-2081-01-HBD
Congratulations! You have enabled Disaster Recovery Protection for a VM. In the next
exercise we will test this protection.
HOL-2081-01-HBD
Introduction to Interactive Simulation:

HCX for Disaster Recovery
This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will
allow you to experience steps which are too time-consuming or resource intensive to do
live in the lab environment. In this simulation, you can use the software interface as if
you are interacting with a live environment.
window or tab.
2. When finished, click the “Return to the lab” link to continue with this lab.
The lab continues to run in the background. If the lab goes into standby mode, you can
resume it after completing the module.
HOL-2081-01-HBD
Introduction to Interactive Simulation:

SRM with HCX
window or tab.
HOL-2081-01-HBD
Conclusion
You have learnt
• Multiple benefits of the Disaster Recovery Solution.

• How to Protect VMs for Disaster Recovery.
• How to Test recover, Recover and Reverse Replicate.
Day-Day Applicability of this Module
1. No longer need a dedicated DR site, as with HCX, the same VLANs can be
stretched to the cloud instance.
2. No Massive re-IPing or application dependency mapping exercise.
3. Bi-directional DR protection helps you make the most efficient hybrid cloud
architecture.
Congratulations on completing Module 3!!
Proceed to fourth module below if it is of interest to you.
HOL-2081-01-HBD
Module 4 - OS Assisted
Migration (15 minutes)
HOL-2081-01-HBD
OS Assisted Migration
In this module you will learn about OS Assisted Migration. The HCX OS Assisted
Migration service uses the Sentinel software installed on Linux or Windows-based guest
VMs to assist with communication and replication of guest VMs from their current
environment to a VMware vSphere SDDC.
HOL-2081-01-HBD
Hand-On Labs Interactive Simulation:

OS Assisted Migrations
live in the lab environment.
OS Assisted Migrations
OS Assisted Migrations enables users to seamlessly migrate VMs from non-vSphere

environments, like KVM to vSphere.
Here's a Brief Overview -
1. A small agent is installed at the source VM

2. HCX migrates the VM to vSphere
Key Use Case: Migrating off of non-vSphere environments.

HOL-2081-01-HBD
Launch Interactive Simulation
In this lab simulation, you can use the software interface as if you are interacting with a
live environment.
window or tab.

HOL-2081-01-HBD
Module 5 - Day 2 –
Monitoring and
Operations with HCX (15
minutes)

HOL-2081-01-HBD
Introduction
In this module we will walk through the insight vRealize Operations will give us when
paired with HCX.

HOL-2081-01-HBD
Hands-on Labs Interactive Simulation:

Day 2 – Monitoring and Operations
with HCX
window or tab.

HOL-2081-01-HBD
Conclusion
Thank you for participating in the VMware Hands-on Labs. Be sure to visit
http://hol.vmware.com/ to continue your lab experience online.
Lab SKU: HOL-2081-01-HBD
Version: 20191021-185918

Hol-2081-01-Hbd - PDF - en - HCX - LAB

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Hol-2081-01-Hbd - PDF - en - HCX - LAB

Transféré par

Droits d'auteur :

Formats disponibles

Lab Abstract: Datacenter migrations are complex elongated processes. Moving to a

On-Premise vSphere Environment:

• VC 6.7 (x1) (Can be a 5.x environment)

Cloud vSphere Environment:

Lab Module List:

• Module 1 - Establishing a State of Hybridity (60 minutes) (Basic)

• Module 2 - Bi-Directional Cloud Migrations (30 minutes) (Intermediate)

• Module 3 - Hybrid Disaster Recovery (DR) (30 minutes) (Intermediate)

• Module 4 - Day 2 Monitoring and Operations (15 minutes) (Intermediate)

• Module 1 - Alex Fanous, Staff Solutions Engineer, USA

Location of the Main Console

Alternate Methods of Keyboard Data Entry

Click and Drag Lab Manual Content Into Console Active

Accessing the Online International Keyboard

Click once in active console window

1. Click once in the active console window.

Click on the @ key

1. Click on the "@ key".

Notice the @ sign entered in the active console window.

Activation Prompt or Watermark

This cosmetic issue has no effect on your lab.

Look at the lower right portion of the screen

Introducing VMware HCX

Has your team faced these Issues?

1. Incompatible, non-interoperable stacks in application dependency mapping

We think there is a better way of doing this.

VMware HCX Provides

Use Case 1: Application Migration: Common scenarios include datacenter closures

Furthermore, Operational Benefits of HCX:

1. Modernize your application infrastructure with minimal operational overhead.

3. No products or appliances to manage – pure service-driven model; user signals

What is Cross-Cloud/Site Mobility?

Cross-Cloud/Site Mobility is the capability to pair any cloud infrastructure together

Please note that here Cloud/Site can be a public or private cloud.

What is the 'State of Hybridity'?

HCX's state of hybridity is made up of 2 primary components -

1. HCX interconnect Service

duplication and line conditioning. This makes performance closer to

2. Network Extension Service

1. Explore New Hybrid Datacenter Architectures. For e.g. DB tier on-premises

Day-To-Day IT Operations Applicability of the State of

On-Premises and Cloud HCX Walkthrough

In this exercise, we will do 2 things -

1. Record the On-Premises and Cloud vSphere Infrastructure specifics.

HOL Console Screen

1. Make sure the lab is in Ready state.

1. Verify the address as : https://vcsa-01a.corp.local/ui/

Verify vCenter version for Site A (On-Premises)

Verify vCenter version for Site A continued

Under Summary tab, you will see the Version information.

Verify ESX version for Site A (On-Premises)

1. Select host esx-01a.corp.local

Verify vSphere Instance on Site B (Cloud)

1. Open a new tab on the browser.

Verify vCenter version for Site B (Cloud)

1. Verify the address as : https://vcsa-01b.corp.local/ui/

Verify vCenter version for Site B (Cloud)

1. Go to Menu > Hosts and Clusters

Verify ESX version for Site B (Cloud)

1. Expand datacenter RegionB01

Access HCX Plugin

To access the HCX plugin,