Internal Static IP on VM in a Virtual Network from Windows Azure

In general I don’t discuss about IT PRO features from Windows Azure, but some of them are very important. Why: because in the end we design solution to run somewhere. In today post we will talk about how static IP on VM from Windows Azure.
I assume that this is the first time when you hear about this subject. Let’s start with the begging. On Azure we have a Virtual Network where we can add our VM. Of course each machine from this network will have an IP based on the Virtual Network configuration (subnet range, available IPs in our Virtual Network and so on).
When we restart of machine (OS upgrades, application upgrades, …) the IP allocated to the machine will remain the same. If we deallocate one of VM machines from Virtual Network, the IP will be automatically available to other new VM that will be added. This means that if we have a machine with 192.168.1.2 (internal IP) and we deallocate it, the next VM that will be added to the network will have this IP, even if there will be other IP’s available in our network.
Unfortunately, if we deallocate our machine the machine and recreate it, the IP that is allocate to it will not be the same (if other VM were already added to the network or an IP with smaller value is available). Because of this, if we configure other VM to connect to a specific IP, we will have problems with machines IP – we will need to change the configuration of the VM that tries to connect to a resource using the IP (sticky connection).
First of all we should access the machines based on the name and not based on IP, but there are times when we cannot use the name of the machine. A new feature was added to Windows Azure that give us the possibility to configure the internal IP of a VM that is created on our private network.
This mean that when you create the VM you can specify what the internal IP will be. Unfortunately this cannot be made from Windows Azure portal (yet, in the future we may have this option available).
We can configure the internal IP using power shell scripts. In the setup of our VM we have a new configuration called “Set-AzureStaticVNetIP”. This will allow us to set the internal IP

Set-AzureStaticVNetIP -IPAddress 192.168.1.2

To get the IP of the machine we can use the following command

Get-AzureStaticVNetIP -VM {VirtualMchine}

To remove the internal static IP you need to use the following command “Remove-AzureStaticVNetIP”
Enjoy!

Comments

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud as a Story - Vunvulea Radu

Search This Blog