l to make this task faster. How it works The Logical Switch, Default, sits on top of the NIC team that was declared in the Standard Uplink Port Profile. The virtual network adapters are then created within the management partition of the Hyper-V host and attached to this Logical Switch; all network traffic from virtual machines and from the host flows through the switch. The weighting that was declared in the tenant Virtual Port Profile and the profiles that were used for the Management, Cluster, and Live Migration ensure that the critical management functions of the Hyper-V host are not overwhelmed by the virtual machine traffic. Chapter 2 There's more... Now, the Hyper-V hosts have the switches and the required virtual network adapters, so these Hyper-V hosts should be clustered. Please visit http://technet.microsoft.com/ en-gb/library/gg610621. aspx for instructions on how to cluster these Hyper-V hosts. Creating the Virtual Machine Networks for Tenants Each Tenant requires its own VM Network, and optionally a subnet (or several) within. Once the VM Networks for the Tenants have been created, it will be possible to create VMs and deploy them into each VM Network. A VM Network is the software defined network. Each VM network is completely isolated and you can have up to 16,777,216 VM Networks. In this recipe, we will create two VM Networks: Tenant A using an IP subnet 10.0.0.0/24 Tenant B using an IP subnet 10.0.0.0/24 Getting ready Decide what VM Network names the Tenants will have and the IP subnets they will have. How to do it... The following diagram shows you the high-level steps involved in this recipe: Overview of Recipe: Actions: Creation of 2 VM Networks (one for Tenant A and one for Tenant B) Creation of 1 IP Pool per VM Network Configuring Networks for Hyper-V Network Virtualization This will result in two VM Networks, each with one IPv4 subnet containing a pool of IPs that can be distributed to newly created VMs. Now perform the following steps: 1. Open the VMs and Services workspace, navigate to VM