0

For an Azure VM deployed with the classic method I need to be sure that my output IP address never change and never get translated by SNAT. As far as I know I must reserve an IP Address in order to be sure that it never change, and I need to assign an Instance Level IP in order to avoid SNAT, but how can I associate a reserved IP Address to an Instance Level IP ? (ILPIP)

I've found something similar here, but couldn't find a way to have an output address for an Azure VM that never change and never get translated.

Many thanks

mCasamento
  • 103
  • 3

2 Answers2

2

In the classic deployment model, an instance level public IP address cannot be static. They are dynamic only. Refer to the table labeled Differences between Resource Manager and classic deployments in the following link:

https://azure.microsoft.com/en-us/documentation/articles/virtual-network-ip-addresses-overview-classic/

You have not shared the specifics of your requirements, but assuming the no-NAT requirement is firm you have the following choices:

  • Use a static public IP assigned to the VM NIC in the Resource Manager deployment model
  • Remain in the classic model and plan to change DNS/other configurations if the VM has to be stopped and started again for some reason.
learley
  • 469
1

I've ammended this response based on my incorrect assumuption that ILIP's were static. If you want a static outbound IP with a classic deployment then you need to look at setting a reserved IP for the cloud service. By default the outbound IP of an instance is that of the IP configured for the cloud service, so the solution to your issue is to get a reserved IP for your cloud service and you are done. All your outbound traffic will use the cloud service IP and it won't change because it is reserved.

You can get an Instance Level IP for the specific VM. This will then use this IP as the outbound address, not the cloud service. However the ILIP will not keep the same IP if the machine is de-allocated and started again. If you want a persistent IP address you will need to use the cloud service method.

This all changes with V2 (resource manager) deployments where there are no cloud services and you can assign static IP's directly to VM's.

Sam Cogan
  • 39,089