108 CHAPTER 2 Configuring Hyper-V Hosts FIGURE 2-26 The Create Virtual Networks page of the Hyper-V role Installation Wizard After the virtual switch is created, the network adapter begins to act like a normal switch, except that the switch is software-based and ports are added and removed dynamically as needed. This process is not duplicated when you work with Hyper-V on Server Core. Because you use a command line to add the Hyper-V role, you do not get to create a virtual network switch. Instead, the virtual network switch must be created manually after the role installation and its corresponding reboot. External connections will automatically be linked to the virtual network switch. In this case, all network traffic is routed through the virtual switch as if it were a physical switch (see Figure 2-27). Because the external connection is linked to a port on the virtual switch, applications within the VM that must connect externally will have all traffic routed through the virtual network adapter to the port on the virtual switch, then through the physical network adapter and out to the external world. Lesson 3: Configuring Virtual Networking CHAPTER 2 109 Networking Application Virtual NIC Virtual Switch VMOne Networking Application Virtual NIC VMTwo Networking Application Physical Server Virtual NIC binding: All except Microsoft virtual network switch protocol Physical NIC binding: Microsoft virtual network switch protocol Physical Switch FIGURE 2-27 The operation of an external network in Hyper-V Internal connections are not linked to the virtual network switch. Because of this, they can only communicate with the host and with other virtual machines bound to the same network (see Figure 2-28). Private networks are not linked to the virtual network switch either. They only provide access to other virtual machines linked to the same network (see Figure 2-29). Hyper-V can emulate two different types of network adapters: the network adapter and the legacy network adapter. For virtual machines to be able to work with the network adapter, they must be able to install and run the Hyper-V Integration Services. If the operating system in a VM does not support Integration Services, it must use the legacy network adapter, which emulates an Intel 21140–based PCI Fast Ethernet Adapter. Note that the legacy network adapter is also required if a virtual machine needs to boot from a network, such as when you use the Preboot Execution Environment (PXE) to boot a machine from the network to install an operating system into it. In this example, there is no operating system yet on the VM and thus no Integration Services are installed. This is why only the legacy network adapter works in this case. 110 CHAPTER 2 Configuring Hyper-V Hosts Virtual Switch Networking Application Virtual NIC binding: All except Microsoft virtual network switch protocol Networking Application Virtual NIC VMOne Networking Application Virtual NIC VMTwo FIGURE 2-28 The operation of an internal network in Hyper-V Virtual Switch Networking Application Virtual NIC VMOne Networking Application Virtual NIC VMTwo FIGURE 2-29 The operation of a private network in Hyper-V exaM tIp LEGACY NETWORK ADAPTERS Make sure to remember that you must use the legacy network adapter to have a machine boot from the network—this is definitely on the exam. When VMs need to communicate to the parent partition, they can do so in one of two ways. First, the VM can be linked to an external virtual network adapter that then routes the traffic to the port on the virtual switch and out to the physical adapter. The traffic then returns through a second physical adapter to communicate with the Hyper-V system. Second, the VM can be routed directly through the virtual network adapter to the parent partition. Although this Lesson 3: Configuring Virtual Networking CHAPTER 2 111 second method is more efficient because the traffic does not have to loop back into the system, this won’t occur until the virtual network uses its built-in algorithm to determine the most efficient port to direct traffic to and then send the traffic to that port. Traffic is sent to all ports by default until the algorithm kicks in and determines the best possible route. Using the Virtual Network Manager Tool You rely on the Virtual Network Manager tool within Hyper-V Manager to create and modify virtual networks. As a best practice, you should create at least one of each of the three virtual network adapter types and name them appropriately. This will facilitate your choices when you create or configure virtual machines and you need to attach them to a given network. As mentioned in the previous section, when you install the Hyper-V role on a full installation and you select to create a virtual network during the installation process, Hyper-V automatically turns the selected physical adapter into a virtual network switch and creates the first external virtual network adapter. However, Hyper-V does not rename either adapter, which can lead to some confusion when working with network adapters on Hyper-V hosts. Creating virtual network adapters is relatively simple. You use the Virtual Network Manager link in the Actions pane to launch the tool (see Figure 2-30). This tool lets you create any of the three network adapter types as well as rename and modify existing virtual network adapters. If you are using the full installation of Windows Server 2008, the first thing you should do is rename the external virtual network adapter that was automatically created during the installation of the Hyper-V role to a more significant name such as Hyper-V External. FIGURE 2-30 Using the Virtual Network Manager 112 CHAPTER 2 Configuring Hyper-V Hosts You can then proceed to create additional networks. Create at least one of each of the three network adapter types. To do so, you need to click New Virtual Network to the left of the dialog box, choose the type of network you want to create, and then click Add. This creates the network adapter. Name it and provide a description for the adapter. Click Apply to set your changes. Repeat the process for each adapter type. Note that you can assign a virtual local area network (VLAN) number to both the external and internal network adapter types. This assignment can be done at any time, either during the creation of a network adapter or through reconfiguration once it has been created. This is done through the Enable Virtual LAN Identification For The Parent Partition option and is used to specify an identification number to isolate network traffic from the operating system that runs in the parent partition (see Figure 2-31). FIGURE 2-31 Assigning a VLAN to the parent partition You can use virtual LAN identification as a way to isolate network traffic. However, this type of configuration must be supported by the physical network adapter. VLAN tagging isolates all parent partition traffic using this network adapter. This does not affect the operation of a virtual machine in any way, but it segregates parent partition traffic from virtual machine traffic. You can also assign VLANs to virtual machines through the virtual machine configuration (see Figure 2-32). In this case, the traffic initiated by the virtual machine going through this network adapter will be limited to the virtual LAN ID number you assign. FIGURE 2-32 Assigning a VLAN to a network adapter in a VM More Info PARENT PARTITION VLAN TAGGING For more information about configuring virtual LAN identification for the parent partition, see the Hyper-V deployment content at http://go.microsoft.com/fwlink/?LinkID=108560. Note that when you create virtual network adapters, corresponding adapters are created in the network connections of the parent partition. This occurs for both the external and internal network adapter but not for the private network adapter because the private adapter is not bound to the physical adapter in any way. Lesson 3: Configuring Virtual Networking CHAPTER 2 113 You should rename the connections created in Network Connections so that you can more easily identify which connection is which (see Figure 2-33). Do this using the Rename command in the shortcut menu for each adapter. FIGURE 2-33 Renaming adapters to better identify them Practice Working with Virtual Networks In this practice, you will configure virtual networking on your two host servers, ServerFull01 and ServerCore01. This practice consists of two exercises. The first focuses on creating additional virtual network adapters on the full installation of Windows Server 2008. In the second, you create a virtual network switch on Server Core and then you create virtual network interface cards on Server Core. When this practice is complete, your host servers will be configured to support all types of networking in Hyper-V. exercise 1 Create Virtual Network Interface Cards on a Full Installation In this exercise you will configure additional network adapters on the full installation of Windows Server 2008. This exercise is performed on ServerFull01. Log in with domain administrator credentials. 1. This operation is performed either with Hyper-V Manager or with the Hyper-V Manager section of Server Manager. Click ServerFull01 in the tree pane under Hyper-V Manager. 2. Click Virtual Network Manager in the Actions pane of the console. This opens the Hyper-V Virtual Network Manager dialog box. Note the existing network. This network was created when you installed the Hyper-V role. 3. Rename the existing connection. Click the connection in the left pane of the dialog box, select the name in the right pane, and rename it Hyper-V External. Click Apply. Note that this network is of an external type and is bound to one of your physical network interfaces. 114 CHAPTER 2 Configuring Hyper-V Hosts 4. Now create a second virtual adapter. Click New Virtual Network in the left part of the dialog box, choose Internal, and then click Add. 5. Name the adapter Hyper-V Internal and make sure Internal Only is selected as the connection type. Note that as with the External connection type, you can assign a VLAN to the parent partition. You do not need to do so at this time. Click Apply. 6. Now create a third virtual adapter. Click New Virtual Network in the left part of the dialog box, choose Internal, and then click Add. 7. Name the adapter Hyper-V Private and make sure Private Virtual Machine Network is selected as the connection type. Note that this network type does not allow you to assign a VLAN to the parent partition because there is no link to the parent partition in this network connection type. Click OK. Your three network types have been created. 8. Move to the Network Connections window to rename the connections. Renaming the connections makes it much easier to link the network with the network type when working in the Windows interface of the parent partition. Click Start and then Control Panel. In Control Panel, click Network And Internet, then click Network And Sharing Center, and then click Manage Network Connections in the Tasks section of the window. This opens the Network Connections window. 9. Rename each connection. You can check each connection’s properties to make sure you are renaming the appropriate network. Begin with the new virtual switch, which actually is your physical network adapter. Right-click it and choose Rename. Type Physical NIC and press Enter. The properties of this NIC should only list the Microsoft Virtual Network Switch as enabled. 10. Repeat the process with each adapter in the window. Rename the external adapter to Hyper-V External and the internal adapter to Hyper-V Internal. Your Hyper-V network configuration is complete. exercise 2 Create a Virtual Switch on a Server Core installation In this exercise you will create a virtual network switch on Server Core. Note that the Server Core Hyper-V role installation does not create this virtual switch the way the full installation does. You must create this switch interactively. Perform this operation from ServerFull01. Log on with domain administrator credentials. 1. This operation is performed either with Hyper-V Manager or with the Hyper-V Manager section of Server Manager. Click ServerCore01 in the tree pane under Hyper-V Manager. 2. Click Virtual Network Manager in the Actions pane of the console. This opens the Hyper-V Virtual Network Manager dialog box. Note the there is no existing network adapter in this interface. 3. The New Virtual Network and the External Network type should already be selected. Click Add. 4. Name this adapter Hyper-V External, make sure the External connection type is selected, and make sure the appropriate adapter is selected in the drop-down list. Lesson 3: Configuring Virtual Networking CHAPTER 2 115 This adapter should not be the one you are using to remotely connect to Server Core. Do not apply a VLAN to the parent partition at this time. Click Apply. The Apply Networking Changes warning will appear (see Figure 2-34). Click Yes. You shouldn’t have issues with this change as long as you selected the appropriate adapter in the drop-down list. If you don’t, you will lose connectivity with the Server Core computer. FIGURE 2-34 The Hyper-V Networking Changes warning 5. Create a second virtual adapter. Click New Virtual Network in the left part of the dialog box, choose Internal, and then click Add. 6. Name the adapter Hyper-V Internal and make sure Internal Only is selected as the connection type. Note that as with the External connection type, you can assign a VLAN to the parent partition. You do not need to do so at this time. Click Apply. 7. Create a third virtual adapter. Click New Virtual Network in the left part of the dialog box, choose Internal, and then click Add. 8. Name the adapter Hyper-V Private and make sure Private Virtual Machine Network is selected as the connection type. Note that this network type does not allow you to assign a VLAN to the parent partition because there is no link to the parent partition in this network connection type. Click OK. Your three network types have been created. 9. You can also rename the network adapters in Server Core to make them easier to manage. To do so, you need to log on to the Server Core machine and use the netsh command to rename each connection. Log on with domain administrator credentials. 10. Begin by listing the adapters, making note of the adapter ID number and then rename each adapter. Use the following commands. In this case, the old connection names were Local Area Connection 3 and Local Area Connection 4. Your connection names may differ from these. This is why you run the show interface command first. netsh interface ipv4 show interface netsh interface set interface name="Local Area Connection 3" newname ="Hyper-V External" netsh interface set interface name="Local Area Connection 4" newname ="Hyper-V Internal" 116 CHAPTER 2 Configuring Hyper-V Hosts If you run the show interface command again (hint: use the up arrow to call the command back), you will see that the interfaces have been renamed. Networking is ready on this server. Quick Check 1. How many virtual networks cards can each enlightened VM access? 2. What is the difference between an external connection and an internal connection? Quick Check Answers 1. Each enlightened VM can access up to 12 virtual network cards—8 virtual network adapters and 4 legacy virtual network adapters. 2. The external adapter is a connection to a physical network adapter. Machines using this adapter can access a physical network, other virtual machines on this network, the host server, and all other external virtual or physical machines connected to this network. The internal adapter is a connection that only supports communications between the host server and the VM and other virtual machines on the same network. Suggested Practices CHAPTER 2 117 Case Scenario: Networking Virtual Machines In the following case scenario, you will apply what you have learned about preparing your Hyper-V host servers. You can find answers to these questions in the “Answers” section on the companion CD which accompanies this book. You are the resource pool administrator for the Graphics Design Institute and you have been asked to prepare the network connections required to host virtual machines on a Hyper-V server. Table 2-3 outlines the VMs you will require and the type of networking traffic each will generate. Your job is to propose which type of virtual network adapter should be used for each VM. TABLE 2-3 Virtual Machine List VIRTUAL MACHINE NETWORK TRAFFIC TYPE DC01 AD DS for a production forest. DC02 AD DS for a production forest. Web01 Web server running Internet Information Services for a public Web site. File01 Internal production file server. DCTest01 AD DS for a test forest. This forest should not have any connection to the production forest. WebTest01 Staging Web server for the production Web site. 1. Based on the information in Table 2-3, which connection type would you use for the production machines? 2. Which connection type should you use for the test machines? 3. The Web production team wants to be able to upload content into the test Web server, and once it passes approval, they want to automatically upload it from the test server to the production server. Which type of connections should each server contain to make this scenario work? Suggested Practices To help you successfully master the exam objectives presented in this chapter, complete the following tasks. Windows Server 2008 Configuration n Practice 1 Take the time to become thoroughly familiar with the configuration of the full installation. It will be useful for the exam, and also for the configuration of your own servers. [...]... http://www .microsoft. com/windowsserver2008/en/us/clustering-multisite.aspx For a full list of partners for Windows Server 2008 clusters, go to http://www .microsoft. com/­ windowsserver2008/en/us/clustering-partners.aspx For information on what to consider when deploying a multi-site cluster, look up Knowledge Base article number 9 4704 8 at http://support .microsoft. com/default.aspx/kb/9 4704 8/en-us Creating a Hyper-V Two-Node Cluster... other node More Info  Quick Migration with Hyper-V Microsoft has released a white paper on how to use Quick Migration with Hyper-V D ­ ownload it from http://www .microsoft. com/downloads/details.aspx?FamilyID= fdd083c 6 -3 fc 7-4 70b-856 9-7 e6a19fb0fdf&DisplayLang=en More Info  Working with Failover Clustering Microsoft has released an online virtual lab for Windows Server 2008 Enterprise Failover Clustering If... work with the Microsoft StorPort storage driver As outlined in Table 3- 1 , you can use several different configurations to run the single-site two-node cluster Table 3- 2 outlines the required components based on the type of storage connectivity you will use Table 3- 2   Network and Storage Component Requirements Component SAS iSCSI Fibre Channel Comments Network adapter for network traffic 3 3 3 2 Network... to the passive node for that service The advantage of a multi-site cluster is that the services it hosts are protected not only from equipment failures, but also from disasters affecting an entire site (see Figure 3- 3 ) Multi-Site Cluster Cluster VLAN Direct-Attached Storage Third-Party Replication Engine Witness File Share Figure 3- 3   Multi-site clusters use replication to protect a service’s data and... there is no GUI in Server Core Download the update to a location that is accessible to the computer you need to install it on and double-click to install Click OK to accept the installation (see Figure 3- 7 ) and click Close when the installation is complete Figure 3- 7   Adding the Failover Clustering Update for Hyper-V 1 36 CHAPTER 3 Completing Resource Pool Configurations Update Alert The Microsoft Cluster... unique, only one server hosts a particular service at one point in time This is different from the NLB cluster where each machine provides the same service Lesson 1: Configuring Hyper-V High Availability CHAPTER 3 1 23 End Users Unique NLB IP address NLB Redirector NLB Node 1 NLB Node 2 NLB Node 3 NLB Node 4 NLB Node 32 Figure 3- 1   Stateless NLB clusters can include up to 32 nodes Windows Server Failover... “ Understanding Failover Clustering Requirements The most common cluster type is the two-node single-site cluster This cluster requires several components to make it work Table 3- 1 outlines the requirements of this cluster configuration Lesson 1: Configuring Hyper-V High Availability CHAPTER 3 127 Table 3- 1   Two-Node Cluster Requirements Requirement Description Hardware Components The most common cluster... you have configured your Hyper-V hosts to run the Server Core i ­nstallation of Windows Server 2008 Remote management tools include the Hyper-V Manager, which is available as part of the Remote Server Administration Tools (RSAT) for Window Server Hyper-V Manager is sufficient to manage a small number of host servers However, when you begin to create massive farms of host servers all clustered together,... in Windows Server 20 03 clusters, however Also make sure your host servers are running the Enterprise or Datacenter editions of W ­ indows Server 2008 Other editions do not include the WSFC feature Note that Hyper-V 1 30 CHAPTER 3 Completing Resource Pool Configurations Server 2008 cannot run the Failover Clustering service either because it is based on the S ­ tandard edition of Windows Server 2008... Exam Tip  Hyper-V Two-node Clusters Pay close attention to the requirements and considerations for Hyper-V single-site clusters They are a definite part of the exam Multi-Site Clustering Requirements Although you can create single-site Hyper-V clusters and you must use shared storage to do so, you’ll find that the system requirements are considerably different in a Windows Server 2008 multi-site cluster . Configuring Hyper-V High Availability . . . . . . . . . . . . . . . . . . . .1 23 Understanding Failover Clustering 1 23 Creating a Hyper-V Two-Node Cluster 132 Lesson 2: Working with Hyper-V Host Remote. 2 NLB Node 3 NLB Node 4 NLB Node 32 FIGURE 3- 1 Stateless NLB clusters can include up to 32 nodes. Windows Server Failover Clustering supports two types of configurations: the single-site cluster. CHAPTER 3 Completing Resource Pool Configurations n Mix-and-match clusters In a mix-and-match cluster configuration, some nodes are configured as active-active whereas others are configured as active-passive.