Scenario
You have been asked to demonstrate how you can use network virtualization to separate test and
preproduction environments that are using the same network infrastructure. IT management would like to ensure that the servers in both environments can use the same IP addresses, and can communicate with other servers that are part of the same environment.
Objectives
After completing this lab, you will be able to: • Configure Hyper-V network virtualization.
Lab Setup
Estimated Time: 20 minutes
Virtual machines: 20409B-LON-HOST1, 20409B-LON-HOST2, 20409B-LON-DC1, 20409B-LON-PROD1, 20409B-LON-PROD2, 20409B-LON-TEST1, and 20409B-LON-TEST2
User name: Adatum\Administrator Password: Pa$$w0rd
For this lab, you will use the available virtual machine environment.
Note: Because you will be using the same virtual machines in the next lab, do not revert the virtual machines. However, you can shut down all virtual machines after finishing this lab. You will be working in pairs. Communicate clearly with your lab partner, and cooperate fully with each other during this lab.
Exercise 1: Configuring Hyper-V Network Virtualization
Scenario
Your company is using VLANs to isolate network traffic between test and production environments. While this solution is sufficient, reconfiguring network equipment while removing servers and adding new virtual machines is challenging. As a result, you have been asked to demonstrate how network virtualization can achieve the same goal. To do this, you need to set up a proof of concept environment with four virtual machines. You then will use these virtual machines to demonstrate how to configure Hyper-V network virtualization.
The main tasks for this exercise are as follows:
1. Verify that network virtualization is not configured on LON-HOST1. 2. Verify that network virtualization is not configured on LON-HOST2. 3. Configure Hyper-V network virtualization.
4. Test Hyper-V network virtualization. 5. Remove Hyper-V network virtualization.
MCT USE ONL
Y. STUDENT USE PROHIBITED
Server Virtualization with Windows Server Hyper-V® and System Center 4-35
Task 1: Verify that network virtualization is not configured on LON-HOST1
Note: Only the student who is using LON-HOST1 performs this task.1. On LON-PROD1, ping the IP addresses of the following virtual machines: o LON-TEST1: 10.0.0.16
o LON-PROD2: 10.0.0.25 o LON-TEST2: 10.0.0.26
2. Confirm that LON-PROD1 has connectivity with all three virtual machines.
3. On LON-HOST1, in Windows PowerShell, use the Get-VMNetworkAdapter cmdlet to confirm that 20409B-LON-PROD1 has a VirtualSubnetId property value of 0, which means that virtual subnets are not in use.
4. On LON-HOST1, use the Get-NetVirtualizationLookupRecord cmdlet to verify that no virtualization lookup records are defined.
5. On LON-HOST1, use the Get-NetVirtualizationCustomerRoute cmdlet to verify that no virtualization customer routes are defined.
6. In Windows PowerShell, run the Get-NetAdapter cmdlet.
7. For the physical network adapter, under the ifIndex column, write down the Index number.
Task 2: Verify that network virtualization is not configured on LON-HOST2
Note: Only the student who is using LON-HOST2 performs this task. 1. On LON-TEST2, ping IP addresses of the following virtual machines:
o LON-PROD1: 10.0.0.15 o LON-TEST1 10.0.0.16 o LON-PROD2: 10.0.0.25
2. Confirm that LON-TEST2 has connectivity with the three virtual machines.
3. On LON-HOST2, use the Get-VMNetworkAdapter cmdlet to confirm that 20409B-LON-TEST2 has a VirtualSubnetId property value of 0, which means that virtual subnets are not in use.
4. On LON-HOST2, use the Get-NetVirtualizationLookupRecord cmdlet to verify that virtualization lookup records are not yet defined.
5. On LON-HOST2, use the Get-NetVirtualizationCustomerRoute cmdlet to verify that virtualization customer routes have yet to be defined.
6. In Windows PowerShell, run the Get-NetAdapter cmdlet.
MCT USE ONL
Y. STUDENT USE PROHIBITED
4-36 Creating and Configuring Virtual Machine Networks
Task 3: Configure Hyper-V network virtualization
1. On LON-HOSTx, open the file C:\LabFiles\Mod04\ConfigureNWx.ps1 in Windows PowerShell ISE. 2. Review the Windows PowerShell script to see how network virtualization is configured. Review also
the variables that are defined at the start.
3. In Windows PowerShell ISE, on the toolbar, press Run Script, or press F5. If you run the script on LON-HOST1, enter the index number of your physical server network adapter and the index number of your partner physical server network adapter that were recorded earlier.
Task 4: Test Hyper-V network virtualization
1. On LON-HOSTx, in Windows PowerShell ISE, use the Get-NetVirtualizationLookupRecord cmdlet to confirm that virtualization records are created for the IP addresses of LON-PRODx and LON-TESTx virtual machines.
2. Use the Get-NetVirtualizationCustomerRoute cmdlet to confirm that one virtualization route is defined.
Note: Only the student who is using LON-HOST1 will perform steps 3 and 4.
3. On LON-HOST1, use the Get-VMNetworkAdapter cmdlet to confirm that 20409B-LON-PROD1 has a VirtualSubnetId property with the value 5001, which you configured with the Windows PowerShell script.
4. On LON-PROD1, ping the following IP addresses: o LON-TEST1: 10.0.0.16
o LON-PROD2: 10.0.0.25 o LON-TEST2: 10.0.0.26
5. Verify that four replies are returned, but only from IP 10.0.0.25, which confirms that LON-PROD1 has connectivity with LON-PROD2, but it does not have connectivity with LON-TEST1 and LON-TEST2. Note: Only the student who is using LON-HOST2 will perform steps 6 and 7.
6. On LON-HOST2, use the Get-VMNetworkAdapter cmdlet to confirm that 20409B-LON-TEST2 has a VirtualSubnetId property with the value 6001, which you configured with the Windows PowerShell script.
7. On LON-TEST2, ping the following IP addresses: o LON-TEST1: 10.0.0.16
o LON-PROD1: 10.0.0.15 o LON-PROD2: 10.0.0.25
8. Verify that four replies are returned, but only from IP 10.0.0.16, which confirms that LON-TEST2 has connectivity with LON-TEST1, but it does not have connectivity with LON-PROD1 and LON-PROD2.
MCT USE ONL
Y. STUDENT USE PROHIBITED
Server Virtualization with Windows Server Hyper-V® and System Center 4-37
Task 5: Remove Hyper-V network virtualization
1. On LON-HOSTx, open the file C:\LabFiles\Mod04\RemoveNWx.ps1 in Windows PowerShell ISE. 2. Review the script to see how network virtualization configuration is removed.
3. In Windows PowerShell ISE, on the toolbar, press Run Script, or press F5. If you run the script on LON-HOST1, enter the index number of your physical server network adapter and the index number of your partner’s physical server network adapter that you recorded earlier.
4. After network virtualization is removed, confirm network connectivity by performing the following steps:
a. If you are using LON-HOST1, on LON-PROD1, ping the IP addresses of the following virtual machines:
LON-TEST1: 10.0.0.16 LON-PROD2: 10.0.0.25 LON-TEST2: 10.0.0.26
b. If you are using LON-HOST2, on LON-TEST2, ping the IP addresses of the following virtual machines:
LON-PROD1: 10.0.0.15 LON-TEST1: 10.0.0.16 LON-PROD2: 10.0.0.25
MCT USE ONL
Y. STUDENT USE PROHIBITED
4-38 Creating and Configuring Virtual Machine Networks
Module Review and Takeaways
Review Questions
Question: Where can you configure extended virtual switch functionalities, such as traffic monitoring and DHCP guard protection?
Question: Is there a limit on how many virtual switches you can create on a Hyper-V host? Question: Why is it that you can configure VLAN IDs for external and internal virtual switches, but you cannot configure VLAN ID for a private virtual switch?