You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/azure/migrate-vmware-workloads-on-premises-azure-vmware-solution/3-vmware-hcx-deployment-installation.yml
Copy file name to clipboardExpand all lines: learn-pr/azure/migrate-vmware-workloads-on-premises-azure-vmware-solution/4-configure-networking-compute-profiles.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ metadata:
5
5
unitType: learning-content
6
6
title: Configure networking and compute profiles for VMware HCX
7
7
description: Configure networking and compute profiles for VMware HCX.
Copy file name to clipboardExpand all lines: learn-pr/azure/migrate-vmware-workloads-on-premises-azure-vmware-solution/7-knowledge-check.yml
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ metadata:
5
5
unitType: knowledge_check
6
6
title: Module assessment
7
7
description: Knowledge check.
8
-
ms.date: 08/01/2024
8
+
ms.date: 06/19/2025
9
9
author: Orin-Thomas
10
10
ms.author: orthomas
11
11
ms.topic: unit
@@ -44,7 +44,7 @@ quiz:
44
44
explanation: "Port 443 needs to be open between the on-premises VMware HCX Connector and the VMware HCX Cloud Manager environment in Azure VMware Solution."
45
45
- content: "3389"
46
46
isCorrect: false
47
-
explanation: "Port 3389 is for Remote Desktop Protocol, and doesn't have to do with the HCX Connector on-premises routing traffic to the VMware HCX Cloud Manager environment."
47
+
explanation: "Port 3389 is for Remote Desktop Protocol, and it doesn't have to do with the HCX Connector on-premises routing traffic to the VMware HCX Cloud Manager environment."
48
48
- content: "53"
49
49
isCorrect: false
50
50
explanation: "Port 53 is for DNS, and doesn't have to do with the VMware HCX Connector on-premises routing traffic to the VMware HCX Cloud Manager environment."
@@ -59,4 +59,3 @@ quiz:
59
59
- content: "Redeploy VMware HCX on-premises to connect to Azure VMware Solution."
60
60
isCorrect: false
61
61
explanation: "Redeploying the VMware HCX appliance on-premises won't help create the service mesh."
Copy file name to clipboardExpand all lines: learn-pr/azure/migrate-vmware-workloads-on-premises-azure-vmware-solution/includes/2-plan-hcx-deployment.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,23 +15,23 @@ For a supported migration pattern that uses VMware HCX, there are vSphere versio
For older versions of vSphere (5.0+), VMware HCX Connector needs to be deployed and downgraded. VMware will support the migration for a limited period of time.
21
21
22
22
## Network connectivity and ports
23
23
24
24
Azure VMware Solution configures an Azure ExpressRoute circuit during the resource's deployment in Azure. You then need to peer the circuit into an Azure virtual network for access to all resources in Azure.
25
25
26
-
Next, configure network connectivity between the on-premises VMware vSphere environment and the Azure VMware Solution. Global Reach serves as the default choice for hybrid connectivity in Azure VMware Solution. However, there are scenarios where Global Reach might not be applicable: either due to its unavailability in your region, specific network, or security requirements that won't be met by Global Reach. In such cases, you can consider transiting data over ExpressRoute Private Peering or using IPSec VPN. Before VMware HCX Connector can be deployed and a site pairing established, you must enable network connectivity between the on-premises VMware vSphere environment and Azure VMware Solution.
26
+
Next, configure network connectivity between the on-premises VMware vSphere environment and the Azure VMware Solution. Global Reach serves as the default choice for hybrid connectivity in Azure VMware Solution. However, there are scenarios where Global Reach might not be applicabledue to its unavailability in your region, specific network, or unmet security requirements. In such cases, you can consider transiting data over ExpressRoute Private Peering or using IPSec VPN. Before VMware HCX Connector can be deployed and a site pairing established, you must enable network connectivity between the on-premises VMware vSphere environment and Azure VMware Solution.
27
27
28
28
All required network ports need to be open for communication between the on-premises VMware vSphere environment and Azure VMware Solution. The following table outlines all ports, protocols used, and what VMware solution components need open ports for configuration.
29
29
30
30
| Port | Protocol | Notes |
31
31
| :------| :------- | :---- |
32
-
| 4500 | UDP | Used for VMs in the source network communicating with VMs in the VMware HCX extended network, IX transport path carries VMware HCX migration and disaster recovery traffic.
33
-
| 443 | TCP | Configure and manage: VMware HCX services, activation and service updates, VMware HCX initiated connections, VPXA listener, VMware HCX vMotion control, traffic control for vMotion migration operations, ESX authentication, vCloud Director API, VMware HCX metrics for Aria Operations, virtual machine data transfer, VMware HCX HTTPS communication, and NSX API.
34
-
| 9443 | TCP | VMware HCX service appliance configuration and control, VMware HCX internal control, activate, and register vCenter Server and management servers.
32
+
| 4500 | UDP | Used for VMs in the source network communicating with VMs in the VMware HCX extended network, IX transport path carries VMware HCX migration and disaster recovery traffic.|
33
+
| 443 | TCP | Configure and manage: VMware HCX services, activation and service updates, VMware HCX initiated connections, VPXA listener, VMware HCX vMotion control, traffic control for vMotion migration operations, ESX authentication, vCloud Director API, VMware HCX metrics for Aria Operations, virtual machine data transfer, VMware HCX HTTPS communication, and NSX API.|
34
+
| 9443 | TCP | VMware HCX service appliance configuration and control, VMware HCX internal control, activate, and register vCenter Server and management servers.|
35
35
| 45000 to 44600 | TCP | Virtual machine data transfer. |
@@ -47,18 +47,18 @@ Next, you need to factor in the following network segments in the on-premises VM
47
47
| Network segment | Notes |
48
48
| :-------------- | :---- |
49
49
| Management network | - Use the same management network as the on-premises VMware cluster. <br>- At a minimum, select two IPs on this network segment for VMware HCX. <br>- Create a new /26 network segment for larger environments. <br>- Present that network segment as a port group to the on-premises VMware cluster. |
50
-
Uplink network | - Use the same management network for the uplink network segment. |
51
-
| vMotion network | - Use the same network as vMotion by the on-premises VMware cluster. <br>- At a minimum, identify two IPs on this network segment for VMware HCX. <br>- You might need more IPs, depending on the scale of the deployment. <br>- The vMotion network should be exposed to a distributed virtual switch or vSwitch0. <br>- If the vMotion isn't configured that way, you need to modify the configuration. <br>- VMware vSphere environments typically use nonrouted network segments for vMotion, which doesn't cause a problem.
52
-
| Replication network | - Use the same network segment as the management and uplink network segments. <br>- If the on-premises hosts use a dedicated replication VMkernel network, reserve two IP addresses in this network segment. <br>- Use the replication VMkernel network for the replication network segment.
50
+
|Uplink network | - Use the same management network for the uplink network segment. |
51
+
| vMotion network | - Use the same network as vMotion by the on-premises VMware cluster. <br>- At a minimum, identify two IPs on this network segment for VMware HCX. <br>- You might need more IPs, depending on the scale of the deployment. <br>- The vMotion network should be exposed to a distributed virtual switch or vSwitch0. <br>- If the vMotion isn't configured that way, you need to modify the configuration. <br>- VMware vSphere environments typically use nonrouted network segments for vMotion, which doesn't cause a problem.|
52
+
| Replication network | - Use the same network segment as the management and uplink network segments. <br>- If the on-premises hosts use a dedicated replication VMkernel network, reserve two IP addresses in this network segment. <br>- Use the replication VMkernel network for the replication network segment.|
53
53
54
54
## Different migration types
55
55
56
56
VMware HCX offers a few different ways to migrate workloads:
57
57
58
58
| Migration type | Use cases | Capabilities |
59
59
| :------------- | :-------- | :-------- |
60
-
| Live migration | Production VMs that need to remain online with minimal downtime. | - Migrates a powered-on VM. <br>- Needs a VMware HCX-enabled vCenter Server configured. <br>- Needs a VMware HCX-enabled destination site configuration. <br>- vMotion captures the VM's active memory, execution state, IP address, and MAC address. <br>- Migration duration depends on connectivity. <br>- Connectivity includes bandwidth available and the latency between both sites. <br>- The VM never powers off, there's no service disruption, and workloads remain online.
61
-
| Cold migration | Dev/test workloads that might not be online during migration, but need to be migrated. |<br>- Transfers a powered-off VM. <br>- Uses same network path as VMware HCX vMotion. <br>- VM IP address and MAC address are preserved. |
60
+
| Live migration | Production VMs that need to remain online with minimal downtime. | - Migrates a powered-on VM. <br>- Needs a VMware HCX-enabled vCenter Server configured. <br>- Needs a VMware HCX-enabled destination site configuration. <br>- vMotion captures the VM's active memory, execution state, IP address, and MAC address. <br>- Migration duration depends on connectivity. <br>- Connectivity includes bandwidth available and the latency between both sites. <br>- The VM never powers off, there's no service disruption, and workloads remain online.|
61
+
| Cold migration | Dev/test workloads that might not be online during migration but need to be migrated. | - Transfers a powered-off VM. <br>- Uses same network path as VMware HCX vMotion. <br>- VM IP address and MAC address are preserved. |
62
62
| Bulk migration | Many VMs that need to be migrated on a schedule. | - Moves VMs in parallel. <br>- Predefined schedule. <br>- VMs run at the source site until the cutover begins. <br>- The service interruption is equivalent to a reboot. |
63
63
64
64
## Scenario readiness and preparation for Azure VMware Solution
Copy file name to clipboardExpand all lines: learn-pr/azure/migrate-vmware-workloads-on-premises-azure-vmware-solution/includes/3-vmware-hcx-deployment-installation.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Before you deploy VMware HCX Connector in the on-premises vCenter Server, downlo
28
28
29
29
1. Select **+ Add** under **Connect with on-premise using HCX keys** to generate a key that you use for the on-premises HCX Connector installation.
30
30
31
-
1. Supply a VMware HCX key name and you see the activation key shows up within this pane. This key is used to activate the on-premises VMware HCX Connector appliance.
31
+
1. Supply a VMware HCX key name, and you see the activation key shows up within this pane. This key is used to activate the on-premises VMware HCX Connector appliance.
32
32
33
33
:::image type="content" source="../media/3-add-vmware-hcx-activation-key.png" alt-text="Screenshot that shows where to add the VMware HCX key in the Azure portal for use on-premises."lightbox="../media/3-add-vmware-hcx-activation-key.png":::
34
34
@@ -60,7 +60,7 @@ Before you deploy VMware HCX Connector in the on-premises vCenter Server, downlo
60
60
61
61
Next, the VMware HCX Connector OVA file needs to be installed in the on-premises VMware vSphere environment. Sign in to the web GUI of vCenter Server and begin deployment of the OVA file on-premises.
62
62
63
-
1. Right-click the vCenter Server datacenter and select **Deploy OVF Template**.
63
+
1. Right-click the vCenter Server datacenter, and select **Deploy OVF Template**.
64
64
65
65
:::image type="content" source="../media/3-deploy-ovf-template.png" alt-text="Screenshot that shows how to deploy the OVA file downloaded for VMware HCX Connector on-premises in vCenter Server.":::
66
66
@@ -72,7 +72,7 @@ Next, the VMware HCX Connector OVA file needs to be installed in the on-premises
72
72
73
73
:::image type="content" source="../media/3-select-name-folder.png" alt-text="Screenshot of where to name the VMware HCX Connector appliance and where to select the datacenter within vCenter Server on-premises.":::
74
74
75
-
1. For **Select a compute resource**, select the vSphere cluster, then select **Next**.
75
+
1. For **Select a compute resource**, select the vSphere cluster, and then select **Next**.
76
76
77
77
:::image type="content" source="../media/3-select-compute-resource.png" alt-text="Screenshot that selects the vSphere cluster to deploy the VMware HCX Connector appliance to during deployment on-premises.":::
78
78
@@ -96,7 +96,7 @@ Next, the VMware HCX Connector OVA file needs to be installed in the on-premises
96
96
97
97
:::image type="content" source="../media/3-customize-template-hcx-vmware.png" alt-text="Screenshot of customizing the OVA template file for the VMware HCX Connector deployment on-premises."lightbox="../media/3-customize-template-hcx-vmware.png":::
98
98
99
-
1. On **Ready to complete**, verify all configurations and select **Finish**.
99
+
1. On **Ready to complete**, verify all configurations, and select **Finish**.
100
100
101
101
:::image type="content" source="../media/3-ready-complete-hcx-on-premises.png" alt-text="Screenshot that shows the appliance is ready to complete the installation on-premises."lightbox="../media/3-ready-complete-hcx-on-premises.png":::
102
102
@@ -110,7 +110,7 @@ After deploying and powering on the VMware HCX Connector appliance on-premises,
110
110
111
111
:::image type="content" source="../media/3-add-vmware-hcx-activation-key-portal.png" alt-text="Screenshot to add the VMware HCX Advanced key in the Azure portal."lightbox="../media/3-add-vmware-hcx-activation-key-portal.png":::
112
112
113
-
1. Provide a name for the key and wait for Azure to generate a VMware HCX Enterprise key for use on-premises.
113
+
1. Provide a name for the key, and wait for Azure to generate a VMware HCX Enterprise key for use on-premises.
114
114
115
115
:::image type="content" source="../media/3-request-vmware-hcx-activation-key.png" alt-text="Screenshot after the VMware HCX Advanced key is requested from the Azure portal."lightbox="../media/3-request-vmware-hcx-activation-key.png":::
0 commit comments