Virtual Network Basic Overview

 

Applies To: Windows Azure Pack

When you use VM networks in Windows Azure Pack for Windows Server, you create networks that allow the virtual machines assigned to them, to communicate with other virtual machines, other networks, or even the internet. For more information about VMM networking, see Understanding Hyper-V Networking with System Center Virtual Machine Manager 2012 R2 by John Savill

This topic covers some basic conceptual material related to these networking areas of IaaS for Windows Azure Pack.

The following diagram illustrates how the Network Entities relate to each other and if one type depends on the existence of another type.

SPF Networking

The virtual machine (VM) network adapter is a hardware configuration for a virtual machine that represents a physical network adapter. The VM network adapter is assigned to a virtual machine and a VM network, giving the virtual machine access to the VM network.

When a virtual machine is created, one or more VM network adapters may have been created and attached to it. You can use an existing adapter, or create a new one. The adapter is configured to connect the virtual machine to the VM network. All VM network adapters are available through the VirtualNetworkAdapters collection. If you want to see the VM network adapters for a single virtual machine, filter a GET query with the VirtualNetworkAdapter.VMId property.

To work with virtual adapters, including basic code examples, see the VirtualNetworkAdapters Collection [SPFSDK][VMMREF] topic. Here are a few highlighted code examples.

Virtual machine networks provide a virtual infrastructure to facilitate communication between virtual machines. The VM network also isolates the virtual machines assigned to it from virtual machines that are not assigned to it. The VMNetworks collection provides access the VM network objects, which are the VMNetwork entity type.

To work with VM networks, including basic code examples, see the VMNetworks Collection [SPFSDK][VMMREF] topic.

Subnets can be created and attached to a VM network. Additionally, there is an option to automatically create a subnet when you create a VM network, by setting the VMNetwork.AutoCreateSubnet property to true. You only need to use a subnet when you are using static IP addresses. If IP addresses are being assigned by a DHCP server, you can skip working with subnets. Otherwise, if you want to create a subnet, send an HTTP POST (create) operation to the VMSubnets collection with the VMSubnet entity you are creating. Set the VMSubnet.VMNetworkID property to the GUID of the network you are creating the subnet for.

To work with subnets, including basic code examples, see the VMSubnets Collection [SPFSDK][VMMREF] topic.

Here are a few highlighted code examples related to VM networks and VM subnets.

Virtual Networks do not have any external connectivity. Virtual machines connected to the virtual networks will only be able to communicate with other virtual machines on the same network. To provide connectivity to an external network, a gateway service must be created. But, before a network gateway can be created, the backing-fabric VM network must be assigned to a logical network that already has been configured with a gateway service. See Configuring VM Networks and Gateways in VMM for more information.

A gateway can be configured for either NAT or VPN functionality during creation. Once created, the gateway cannot be changed and must be deleted and recreated if you wish to switch from NAT to VPN or vice versa. To work with a gateway, start with the VMNetworkGateways Collection [SPFSDK][VMMREF]. The following collections are related:

Here are a few highlighted code examples related to gateways.

Show: