A quick article to note down the steps to assign static IP, I am sure not all my terminology will be correct.
If you are reading this then you are probably aware of the fact that windows azure VMs are given internal IPs via DHCP, and they are dished out in order. The first four addresses are reservered, so for a range of 192.168.1.0/24, IPs
- 192.168.1.0 (network address),
- 192.168.1.1,
- 192.168.1.2,
- 192.168.1.3
are all taken by Azure.
So the first VM you fire-up will take the next IP 192.168.1.4. All seems good..
It is, however as these are DHCP they have a lease as it can expire. So say you down a couple of machines for maintenance, depending on in what order these machines are restarted you can find the machine will come up with a difference IP address.
Now late in 2014 Microsoft announced that you can actually force an IP to be assigned to a particular VM. It is still given via DHCP but the VM is guaranteed the same IP.
Currently there is no way to achieve this via the GUI/portal and it maust be achieved via powershell.
If you have not used powershell to configure windows azure, you will need to download and install the powershell
OK, now first thing is to configure the computer to talk to Azure this can be down manually or automatically. Below I show how to setup automatically.
Open powershell and type
Get-AzurePublishSettingsFile
A browser window will appear to
Login and a file download should begin. If you open this file you will see its an XML file containing subscription information.
Now we need to get the powershell session logged into Azure, we do this by calling get-crendential and assigning to a variable.
$cred =
get-credential
This command will open a dialog that will allow you to type in your azure username and password.
Now lets import the subscription info.
Change to the path and name of the publish file downloaded earlier, you should see the contents of this file printed on the screen.
Import-AzurePublishSettingsFile .publishsettings
Ok, lets now test the IP we want to assign is available
Test-AzureStaticVNetIP -VNetName -IPAddress
Output should tell its or isn't available. If its not available it probably means the VM is still running, go to the azure and shutdown properly and then retest.
Ok now we get to the pointy end.
Get-AzureVM -ServiceName -Name |
Set-AzureStaticVNetIP -IPAddress | Update-AzureVM
No comments:
Post a Comment