Skip to content

Commit cc5865c

Browse files
Merge pull request #292897 from frankeb84/frankeb-patch1
Updating retiring VMware documentation links
2 parents ad53f2f + f8a7a03 commit cc5865c

File tree

2 files changed

+45
-45
lines changed

2 files changed

+45
-45
lines changed

articles/azure-vmware/move-azure-vmware-solution-across-regions.md

Lines changed: 31 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Move Azure VMware Solution resources across regions
3-
description: This article describes how to move Azure VMware Solution resources from one Azure region to another.
3+
description: This article describes how to move Azure VMware Solution resources from one Azure region to another.
44
ms.custom: "subject-moving-resources, engagement-fy23"
55
ms.topic: how-to
66
ms.service: azure-vmware
7-
ms.date: 3/28/2024
7+
ms.date: 01/10/2025
88

99
# Customer intent: As an Azure service administrator, I want to move my Azure VMware Solution resources from Azure Region A to Azure Region B.
1010
---
@@ -18,7 +18,7 @@ You can move Azure VMware Solution resources to a different region for several r
1818

1919
This article helps you plan and migrate Azure VMware Solution from one Azure region to another, such as Azure region A to Azure region B.
2020

21-
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the purple line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#section1).
21+
The diagram shows the recommended ExpressRoute connectivity between the two Azure VMware Solution environments. An HCX site pairing and service mesh are created between the two environments. The HCX migration traffic and Layer-2 extension moves (depicted by the purple line) between the two environments. For VMware recommended HCX planning, see [Planning an HCX Migration](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
2222

2323
:::image type="content" source="media/move-across-regions/move-ea-csp-across-regions-2.png" alt-text="Diagram showing ExpressRoute Global Reach communication between the source and target Azure VMware Solution environments." border="false" lightbox="media/move-across-regions/move-ea-csp-across-regions-2.png":::
2424

@@ -42,21 +42,21 @@ In this article, walk through the steps to:
4242
4343
## Prerequisites
4444

45-
- [VMware HCX appliance is upgraded to the latest patch](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-02DB88E1-EC81-434B-9AE9-D100E427B31C.html) to avoid migration issues if any.
45+
- [VMware HCX appliance is upgraded to the latest patch](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/vmware-hcx-user-guide-4-9/updating-vmware-hcx.html) to avoid migration issues if any.
4646

47-
- Source's local content library is a [published content library](https://docs.vmware.com/en/VMware-Validated-Design/services/deployment-of-vrealize-suite-2019-on-vmware-cloud-foundation-310/GUID-59E0CBA1-2CF6-488D-AA58-C97C76FD8159.html?hWord=N4IghgNiBcIA4FcBGECWBnAFgAgMYHsA7AFwFMTs0kAnMagTxAF8g).
47+
- Source's local content library is a [published content library](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0/using-content-librariesvsphere-vm-admin/publish-the-contents-of-a-library-and-a-single-template-to-a-subscribervsphere-vm-admin.html).
4848

4949
## Prepare
5050

5151
The following steps show how to prepare your Azure VMware Solution private cloud to move to another Azure VMware Solution private cloud.
5252

5353
### Export the source configuration
5454

55-
1. From the source, [export the extended segments, firewall rules, port details, and route tables](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-FCE6567E-1174-49CC-90F1-BA7B695B28F0.html).
55+
1. From the source, [export the extended segments, firewall rules, port details, and route tables](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-1-1/administration-guide/security/distributed-firewall/export-or-import-a-firewall-configuration.html).
5656

57-
1. [Export the contents of an inventory list view to a CSV file](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-C0E8DD52-677E-464F-A3EA-044EE20B7B92.html).
57+
1. [Export the contents of an inventory list view to a CSV file](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/using-the-vsphere-client-host-management/working-with-the-vsphere-client-inventory-host-management.html#GUID-C0E8DD52-677E-464F-A3EA-044EE20B7B92-en).
5858

59-
1. [Sort workloads into migration groups (migration wave)](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#sec4-sub1).
59+
1. [Sort workloads into migration groups (migration wave)](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
6060

6161

6262
### Deploy the target environment
@@ -94,7 +94,7 @@ Azure VMware Solution supports all backup solutions. You need CloudAdmin privile
9494

9595
2. Select **Manage** > **Connectivity** > **ExpressRoute**.
9696

97-
3. Copy the source’s **ExpressRoute ID**. You need it to peer between the private clouds.
97+
3. Copy the source’s **ExpressRoute ID**. You need it to peer between the private clouds.
9898

9999
### Create the target’s authorization key
100100

@@ -128,9 +128,9 @@ Now that you have the ExpressRoute circuit IDs and authorization keys for both e
128128

129129
:::image type="content" source="./media/expressroute-global-reach/expressroute-global-reach-tab.png" alt-text="Screenshot showing the ExpressRoute Global Reach tab in the Azure VMware Solution private cloud.":::
130130

131-
1. Paste the ExpressRoute circuit ID and target’s authorization key you created in the previous step. Then select **Create**:
131+
1. Paste the ExpressRoute circuit ID and target’s authorization key you created in the previous step. Then select **Create**:
132132

133-
:::image type="content" source="./media/expressroute-global-reach/on-premises-cloud-connections.png" alt-text="Screenshot that shows the dialog for entering the connection information.":::
133+
:::image type="content" source="./media/expressroute-global-reach/on-premises-cloud-connections.png" alt-text="Screenshot that shows the dialog for entering the connection information.":::
134134

135135
### Create a site pairing between private clouds
136136

@@ -159,42 +159,42 @@ After you establish connectivity, you'll create a VMware HCX site pairing betwee
159159
>
160160
> * Ports UDP 500/4500 are open between your on-premises VMware HCX Connector 'uplink' network profile addresses and the Azure VMware Solution HCX Cloud 'uplink' network profile addresses.
161161
>
162-
> * Be sure to review the [VMware HCX required ports](https://ports.vmware.com/home/VMware-HCX).
162+
> * Be sure to review the [VMware HCX required ports](https://ports.broadcom.com/home/VMware-HCX).
163163
164-
1. Under **Infrastructure**, select **Interconnect** > **Service Mesh** > **Create Service Mesh**.
164+
1. Under **Infrastructure**, select **Interconnect** > **Service Mesh** > **Create Service Mesh**.
165165

166166
:::image type="content" source="media/tutorial-vmware-hcx/create-service-mesh.png" alt-text="Screenshot of selections to start creating a service mesh." lightbox="media/tutorial-vmware-hcx/create-service-mesh.png":::
167167

168168
1. Review the prepopulated sites, and then select **Continue**.
169169

170170
> [!NOTE]
171-
> If this is your first service mesh configuration, you won't need to modify this screen.
171+
> If this is your first service mesh configuration, you won't need to modify this screen.
172172
173-
1. Select the source and remote compute profiles from the drop-down lists, and then select **Continue**.
173+
1. Select the source and remote compute profiles from the drop-down lists, and then select **Continue**.
174174

175-
The selections define the resources where VMs can consume VMware HCX services.
175+
The selections define the resources where VMs can consume VMware HCX services.
176176

177177
:::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":::
178178

179179
:::image type="content" source="media/tutorial-vmware-hcx/select-compute-profile-remote.png" alt-text="Screenshot that shows selecting the remote compute profile." lightbox="media/tutorial-vmware-hcx/select-compute-profile-remote.png":::
180180

181-
1. Review services that you want to be enabled, and then select **Continue**.
181+
1. Review services that you want to be enabled, and then select **Continue**.
182182

183-
1. In **Advanced Configuration - Override Uplink Network profiles**, select **Continue**.
183+
1. In **Advanced Configuration - Override Uplink Network profiles**, select **Continue**.
184184

185-
Uplink network profiles connect to the network through which the remote site's interconnect appliances can be reached.
185+
Uplink network profiles connect to the network through which the remote site's interconnect appliances can be reached.
186186

187187
1. In **Advanced Configuration - Network Extension Appliance Scale Out**, review and select **Continue**.
188188

189-
You can have up to eight Network Segments per appliance, but you can deploy another appliance to add another eight Network Segments. You must also have IP space to account for the more appliances, and it's one IP per appliance. For more information, see [VMware HCX Configuration Limits](https://configmax.vmware.com/guest?vmwareproduct=VMware%20HCX&release=VMware%20HCX&categories=41-0,42-0,43-0,44-0,45-0).
189+
You can have up to eight Network Segments per appliance, but you can deploy another appliance to add another eight Network Segments. You must also have IP space to account for the more appliances, and it's one IP per appliance. For more information, see [VMware HCX Configuration Limits](https://configmax.broadcom.com/guest?vmwareproduct=VMware%20HCX&release=VMware%20HCX&categories=41-0,42-0,43-0,44-0,45-0).
190190

191191
:::image type="content" source="media/tutorial-vmware-hcx/extend-networks-increase-vlan.png" alt-text="Screenshot that shows where to increase the VLAN count." lightbox="media/tutorial-vmware-hcx/extend-networks-increase-vlan.png":::
192192

193193
1. In **Advanced Configuration - Traffic Engineering**, review and make any modifications that you feel are necessary, and then select **Continue**.
194194

195195
1. Review the topology preview and select **Continue**.
196196

197-
1. Enter a user-friendly name for this service mesh and select **Finish** to complete.
197+
1. Enter a user-friendly name for this service mesh and select **Finish** to complete.
198198

199199
1. Select **View Tasks** to monitor the deployment.
200200

@@ -230,17 +230,17 @@ In this section, you migrate the:
230230

231231
In this step, copy the source vSphere configuration and move it to the target environment.
232232

233-
1. From the source vCenter Server, use the same resource pool configuration and [create the same resource pool configuration](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D.html#example-creating-resource-pools-4) on the target's vCenter Server.
233+
1. From the source vCenter Server, use the same resource pool configuration and [create the same resource pool configuration](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-resource-management-8-0/managing-resource-pools.html#GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D-en) on the target's vCenter Server.
234234

235-
2. From the source's vCenter Server, use the same VM folder name and [create the same VM folder](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-031BDB12-D3B2-4E2D-80E6-604F304B4D0C.html?hWord=N4IghgNiBcIMYCcCmYAuSAEA3AthgZgPYQAmSCIAvkA) on the target's vCenter Server under **Folders**.
235+
2. From the source's vCenter Server, use the same VM folder name and [create the same VM folder](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/organizing-your-inventory-host-management/create-a-folder-host-management.html) on the target's vCenter Server under **Folders**.
236236

237237
3. Use VMware HCX to migrate all VM templates from the source's vCenter Server to the target's vCenter Server.
238238

239239
1. From the source, convert the existing templates to VMs and then migrate them to the target.
240240

241241
2. From the target, convert the VMs to VM templates.
242242

243-
4. From the source environment, use the same VM Tags name and [create them on the target's vCenter](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-05323758-1EBF-406F-99B6-B1A33E893453.html).
243+
4. From the source environment, use the same VM Tags name and [create them on the target's vCenter](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vcenter-and-host-management-8-0/vsphere-tags-and-attributes-host-management/vsphere-tags-host-management.html#GUID-2FF21224-B6BC-499B-AD8B-D2C4309AD9DC-en).
244244

245245
5. From the source's vCenter Server Content Library, use the subscribed library option to copy the ISO, OVF, OVA, and VM Templates to the target content library:
246246

@@ -261,27 +261,27 @@ In this step, use the source NSX-T Data Center configuration to configure the ta
261261
262262
1. [Configure NSX-T Data Center network components](tutorial-nsx-t-network-segment.md) required in the target environment under default Tier-1 gateway.
263263

264-
1. [Create the security group configuration](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-41CC06DF-1CD4-4233-B43E-492A9A3AD5F6.html).
264+
1. [Create the security group configuration](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-1-1/administration-guide/inventory/add-a-group.html#GUID-9DFF6EE2-2E00-4097-A412-B72472596E4D-en).
265265

266-
1. [Create the distributed firewall policy and rules](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-41CC06DF-1CD4-4233-B43E-492A9A3AD5F6.html).
266+
1. [Create the distributed firewall policy and rules](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-1-1/administration-guide/security/distributed-firewall/add-a-distributed-firewall.html).
267267

268-
1. [Create the gateway firewall policy and rules](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-DE6FE8CB-017E-41C8-85FC-D71CF27F85C2.html).
268+
1. [Create the gateway firewall policy and rules](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-1-1/administration-guide/security/gateway-firewall/add-a-gateway-firewall-policy-and-rule.html).
269269

270270
1. [Create the DHCP server or DHCP relay service](configure-dhcp-azure-vmware-solution.md).
271271

272272
1. [Configure port mirroring](configure-port-mirroring-azure-vmware-solution.md).
273273

274274
1. [Configure DNS forwarder](configure-dns-azure-vmware-solution.md).
275275

276-
1. [Configure a new Tier-1 gateway (other than default)](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-A6042263-374F-4292-892E-BC86876325A4.html). This configuration is based on the NSX-T Data Center configured on the source.
276+
1. [Configure a new Tier-1 gateway (other than default)](https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-1-1/administration-guide/tier-1-gateways/add-an-nsx-tier-1-gateway.html). This configuration is based on the NSX-T Data Center configured on the source.
277277

278278
### Migrate the VMs from the source
279279

280280
In this step, use VMware HCX to migrate the VMs from the source to the target. You can opt to do a Layer-2 extension from the source and use HCX to vMotion the VMs from the source to the target with minimal interruption.
281281

282-
Besides vMotion, other methods, like Bulk and Cold vMotion, are also recommended. Learn more about:
282+
Besides vMotion, other methods, like Bulk and Cold vMotion, are also recommended. Learn more about:
283283

284-
- [Plan an HCX Migration](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#sec4-sub1)
284+
- [Plan an HCX Migration](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration)
285285

286286
- [Migrate Virtual Machines with HCX](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-14D48C15-3D75-485B-850F-C5FCB96B5637.html)
287287

@@ -294,7 +294,7 @@ In this step, perform a final gateway cutover to terminate the extended networks
294294
295295
Before the gateway cutover, verify all migrated workload services and performance. Once application and web service owners accept the performance (except for any latency issues), you can continue with the gateway cutover. Once the cutover is completed, you need to modify the public DNS A and PTR records.
296296

297-
For VMware recommendations, see [Cutover of extended networks](https://vmc.techzone.vmware.com/vmc-solutions/docs/deploy/planning-an-hcx-migration#section9).
297+
For VMware recommendations, see [Cutover of extended networks](https://www.vmware.com/docs/vmware-cloud-planning-an-hcx-migration).
298298

299299
### Public IP DNAT for migrated DMZ VMs
300300

0 commit comments

Comments
 (0)