Shutting down a VM with a reserved IP address

Question

_{Friday, August 22, 2014 4:42 PM | 1 vote}

Shutting down a VM through the new portal (portal.azure.com) prompts in a warning that the public IP address will be lost.

However, in this case the machine has a reserved PIP address which will not be lost. We are currently shutting down our development machine every night and the PIP reservation works. We have also a legacy machine without a reserved PIP which we cannot shut down since we would indeed loose the PIP which is used in our network configuration.

The warning is therefore misleading. The portal should check whether a VM/cloudservice has a reserved PIP or not. The same is true for the internal IP which is set to be static within our virtual network and will not change when the VM is started up the next morning.

Best,

Dennis

All replies (5)

_{Saturday, August 23, 2014 12:18 PM ✅Answered}

Hi,

Public IP addresses allow you to access your VMs directly from outside the datacenter, without having to define any endpoints on the virtual IP address (VIP) of the corresponding cloud service.

Shutdown the VM in the portal (don’t do it in the RDP session). This will deprovision the machine, i.e. release the cloud service deployment and you will stop to pay for compute time. The Status column in the Dashboard section of the portal should show Stopped (Deallocated). Then start the VM again and wait for it to come up. Repeat the Get-AzureRole PowerShell statement shown above in order to find out if we still have a PIP.

As you can see, the VM remembered that it was assigned a PIP and created a new one (in my case 23.100.1.5). Although it is currently not possible to reserve a fixed PIP address (as you can now do with VIP addresses as), the VM keeps it’s configuration which is quite cool.

Today, you can assign one PIP per virtual machine, and there’s a maximum of two PIPs per Azure subscription.

Hope this helps !

Regards,

Sowmya

_{Tuesday, August 26, 2014 4:13 PM ✅Answered}

Hi,

Public IP (PIP) is generally associated with Virtual Machine and Virtual IP (VIP) is associated with the cloud service. 

The message that is shown above relates to Public IP (PIP) of VM which cannot be reserved. Each time the machine is shut down or restarted, the PIP gets released to the pool.

Public IP mentioned in the message relates to the IP of VM and not cloud service

On the contrary, VIP which is associated with cloud service does not change unless the Cloud Service is deleted.

Hence if you have already reserved IP to the cloud service, that will still be retained.

Regards,

Sowmya

_{Wednesday, August 27, 2014 8:07 AM ✅Answered | 1 vote}

Hi Dennis,

As we all known, if all the VMs(without reserving Public IP addresses) in a cloud service are in the status of stopped (Deallocated), the public IP address associated with that cloud service will be released. The next time you start a VM in the cloud service, the public IP address will be changed.

You are correct. When you shut down an Azure VM which is the unique VM which is not in the stopped (deallocated) status in the cloud service in the Azure mangement portal, it will warn you that the public IP address will be changed.

Since Reserved IP is a new feature in Azure, maybe when you shut down the Azure VM in the Azure management portal, it only checks if this VM is the unique VM which is not in the stopped (deallocated) status in the cloud service or not.

Thanks for your feedback and I will submit this issue to the related team. I hope the function of checking the reserved IP when we shut down an Azure VM will be added soon.

By the way, you can also submit this to the link below:

http://feedback.azure.com/forums/34192--general-feedback

Best regards,

Susie

_{Monday, August 25, 2014 2:48 PM}

I am sorry but this isn't related at all to my comment about PIP reservation. I have a pretty good understanding how the PIP reservation within Microsoft Azure works. My comment was about a misleading and wrong message when a machine is shutdown in the portal.

I have reserved an address at the creation of the cloud service. This means that every time when I start the service the same address will be assigned.

The portal should check whether a service is using a reserved address and warn accordingly.

Best,

Dennis

_{Wednesday, August 27, 2014 3:00 PM}

Nevertheless the warning message is wrong. Regardless of how you call the addresses. Neither address in the message will be lost both are reserved|static.

Dennis