I'm helping a client transition 11 out of 23 VMs from their on-prem VMware setup to Azure. We've already established a site-to-site connection using Azure VPN Gateway and a Cisco ASA firewall. The Azure virtual network has an address space of 172.31.2.5, while the on-prem VMs are using the 192.168.200.x range. After migrating one VM for testing, it was able to communicate with the on-prem VMs, and vice versa. This VM received the IP address 172.31.2.5 post-migration, but the client wants it to retain its original IP of 192.168.200.6. I read about the Azure Extended Network option but am curious about any other methods to keep the original private IPs of the VMs during migration. Any suggestions would be greatly appreciated!
3 Answers
The best approach is to align both networks with the same subnet and implement NAT translation to facilitate communication between them. By setting up your NAT layer, local subnet can map to an Azure subnet. So, for instance, if your original local IP is 192.168.200.54, it could translate to 172.x.x.6 in Azure, maintaining the IP addresses you want. This way, clients on the local network can still use the original DNS names with static A records pointing to this NAT setup. It can make the whole migration smoother without clients needing to adjust to new IPs.
So, just to clarify, does the NAT translation need to be handled on the on-prem Cisco ASA device? I'm really new to this networking stuff!
Related Questions
How To Get Your Domain Unblocked From Facebook
How To Find A String In a Directory of Files Using Linux