Beruflich Dokumente
Kultur Dokumente
Aidan Finn
Books
System Center
2012 VMM
Windows Server
2012 Hyper-V
Networking Basics
VLAN ID = 101
Virtual Machines
VLAN ID = 102
VLAN Trunk
Virtual NICs
Generation 1 VMs can have:
(Synthetic) network adapter
Requires drivers (Hyper-V integration
components/services)
Does not do PXE boot
Best performance
Legacy network adapter
Emulated - does not require Hyper-V drivers
Does offer PXE
Bad performance
Generation 2 VMs have synthetic network adapters with PXE
7
Hyper-V Extensible
Switch
Replaces Virtual
Network
Handles network traffic
between:
Virtual machines
The physical network
The management OS
NIC = network
adapter
Switch Extensibility
Extension Types
Capturing
Monitoring
Example: InMon sFlow
Filtering
Packet monitoring/security
Example: 5nine Security
Forwarding
Does all the above & more
Example: Cisco Nexus
1000V
NIC Teaming
NIC Teaming
Failover:
If one physical path (NIC or top-of-rack switch) fails
then traffic automatically moved to another NIC in the
team.
Terminology
Team
Interfaces,
Team NICs, or
tNICs
Team
Team
members
--or-Network
Adapters
Connection Modes
Switch Independent mode
Doesnt require any configuration of a
switch
Protects against adjacent switch
failures
Allows Standby NIC
Switch
independent
team
2. LACP Teaming
Also known as IEEE 802.1ax or 802.3ad
Switch
dependent
team
2. Hyper-V port
Hashes the port number on the Hyper-V switch that the traffic is
coming from. Normally this equates to per-VM traffic. Best if
using DVMQ.
NIC Team
Networking Stack
NIC Team
Hardware Offloads
RSS
100% utilized
Logical Processors {
Cores {
Core 1
Core 2
Core 3
Processors (Hyperthreading) {
Core 4
10
Core 5
CPU 0
11
Core 6
12
13
Core 7
14
15
Core 8
16
17
Core 9
18
19
Core 10
CPU 1
Management OS
Management
Live Migration
Cluster
SMB 3.0
Backup
rNIC1
rNIC2
Virtual Machine
NIC Team
20
21
Core 11
22
23
Core 12
DVMQ
100% utilized
Logical Processors {
Cores {
Core 1
Core 2
Core 3
Processors (Hyperthreading) {
Core 4
10
Core 5
CPU 0
11
Core 6
12
13
Core 7
14
15
Core 8
16
17
Core 9
18
19
Core 10
CPU 1
Management OS
Management
Live Migration
Cluster
SMB 3.0
Backup
rNIC1
rNIC2
Virtual Machine
NIC Team
20
21
Core 11
22
23
Core 12
vRSS
Added in WS2012 R2
RSS provides extra processing capacity for inbound traffic to a
physical server
Using cores beyond Core 0.
vRSS does the same thing in the guest OS of a VMM
Using additional virtual processors.
Allows inbound networking to VMM to scale out.
Obviously requires VMs with additional virtual processors.
The physical NICs used by the virtual switch must support DVMQ.
Enable RSS in the advanced NIC properties in the VMs guest OS
vRSS
100% utilized
CPU 0
CPU 2
CPU 1
CPU 3
CPU 4
CPU 5
CPU 6
CPU 7
Management OS
Management
Live Migration
Cluster
SMB 3.0
Backup
rNIC1
rNIC2
Demo: vRSS
SR-IOV Illustrated
Host
Root Partition
Host
Virtual
Machine
Hyper-V Switch
Root Partition
Virtual
Machine
Hyper-V Switch
Virtual
Function
Virtual NIC
Routing
VLAN Filtering
Data Copy
Physical
NIC
Routing
VLAN Filtering
Data Copy
Implementing SR-IOV
All management OS
networking features are
bypassed
You must create SR-IOV
virtual switches to begin with:
New-VMSwitch IOVSwitch1 NetAdapterName pNIC1
EnableIOV $True
NIC Team
Virtual NIC 1
SR-IOV Enabled
Virtual Switch 1
Physical NIC 1
Virtual NIC 2
SR-IOV Enabled
Virtual Switch 2
Physical NIC 2
Converging Networks
Not a new concept from hardware vendors
Introduces as a software solution in WS2012
Will cover this topic in the High Availability session
SMB 3.0
No longer just a file & print protocol
Learn more in the SMB 3.0 and Scale-Out File Server session
Thank You!
Aidan Finn
@joe_elway
www.aidanfinn.com
Petri IT Knowledgebase