Module 1 - Managing a Windows Server 2012 Network Infrastructure Student Manual

7/30/2019 Module 1 - Managing a Windows Server 2012 Network Infrastructure Student Manual

1/13

Published: [Enter Date]

Managing A Windows Server 2012 Network infrastructure

Module 1: Managing Network Infrastructure

Module ManualAuthor: James Hamilton-Adams, Content Master


2/13

Microsoft Virtual Academy Student Manual ii

Information in this document, including URLs and other Internet Web site references, are subject to change

without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail

addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real

company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should

be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the

rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval

system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or

otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights

covering subject matter in this document. Except as expressly provided in any written license agreement from

Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights,

or other intellectual property.

2012 Microsoft Corporation. All rights reserved.

Microsoft is either a registered trademark or trademark of Microsoft Corporation in the United States and/or

other countries.

The names of actual companies and products mentioned herein may be the trademarks of theirrespective owners.


3/13

Microsoft Virtual Academy Student Manual iii

Contents

CONTENTS .................................................................................................................................................................................................................. III

MODULE 1: MANAGING NETWORK INFRASTRUCTURE. .......................................................................................................................... 4

Module Overview ................................................................................................................................................................................................ 4

DHCP HIGH AVAILABILITY .................................................................................................................................................................................... 5

DHCP FAILOVER LOAD SHARING MODE ........................................................................................................................................................ 6

DHCP FAILOVER HOT STANDBY MODE .......................................................................................................................................................... 7

WHAT IS NIC TEAMING? ........................................................................................................................................................................................ 8

NIC TEAMING OPTIONS ...................................................................................................................................................................................... 10

WHAT IS HYPER-V QOS? ..................................................................................................................................................................................... 12

FURTHER READING AND RESOURCES ........................................................................................................................................................... 13

Send Us Your Feedback About This Document ........................................................................ Error! Bookmark not defined.


4/13


Microsoft Virtual Academy Student Manual 4

Module 1: Managing Network Infrastructure.

Module Overview

This module introduces key new networking capabilities within Windows Server 2012. You will

examine the new Dynamic Host Configuration Protocol (DHCP) high-availability solution, see optionsfor providing fault tolerance and higher bandwidth for network adapters, and see how you can apply

Quality of Service (QoS) within a Hyper-V environment to ensure predictability of networkperformance for virtual machine (VM) workloads.


5/13



DHCP High Availability

In Windows Server 2008 R2, you could provide high availability for DHCP by using two methods:

Configure DHCP on a Windows failover cluster.

Configure a split scope across two DHCP servers.

In Windows Server 2012, you can use a new feature called DHCP server failover to provide high

availability for DHCP without some of the limitations of the Windows Server 2008 R2 methods.

DHCP server failover enables you to configure two Windows Server 2012 DHCP servers to replicateIPv4 address pools and address leases to provide high availability for DHCP scopes. You can

configure DHCP failover on a per-scope basis, although you can also choose to provide DHCP failover

for all scopes on a given server.You can only use DHCP failover to make IPv4 DHCP scopes highly available. For IPv6 addressassignment, this will either be stateless IP auto configuration, which only uses DHCP to acquire

option details, or stateful DHCPv6, which you can configure as a split scope without risk ofexhausting the IP address pool.You can configure DHCP scopes as either load sharing or as hot standby, but you cannot use more

than two DHCP servers in the DHCP failover configuration.


6/13



DHCP Failover Load Sharing Mode

In load sharing mode, you enable both DHCP servers to respond to IPv4 lease requests and grant

leases to devices on connected subnets for which there is a corresponding DHCP scope.

If you configure two DHCP serversDHCP A and DHCP Bin a DHCP failover load sharing

configuration on your network, devices that request an IP address will be provided an address fromone of the DHCP servers based on the load sharing algorithm that you specify. For load sharing, the

default is to split the requests so that 50 percent of the requests are handled by each server. Youcan set the percentage of requests that each server will handle when configuring failover for the

scope.


7/13



DHCP Failover Hot Standby Mode

In hot standby mode, you configure one DHCP server to respond to IPv4 lease requests unless that

DHCP server fails, at which point the second DHCP server takes over issuing new lease requests.

If you configure two DHCP serversDHCP A and DHCP Bin a DHCP failover hot standby

configuration on your network, devices that request an IP address will be provided an address fromone of the DHCP servers based on which server you specify as active. When you configure thefailover relationship, you also choose what percentage of the address pool should be reserved for the

standby server. If the active server fails, the standby server should be able to issue addresses from

the reserved part of the address pool and be able to renew existing address leases.

You can configure each scope as either load sharing or hot standby independently.


8/13



What Is NIC Teaming?

Network interface card (NIC) teaming is the ability to combine two or more network adapters in a

single computer to behave as a single NIC within Windows.

NIC teaming provides two key benefits:

Network adapter fault tolerance. If one of the network adapters in the team fails, all

network traffic can be sent and received through the remaining adapters in the team.

Bandwidth aggregation. If you team three one-gigabit network adapters in a team, theteam can function as a single three-gigabit network adapter.

In addition, a teaming solution may also enable you to configure additional virtual network interfaces

(referred to as tNICs) in a team to send and receive traffic only from specified virtual LANs (VLANs).

In previous versions of Windows Server, NIC teaming has only been available through third-party

software or driver solutions, and often only for specific network adapter hardware. In Windows

Server 2012, NIC teaming is vendor, hardware, and line-speed agnostic. For example, you canconfigure a NIC team by using a combination of a one-gigabit Broadcom NIC, a one-gigabit Intel NIC,and a 100-megabit Realtek NIC.

You can configure up to 32 adapters in one team and up to 32 teams per server. You can also createteams within a VM that has two or more network adapters; however, within a VM, only two team

members are supported, although the interface is not automatically limited to two members.

Note: You can only team Ethernet adapters. You cannot create a team using other NIC teams as

team members. NIC teaming is not compatible with Single Root I/O Virtualization (SR-IOV), remotedirect memory access (RDMA), or TCP Chimney offloading.

When you create a NIC team, Windows Server 2012 creates a default team NIC (tNIC) to represent

the team interface. This tNIC receives and processes all traffic no matter which VLAN ID the traffic istagged with. You can create additional tNICs for the same team that act as virtual network interfaces


9/13



that can have a specific VLAN ID associated with them. These tNICs only receive traffic tagged with

the associated VLAN ID. If the default tNIC is removed, only associated VLAN traffic can be received

by the team.

Note: Do not use tNICs with VLAN IDs for Hyper-V VMs. For Hyper-V, it is important to use thedefault tNIC on the team and perform any VLAN segregation within a Hyper-V Extensible Switch;

otherwise, VMs may never receive network packets.


10/13


Microsoft Virtual Academy Student Manual

10

NIC Teaming Options

NIC teaming in Windows Server 2012 offers a choice of teaming mode and load balancing mode.

The following teaming modes are available:

Switch independent teaming. Switch independent teaming does not require any specialconfiguration at the network switches connected to the tNICs.

Switch dependent static teaming (also known as generic teaming). Static teaming

uses Institute of Electrical and Electronics Engineers, Inc. (IEEE) 802.3ad draft v1, and itrequires additional configuration of the connected network switch. Any changes to the team

configuration, such as adding an additional NIC to the team, also require manualconfiguration of the switch.

Switch dependent dynamic teaming. Dynamic switch dependent teaming is possible byusing IEEE 802.1ax, which implements Link Aggregation Control Protocol (LACP). LACP

enables the dynamic creation and reconfiguration of the team information on the network

switch that the tNICs are connected to, although you must first enable LACP on the switch.

The following load balancing modes are available: Hashing. The NIC teaming component creates a hash from information within the packet and

uses the hash value to determine which tNIC should handle the packets. This ensures that

packets from the same TCP stream are handled by the same adapter. Hashing also typically

ensures load balancing of packets across the adapters in the team, although some third-partysolutions offer smart or adaptive load balancing, which can improve the load balancing effort.

Hashing can use one of three different sets of information in the packet:o Source and destination media access control (MAC) address.o Source and destination IP address, with or without MAC addresses (known as 2-tuple

hashing).o Source and destination TCP ports, usually with IP addresses (known as 4-tuple

hashing). This is the default hashing mode.


11/13



11

Hyper-V switch port. This hashes the port number on the Hyper-V switch that the traffic is

coming from. You should only use this mode when running Hyper-V VMs on the host.

Note: Switch independent teaming with hashing sends traffic from all active members but only

receives on the primary member. However, switch dependent hashing sends and receives on allactive members.


12/13



12

What Is Hyper-V QoS?

In Windows Server 2012, Hyper-V QoS enables you to configure maximum and minimum network

transmission rates for VM network adapters.

Setting a maximum transmission rate to a specified value ensures that the VM network adapter

cannot transmit or receive more data per second than the limit. Setting a maximum transmissionrate to 0 removes any maximum rate limit.

You can set a minimum bandwidth weight (a value between 0 and 100) to apply relative values to

different VM adapters on the same host, or you can specify an absolute minimum bandwidth value inbits per second for a VM adapter. Hyper-V QoS can use a Hyper-V virtual switch or a 5-tuple traffic

filter, which can identify a traffic flow for which a minimum bandwidth is guaranteed.

You set maximum and minimum bandwidth by using the Set-VMNetworkAdapter Windows

PowerShell cmdlet.

Windows Server 2012 also supports data center bridging (DCB) when using appropriate hardware,

such as DCB-capable network adapters and switches. You can use DCB to provide guaranteedbandwidth to different types of network traffic on a converged network infrastructure, sometimescalled a converged fabric. Converged fabric typically has several different traffic types, such as

traditional Windows Server workloads, high-speed storage area network (SAN) storage traffic, and

voice over IP (VoIP). For these traffic types to coexist, it is important to be able to specify minimumbandwidth for SAN storage protocols, for example. With DCB, you can specify eight traffic types with

corresponding minimum bandwidth settings.


13/13



13

Further Reading and ResourcesStep-by-Step: Configure DHCP for FailoverNIC Teaming OverviewQuality of Service (QoS) Overview
http://technet.microsoft.com/en-us/library/hh831385http://technet.microsoft.com/en-us/library/hh831385http://technet.microsoft.com/en-us/library/hh831648http://technet.microsoft.com/en-us/library/hh831648http://technet.microsoft.com/en-us/library/hh831679http://technet.microsoft.com/en-us/library/hh831679http://technet.microsoft.com/en-us/library/hh831679http://technet.microsoft.com/en-us/library/hh831648http://technet.microsoft.com/en-us/library/hh831385

Documents

Module 1 - Managing a Windows Server 2012 Network Infrastructure Student Manual