Configuring VM Networks in VMM in System Center 2012 SP1 Illustrated Overview

The following illustration shows VM networks that are configured with network virtualization in VMM in System Center 2012 SP1. For some networking elements, fictitious names, such as “AdventureWorks” and “Contoso1,” are included to help illustrate the purpose of those elements.

Figure 2    VM networks with network virtualization

Network virtualization extends the concept of server virtualization to make it possible for you to deploy multiple VM networks on the same logical network. In the illustration, the “AdventureWorks” VM network is configured on top of the logical network called “Contoso1.” As indicated in the illustration, additional VM networks can be configured on top of the same logical network, so that additional tenants, clients, or customers can each have their own network and choose their own IP addresses, regardless of the IP addresses that are used in other VM networks.

In the preceding illustration, the names of elements that you configure by running a wizard or opening a property sheet are shown in bold text, while elements that are on a page of the wizard or on a tab of the property sheet are shown without bold text.

For an illustration that shows the underlying network object model for this configuration, see Figure 7, Network object model for VM networks configured with network virtualization.

In System Center 2012 Service Pack 1 (SP1), many of the VMM networking enhancements are based on Hyper-V network virtualization in Windows Server 2012. To understand these networking enhancements, it can be useful to review the illustrations and descriptions (especially the first illustration) of Hyper-V network virtualization in Network Virtualization technical details.

The following illustration shows VM networks in a VLAN-based configuration, in other words, where VLANs already exist in the physical and logical networks. For some networking elements, fictitious names, such as “Contoso2” and “VLAN_1” are included to help illustrate the purpose of those elements.

Figure 3   VM networks in a VLAN-based configuration

In the scenario that is illustrated here, the VLANs exist for a specific purpose such as isolation, and not for broadcast boundaries only. The illustration shows two VM networks that have been created, to match the two VLANs in the underlying physical and logical networks. With more VLANs, more VM networks could be created—typically, one VM network per VLAN.

In the preceding illustration, the names of elements that you configure by running a wizard or opening a property sheet are shown in bold text, while elements that are on a page of the wizard or on a tab of the property sheet are shown without bold text.

For an illustration that shows the underlying network object model for this configuration, see Figure 8, Network object model for VM networks in a VLAN-based configuration.

The following illustration shows a VM network that is configured to provide direct access to the underlying logical network. For some networking elements, fictitious names, such as “Contoso1” and “Internet_connection1,” are included to help illustrate the purpose of those elements.

Figure 4    VM network that provides direct access to the logical network

A VM network that provides direct access to the logical network contrasts with VM networks that use network virtualization. Another way of describing this is to say that a VM network that provides direct access provides “no isolation,” while VM networks that use network virtualization provide isolation from the logical network and from each other. On each logical network, you can have only one VM network that is configured with No isolation. However, on a logical network that allows network virtualization, you can have one VM network with no isolation and other VM networks with isolation (that is, with network virtualization).

In the configuration shown in the illustration, when a virtual machine is deployed, the choice of IP subnet/VLAN pair is made by VMM, based on the location (the host or cloud) where you are deploying the virtual machine.

In the preceding illustration, the names of elements that you configure by running a wizard or opening a property sheet are shown in bold text, while elements that are on a page of the wizard or on a tab of the property sheet are shown without bold text.

For an illustration that shows the underlying network object model for this configuration, see Figure 9, Network object model for a VM network that provides direct access to the logical network.

The following illustration shows a vendor network-management console that has been used to configure settings on a forwarding extension, for example, settings for logical networks, network sites, and VM networks. The illustration also shows a VMM management server that has been configured to import settings from the vendor network-management database. For some networking elements, fictitious names, such as “External1” and “AdventureWorks,” are included to help illustrate the purpose of those elements.

Figure 5   VM networks configured through a vendor network-management console

As the preceding illustration indicates, the VMM management server contains the appropriate provider software (which you must install). Although the illustration shows a particular configuration of VM networks, the VM network configuration could be different—it directly reflects any configuration that is in the vendor network-management database. With the configuration shown in the illustration, if network settings have been configured on the network-management console, they do not have to be configured again in VMM. Instead, the settings automatically appear in VMM.

For an illustration that shows the underlying network object model for this configuration, see Figure 10, Network object model for VM networks configured through a vendor network-management console.

The following illustration shows the network object model for VM networks that are configured with network virtualization.

For some objects, sample names such as “AdventureWorks” and “Contoso1” are included to help illustrate the purpose of those objects.

Figure 7   Object model for VM networks configured with network virtualization

As indicated in the illustration, the IP addresses on the VM network are also called the “customer address (CA) space” because these IP addresses are used by customers (or clients or tenants). The IP addresses on the logical network are also called the “provider address (PA) space” because these IP addresses are used by providers (or hosters).

The notation 1-M means “one to many.”

In the preceding illustration, bold text is used for each VMM object name, regardless of how that object is configured through the VMM console.

For an illustration of this configuration that is based more on how it appears in the VMM console, see Figure 2, VM networks configured with network virtualization.

The following illustration shows the network object model for VM networks in a VLAN-based configuration.

Figure 8   Object model for VM networks in a VLAN-based configuration

The following key explains the notations on the arrows:

• 1-1 means “one to one.”
  
  
• 1-M means “one to many.”
  
  
• M-1 means “many to one.”
  
  

In the preceding illustration, bold text is used for each VMM object name, regardless of how that object is configured through the VMM console.

For an illustration of this configuration that is based more on how it appears in the VMM console, see Figure 3, VM networks in a VLAN-based configuration.

The following illustration shows the network object model for a VM network that provides direct access to the logical network, with no isolation. This is the simplest configuration, where the VM network is the same as the logical network on which it is configured.

Figure 9   Object model for a VM network that provides direct access to the logical network

The following key explains the notations on the arrows:

• 1-1 means “one to one.”
  
  
• 1-M means “one to many.”
  
  

In the preceding illustration, bold text is used for each VMM object name, regardless of how that object is configured through the VMM console.

For an illustration of this configuration that is based more on how it appears in the VMM console, see Figure 4, VM network that provides direct access to the logical network with no isolation.

The following illustration shows the network object model for VM networks that are configured through a vendor network-management console and a forwarding extension. This configuration uses a virtual switch extension manager to enable communication with the vendor network-management console.

Figure 10   Object model for VM networks configured through a vendor network-management console

The following key explains the notations on the arrows:

• 1-1 means “one to one.”
  
  
• 1-M means “one to many.”
  
  

In the preceding illustration, bold text is used for each VMM object name, regardless of how that object is configured through the VMM console.

For an illustration of this configuration that is based more on how it appears in the VMM console, see Figure 5, VM networks configured through a vendor network-management console and a forwarding extension.