Must have static IP address pool and VLANs for Provider Address (PA) network – network on which NVGRE encapsulated packets are sent All subnets in PA network must be routable to each other Front-end network(s) – network onto which packets are routed as they enter/exit the virtual network Routing must be configured to forward to virtual subnets if forwarding gateways are used Physical infrastructure requirements L2&L3
LogicalNetworkRequirements Management Can be DHCP or Static VMM, Hyper-V host OS, HNV Gateways must be able to communicate with each other over this network HNV PA Must have static IP pool Must be “one connected network”. Can contain multiple sites/VLANs, but all must be routable to each other. Must check box in UI that says “Allow hyper-v network virtualization on this logical network” Front-end Must have a static IP pool. May have multiple depending on security zones/VLANs you will route onto.
Physical switches must expose same L2 networks to each physical adapter in team Technologies like MC-LAG required with LACP teaming to different physical switches Physical switch requirements for NIC teaming Team
NVGRE task offload and VMQ strongly advised for 10Gb NICs and up Hyper-V host physical requirements
LACP Teaming RSS enabled on Host and Guest Enable VMQ NVGRE Offload Processor Performance Maximum Performance
RSS kicks in here
Hyper-V Network Virtualization VMNetwork in SCVMM Hyper-V Virtual Switch Use Logical Switch in SCVMM for team and vSwitch configuration HNV Core services
VM1 VM2 …
VM1 VM2 … Recommended teaming modes: Switch independent or LACP Load balancing mode: Hyper-V Port (Hyper-V 2012) Dynamic (Hyper-V 2012 R2) Mgmt NICCluster NICLM NIC SMB1 SMB2 SMB3 SMB4 Replica NIC
VM1 VM2 … Mgmt NICCluster NICLM NIC Replica NIC
VM1 VM2 …
Virtual switch settings Physical adapter Settings (Uplink) VM1 VM2 … Mgmt NICCluster NICLM NIC SMB1 SMB2 SMB3 SMB4 Replica NIC Physical adapter Settings (Uplink) Virtual switch settings Mgmt Cluster SMBReplica High Performance VM2 Live Migration Virtual adapter Settings
Multi-tenant gateway Forwarding gateway Deployed by VMM using service template. Service template requires: Scale-out file server Uses logical networks previously created Dedicated host node, two for high availability Edge Services
Hyper-V Node 1 Hyper-V Node 2 Management /24 VM Node1 (active) (VIP) VM Node2 (standby) Hyper-V Cluster VM guest Cluster
Hyper-V Node 1 Hyper-V Node 2 Management /24 VM Node1 (standby) VM Node2 (active) (VIP) Hyper-V Cluster VM guest Cluster
S2S NAT
NICs AD DNS DHCP WAP NVGRE Gateway NICs VMM SQL Tenant VM..
NIC AD DNS DHCP WAP1 NVGRE Gateway NIC WAP2 NIC Tenant VM AD DNS DHCP VMM1 SQL1 AD DNS DHCP VMM2 SQL2 NVGRE Gateway HA VM App. HAGuest Cluster Load Balancer
NIC FW/NAT AD DNS DHCP WAP1 NVGRE Gateway NIC WAP2 NIC Tenant VM AD DNS DHCP VMM1 SQL1 AD DNS DHCP VMM2 SQL2 NVGRE Gateway AD DNS AD DNS AD DNS
VMNetwork VMSubnet NetworkGateway VMNetworkGateway VPNConnection NATConnection
Internet
Destination IP:
Internet Destination IP:
Internet Destination IP:
NIC NVGRE Gateway NIC AD DNS DHCP VMM1 SQL1 AD DNS DHCP VMM2 SQL2 NVGRE Gateway HA VM App. HAGuest Cluster Load Balancer NIC Tenant VM NIC Tenant VM