0% found this document useful (0 votes)
0 views

Configuring Advanced Networking Features Hyper-V

This document outlines a lab exercise for configuring advanced networking features in Hyper-V, focusing on creating and using virtual switches, network adapters, and implementing DHCP guarding, VLANs, and bandwidth management. It provides step-by-step tasks for setting up virtual networks, verifying configurations, and demonstrating advanced features to enhance network security and performance. The lab aims to ensure users can effectively manage virtual machine networking in a Windows Server environment.

Uploaded by

rajbharathi821
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
0 views

Configuring Advanced Networking Features Hyper-V

This document outlines a lab exercise for configuring advanced networking features in Hyper-V, focusing on creating and using virtual switches, network adapters, and implementing DHCP guarding, VLANs, and bandwidth management. It provides step-by-step tasks for setting up virtual networks, verifying configurations, and demonstrating advanced features to enhance network security and performance. The lab aims to ensure users can effectively manage virtual machine networking in a Windows Server environment.

Uploaded by

rajbharathi821
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 62

Module 10: Configuring advanced networking features

Lab: Configuring advanced Hyper-V networking features

Scenario

Hyper V provides several options for allowing network communication among virtual
machines. You can use Hyper V to configure virtual machines that communicate with an
external network similar to the physical hosts that you deploy traditionally. You also can use
Hyper V to configure virtual machines that can communicate only with a limited number of
other virtual machines that are hosted on the same Hyper-V host. Windows Server provides
several advanced networking features for Hyper V and virtual machines. This lesson
describes the various advanced features that are available for Hyper V virtual networks,
which you can use to best meet your organization's needs.
Exercise 1: Creating and using Hyper-V virtual switches

Scenario

A. Datum Corporation has the Hyper V virtualization platform already installed. Before
deploying Hyper V and virtual machines in the production environment, you need to ensure
that you understand the different networking options that you can configure in Hyper V. First,
you will review the current networking configuration of the Hyper V host. Then, you will
create new virtual network adapters in the parent partition. You will also create different
types of Hyper V virtual switches and explore the connectivity options that exist when using
each of the switches.

Result After completing this exercise, you should have successfully configured the Hyper V
virtual switch.
Task 1: Verify the current Hyper-V network configuration

1. On LON-HOST1 send the CTRL+ALT+DEL command and login


as Administrator with the password Pa55w.rd
2. On LON-HOST1, on the task bar, click Hyper-V Manager.
3. In Hyper-V Manager, in the Actions pane, click Virtual Switch Manager.
4. In the Virtual Switch Manager for LON-HOST1 window, note the virtual
switch, Private Network, that has been created for LON-HOST1.

Task 2: Create virtual switches

1. On LON-HOST1, in the Virtual Switch Manager for LON-HOST1 window, in the


console tree, select the New virtual network switch item, and then in
the details pane, in the What type of virtual switch do you want to create? area,
ensure that External is selected, and then click Create Virtual Switch.
2. In the Name box, type External Switch, and then click OK.
3. In the Apply Networking Changes dialog box, click Yes.

4. The Virtual Switch Manager window closes. Open it again, and then note
the External Switch that you just created.
5. Repeat steps 1-4 to create an internal switch named Internal Switch.
6. Open the Virtual Switch Manager again, and then note the Internal Switch that you
just created.

Task 3: Create virtual network adaptersOn


LON-HOST1 minimize Hyper-V Manager and right
click Start, and select click Windows PowerShell (Admin).
1. At the Windows PowerShell command prompt, type the following commands, and
then press Enter after each line:
2. Add-VMNetworkAdapter -VMName LON-SVR1 -Name "New Network Adapter"

Connect-VMNetworkAdapter -VMName LON-SVR1 -Name "New Network Adapter" -SwitchName


"External Switch"

Task 4: Use the Hyper-V virtual switches

1. Minimize the PowerShell window and Return to Hyper-V Manager.


2. In Hyper-V Manager, in the Virtual Machines pane, right-click LON-SVR1, and
then click Settings.
3. In the Settings for LON-SVR1 window, in the console tree, select the New Network
Adapter.
4. Note that the virtual switch assigned is External Switch.

5. In the Settings window, click Cancel.In the Hyper-V Manager console,


highlight LON-SVR1 and then right-click and then click Start.
6. Wait 30 seconds for the virtual machine to boot then right-click LON-SVR1, and then
click Connect.

7. Send the CTRL+ALT+DEL command by using the shortcut key on the menu.
8. Click the View menu then select Full screen mode.

Sign in to LON-SVR1 as Adatum\AdatumAdmin with the password Pa55w.rd.

9. In the Networks dialog box, click Yes.


/8

10. Click Start, and then click Server Manager.

11. In the Server Manager console tree, select the Local Server node.
12. Click the hyperlink entitled IPv4 address assigned by DHCP, IPv6 enabled on
the Ethernet line.
13. In the Network Connections window, right-click Ethernet , and then click Status.
14. In the Ethernet Status window, click Details.

15. Note the IP address and other settings assigned to the network adapter. They should
be on the 10.0.0.39 network which is external to your virtual machine environment
which is on the 172.16.0.0/16 network.
16. Close all open windows and leave the Server Manager open.

Task 5: Add NIC Teaming

1. On LON-SVR1 in the Server Manager console tree, select the Local Server node.
2. In the Properties details pane, next to NIC Teaming, click the Disabled hyperlink.

In
the NIC Teaming dialog box, in the Adapters and Interfaces pane, select Ethernet ,
click Tasks and then click Add to New Team.
3. In the New team dialog box, in the Team name box, type LON-SVR1 NIC Team,
select Ethernet, and then click OK.

4. In the NIC Teaming dialog box, in the Teams pane, note the following:

• Team: LON-SVR1 NIC Team


• Status: OK
• Teaming Mode: Switch Independent
• Load Balancing: Address Hash
• Adapters: 1
Note: You have created a NIC team with only one adapter, which is not fault tolerant but
allows for the separation of network traffic when you are also using virtual local area
networks (VLANs).
Results: After completing this exercise, you should have successfully configured the
Hyper-V virtual switch.
Exercise 2: Configuring and using the advanced features of a virtual switch

Scenario

One of your managers wants to see how the Hyper V virtual switch can help to protect the
network clients from unauthorized DHCP servers. You plan to demonstrate how to configure
DHCP guarding and, at the same time, show the manager how simple it is to configure
VLANs and bandwidth management.

Result After completing this exercise, you should have successfully configured the advanced
features of the Hyper V virtual switch.
Task 1: Configure the network adapters to use DHCP guarding

1. Minimize the virtual machine connection window for LON-SVR1.


2. On LON-HOST1, return to Hyper-V Manager.
3. In Hyper-V Manager , in the Virtual Machines pane, select and right-click LON-
SVR1, and then click Settings.

4. In the Settings for LON-SVR1 on LON-HOST1 window, in the console tree, select
and then expand Network Adapter.
5. Under Network Adapter, click Advanced Features.

6. In the details pane, in the DHCP guard area, click Enable DHCP guard, and then
click OK.
7. Repeat steps 2-5 for LON-CL1.

Task 2: Configure and use DHCP guard


1. Connect to LON-CL1.

2. Send the CTRL+ALT+DEL command by using the shortcut key on the menu.
3. Click the View menu then select Full screen mode.

4. Log on as Adatum\AdatumAdmin with the password Pa55w.rd.

5. On LON-CL1, in the notification area of the taskbar, right-click the Network icon,
and then click Network and Internet Settings.
6. In the Windows Settings App on the Network & internet option scroll down and
select Advanced network settings.
7. On the Advanced network settings menu select More network adapter options.

8. Right click the London_Network network adapter and click Properties.

9. In the London_Network Properties window, in the This connection uses the


following items section, select Internet Protocol Version 4 (TCP/IPv4), and then
click Properties.
10. Note that LON-CL1 is using the following TCP/IP settings:
o IP Address: 172.16.0.50
o Subnet Mask: 255.255.255.0
o Default Gateway: 172.16.0.1
o Preferred DNS Server: 172.16.0.10
11. In the Internet Protocol Version 4 (TCP/IPv4) Properties window, click
the Obtain an IP address automatically and Obtain the DNS server address
automatically options, and then click OK.
12. In the London_Network Properties window, click Close.

Right click the London_Network and select Status.


13. In the Ethernet Status window, click Details.

14. Note the IP address shown on the IPv4 DHCP Server line of the Network
Connections Details window. It should be 172.16.0.10.
15. Click Close twice, and then close the Network and Sharing Center.
16. Minimize the virtual machine connection to LON-CL1.

17. Switch to the LON-SVR1 virtual machine connection window, and if Server Manager
is not already open, click Start, and then click Server Manager.
18. In Server Manager, click Dashboard and then click Add Roles and Features.

19. In the Add Roles and Features Wizard, click Next three times.
20. On the Select Server Roles page, click DHCP Server.
21. In the Add Roles and Features that are required dialog box that opens, click Add
Features, and then click Next.

22. On the Select Features page, click Next.


23. On the DHCP Server page, click Next.

24. On the Confirm installation selections page, click Install.


25. When the DHCP Server role installation successfully completes, select the
hyperlink Complete DHCP configuration.

26. On the DHCP Post-Install configuration dialog box, click Next.


27. On the authorization screen select Commit.
28. Finally select Close.

29. On the Add Roles and Featurs wizard on the Install progress screen select Close.
30. In Server Manager, click Tools, and then click DHCP.
31. In the console tree, expand DHCP and lon-svr1.adatum.com.

32. In the console tree, select and then right-click IPv4, and then click New Scope.

33. In the New Scope Wizard, on the Welcome page, click Next.
34. On the Scope Name page, in the Name box, type Lab 10 Scope, and then click Next.
35. On the IP Address Range page, in the Start IP address box, type 172.16.0.200, in
the End IP address box, type 172.16.0.210, in the Subnet Mask box, type 255.255.0.0,
and then click Next.

36. On the Add Exclusions and Delay page, click Next.


37. On the Lease Duration page, click Next.

38. On the Configure DHCP Options page, ensure that Yes, I want to configure these
options now is selected, and then click Next.
39. On the Router (Default Gateway) page, in the IP Address box, type 172.16.0.1,
click Add, and then click Next.

40. On the Domain Name and DNS Servers page, select 10.0.0.1 and select Remove,
and then click Next.
41. On the WINS servers page, click Next.

42. On the Activate Scope page, ensure that Yes, I want to activate this scope now is
selected, and then click Next.

43. On the Completing the New Scope Wizard page, click Finish.
44. Minimize the virtual machine connection window for LON-SVR1.

45. On LON-HOST1, click Start, and then click Windows PowerShell.


46. At the Windows PowerShell command prompt, type the following commands to
prevent LON-DC1 from issuing a DHCP lease, and then press Enter after each line:
47. Set-VMNetworkAdapter -VMName LON-DC1 -DhcpGuard On

Set-VMNetworkAdapter -VMName LON-SVR1 -DhcpGuard Off


48. Return to the LON-CL1 virtual machine connection window.
49. On LON-CL1, right-click Start, and then click Windows Termainal (Admin).

50. On the UAC prompt click Yes.


51. In the Command Prompt window, type the following commands, and then press
Enter after each line:
52. IPConfig /release

IPConfig /renew
53. Note that the IP address received by LON-CL1 is from the LON-SVR1 DHCP scope
that you created.
54. In the Windows Admin terminal window enter the following command:
55. ipconfig /all
56.
57. Note the DHCP server is 172.16.0.11 which is LON-SVR1.
Task 3: Configure and use VLANs

1. Minimize the virtual machine connection to LON-CL1.


2. Switch to the LON-SVR1 virtual machine connection window, and if Server Manager
is not already open, click Start, and then click Server Manager.
3. On LON-SVR1 in the Server Manager console tree, select the Local Server node.

4. In the Properties details pane, next to the NIC Teaming item, click
the Enabled hyperlink.
5. In the NIC Teaming dialog box, in the Teams pane, select LON-SVR1 NIC Team,
and then on the Tasks menu, click Delete.

6. In the NIC Teaming dialog box, click Delete team.


7. Minimize the virtual machine connection window for LON-SVR1.
8. On LON-HOST1, open Hyper-V Manager.

9. In Hyper-V Manager, in the Actions pane, click Virtual Switch Manager.


10. In the Virtual Switch Manager for LON-HOST1 window, select External Switch.

11. In the details pane for External Switch, in the VLAN ID area, select Enable virtual
LAN identification for management operating system, and then click OK.

12. While still on LON-HOST1, in Hyper-V Manager, in the Virtual Machines pane,
right-click LON-SVR1, and then click Settings.
13. In the Settings for LON-SVR1 on LON-HOST1 window, in the console tree,
select New Network Adapter.
14. In the details pane, in the VLAN ID section, select Enable virtual LAN
identification, and then click OK.

15. Carry out the above steps again but REMOVE the check box for the Enable virtual
LAN identification for both the External Network in Virtual Switch Manager and
on the New Network Adapter of LON-SVR1.

Note: If these settings are left enabled the next task will fail.
Task 4: Configure and use bandwidth management

1. While still LON-HOST1, in Hyper-V Manager, in the Virtual Machines pane,


right-click LON-SVR1, and then click Settings.
2. In the Settings for LON-SVR1 on LON-HOST1 window, in the console tree,
select New Network Adapter.
3. In the details pane, in the Bandwidth Management area, select Enable bandwidth
management.

4. In the Maximum bandwidth box, type 100, and then click OK.
5. Return to the LON-SVR1 virtual machine connection window.
6. On the LON-SVR1 in Server Manager. select Local Server, then select the Ethernet
IP address hyperlink.
7. In the Network Connections window, right click the Ethernet network adapter and
click Properties.

8. Select IPv4 and click Properties.


9. Click Use the following DNS server addresses and enter 8.8.8.8 in the Preferred
DNS server box and click OK.

10. Close all other open windows.


11. On the LON-SVR1 virtual machine, right-click the taskbar, and then click Task

Manager.
12. In the Task Manager window, click the More details arrow.
13. In Task Manager, click the Performance tab, and then select the second Ethernet
item. The Adapter name should be Ethernet.

14. Open Microsoft Edge from the Taskbar.


15. Move the Microsoft Edge window to one side with the Task Manager on the other
side, so that you can see both windows at same the time.
16. In the address bar of Internet Explorer, type www.microsoft.com and then press Enter.
17. While the data loads or attempts to load in the browser, observe the Task
Manager Ethernet item. It should not exceed a bandwidth speed of 100 Mbps.

Results: After completing this exercise, you should have successfully configured the
advanced features of the Hyper-V virtual switch.
Congratulations! You have now completed this lab. To continue to the next lab click End
Lab in the Tools Menu . If you wish to contiue with this lab at a later date ensure you save the
lab environment rather than ending it.

You might also like