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
- VMware HCX Enterprise is now available and supported on Azure VMware Solution at no extra cost. HCX Enterprise is automatically installed for all new HCX add-on requests, and existing HCX Advanced customers can upgrade to HCX Enterprise using the Azure portal.
30
+
- VMware HCX Enterprise is available and supported on Azure VMware Solution at no extra cost. HCX Enterprise is automatically installed for all new HCX add-on requests, and existing HCX Advanced customers can upgrade to HCX Enterprise using the Azure portal.
31
31
32
32
- If you plan to [enable VMware HCX MON](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/extending-networks-with-vmware-hcx/hcx-network-extension-with-mobility-optimized-networking/configuring-hcx-mobility-optimized-networking.html), make sure you have:
33
33
@@ -36,15 +36,15 @@ After you complete these steps, you'll have a production-ready environment for c
36
36
- One or more active stretched network segments.
37
37
38
38
39
-
-Meet the [VMware software version requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/preparing-for-hcx-installations/software-version-requirements.html).
39
+
-Verify you meet the [VMware software version requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/preparing-for-hcx-installations/software-version-requirements.html).
40
40
41
-
-Your on-premises vSphere environment (source environment) meets the [minimum requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/preparing-for-hcx-installations/system-requirements-for-hcx.html).
41
+
-Verify your on-premises vSphere environment (source environment) meets the [minimum requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/preparing-for-hcx-installations/system-requirements-for-hcx.html).
42
42
43
-
-[Azure ExpressRoute Global Reach](tutorial-expressroute-global-reach-private-cloud.md) is configured between on-premises and Azure VMware Solution private cloud ExpressRoute circuits.
43
+
-Verify [Azure ExpressRoute Global Reach](tutorial-expressroute-global-reach-private-cloud.md) is configured between on-premises and Azure VMware Solution private cloud ExpressRoute circuits.
44
44
45
-
-[All required ports](https://ports.broadcom.com/home/VMware-HCX) are open for communication between on-premises components and Azure VMware Solution private.
45
+
-Verify [all required ports](https://ports.broadcom.com/home/VMware-HCX) are open for communication between on-premises components and Azure VMware Solution private.
46
46
47
-
-[Define VMware HCX network segments](plan-private-cloud-deployment.md#define-vmware-hcx-network-segments). The primary use cases for VMware HCX are workload migrations and disaster recovery.
47
+
-[Define VMware HCX network segments](plan-private-cloud-deployment.md#define-vmware-hcx-network-segments). The primary use cases for VMware HCX are workload migrations and disaster recovery.
48
48
49
49
-[Review the VMware HCX Documentation](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/overview.html) for information on using HCX.
50
50
@@ -83,7 +83,7 @@ VMware HCX Connector deploys a subset of virtual appliances (automated) that req
83
83
> [!NOTE]
84
84
> * For Azure VMware Solution connected via VPN, set Uplink Network Profile MTU's to 1350 to account for IPsec overhead.
85
85
> * Azure VMware Solution defaults to 1500 MTU, which is sufficient for most ExpressRoute implementations.
86
-
> * If your ExpressRoute provider does not support jumbo frames, you may need to lower the MTU in ExpressRoute setups as well.
86
+
> * If your ExpressRoute provider doesn't support jumbo frames, you might need to lower the MTU in ExpressRoute setups as well.
87
87
> * Adjust MTU settings on both HCX Connector (on-premises) and HCX Cloud Manager (Azure VMware Solution) network profiles.
88
88
89
89
1. Under **Infrastructure**, select **Interconnect** > **Multi-Site Service Mesh** > **Network Profiles** > **Create Network Profile**.
@@ -165,14 +165,14 @@ For an end-to-end overview of this procedure, view the [Azure VMware Solution: C
165
165
1. Review the prepopulated sites, and then select **Continue**.
166
166
167
167
> [!NOTE]
168
-
> If this is your first service mesh configuration, you won't need to modify this screen.
168
+
> For your first service mesh configuration, you don't need to modify the screen.
169
169
170
170
1. Select the source and remote compute profiles from the drop-down lists, and then select **Continue**.
171
171
172
172
The selections define the resources where VMs can consume VMware HCX services.
173
173
174
174
> [!NOTE]
175
-
> In a mixed-mode SDDC with an AV64 cluster, deploying service mesh appliances on the AV64 cluster is not viable or supported. Nevertheless, this doesn't impede you from conducting HCX migration or network extension directly onto AV64 clusters. The deployment container can be cluster-1, hosting the HCX appliances.
175
+
> In a mixed-mode SDDC with an AV64 cluster, deploying service mesh appliances on the AV64 cluster isn't viable or supported. Nevertheless, it doesn't impede you from conducting HCX migration or network extension directly onto AV64 clusters. The deployment container can be cluster-1, hosting the HCX appliances.
176
176
177
177
:::image type="content" source="media/tutorial-vmware-hcx/select-compute-profile-source.png" alt-text="Screenshot that shows selecting the source compute profile." lightbox="media/tutorial-vmware-hcx/select-compute-profile-source.png":::
178
178
@@ -211,11 +211,11 @@ For an end-to-end overview of this procedure, view the [Azure VMware Solution: C
211
211
:::image type="content" source="media/tutorial-vmware-hcx/interconnect-appliance-state.png" alt-text="Screenshot displaying options to check the status of the appliance." lightbox="media/tutorial-vmware-hcx/interconnect-appliance-state.png":::
212
212
213
213
>[!NOTE]
214
-
>After establishing the service mesh, you may notice a new datastore and a new host in your private cloud. This is normal behavior after establishing a service mesh.
214
+
>After establishing the service mesh, you might notice a new datastore and a new host in your private cloud, which is normal behavior after establishing a service mesh.
215
215
>
216
216
>:::image type="content" source="media/tutorial-vmware-hcx/hcx-service-mesh-datastore-host.png" alt-text="Screenshot displaying the HCX service mesh datastore and host." lightbox="media/tutorial-vmware-hcx/hcx-service-mesh-datastore-host.png":::
217
217
218
-
The HCX interconnect tunnel status should display **UP** in green. Now you're ready to migrate and protect Azure VMware Solution VMs using VMware HCX. Azure VMware Solution supports workload migrations with or without a network extension that allow you to migrate workloads in your vSphere environment, create networks on-premises, and deploy VMs onto those networks. For more information, see the [VMware HCX Documentation](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10.html).
218
+
The HCX interconnect tunnel status should display **UP** in green. Now you're ready to migrate and protect Azure VMware Solution VMs using VMware HCX. Azure VMware Solution supports workload migrations with or without a network extension, which allows you to migrate workloads in your vSphere environment, create networks on-premises, and deploy VMs onto those networks. For more information, see the [VMware HCX Documentation](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10.html).
219
219
220
220
For an end-to-end overview of this procedure, watch the [Azure VMware Solution: Service Mesh](https://www.youtube.com/embed/COY3oIws108) video.
0 commit comments