html5-img
1 / 49

Windows Server 2012 NIC Teaming and SMB Multichannel Solutions

WSV314. Windows Server 2012 NIC Teaming and SMB Multichannel Solutions. Don Stanwyck, Jose Barreto Program Managers Microsoft Corporation. Agenda - Reliability is job one !. NIC Teaming Overview Configuration choices Managing NIC Teaming Demo SMB Multichannel Overview

zeal
Télécharger la présentation

Windows Server 2012 NIC Teaming and SMB Multichannel Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WSV314 Windows Server 2012NIC Teaming and SMB Multichannel Solutions Don Stanwyck, Jose Barreto Program Managers Microsoft Corporation

  2. Agenda - Reliability is job one! • NIC Teaming • Overview • Configuration choices • Managing NIC Teaming • Demo • SMB Multichannel • Overview • Sample Configurations • Troubleshooting • Demo

  3. What do NIC Teaming and SMB Multichannel have in common? • Reliability is job one • NIC Teaming provides protection against failures in the host • SMB Multichannel provides multi-path protections • More bandwidth is always a good thing • NIC Teaming and SMB Multichannel both provide bandwidth aggregation when possible • NIC Teaming and SMB Multichannel work together!

  4. Windows Server 2012Cloud Optimize Your IT Beyond Virtualization Windows Server 2012 offers a dynamic, multi-tenant infrastructure that goes beyond virtualization to provide maximum flexibility for delivering and connecting to cloud services. Modern Workstyle, Enabled Windows Server 2012 empowers IT to provide users with flexible access to data and applications from virtually anywhere on any device with a rich user experience, while simplifying management and helping maintain security, control and compliance. The Power of Many Servers, the Simplicity of One Windows Server 2012 offers excellent economics by integrating a highly available and easy to manage multi-server platform with breakthrough efficiency and ubiquitous automation. Every App, Any Cloud Windows Server 2012 is a broad, scalable and elastic server platform that gives you the flexibility to build and deploy applications and websites on-premises, in the cloud and in a hybrid environment, using a consistent set of tools and frameworks. NIC Teaming SMB Multichannel

  5. title NIC Teaming

  6. What is NIC Teaming? • Also known as….. • NIC Bonding • Load Balancing and Failover (LBFO) • . . . Other things • The combining of two or more network adapters so that the software above the team perceives them as a single adapter that incorporates failure protection and bandwidth aggregation.

  7. . . . And? • NIC teaming solutions also provide per-VLAN interfaces for VLAN traffic segregation

  8. Why use Microsoft’s NIC Teaming? • Vendor agnostic – anyone’s NICs can be added to the team • Fully integrated with Windows Server 2012 • Lets you configure your teams to meet your needs • Server Manager-style UI that manages multiple servers at a time • Microsoft supported – no more calls to NIC vendors for teaming support or getting told to turn off teaming • Team management is easy!

  9. NIC teaming dismantledand vocabulary lesson Team Interfaces, Team NICs, or tNICs Team Team members --or-- Network Adapters

  10. Team connection modes Switch independent team • Switch independent mode • Doesn’t require any configuration of a switch • Protects against adjacent switch failures • Switch dependent modes • Generic or static teaming • IEEE 802.1ax teaming • Also known as LACP or 802.3ad • Requires configuration of the adjacent switch Switch dependent team

  11. Load distribution modes • Address Hash – comes in 3 flavors • 4-tuple hash: (Default distribution mode) uses the RSS hash if available, otherwise hashes the TCP/UDP ports and the IP addresses. If ports not available, uses 2-tuple instead. • 2-tuple hash: hashes the IP addresses. If not IP traffic uses MAC-address hash instead. • MAC address hash: hashes the MAC addresses. • 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.

  12. Switch/Load Interactions (Summary)

  13. What modes am I using?

  14. Switch/Load Interactions (SI/AH) Sends on all active members using the selected level of address hashing (defaults to 4-tuple hash). Because each IP address can only be associated with a single MAC address for routing purposes, this mode receives inbound traffic on only one member (the primary member). Best used when: a) Native mode teaming where switch diversity is a concern; b) Active/Standby mode c) Servers running workloads that are heavy outbound, light inbound workloads (e.g., IIS)

  15. Switch/Load Interactions (SI/HP) Sends on all active members using the hashed Hyper-V switch port. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth. Because each VM (Hyper-V port) is associated with a single NIC, this mode receives inbound traffic for the VM on the same NIC it sends on so all NICs receive inbound traffic. This also allows maximum use of VMQs for better performance over all. Best used for teaming under the Hyper-V switch when - number of VMs well-exceeds number of team members - restriction of a VM to one NIC’s bandwidth is acceptable

  16. Switch/Load Interactions (SD/AH) Sends on all active members using the selected level of address hashing (defaults to 4-tuple hash). Receives on all ports. Inbound traffic is distributed by the switch. There is no association between inbound and outbound traffic. Best used for: - Native teaming for maximum performance and switch diversity is not required; or - teaming under the Hyper-V switch when an individual VM needs to be able to transmit at rates in excess of what one team member can deliver

  17. Switch/Load Interactions (SD/HP) Sends on all active members using the hashed Hyper-V switch port. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth. Receives on all ports. Inbound traffic is distributed by the switch. There is no association between inbound and outbound traffic. Best used when: - Hyper-V teaming when VMs on the switch well-exceed the number of team members and - when policy calls for e.g., LACP teams and when an individual VM does not need to transmit faster than one team member’s bandwidth

  18. Team interfaces (tNICs) • Team interfaces can be in one of two modes: • Default mode: passes all traffic that doesn’t match any another team interface’s VLAN id • VLAN mode: passes all traffic that matches the VLAN • Inbound traffic is always passed to at most one team interface Hyper-V switch VLAN=42 Default (all but 42) VLAN=42 VLAN =99 Default TEAM TEAM TEAM Black hole

  19. Team interface – at team creation • When a team is created it has one team interface. • Team interfaces can be renamed like any other network adapter (Rename-NetAdaptercmdlet) • Team interfaces show up in Get-NetAdapter output • Only this first (primary) team interface can be put in Default mode

  20. Team Interfaces - additional • Team interfaces created after initial team creation must be VLAN mode team interfaces • Team interfaces created after initial team creation can be deleted at any time (UI or PowerShell) • It is a violation of Hyper-V rules to have more than one team interface on a team that is bound to the Hyper-V switch Hyper-V switch Default TEAM

  21. Teams of one • A team with only one member (one NIC) may be created for the purpose of disambiguating VLANs • A team of one has no protection against failure (of course) VLAN=13 VLAN=42 VLAN =99 VLAN =3995 TEAM

  22. Team members • Any physical Ethernet adapter can be a team member and will work as long as the NIC meets the Windows Logo requirements • Teaming of Infiniband, WiFi, WWAN, etc., adapters is not supported • Teams of teams are not supported

  23. Team member roles • A team member may be active or standby.

  24. Teaming in a VM is supported • Limited to Switch independent, Address Hash mode • Teams of two team members are supported • Intended/optimized to support teaming of SR-IOV VFs but may be used with any interfaces in the VM • Requires configuration of the Hyper-V switch or failovers may cause loss of connectivity

  25. Manageability • Intuitive, easy-to-use NIC Teaming UI • So intuitive and powerful that some Beta customers are saying they don’t want to bother with learning the PowerShell cmdlets • UI operates completely through PowerShell – uses PowerShell cmdlets for all operations • Manages Servers (including Server Core) remotely from your Windows 8 client PC • Powerful PowerShell cmdlets • Object: NetLbfoTeam (New, Get, Set, Rename, Remove) • Object: NetLbfoTeamNic (Add, Get, Set, Remove) • Object: NetLbfoTeamMember (Add, Get, Set, Remove)

  26. Feature interactions

  27. Limits on NIC Teaming • Maximum number of NICs in a team: 32 • Maximum number of team interfaces: 32 • Maximum teams in a server: 32 • Not all maximums may be available at the same time due to other system constraints

  28. demo NIC Teaming Don Stanwyck Senior Program Manager Windows Networking

  29. title SMB Multichannel

  30. SMB MultichannelMultiple connections per SMB session Full Throughput • Bandwidth aggregation with multiple NICs • Multiple CPUs cores engaged when using Receive Side Scaling (RSS) Automatic Failover • SMB Multichannel implements end-to-end failure detection • Leverages NIC teaming if present, but does not require it Automatic Configuration • SMB detects and uses multiple network paths Sample Configurations Single 10GbE RSS-capable NIC Multiple 1GbE NICs Multiple 10GbE in a NIC team Multiple RDMA NICs SMB Client SMB Client SMB Client SMB Client NIC Teaming RSS NIC 10GbE/IB NIC 10GbE/IB NIC 10GbE NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE Switch 10GbE/IB Switch 10GbE/IB Switch 10GbE Switch 10GbE Switch 1GbE Switch 1GbE Switch 10GbE SMB Server SMB Server SMB Server SMB Server NIC 10GbE/IB NIC 10GbE NIC 10GbE/IB NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE RSS NIC Teaming Vertical lines are logical channels, not cables

  31. 1 session, without Multichannel SMB Multichannel – Single 10GbE NIC • No failover • Can’t use full 10Gbps • Only one TCP/IP connection • Only one CPU core engaged CPU utilization per core SMB Client RSS NIC 10GbE Switch 10GbE SMB Server NIC 10GbE RSS Core 1 Core 2 Core 3 Core 4

  32. 1 session, with Multichannel 1 session, without Multichannel SMB Multichannel – Single 10GbE NIC • No failover • Can’t use full 10Gbps • Only one TCP/IP connection • Only one CPU core engaged • No failover • Full 10Gbps available • Multiple TCP/IP connections • Receive Side Scaling (RSS) helps distribute load across CPU cores SMB Client CPU utilization per core CPU utilization per core SMB Client RSS NIC 10GbE RSS NIC 10GbE Switch 10GbE Switch 10GbE SMB Server NIC 10GbE SMB Server NIC 10GbE RSS Core 1 Core 2 Core 3 Core 4 RSS Core 1 Core 2 Core 3 Core 4

  33. SMB Multichannel – Multiple NICs 1 session, without Multichannel • No automatic failover • Can’t use full bandwidth • Only one NIC engaged • Only one CPU core engaged SMB Client 1 SMB Client 2 RSS RSS NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE SMB Server 1 SMB Server 2 NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE RSS RSS

  34. SMB Multichannel – Multiple NICs 1 session, with Multichannel 1 session, without Multichannel • No automatic failover • Can’t use full bandwidth • Only one NIC engaged • Only one CPU core engaged • Automatic NIC failover • Combined NIC bandwidth available • Multiple NICs engaged • Multiple CPU cores engaged SMB Client 1 SMB Client 2 SMB Client 1 SMB Client 2 RSS RSS RSS RSS NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE SMB Server 1 SMB Server 2 SMB Server 1 SMB Server 2 NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE NIC 10GbE RSS RSS RSS RSS

  35. SMB Multichannel Performance • Preliminary results using four 10GbE NICs simultaneously • Linear bandwidth scaling • 1 NIC – 1150 MB/sec • 2 NICs – 2330 MB/sec • 3 NICs – 3320 MB/sec • 4 NICs – 4300 MB/sec • Leverages NIC support for RSS (Receive Side Scaling) • Bandwidth for small IOs is bottlenecked on CPU Data goes all the way to persistent storage. White paper provides full details.See http://go.microsoft.com/fwlink/p/?LinkId=227841 Preliminary results based on Windows Server “8” Developer Preview

  36. SMB Multichannel + NIC Teaming 1 session, with NIC Teaming, no MC • Automatic NIC failover • Can’t use full bandwidth • Only one NIC engaged • Only one CPU core engaged SMB Client 1 SMB Client 2 NIC Teaming NIC Teaming NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE Switch 10GbE Switch 1GbE Switch 1GbE Switch 10GbE SMB Server 2 SMB Server 2 NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE NIC Teaming NIC Teaming

  37. SMB Multichannel + NIC Teaming 1 session, with NIC Teaming and MC 1 session, with NIC Teaming, no MC • Automatic NIC failover • Can’t use full bandwidth • Only one NIC engaged • Only one CPU core engaged • Automatic NIC failover (faster with NIC Teaming) • Combined NIC bandwidth available • Multiple NICs engaged • Multiple CPU cores engaged SMB Client 1 SMB Client 2 SMB Client 1 SMB Client 2 NIC Teaming NIC Teaming NIC Teaming NIC Teaming NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE Switch 10GbE Switch 1GbE Switch 1GbE Switch 10GbE Switch 10GbE Switch 1GbE Switch 1GbE Switch 10GbE SMB Server 2 SMB Server 2 SMB Server 1 SMB Server 2 NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE NIC 10GbE NIC 10GbE NIC 1GbE NIC 1GbE NIC Teaming NIC Teaming NIC Teaming NIC Teaming

  38. SMB Direct and SMB Multichannel 1 session, without Multichannel • No automatic failover • Can’t use full bandwidth • Only one NIC engaged • RDMA capability not used SMB Client 1 SMB Client 2 R-NIC 10GbE R-NIC 10GbE R-NIC 54GbIB R-NIC 54GbIB Switch 10GbE Switch 10GbE Switch 54GbIB Switch 54GbIB SMB Server 1 SMB Server 2 R-NIC 10GbE R-NIC 10GbE R-NIC 54GbIB R-NIC 54GbIB

  39. SMB Direct and SMB Multichannel 1 session, with Multichannel 1 session, without Multichannel • No automatic failover • Can’t use full bandwidth • Only one NIC engaged • RDMA capability not used • Automatic NIC failover • Combined NIC bandwidth available • Multiple NICs engaged • Multiple RDMA connections SMB Client 1 SMB Client 2 SMB Client 1 SMB Client 2 R-NIC 10GbE R-NIC 10GbE R-NIC 10GbE R-NIC 10GbE R-NIC 54GbIB R-NIC 54GbIB R-NIC 54GbIB R-NIC 54GbIB Switch 10GbE Switch 10GbE Switch 10GbE Switch 10GbE Switch 54GbIB Switch 54GbIB Switch 54GbIB Switch 54GbIB SMB Server 1 SMB Server 2 SMB Server 1 SMB Server 2 R-NIC 10GbE R-NIC 10GbE R-NIC 10GbE R-NIC 10GbE R-NIC 54GbIB R-NIC 54GbIB R-NIC 54GbIB R-NIC 54GbIB

  40. SMB Multichannel – Not applicable SMB Client SMB Client NIC Wireless NIC 1GbE Single NIC configurations where full bandwidth is already available without MC Switch Wireless Switch 1GbE SMB Server SMB Server NIC 1GbE NIC Wireless Configurations with different NIC type or speed SMB Client SMB Client SMB Client SMB Client RSS NIC 1GbE NIC Wireless R-NIC 10GbE NIC 1GbE R-NIC 10GbE NIC 10GbE NIC 1GbE R-NIC32GbIB Switch Wireless Switch 1GbE Switch 1GbE Switch 10GbE Switch 1GbE Switch 10GbE Switch 10GbE Switch IB SMB Server SMB Server SMB Server SMB Server NIC 1GbE R-NIC 10GbE NIC 1GbE R-NIC 10GbE NIC 10GbE NIC 1GbE R-NIC 32GbIB RSS

  41. SMB Multichannel Configuration Options • Multichannel is on by default for SMB. • NIC Teaming is helpful for faster failover. • NIC Teaming is helpful for non-SMB traffic (mixed workloads, management). • NIC Teaming is not compatible with RDMA.

  42. Troubleshooting SMB Multichannel • PowerShell • Get-NetAdapter • Get-SmbServerNetworkInterface • Get-SmbClientNetworkInterface • Get-SmbMultichannelConnection • Event Log • Application and Services Log, Microsoft, Windows, SMB Client • Performance Counters • SMB Client Shares

  43. demo SMB Multichannel Jose Barreto Principal Program Manager Windows Server

  44. SIA, WSV, and VIR Track Resources #TE(sessioncode) Talk to our Experts at the TLC Hands-On Labs DOWNLOAD Windows Server 2012 Release Candidate microsoft.com/windowsserver DOWNLOAD Windows Azure Windowsazure.com/ teched

  45. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

  46. Required Slide Complete an evaluation on CommNet and enter to win!

  47. MS Tag Scan the Tag to evaluate this session now on myTechEd Mobile

  48. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related