Loading

Sorry

Your web browser doesn't support some required capabilities.

This interactive demo works best with the latest version of Chrome, Firefox, or Safari.

Sorry

An error occurred. Please reload the page or try a different browser.

Sorry

Sorry

Unable to initialize the simulation player:

Please reload the page or try a different browser.

X

This is an interactive demo

Drive it with your mouse, your finger, or just use the arrow keys.

Use Learn mode to learn the demo. The orange boxes show where to click.

Use Present mode to hide the orange boxes and notes.

Click a Shortcut to jump to a specific part of the demo.

X
Hide notes
Restore notes
Open notes window
Increase font size
Decrease font size

NSX Hybrid Connect

In this demo, you will see how NSX provides networking and security for workloads that have been migrated to VMC on AWS.  Hybrid connect supports migrations from vSphere to vSphere environments; however, many IT organizations are looking at a future leveraging public cloud services and this VM migration solution allows customers to move workloads from on-prem vSphere enviroments (with and without NSX) to a vSphere environment running in VMC in AWS, which as we'll learn, inherently enables networking and security services for these workloads with NSX.

Verify Environment

vSphere Configuration

First, take notice of the cluster details.  The vSphere cluster in Las Vegas has a few nodes running a number of virtual machines running the SQL service.

  1. Click on the home menu drop-down
  2. Click HCX

HCX Configuration

To verify the information shown in the cluster, and begin the actual migration of the virtual machines, next we will take a look through the various components that have been configured based on the current state of the environment.

  1. Notice the site pairing settings
    • Vegas DC --> VMC on AWS Oregon
    • Vegas DC --> Cordsshop DFW SDDC
  2. Click to scroll down
  3. Click to scroll down again
  4. Click to scroll back up to the top
  5. Click the Interconnect tab
    • Verify the details of created tunnels
    • Status = Tunnel is Up
  6. Click Extended Networks
    • Verify the details of source and destination networks

Migrate Workloads From On-prem to VMC on AWS

Migration Configuration

  1. Click Migration
  2. Click Migrate Virtual Machines
  3. Click the VMC on AWS - Oregon remote site
  4. Click and select the Database Server Pool
  5. Click VM Name selection box
  6. Click the Specify Destination Folder drop-down
  7. Click and select Workloads
  8. Click Select Folder
  9. Click the Specify Destination Container drop-down
  10. Click and select Compute-ResourcePool
  11. Click Select Destination
  12. Click the Select Storage drop-down
  13. Click and select WorkloadDatastore
  14. Click the Migration drop-down
  15. Click and select Cloud Motion with Replication Assisted vMotion
  16. Click the Next button
  17. Click the Finish button
  18. Wait a few moments while the migration completes
  19. Confirm all machines have successfully been migrated

Confirm Migration of Workloads to VMC on AWS

Now that we have completed the migration phase from the on-prem Las Vegas SDDC, we will confirm the configuration and availability details on the machines that have successfully moved to VMC on AWS.

The SQL VMs

  1. Press "TAB" to switch to the VMC browser tab
  2. Click the Cordsshop VMC SDDC link to view the VMC on AWS console. Verify the relevant environment detail
    • CPU/Memory/Storage configuration
    • Hosts details
  3. Click Networking and Security
  4. Verify the relevant details
    • SDDC Details
    • NSX Manager running
    • vCenter running
  5. Click on Distributed Firewall
  6. Click to expand HCX-Migrated-Protected-Workloads
  7. Verify the relevant ruleset information
  8. Click Back to List
  9. Click Open vCenter
  10. Click Compute-ResourcePool
  11. Click Database Server Resource Pool
    • Note all five SQL Virtual Machines been migrated and are powered/running

(End of Demo)

How likely is it that you would recommend this demo to a friend or colleague?
Not at all likely Extremely likely
Thanks, we appreciate your feedback!
Copyright © 2018 VMware, Inc. All rights reserved.