NIC comes from Network Interface Controller. What is connection between NIC and Microsoft Azure?
Starting from now we have the possibility to define multiple virtual network interfaces for each VM that is hosted on Azure. In on-premises this features is used to connect to multiple networks and provide mechanism to isolate different tiers of our system.
This can be used with success, in combination with a VPN connection to connect to multiple on-premises networks or Azure Virtual Networks. In this way we can establish a Cross Premises Connectivity.
In this moment the configuration can be made using PowerShell scripts and commands. An important pre requirement for NIC is to have Azure Virtual Network already configured on that VM.
A NIC can be configured only on VM. You cannot make this configuration on a web role or web sites. In this moment this feature is available only for VM. There is also a limit of number of NICs that you can define on each VM. The number is direct connected to the size of the machine. For example for an A6 you can define 2 NICs, but for an A7 you can define 4 NICS.
Because NICs are a new feature on Azure, there are some limitation in this moment. I expect that in the near future this limitation will be relaxed or even disappear. Below you can find a part of this limitations:
You cannot have multiple NICs on the same subnet
IP and MAC of each NIC will remain the same after a restart. The same thing is also for the network orders even if the order or networks cannot be controlled.
You cannot add/remove NICs once the VM is connected. This is one of the limitations that I hope that will be removed in near future.
Starting from now we have the possibility to define multiple virtual network interfaces for each VM that is hosted on Azure. In on-premises this features is used to connect to multiple networks and provide mechanism to isolate different tiers of our system.
This can be used with success, in combination with a VPN connection to connect to multiple on-premises networks or Azure Virtual Networks. In this way we can establish a Cross Premises Connectivity.
In this moment the configuration can be made using PowerShell scripts and commands. An important pre requirement for NIC is to have Azure Virtual Network already configured on that VM.
A NIC can be configured only on VM. You cannot make this configuration on a web role or web sites. In this moment this feature is available only for VM. There is also a limit of number of NICs that you can define on each VM. The number is direct connected to the size of the machine. For example for an A6 you can define 2 NICs, but for an A7 you can define 4 NICS.
Because NICs are a new feature on Azure, there are some limitation in this moment. I expect that in the near future this limitation will be relaxed or even disappear. Below you can find a part of this limitations:
You cannot have multiple NICs on the same subnet
IP and MAC of each NIC will remain the same after a restart. The same thing is also for the network orders even if the order or networks cannot be controlled.
You cannot add/remove NICs once the VM is connected. This is one of the limitations that I hope that will be removed in near future.
Comments
Post a Comment