In this procedure, you create a logical network that will be used for tenant traffic. The logical tenant network will support VM traffic and, later, network virtualization. As part of completing the creation wizard, you’ll also create a default network site, which will be associated with the default All Hosts host group.
1. Log on to your VMM01 VM using contoso\administrator credentials.
2. From the desktop, launch the System Center Virtual Machine Manager console, and enter VMM-HA as the name. Click Connect. By entering VMM-HA, you’ll be connecting to the highly available System Center Virtual Machine Manager configuration you constructed in Chapter 2, "Deploying the management cluster."
3. Open the Settings workspace. Under Settings in the top-left corner, ensure General is selected.
4. In the main console window, double-click Network Settings.
5. In the Network Settings window, clear the Automatic Creation Of Logical Networks check box, shown in Figure 3-3, and then click OK. By clearing this box, you prevent the automatic creation of a logical network for each DNS suffix on a Hyper-V host when the host is added to System Center Virtual Machine Manager’s management control. In this POC, you want to keep control over the logical networks that are created, and this setting allows that control.
FIGURE 3-3 The Create Logical Networks Automatically check box 6. Open the Fabric workspace on the lower-left side of the console.
7. At the top of the System Center Virtual Machine Manager console, on the Home tab, in the Show group, click Fabric Resources.
8. In the Fabric pane, expand Networking, and then click Logical Networks.
9. On the Home tab, in the Create group, click Create Logical Network.
10. The Create Logical Network Wizard opens. On the Name page, enter Tenant_LN.
11. Leave the One Connected Network option selected, as shown in Figure 3-4, and select the check box next to Allow New VM Networks Created On This Logical Network To Use Network Virtualization. (You will learn more about network virtualization in Chapter 6, "Configuring network virtualization.")
12. Select the check box next to Create A VM Network With The Same Name To Allow Virtual Machines To Access This Logical Network Directly, and then click Next.
FIGURE 3-4 VM network check box settings for a new tenant logical network
13. On the Network Sites page, click Add. System Center Virtual Machine Manager automatically generates a site name that consists of the logical network name followed by an underscore and a number.
14. Under Host Groups That Can Use This Network Site, select All Hosts. For now, you'll assign the logical network and IP address pool to the All Hosts host group because you have yet not created any additional host groups. However, when you start adding compute hosts and management hosts to the System Center Virtual Machine Manager
management scope, you'll assign the logical network and network sites to the particular host groups you create.
15. Under Associated VLANs And IP Subnets, shown in Figure 3-5, click Insert Row. Associate a particular network with the site.
16. Leave the VLAN ID blank, and set the network associated with this site to 10.10.0.0/24 to represent the Tenant Network range. By default, if you leave the VLAN field empty, System Center Virtual Machine Manager assigns a VLAN of 0. This tells System Center Virtual Machine Manager not to use VLANs. In trunk mode, VLAN 0 indicates a native VLAN. You'll define specific IP address pools in a subsequent step. Click Next.
FIGURE 3-5 Tenant network VLAN and IP subnet settings
17. On the Summary page, review the settings, and then click Finish.
18. The Jobs window appears. Make sure the job has a status of Completed, and then click Close to close the Jobs window.
19. Verify that the logical network appears in the Logical Networks And IP Pools pane. Right-click the logical network, and click Properties. Click the Network Site tab, and verify that the intended network sites appear on the tab. Click Close in the Properties window.
20. Stay on the Networking view within the Fabric workspace of the System Center Virtual Machine Manager console for the next step.
Before you proceed to the next step in the configuration, it’s important to understand a little more detail about static IP address pools and how System Center Virtual Machine Manager helps you to manage them.
Static IP address pools
If you associate one or more IP subnets with a network site, you can create static IP address pools from those subnets. Static IP address pools make it possible for System Center Virtual Machine Manager to automatically allocate static IP addresses to VMs that are running on any managed Hyper-V, VMware ESXi, or Citrix XenServer host. From the pool to standalone VMs, System Center Virtual Machine Manager can automatically assign static IP addresses to VMs that are deployed as part of a service and assign IP addresses to physical computers when you use System Center Virtual Machine Manager to deploy them as Hyper-V hosts or scale-out file servers.
Additionally, when you create a static IP address pool, you can define a reserved range of IP addresses that can be assigned to load balancers as virtual IP addresses. System Center Virtual Machine Manager automatically assigns a virtual IP address to a load balancer during the deployment of a load-balanced service tier. You will not be deploying a load balancer as part of this POC.
When you create a static IP address pool, you can configure associated information, such as default gateways, DNS servers, DNS suffixes, and Windows Internet Name Service (WINS) servers. All of these settings are optional. IP address pools support both IPv4 and IPv6 addresses. However, you cannot mix IPv4 and IPv6 addresses in the same IP address pool.