HOL-2181-01-HBD - VMware Hands-on Labs - Content Catalog

HOL-2181-01-HBD

Establishing a State ofHybridity (60 minutes)

H A N D S - O N L A B S M A N U A L - 2 0 2 12 0 2 1

Table of contentsTable of contents

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

What is the 'State of Hybridity'? .........................................................3

HCX Walkthrough .............................................................................4

Enterprise Migration........................................................................25

Zero downtime migration (vMotion) between On-Premises to Cloud

Instance .........................................................................................28

Bulk Migration between Cloud Instance to On-Premises ................... 41

Hands-on Labs Interactive Simulation: Bulk Migrations between Cloud

Instance to On-Premises ................................................................ 50

Zero downtime bi-directional migration without stretched layer 2

(Optional) ...................................................................................... 50

Conclusion..................................................................................... 50

Module 2 - Hybrid Disaster Recovery (DR) (30 minutes) 52

Introduction....................................................................................52

Setup Disaster Recovery Protection for a VM....................................52

Testing the Disaster Recovery Protection for the Protected VM .........67

Simulate, Recover and Reverse Replicate from a Disaster for the

Protected VM .................................................................................85

Introduction to Interactive Simulation: HCX for Disaster Recovery......99

Introduction to Interactive Simulation: SRM with HCX........................99

Conclusion......................................................................................99

Module 3 - Establishing a State of Hybridity 101

HCX Site Pairing ............................................................................ 101

Network Extension Setup ............................................................... 121

Module 4 - Migrating from Hyper-V to vSphere (15 minutes) 129

Introduction...................................................................................129

Hands-on Labs Interactive Simulation: Migrating from Hyper-V to

vSphere.........................................................................................129

HOL-2181-01-HBD: Establishing a State of Hybridity (60 minutes)

H A N D S - O N L A B S M A N U A L | 2

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

[2][2]What is the 'State of Hybridity'?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.

[3][3]OverviewOverview



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

1. HCX interconnect ServiceHCX 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-duplication and line conditioning. This makes performance closer to

a LAN environment.

2.Network Extension ServiceNetwork 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 ArchitecturesExplore 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 cloudsMigrate 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 MappingZero-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 Recoverysimplified and complete Disaster Recovery solution. For e.g. DR site can be a public cloud or another private cloud

across the WAN.

[4][4]Day-To-Day IT Operations Applicability of the State of HybridityDay-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.

[5][5]HCX WalkthroughHCX Walkthrough

In this section, we will familiarize ourselves with On-premises and Cloud vSphere Infrastructure specifics as well as explore the HCXplugin available within the On-Premises vSphere Instance.



[6][6]On-Premises and Cloud HCX WalkthroughOn-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 Region A and Region B before we do a HCX walkthrough.

[7][7]HOL Console ScreenHOL Console Screen

1. Make sure the lab is in ReadyReady state.

2.Double click on Google ChromeGoogle Chrome browser on the desktop.



[8][8]Login to vCenter Region ALogin to vCenter Region A

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

2.Username: [email protected]@corp.local

3.Password: VMware1!VMware1!

4.Click on LoginLogin

Note: For additional screen space, consider closing or pinning the Alarms, Work in Progress and Recent Tasks window's.



[9][9]Verify vCenter version for Region AVerify vCenter version for Region A

1. Go to MenuMenu

2.Click on Hosts and ClustersHosts and Clusters

3.Highlight vcsa-01a.corp.local



[10][10]Verify vCenter version for Region A continuedVerify vCenter version for Region A continued

Under Summary tab, you will see the Version information.In our lab you will see that vCenter is version 6.7version 6.7, however the source side for HCX supports versions back to 5.x.



[11][11]Verify ESX version for Region AVerify ESX version for Region A

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

2.Click on SummarySummary

3.Under SummarySummary find Hypervisor and verify ESXi version is 6.7.06.7.0



[12][12]Verify vSphere Instance in Region BVerify vSphere Instance in Region B

1. Open a newnew tab on the browser.

2.Click on Region B | vcsa-01bRegion B | vcsa-01b from the bookmarks toolbar.

[13][13]Verify vCenter version for Region BVerify vCenter version for Region B

vCenter Region B requires Flash so one must allow Flash to run in Chrome Webbrowser, follow the steps

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

2.Click icon on the top left corner, Get Adobe Flash Player

3.Click allow


H A N D S - O N L A B S M A N U A L | 1 0

https://vcsa-01b.corp.local/ui/



1. Verify the address as : https://vcsa-01b.corp.local/vsphere-client/?csphttps://vcsa-01b.corp.local/vsphere-client/?csp

2.Username: [email protected]@regionb.local





[14][14]Verify vCenter version for Region BVerify vCenter version for Region B

1. Go to Menu > Hosts and ClustersMenu > Hosts and Clusters

2.Click on vcsa-01b.corp.localvcsa-01b.corp.local on the left side

3.Go to SummarySummary

4.Expand Version Information and verify vCenter is version 6.0.0version 6.0.0



[15][15]Verify ESXi version for Region BVerify ESXi version for Region B

1. Expand datacenter RegionB01RegionB01

2.Expand cluster RegionB01-COMP01RegionB01-COMP01

3.Select host esx-01b.corp.localesx-01b.corp.local

4.Go to SummarySummary

5.Expand ConfigurationConfiguration Verify ESXi Version is 6.0.0.



[16][16]Access HCX PluginAccess 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 on RegionB site.

HCX is delivered via SaaS. The reason we have a plugin for VC is to simplify the workflows for customers without having to go tomultiple sites to access various functionalities.

To access the HCX plugin,

1. Stay at the Region-B vCenterRegion-B vCenter (source site) tab in Chrome

2.Click on MenuMenu

3.Click on HCXHCX from the Home menu on the right.



[17][17]DashboardDashboard

The Dashboard is your starting page. It provides a high-level of all HCX related activities in one single page.

1. Click on the DashboardDashboard tab. The above screenshot is for illustration purposes. The actual Dashboard would be empty now.

2.Cloud OverviewCloud Overview shows you -

◦Total # of VMs Migrated,

◦Migrations in Progress,

◦Migrations Scheduled and

◦# of Networks Extended.

3.Site PairingsSite Pairings

◦# of Sites that have been paired.

◦Starting place for new site pairing.



[18][18]InterconnectInterconnect

1. Click on the InterconnectInterconnect tab.

2.Click on the Service MeshService Mesh sub-tab. HCX Components will show up here once we deploy the HCX Fleet Services. (NOTE:(NOTE: In

this lab Service Mesh is already created).Service Mesh is already created).

[19][19]Extended NetworksExtended Networks

1. Click on the Network ExtensionNetwork Extension on the left navigation. Extended Networks will show up here. (NoteNote: In this lab NetworkNetwork

Extension is already configuredExtension is already configured)

Learn more about Extending the network in the next module.



[20][20]Migration ViewMigration View

1. Click on MigrationMigration from the left navigation. Your screen will not be empty like on the picture, because some migrations have

already been performed during lab development.



[21][21]Disaster Recovery ViewDisaster Recovery View

1. Click on DisasterDisaster RecoveryRecovery 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.



[22][22]AdministrationAdministration

1. Click on AdministrationAdministration from the left navigation.

◦All updates and patches are sent via web.

2.Click on the browser tabbrowser tab to create a new browser window and continue to the next page for more instructions.



[23][23]HCX Cloud Service Walkthrough (Cloud Portal)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 tomultiple sites to access various functionalities.

1. Open a new tab

2.Click on HCX-Connector-01bHCX-Connector-01b from the bookmarks toolbar. If not found, enter https://hcx-connector-01b.corp.local

3.Enter the username: [email protected]@regionb.local

4.Enter the password: VMware1!VMware1!

5.Click the LOG INLOG IN button. NOTE: It may take a few seconds to load the first time, please be patient.

[24][24]DashboardDashboard

You are now looking at the HCX Cloud Dashboard.



[25][25]Interconnect - Compute ProfilesInterconnect - Compute Profiles

1. Select InfrastructureInfrastructure under DashboardDashboard on the left navigation menu.

2.Select InterconnectInterconnect

3.Then select Compute ProfilesCompute Profiles on the right side

Here we can see the vSphere resources that we are connected to. Please note that due to the lab environment we use, we limitresources so more customers can get a chance to use the lab. Warnings can be safely ignored.



[26][26]Infrastructure - Interconnect - Network Profiles - NetworksInfrastructure - Interconnect - Network Profiles - Networks

1. Select InterconnectInterconnect from the left navigation.

2.With the InterconnectInterconnect already selected click Network ProfilesNetwork Profiles, we see some predefined networks.

[27][27]AdministrationAdministration



1. Select System UpdatesSystem Updates under AdministrationAdministration 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.

[28][28]ConclusionConclusion

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 start migrating VMs between the sites.

[29][29]Enterprise MigrationEnterprise Migration

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.



[30][30]Workload MigrationWorkload Migration

Migration of VMs typically fall in the following (or a variation of) 3 Operational Buckets -

1. Datacenter ConsolidationDatacenter Consolidation - Merger & Acquisition, Retiring of Datacenter space, upgrade of hardware/software infrastructure

platforms with HCI, etc.

2.Datacenter ReplacementDatacenter Replacement - Moving to a IaaS or modern Private Cloud.

3.Datacenter ExtensionDatacenter 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.

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.



[31][31]Migration With HCXMigration With HCX



With HCX, we are not only looking to solve this problem, but hybridity in general. Which is why -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 .

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.

[32][32]Zero downtime migration (vMotion) between On-Premises to Cloud InstanceZero downtime migration (vMotion) between On-Premises to Cloud Instance

In this lesson we will migrate a VM from Inventory in Region B to Region A while powered on.

[33][33]Migration OptionsMigration Options

This module provides two options to continue, option 1 is a simulated environment, option 2 provides a live configuration lab. Pleasepick 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 makethe configuration live in the lab.

Option 1Option 1. The interactive simulation will allow you to run through the steps in a controlled setting. If you proceed to do the lab versionthe steps may take 5-7 minutes to complete. In this simulation, you can use the software interface as if you are interacting with a liveenvironment.

1. Click here to open the interactive simulation. It will open in a new browser window or tab.

2.When finished, click the Return to the lab link to continue with this lab.

3.Go to Bulk Migration section to continue with the manual.

Option 2Option 2. Live configuration in the lab, go to the next page to continue with this.



http://docs.hol.vmware.com/hol-isim/hol-2021/hol-isim-player.htm?isim=HOL-2181-01-Mod-1-Zero-Downtime-Migrations.json

[34][34]Login to vCenterLogin to vCenter

We will begin by logging into the Region-B VC.







[35][35]Access Hybrid Cloud Services (HCX) PluginAccess Hybrid Cloud Services (HCX) Plugin

To access the HCX plugin:

1. Click the MenuMenu button

2.Click HCXHCX



[36][36]Verify Site PairingVerify Site Pairing

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 completedthe 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.



[37][37]Verify L2 Network StretchVerify L2 Network Stretch

Now we will verify that we have completed the L2 Network Stretch:

1. From the left navigation, select the Network ExtensionNetwork Extension item.

2.Expand the Port Group named HCX-Stretched-NetworkHCX-Stretched-Network by clicking on the triangle icon.

3.You will see the status Extension completeExtension complete stating that we have successfully extended the L2 Network Stretch from Module 1.

NOTE: L2 Network Stretch is optional for VM migration.



[38][38]Starting the MigrationStarting the Migration

1. Click on MigrationMigration from the left navigation.

2.Click on MigrateMigrate.



[39][39]Initial Migration OptionsInitial Migration Options

This screen allows us to select the combination of source / destination and choose a VM for us to proceed on specific details.

1. Select the connection "Source hcx-connector-01b / VC vcsa-01b.corp.local > Destination: hcx-cloud-01a / VChcx-cloud-01a / VC

vcsa-01a.corp.localvcsa-01a.corp.local

2.Enter a name for the group, such as Group2181

3.Check the box next to web-01a

4.Click the green ADD button.



[40][40]Configuring the Migration DetailsConfiguring the Migration Details

1. Check the checkboxcheckbox for VM web-01aweb-01a

2.For Specify Destination ContainerSpecify Destination Container select esx-01a.corp.localesx-01a.corp.local

3.For Specify Destination FolderSpecify Destination Folder select Discovered virtual machineDiscovered virtual machine.

4.From the dropdown menu for Select StorageSelect Storage, select HCX-DS-01aHCX-DS-01a.

5.From the dropdown menu for Select Provisioning TypeSelect Provisioning Type, select Same format as sourceSame format as source.

6.From the dropdown menu for Select Migration ProfileSelect Migration Profile, select vMotionvMotion.

7.Click ValidateValidate.



[41][41]Validate Migration RequestValidate 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 maycome up.

1. Select GoGo to start the migration.

2.Click CloseClose to exit this screen.



[42][42]Migration in ProgressMigration in Progress

1. Click the down arrowdown arrow to see updated progress.

2.Verify the Migration status is 'Migration Started''Migration Started'.

3.Click FinishFinish



[43][43]Migration is CompleteMigration is Complete

1. Click on RefreshRefresh and wait until the migration completes.

2.View Migration completedMigration completed status.

3.Clicking this icon will show you performance stats for the entire mobility group.



[44][44]View migrated VM at Region-AView migrated VM at Region-A

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 the first tabtab.

2.Verify you are on vcsa-01a.corp.localvcsa-01a.corp.local.

3.Enter the User name: [email protected]@corp.local

4.Enter the Password: VMware1!VMware1!

5.Click on LoginLogin to continue.



[45][45]View migrated VM at Region-AView migrated VM at Region-A

1. From the top, select the HomeHome menu.

2.From the Home Menu, select Host and ClustersHost and Clusters.

3.On the left navigation, expand out the arrows for vcsa-01a.corp.local, RegionA01,vcsa-01a.corp.local, RegionA01, and RegionA01-COMP01RegionA01-COMP01. Locate and click

on the VM, web-01aweb-01a. Note: This is the VM from RegionB via vMotion.

4.With the web-01a VM selected, on the right window select the SummarySummary tab. Here we see some summary details about the

web-01a VM. Notice it is running on Host esx-01a.corp.localesx-01a.corp.local where it was vMotioned.

Congratulations! You have vMotioned a VM from Region-B to Region-A successfully. In the next exercise, we will bulk migrate VMs, viavMotion.



[46][46]Bulk Migration between Cloud Instance to On-PremisesBulk 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.

[47][47]Login to vCenter Region BLogin to vCenter Region B



We will now go back to our vCenter for Region-B. If you still have your vSphere Web Client connected to Region-B vCenter, you mayskip this step. If not, please open a new Chrome browser tab:

1. Go to the address: https://vcsa-01b.corp.local/vsphere-client/?csphttps://vcsa-01b.corp.local/vsphere-client/?csp or click from the bookmarks toolbar on RegionB (vcsa01b)RegionB (vcsa01b).





To access the HCX plugin:

1. Click MenuMenu and then select HCXHCX from the drop down.



[49][49]Starting the MigrationStarting the Migration

1. Click on the MigrationMigration tab.

2.Click on MigrateMigrate button.



[50][50]Choose Reverse Migration and Source/DestinationChoose Reverse Migration and Source/Destination

1. Check the Reverse MigrationReverse Migration checkbox. We are now going to migrate VMs from RegionA01 back to RegionB01.

2.Click on the second Destination connector (hcx-cloud-01ahcx-cloud-01a / vcsa-01a.corp.local)/ vcsa-01a.corp.local)

Start all migrations from the enterprise plug in at the destination side. Even if we are doing a reverse migration.



[51][51]Choose the 2 VMsChoose the 2 VMs





1. Check the checkbox next to core-Acore-A VM to select it for vMotion.

2.Check the checkbox next to core-Bcore-B VM to select it for vMotion.

3.Click AddAdd

4.At the top there are universal migration options, the selections you make it will apply to all selected VMs. We will select

Discovered Virtual MachinesDiscovered Virtual Machines as Destination Folder.

5.We will select esx-01b.corp.localesx-01b.corp.local as our host to vMotion to (Destination Container).

6.For Storage, select HCX-DS01bHCX-DS01b.

7.For Provisioning Type, select Same format as sourceSame format as source.

8.For Migration Type, select BulkBulk MigrationMigration.

9.For both VMs core-A and core-B, select RegionB01-vDS-COMP/VM-RegionB01-vDS-COMPRegionB01-vDS-COMP/VM-RegionB01-vDS-COMP as the network to use.

10.We have 2 options to schedule. The default is ASAP. Alternatively you can schedule the migration for some point in the

future.

11.Click ValidateValidate to continue.

[52][52]Validating the MigrationValidating the Migration



Migration process is now being validated for the parameters that were passed. Note: If you happen to have some warning, you maysafely ignore them and proceed.

1. Click on GoGo to start the reverse bulk migration of VMs back to RegionB01.

[53][53]Migration in ProgressMigration in Progress

The Migration screen now shows the bulk migration in progress.

1. Click the RefreshRefresh 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.



[54][54]Migration is CompleteMigration is Complete

The Migration screen now shows the bulk migration in progress.

1. Click the RefreshRefresh 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.

[55][55]VerificationVerification



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-01b.corp.localvcsa-01b.corp.local, RegionB01RegionB01 Datacenter and RegionB01-COMP01RegionB01-COMP01.

2.Select the host esx-01b.corp.localesx-01b.corp.local. Note: Remember we reverse migrated the 2 VMs to this host.

3.On the right panel, select the tab Related ObjectsRelated Objects 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 A to Site B.

[56][56]Hands-on Labs Interactive Simulation: Bulk Migrations between Cloud Instance to On-PremisesHands-on Labs Interactive Simulation: Bulk Migrations between Cloud Instance to On-Premises

This part of the lab is presented as a Hands-on Labs Interactive SimulationHands-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 areinteracting with a live environment.


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.

[57][57]Zero downtime bi-directional migration without stretched layer 2 (Optional)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.


In this module, we walked through the HCX's Cross-Cloud Mobility Solution in its entirety, as well as:

•Establish bi-directional migrations.



http://docs.hol.vmware.com/hol-isim/hol-2021/hol-isim-player.htm?isim=HOL-2181-01-Mod-1-Bulk-Migrations-Between-Cloud-Instances-and-On-Premises.json

•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.

[59][59]Day-to-Day Applicability of this ModuleDay-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).

[60][60]You've finished Module 1You'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 MigrationModule 2 - Bi-Directional Cloud Migration (30 minutes) Zero downtime migration between on-premises and Cloud

•Module 3 - Hybrid Disaster Recovery (DR)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 Module 4 - Day 2 –– Monitoring and Operations with HCX 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 ENDEND button at the top right corner.



Module 2 - Hybrid Disaster Recovery (DR) (30 minutes)Module 2 - Hybrid Disaster Recovery (DR) (30 minutes)

[62][62]IntroductionIntroduction

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.

[63][63]What is Hybrid Disaster RecoveryWhat 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 andnetwork extended, the HCX platform can now be used to provide Active-Active protection for either Partial Recovery or Full Recoveryof 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 singlevirtual data center now is a reality, simplifying disaster recovery to the cloud.

[64][64]Setup Disaster Recovery Protection for a VMSetup Disaster Recovery Protection for a VM

In this lesson, we will configure disaster recovery protection for a VM



[65][65]Login to vSphere Client At Region BLogin to vSphere Client At Region B

1. Go to Chrome browser and click on RegionB,RegionB, click on vcsa-01b.vcsa-01b. Verify the address as : https://vcsa-01b.corp.local/vsphere-https://vcsa-01b.corp.local/vsphere-

client/?cspclient/?csp







To access the Hybrid Cloud Services (HCX) plugin:

1. Click on Menu at the top.

2.Click on HCX.



[67][67]Verify Site PairingVerify 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 completedthe 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.



[68][68]Verify L2 Network StretchVerify L2 Network Stretch

Now we will verify that we have completed the L2 Network Stretch:

1. Click on Network ExtensionNetwork Extension.

2.Click on the Port Group named RegionB01-vDS-COMPRegionB01-vDS-COMP by clicking on the triangle icon.

3.You will see the status Extension completeExtension complete stating that we have successfully extended the L2 Network Stretch from Module 1.



[69][69]Hosts and ClustersHosts and Clusters

1. Click on Hosts and Clusters.Hosts and Clusters.



[70][70]Enable DR Protection on VMEnable DR Protection on VM



1. Expand Datacenter RegionB01RegionB01

2.Expand Cluster RegionB01-COMP01RegionB01-COMP01

3.Right Click on VM app-01aapp-01a

4.Expand HCX ActionsHCX Actions

5.Click on Protect to HCX Target SiteProtect to HCX Target Site

[71][71]VM Replication DetailsVM Replication Details



1. Click Source DestinationSource Destination connector as marked above

2.Check the checkbox for VM Name app-01aVM Name app-01a

3.Expand the VM app-01aapp-01a

4.Select Destination Container as RegionA01-Comp01RegionA01-Comp01

5.Select Storage as HCX-DS-01a-1HCX-DS-01a-1

6.Select RPO as 15 minutes.15 minutes. Recovery Point Objective (RPO) is the maximum targeted period in which datadata might be lost from

an IT service due to a major incident. You can set the range betweenthe range between 5mins - 1 day.

7.Select Snapshots Interval as 1 hour.1 hour. Here we establish multiple recovery points. It can be configured between 1 hour - 7 days.

8.Select No. of Snapshots as 1 snapshot1 snapshot

9.Select HCX-Stretched-Network as L2E_VM-RegionB01-vDS-COM-1-10b3328aL2E_VM-RegionB01-vDS-COM-1-10b3328a

10.Click on Finish,Finish, you might need to scroll down to see next.

[72][72]Go To HCX PluginGo To HCX Plugin

1. Click on MenuMenu

2.Click on HCXHCX



[73][73]Go to Disaster RecoveryGo to Disaster Recovery

1. Select tab DisasterDisaster RecoveryRecovery

2.Local VMsLocal VMs show the following

1. Total # of VMs that are beingare 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 VMsRemote 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.ProgressProgress shows how many VMs are in the following state

1. Configuring

2.Syncing

3.Recovering

4.Testing

5.Cleaning



[74][74]DR Protection is ConfiguringDR Protection is Configuring

1. Currently the Status of the VM is ConfiguringConfiguring

[75][75]DR protection in ProgressDR protection in Progress

This process might take a few minutes.

You will see Detailed Status first move to Not Available,Not Available, to Protection Inactive,Protection Inactive, to Synchronization (Full)Synchronization (Full) and then finally to Active.Active.



[76][76]DR Protection is CompleteDR Protection is Complete

1. VM is now in ActiveActive State - DR Protection is active for this particular VM. This is represented by the green shieldgreen shield.

2.The yellow triangleyellow triangle means that this active VM has not been tested.

3.Green circleGreen circle represents a powered-on VM.

4.Direction of the arrowDirection of the arrow shows the direction of protection. In this case the VM is protected on the remote site.



[77][77]Lets look at Region ALets look at Region A

1. Open a new tab on the browser

2.From the bookmarks menu click on RegionA,RegionA, click on vcsa-01a (HTML)vcsa-01a (HTML)



[78][78]Login to Site ALogin to Site A

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






[79][79]Tasks on Region ATasks on Region A

1. Click on MenuMenu

2.Click on TasksTasks



[80][80]Verify Protection on Region AVerify Protection on Region A

1. Verify the task "Create virtual disk" is CompleteComplete. Do NOT close Region A tab.

Congratulations! You have enabled Disaster Recovery Protection for a VM. In the next exercise we will test this protection.

[81][81]Testing the Disaster Recovery Protection for the Protected VMTesting the Disaster Recovery Protection for the Protected VM

In this lesson, we will learn how to run the Test recovery and Test Cleanup for the Protected VM



[82][82]Login to HCX CloudLogin to HCX Cloud

We will now run Test Recovery on the protected VM on the Remote site.

If not yet open, open a new tab in the browser and click on hcx-connector-01bhcx-connector-01b from the bookmarks toolbar.

1. Enter username as [email protected]@regionb.local

2.Enter password as VMware1!VMware1!

3.Click LOG INLOG IN



[83][83]Go to the Disaster Recovery page on the left sideGo to the Disaster Recovery page on the left side

1. Click on ServicesServices tab

2.Click on DISASTER RECOVERYDISASTER RECOVERY from the left pane.

3.Local VMs here mean the VMs that are local to the Remote site.

4.Remote VMs are the VMs that are remote to the Remote Site (on-premises).

5.The arrow shows DR protection that is incoming to the Remote site.



[84][84]VM Disaster Recovery optionsVM Disaster Recovery options

1. Against the protected VM, Click on the 3 dots3 dots for more options.

2.The operations available to you are -

1. Recover VM (To recover a VM immediately)

2.Test Recover VM (Testing the protected VM on the recovery site to ensure its integrity/state)

3.Test Recover Cleanup (Removes the test VM)

4.Reverse (Change direction of replication)

5.Pause (In the event there is a planned event such as a maintenance window, this options help avoiding conflicts of

replicating at that point of time)

6.Resume (Resume the protection)

7.Remove (Remove the protection plan)

8.Sync Now (Force replication to trigger now)



[85][85]Run a Test RecoveryRun a Test Recovery

Click on Test Recover VM...Test Recover VM...



[86][86]Configure Test RecoveryConfigure Test Recovery

Review the settings and expand the list for TargetTarget network..



[87][87]Choose NetworkChoose Network

Select VM NetworkVM Network.



[88][88]Start Test RecoveryStart Test Recovery

1. Click on TestTest



[89][89]Test Recovery In ProgressTest Recovery In Progress

In the Detailed Status, you will notice Testing: Recovery in ProgressTesting: Recovery in Progress.

[90][90]DR Test Recovery CompleteDR Test Recovery Complete



This process will take a couple of minutes.

1. Detailed Status of the VM shows Completed testRecoverCompleted testRecover.

2.Number of tested VMsNumber of tested VMs under Remote VMs has changed. It now shows 1 of 1 VM tested.

3.Instead of the yellow triangle, there now is a certificate iconcertificate icon.

[91][91]VM Replication DetailsVM Replication Details

Expanding on >Expanding on > gives you more information on the Replication Status, Sites, History, Snapshots, etc



[92][92]Verify Test Recovery on Region AVerify Test Recovery on Region A

1. Go back to Site-A vCenter tab.Site-A vCenter tab. Make sure the web address is https://vcsa-01a.corp.local/vsphere-client/?csphttps://vcsa-01a.corp.local/vsphere-client/?csp

2.Select TasksTasks -> Verify Register virtual machine task is CompletedCompleted.



[93][93]Go to Hosts and Clusters view on Region AGo to Hosts and Clusters view on Region A

1. Click on HomeHome

2.Click on Hosts and ClustersHosts and Clusters



[94][94]Verify VM registered on Site AVerify VM registered on Site A

1. Verify the VM core-Bcore-B is registered and powered on at Site A.

Do NOT close the tab.



[95][95]Start DR Test CleanupStart DR Test Cleanup

Go back to HCX Cloud tab.

1. Click on ServicesServices

2.Click on DISASTER RECOVERYDISASTER RECOVERY

3.Click on the 3 dots.3 dots.

4.Click on Test Recover Cleanup....Test Recover Cleanup....



[96][96]DR Test CleanupDR Test Cleanup

Click on CleanupCleanup.

[97][97]DR Test Cleanup In ProgressDR Test Cleanup In Progress

The Status now reads Test Cleaning or Completed testCleanup.Test Cleaning or Completed testCleanup.



[98][98]DR Test Cleanup CompleteDR Test Cleanup Complete

The Status now reads Completed testCleanup.Completed testCleanup.



[99][99]Verify VM is unregistered at Region AVerify VM is unregistered at Region A

1. Go back to Region A tab.Region A tab. Make sure the web address is https:..vcsa-01a.corp.local

2.Verify the VM core-B is powered off and unregisteredcore-B is powered off and unregistered from Region A.



[100][100]Go to Tasks View at Region AGo to Tasks View at Region A

1. Click on HomeHome

2.Click on TasksTasks



[101][101]Verify DR Test Cleanup Task is Completed on Region AVerify DR Test Cleanup Task is Completed on Region A

1. Verify the UnregisterUnregister and PowerPower offoff tasks for VM core-Bcore-B at Site A is CompletedCompleted

Congratulations, you have successfully tested an actively DR Protected VM!!

[102][102]Simulate, Recover and Reverse Replicate from a Disaster for the Protected VMSimulate, Recover and Reverse Replicate from a Disaster for the Protected VM

In this lesson, we will simulate disaster on-premises site B, recover the VM in site A and later reverse replicate the VM to on-premisessite B.



[103][103]Login to vSphere Web Client on Region BLogin to vSphere Web Client on Region B

We will now simulate a Disaster event and recover the VM from the Remote site.







https://vcsa-01a.corp.local/vsphere-client/?csp

[104][104]Simulate DisasterSimulate Disaster

1. Click on Hosts and ClustersHosts and Clusters



[105][105]Power Off VMPower Off VM

1. Expand Datacenter RegionB01RegionB01

2.Expand Cluster RegionB01-COMP01RegionB01-COMP01

3.Right Click on VM core-Bcore-B

4.Select PowerPower

5.Click on Power OffPower Off



[106][106]Confirm Power Off VMConfirm Power Off VM

Click on YesYes

Wait for the VM to be powered off.



[107][107]Back To HCX Plugin At Region BBack To HCX Plugin At Region B

1. From HomeHome, click on HCXHCX

2.Click on tab Disaster RecoveryDisaster Recovery

3.The VM Status is now Protection InactiveProtection Inactive, represented by the red lightning iconred lightning icon.



[108][108]Configure Recovery Of VM from HCX Cloud PortalConfigure Recovery Of VM from HCX Cloud Portal

We will now go back to HCX Cloud Portal tab

1. Now expand the 3 dots3 dots against the VM and click on Recover VM...Recover VM...



[109][109]Recover the VM in CloudRecover the VM in Cloud

1. By Default it chooses the latest recovery point instancelatest recovery point instance.

2.Click on RecoverRecover.



[110][110]Recovery in ProgressRecovery in Progress

1. Detailed Status shows Recovering:Recovering: Recovery in Progress.

[111][111]Recovery is Complete on the Remote SiteRecovery is Complete on the Remote Site

1. The VM has successfully CompletedCompleted RecoverRecover. This is denoted by the dark grey shield icon.dark grey shield icon.



[112][112]Confirm core-B VM is running At Region AConfirm core-B VM is running At Region A

Switch to the tab running the vCenter from Region B and verify you see core-B running.

Congratulations, you have successfully recovered the VM on the Remote Site after a disaster!



[113][113]Go back to the HCX Plugin At Region BGo back to the HCX Plugin At Region B

1. Switch to Region B tabB tab. Confirm the web address is https://vcsa-01b.corp.local/vsphere-client

2.Click on HomeHome

3.Click on HCXHCX



[114][114]View Replication StatusView Replication Status

1. Click on Disaster RecoveryDisaster Recovery. You will notice the replication status as Completed Recover.Completed Recover.

[115][115]Start Reverse Replication of VMStart Reverse Replication of VM



VM is now running in Cloud. We will configure reverse replication of VM from Cloud to Region-B.

1. Click on 3 dots3 dots to get the options for the VM.

2.Click on ReverseReverse

[116][116]Configure Reverse ReplicationConfigure Reverse Replication

Click on ReverseReverse.



[117][117]Reverse Replication is ScheduledReverse Replication is Scheduled

1. In the Detailed Status notice the reverse replication is in Reverse ProtectingReverse Protecting mode.

[118][118]Reverse Replication is CompletedReverse Replication is Completed



1. VM's Detailed Status is Completed reconfigureCompleted reconfigure.

2.The arrows represents the reverse replication.reverse replication.

Congratulations! You have successfully Simulated a disaster, recovered and reverse replicated protection on a VM with HCX!

[119][119]Introduction to Interactive Simulation: HCX for Disaster RecoveryIntroduction to Interactive Simulation: HCX for Disaster Recovery





[120][120]Introduction to Interactive Simulation: SRM with HCXIntroduction to Interactive Simulation: SRM with HCX






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.

[122][122]Day-Day Applicability of this ModuleDay-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.



http://docs.hol.vmware.com/hol-isim/hol-2020/hol-isim-player.htm?isim=HOL-2081-01-M3_HCX_for_DR.htm

http://docs.hol.vmware.com/hol-isim/hol-2020/hol-isim-player.htm?isim=HOL-2081-01-M3-SRMwithHCX.htm

[123][123]You've finished Module 2You've finished Module 2

Congratulations on completing Module 2!!

If you are looking for additional information on HCX Cross-Cloud Mobility solution, please reach out to your sales team.

Proceed to fourth module below if it is of interest to you.

•Module 3 - Establishing a State of HybridityModule 3 - Establishing a State of Hybridity (15 minutes) iSIM to site pairing and Mesh Setup

In case you want to exit lab, please click on the ENDEND button at the top right corner.


H A N D S - O N L A B S M A N U A L | 1 0 0

Module 3 - Establishing a State of HybridityModule 3 - Establishing a State of Hybridity

[125][125]HCX Site PairingHCX 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 anddisaster recovery features..

Before we configure site pairing, let's take a detailed look at HCX deployment consideration and HCX components.

[126][126]HCX Design ConsiderationsHCX 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.



[127][127]HCX WAN Interconnect ComponentHCX WAN Interconnect Component

The HCX Interconnect (HCX-WAN-IX) component provides migration and cross-cloud vMotion capabilities over the internet and privatelines 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. TheRemote Site HCX InterconnectRemote Site HCX Interconnect (HCX-WAN-IX) appliance is created automatically when a local appliance is deployed.

HCX WAN Interconnect (CGW) Deployment ConsiderationsHCX 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.



[128][128]HCX WAN Optimization ComponentHCX WAN Optimization Component

The HCX WAN Optimization (HCX-WAN-OPT) service improves performance characteristics of the private lines or internet paths byleveraging 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 forDirect 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 pathfor virtual machine migrations.

HCX WAN Optimization Deployment ConsiderationsHCX 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 toservice chain the WAN-OPT



[129][129]HCX Network Extension ComponentHCX 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-Remote HCX-NET-EXTNET-EXT appliance is created automatically whenever a local appliance is deployed. The HCX-NET-EXT service appliance is alwaysdeployed as a service.



[130][130]Site Pairing OptionsSite Pairing Options

This module provides two ways to demonstrate site pairing: Option 1 is a simulated environment, Option 2 provides a live configurationlab. Please pick either Option 1 or Option 2.

Option 1.Option 1. Interactive simulation. You can use the link below to run through an interactive simulation. This interactive simulation alsoincludes 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 softwareinterface as if you are interacting with a live environment.


2.When finished, click the Return to the lab link.

3.Go to Module 2

Option 2Option 2. Live configuration in the lab, go to the next page to continue with this.

[131][131]Option 2. Live configuration in the lab. Login to Region B vCenterOption 2. Live configuration in the lab. Login to Region B vCenter



http://docs.hol.vmware.com/hol-isim/hol-2021/hol-isim-player.htm?isim=HOL-2181-01-Mod-3-HCX-Mesh-Setup.json

If you already have the vSphere Client up, you can skip this step. Go back to Region-B vCenterRegion-B vCenter tab.

1. Start the Chrome Browser from the desktop. Click on RegionB and Site-B vCenterSite-B vCenter. Verify the address as :

https://vcsa-01b.corp.local/vsphere-client/?csphttps://vcsa-01b.corp.local/vsphere-client/?csp

2.Enter Username: [email protected]@regionb.local

3.Enter Password: VMware1!VMware1!


[132][132]Return to the HCX DashboardReturn to the HCX Dashboard



1. Click MenuMenu

2.Click HCXHCX

[133][133]Site PairingSite Pairing

1. Select Site PairingSite Pairing from the left navigation menu.

2.In the middle of the page click Connect to Remote SiteConnect to Remote Site.



[134][134]Register new ConnectionRegister new Connection

Before any migrations can be done you will need to register the Public Cloud instance with the HCX Manager.

1. For the Remote Site URL type in hcx-cloud-01a.corp.localhcx-cloud-01a.corp.local

2.Enter the username [email protected]@corp.local

3.The password is VMware1!VMware1!

4.Click ConnectConnect



[135][135]Verify Remote Site PairingVerify Remote Site Pairing

1. New Site pairing would show the Remote Site Connection now.



[136][136]Service MeshService Mesh

1. With InterconnectInterconnect select from the left navigation.

2.Select Service MeshService Mesh in the sub tabs.

3.Click Create Service Mesh.Create Service Mesh.



[137][137]Select SitesSelect Sites

Verify the sites we want to connect.

1. Click Continue.Continue.



[138][138]Select Compute Profiles for SourceSelect Compute Profiles for Source

Select the Source Compute Profiles

1. Click the drop down menu for the Source Compute ProfileSource Compute Profile

2.Check the box next to connector-profileconnector-profile

3.Click CloseClose



[139][139]Select Compute Profile for RemoteSelect Compute Profile for Remote

1. Click the drop down menu for the Remote Compute ProfileRemote Compute Profile

2.Check the box next to cloud-profilecloud-profile

3.Click CloseClose

4.Click ContinueContinue



[140][140]Review the Services to be enabled.Review the Services to be enabled.

For our example, we will have all services enabled except the WAN Optimization Service.

1. Click ContinueContinue



[141][141]Review Network ProfilesReview Network Profiles

Review the Network profiles. We will leave the default.

1. Click ContinueContinue.



[142][142]Network Extension ScaleNetwork Extension Scale

Review the Network Extension Appliance Scale Out options. We'll leave the settings at the default.

1. Click ContinueContinue.



[143][143]Topology ReviewTopology Review



1. Click Continue



[144][144]NamingNaming

1. Enter a name for the Service Mesh, such as HOL-1HOL-1 or Interconnect-1

2.Click FinishFinish

It is normal for the deployment to take 5-9 minutes.



[145][145]Refresh pageRefresh page

1. Click on TasksTasks in the sub menu to see the list of ongoing tasks.

2.Click the arrow next to the Deploy taskDeploy task to expand the list

3.Click the arrow next to the Prepare Fleet PoolsPrepare Fleet Pools to expand the list and review.

4.Click the arrow next to the Appliance Deployment JobAppliance 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.



[146][146]Verify Components Deployed and Tunnel is UpVerify 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 RefreshRefresh 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 theOn-Premise Network to the Cloud.

[147][147]Network Extension SetupNetwork Extension Setup

In this lesson, we will extend network to the Cloud.




On Site-B vCenter, if you are not already in the HCX window, you can:

1. Click HCXHCX from the Home menu at the top.



[149][149]Extend NetworkExtend Network

In the HCX section, we will:

1. Click on Network ExtensionNetwork Extension from the left navigation.

2.Click on the Extend networkExtend network option.



[150][150]Extend Network to the CloudExtend Network to the Cloud



In the popup screen, we will configure the extend/stretch network to the cloud:

1. Click Source hcx-connector-01b / VC vcsa-01b.corp.localSource hcx-connector-01b / VC vcsa-01b.corp.local

2.From the EdgeEdge drop-down menu, select T1GWT1GW if not already selected

3.Select the line with the DPortGroupDPortGroup network,

4.Enter the following ip information under Gateway /Prefix length with 192.168.151.1/24192.168.151.1/24

5.Click the ExtendExtend button to complete the operationcomplete the operation to stretch the network to the cloud.

[151][151]Verify L2 Tunnel StatusVerify L2 Tunnel Status

1. Click on 'Refresh' until Status changes to

2.ExtensionExtension completecomplete.

3.View the Destination NetworkDestination Network name.

It will take few minutes for network extension to complete, please be patient.



[152][152]Go to vcsa-01a to verify Stretch NetworkGo to vcsa-01a to verify Stretch Network

1. Open a newnew tab on the browser.

2.Click on RegionA - vcsa-01a Web Client (HTML)RegionA - vcsa-01a Web Client (HTML) from the bookmarks toolbar.



[153][153]Login to vCenterLogin to vCenter

1. Enter username as [email protected]@corp.local

2.Enter password as VMware1!VMware1!

3.Click LOG INLOG IN



[154][154]View Stretch L2 NetworkView Stretch L2 Network

1. Click on esx-01a.corp.localesx-01a.corp.local from the left menu.

2.Click NetworksNetworks 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-RgionB01-vDS-L2E_VM-RgionB01-vDS-

COM-1-10b3328aCOM-1-10b3328a



Module 4 - Migrating from Hyper-V to vSphere (15 minutes)Module 4 - Migrating from Hyper-V to vSphere (15 minutes)

[156][156]IntroductionIntroduction

In this module we will walk through Migrating a Hyper-V based virtual machine to vSphere using VMware HCX.

[157][157]Hands-on Labs Interactive Simulation: Migrating from Hyper-V to vSphereHands-on Labs Interactive Simulation: Migrating from Hyper-V to vSphere







http://docs.hol.vmware.com/hol-isim/hol-2021/hol-isim-player.htm?isim=HOL-2181-01-Mod-5-Migrating-from-Hyper-V-to-vSphere.json

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 vmware.com.Copyright © 2021 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one ormore patents listed at vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. and its subsidiaries in the United States and other jurisdictions. All othermarks and names mentioned herein may be trademarks of their respective companies. Lab SKU: HOL-2181-01-HBD Version: 20210724-191413Lab SKU: HOL-2181-01-HBD Version: 20210724-191413

HOL-2181-01-HBD - VMware Hands-on Labs - Content Catalog

Documents