Forum Discussion
Azure Migrate - maintain the same IP of the source virtual machines
Hello everyone,
i'm testing Azure Migrate features with my test Lab in VMware.
I would maintain the same IP of the source virtual machines (of course i have the same address space in the target VNET in Azure) but when the virtual machines is replicated Azure assign always the first free IP of the subnet in DHCP.
Is there any option when i configure the migration?
Thanks a lot
Davide
When configuring the migration using Azure Migrate, you can indeed maintain the same IP address for your virtual machines (VMs) in Azure. Let’s explore how to achieve this:
Static IP Assignment:
- By default, Azure assigns dynamic IP addresses (using DHCP) to VMs during replication. However, you can configure static IP assignment to ensure that the VMs retain the same IP address after migration.
- Here’s how to set up static IP assignment during the migration process:
Steps:
Before Replication:
- In your VMware environment, ensure that each VM has a static IP address assigned.
- Note down the static IP addresses for each VM that you want to migrate.
During Replication Configuration:
- When configuring replication in Azure Migrate, you’ll reach a step where you map the source VMs to target VMs in Azure.
- For each VM, you’ll see an option to specify the NIC (Network Interface Card) settings. Here, you can choose to assign a static IP address.
- Select the option to assign a static IP address and provide the desired IP address for each VM.
After Migration:
- Once the VMs are successfully migrated to Azure, they will retain the specified static IP addresses.
- Azure will ensure that the IP address is reserved and assigned to the correct VM.
Considerations:
- Make sure that the target virtual network (VNET) in Azure has the same address space as your on-premises network.
- Verify that the static IP addresses you choose are within the subnet range of the target VNET.
In summary, during the replication configuration, you can explicitly set static IP addresses for your VMs in Azure. This way, your VMs will maintain the same IP addresses even after migration. If you encounter any issues during the process, feel free to ask for further assistance! 😊
"If my answer was helpful, please mark it as 'Accepted' to assist others."
- juhua
Microsoft
during the migration process, Azure does indeed default to using DHCP for IP address allocation for the VMs being migrated. However, if you need to retain the same IP addresses for your virtual machines in Azure as they had on-premises (assuming the target Azure VNet's address space accommodates this), you'll need to manually configure this post-migration.- Hello,
How you can have same subnets on-prem and on Azure this is not possible you will have overlapping. I would like to know if there is any solution. Thanks
- Remove DHCP option. Create NIC Card and Assign IP Address. Once the VM is migrated, assign the newly created NIC to the migrated VM.
What is your IP address assessment, private or public?
- Is there any solution for retaining public IPs
- can you explain in more detail what you meant?
- I have created an automation for all my tasks after the migration.. for example: set static ip, expand disk size, expand disk partition on windows and so on.. with azure migrate you can only define wich vnet will be the target vnet.
