Hello friends, you can find the post at below link –
Hello friends, you can find the post at below link –
In this blog we will discuss about how to check the details about Azure VM tiers and sizes.
Microsoft Azure has basically three tiers: Basic, Standard and Premium.
Difference between these two tiers are the features present in them for virtual machine like high availability, auto scale etc.
When we create the VM we need to select the size of VM from Basic or Standard tier as per the requirement of cores, memory, disk space etc… But when we create the VM using PowerShell we need to first check the options of sizes of virtual machine available.
To get the available sizes for Azure VM we need to write command –
It lists out all the sizes available to azure VM with detailed information like Cores, Memory etc. as shown in below image.
If we need to just check the name of instance sizes without need of detailed information we can write the command –
To check the detailed information about a specific VM size we just need to specify the name of instance size with command like –
Get-AzureRoleSize –InstanceSize Standard_G1
So, using these few cmdlets we can check the available VM sizes available before creating any virtual machine.
Hello friends, when we create any virtual machine using management portal we need to select the location for cloud service and azure portal shows us list of available locations.
We just select the location we want and move further to next steps.
We can also do this same using PowerShell and we need to check the locations available to us using azure cmdlet.
It will return a lot of information about Azure location like –
What Virtual Machine different sizes are available for a particular location?
What type of storage account types are available?
So we will have detailed information for every location because not all locations/regions have all the features available and its helps to find out which location is best for our purpose based on the available features.
To display the names of available location we need to write cmdlet –
(Get – AzureLocation).DisplayName
It will display all the available location to your subscription and you can select the location of your choice based on the features available.
So friends, this is how we get detail information about the locations available in Azure.
Hello friends, in this blog we will learn how to check whether a cloud service is available to use with virtual machine or not. Cloud service is basically how to access virtual machine using virtual IP address (VIP).
Cloud services can contain multiple virtual machine by creating cloud service first and then associate that public VIP to multiple virtual machine.
When we create cloud service using management portal it tells us that whether this cloud service is available or not. But when we do this using PowerShell we will not get such facility and we need to test it manually using some cmdlets to check whether this cloud service is available or not.
So, lets login to our azure account from PowerShell and check the current VM that we already have in our azure subscription.
Now, write the command to test whether cloud service “kkvm015093” is available or not.
Test-AzureName –Service “kkvm015093”
In the result it returns True which means this service is already taken or present.
But you can still create the virtual machine using this cloud service as we know that multiple VM can use the same cloud service.
If we write any service name that is not present it will return False.
To get the more information about an existing cloud service we will write command –
Get-AzureService –ServiceName “kkvm015093”
If you try to get the information of cloud service which had returned False it will throw an error, saying ‘The hosted service does not exist’.
So, we today we have learnt that how to check the cloud service availability using PowerShell.
In my previous blog, we learnt that a Virtual IP (VIP) get lost or changed when we stop or deallocate the virtual machine (VM). So, to overcome this we can assign a reserved IP so that whenever we restart the virtual machine we would get the same IP.
Microsoft Azure allows default 20 reserved IP per subscription and you can contact to Microsoft if you need more reserved IP.
Reserved IP associate a static IP to cloud service and removes the limitation of VIP when VM restarts and VIP gets changed.
There are few limitations with Reserved IP:
~ Existing VIP cannot be converted into a reserved IP.
~ To get a static IP VMs must be created with reserved VIP first.
So, let us create a VM with reserved IP today using Azure Portal and PowerShell.
We will login to our Azure account as we did in our previous blogs using azure cmdlet Get-AzureAccount.
After we login to Azure account we will write cmdlet to create a new reserved IP.
New-AzureReservedIP –ReservedName “KKReservedIP01” –Label “KKReservedLabel01” –Location “South India”
Here “KKReservedIP01” is the name of reserved VIP.
“KKReservedLabel01” is the name of label.
“South India” is the location where we want to reserved VIP so Azure will provide a reserved VIP based on the region we select.
Now we have created a reserved VIP we will check which reserved VIP address is allocated by Azure based on the region.
So here we can see from the details the VIP address issued by Azure based on location.
Also, its showing that new reserved ip (188.8.131.52) is currently not in use and showing as False in InUse label.
Now we will assign this reserved IP to a virtual machine.
We will create a new virtual machine from Azure portal and select the new reserved ip name from list.
So we have created a virtual machine with reserved IP.
Let’s check again the values of labels from cmdlet Get-AzureReservedIP.
Here we can see that value of InUse label has changed to True which means that this reserved IP is currently in use now as we have assigned this VIP to our new virtual machine.
It also showing values for ServiceName, DeploymentName which were blank previously.
Now let’s restart the virtual machine and check whether VIP value gets changed or not.
To check the VIP values, we write the cmdlet Get-AzureVM –ServiceName kkvm02909 | Get-AzureEndpoint
Here, we can see that the VIP value is not changed and same as our reserved VIP.
We can also check the value of VIP from Azure Portal. For it, just click on the virtual machine name and select overview section or IP address section.
So, this is how we can reserve the VIP for a virtual machine if we don’t want to get its value changed every time we restart the virtual machine.
Virtual IP (VIP) is a public IP address and created when a cloud service is created.
A VIP is a public IP address that can be used to access Virtual machine in Azure. All VM in same domain name share a single VIP. By using a reserved IP address, you can ensure that the virtual IP address for you Virtual Machine never changes.
Default behavior of VIP address works as:
~ VIP is lost or changed when virtual machine is stopped or deallocated.
~ VIP is lost or changed when cloud service is deleted.
In this blog, we will discuss that VIP gets changed or lost whenever we stop/deallocate the Virtual Machine (VM).
I have already created a VM with the default settings like cloud service, virtual network etc.
We can see the information about our VM below:
When we created a VM, a virtual IP address 184.108.40.206 gets assigned by azure itself, automatically.
We can also check the value of the virtual IP address through PowerShell commands:
The values are same as we saw in the portal.
Now, let’s stop the virtual machine and we will see that the virtual IP address gets changed whenever we restart the virtual machine.
So we can see the new value has been assigned as the Virtual IP.
We can also see the values of virtual ip address from the IP addressess section of the virtual machine.
So, we have learned about the behaviour of virtual ip address that its value is lost or change when we stop or de-allocate the virtual machine.
We can overcome from this behaviour by using reserved virtual ip address. We will learn more about it in upcoming blogs.
Have a nice learning!!