Skip to content

Commit 41eee18

Browse files
committed
changes + art file
1 parent 0d004c4 commit 41eee18

File tree

2 files changed

+13
-11
lines changed

2 files changed

+13
-11
lines changed
53 KB
Loading

azure-local/migrate/migrate-maintain-ip-addresses.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Maintain static IP addresses during migration (preview)
33
description: Learn how to maintain static IP addresses for VMs during migration.
44
author: alkohli
55
ms.topic: how-to
6-
ms.date: 01/10/2025
6+
ms.date: 01/13/2025
77
ms.author: alkohli
88
ms.reviewer: alkohli
99
---
@@ -20,7 +20,7 @@ Download the [Windows static IP migration package](https://aka.ms/hci-migrate-st
2020

2121
The .zip file includes the following scripts:
2222

23-
- **Prepare-MigratedVM.ps1** – Prepares the VM for static IP migration using the `-StaticIPMigration` cmdlet, which runs the *Initialize-StaticIPMigration.ps1* script.
23+
- **Prepare-MigratedVM.ps1** – Prepares the VM for static IP migration using the `-StaticIPMigration` cmdlet, which runs the *Initialize-StaticIPMigration.ps1* script.
2424

2525
Logs are automatically created in the script's directory.
2626

@@ -37,19 +37,21 @@ The .zip file includes the following scripts:
3737

3838
Before you begin, prepare the source and target environments for IP migration.
3939

40-
### Prepare source environment for IP migration
40+
### Prepare source VMs for IP migration
4141

42-
To migrate VMs with static IPs from Hyper-V or VMware, ensure the following are completed:
42+
To migrate VMs with static IPs from the source system (Hyper-V or VMware), follow these steps:
4343

44-
- The VMs are powered on throughout the replication process and up to planned failover (migration).
44+
- Ensure the VMs are powered on throughout the replication process and up to planned failover (migration).
4545

46-
- For VMware VMs, **VMware Tools** are installed.
46+
- For VMware VMs, ensure that **VMware Tools** are installed.
4747

48-
- For Hyper-V VMs, that **Hyper-V Integration Services** are installed. For non-Windows VMs, that **Linux Integration Services** are installed. For more information, see [Manage Hyper-V Integration Services](/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services).
48+
- For Hyper-V VMs, ensure that **Hyper-V Integration Services** are installed. For more information, see [Manage Hyper-V Integration Services](/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services).
4949

50-
- The preparation script is run on the source VM by an account with administrator privileges to create scheduled tasks.
50+
- For Linux VMs, ensure that **Linux Integration Services** are installed.
5151

52-
### Prepare target Azure Local instance for IP migration
52+
- Ensure the preparation script is run on the source VM by an account with administrator privileges to create scheduled tasks.
53+
54+
### Prepare target VMs for IP migration
5355

5456
On the target system, provision a static Azure Arc logical network to support the migration. This setup requires defining the IP address space, gateway address, DNS servers, and optionally an IP pool range.
5557

@@ -176,7 +178,7 @@ Follow these steps to set up static IP migration at scale on domain-joined VMs u
176178
177179
## Known limitations
178180
179-
There are several limitations regarding the network interface information displayed in Azure portal.
181+
These are the known limitations and display issues when migrating static IP addresses:
180182
181183
### Old network adapter information in Device Manager
182184
@@ -190,7 +192,7 @@ When the source VM has multiple static IP addresses assigned to a single network
190192
191193
If the source VM has multiple network adapters with a mix of DHCP and static configurations, the migrated VM will preserve the correct number of network adapter, network adapter types, and static IP addresses on the static network adapter. However, the Arc portal view of the migrated VM may incorrectly display duplicate or inaccurate IPs on the network adapters. This is a known display issue in the Arc portal and doesn't impact the functionality of the IP addresses on the migrated VM. See the example below of a migrated VM with a DHCP network adapter and a static network adapter.
192194
193-
:::image type="content" source="./media/migrate-maintain-ip-addresses/.png" alt-text="Screenshot of network adapters." lightbox="./media/migrate-maintain-ip-addresses/.png":::
195+
:::image type="content" source="./media/migrate-maintain-ip-addresses/display-issue.png" alt-text="Screenshot of network adapters." lightbox="./media/migrate-maintain-ip-addresses/display-issue.png":::
194196
195197
196198
## Next steps

0 commit comments

Comments
 (0)