Skip to main content

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

Popular posts from this blog

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see