Tag: Port Profiles

NIC Teaming

Overview on Windows Server and Hyper-V 2012 R2 NIC Teaming and SMB Multichannel

I know this is nothing new but since I had to mention the Whitepaper on NIC Teaming and the use of SMB Multichannel as well as the configuration with System Center Virtual Machine Manager in a couple of meetings I want to make sure you have an overview on my blog. Here is a no overview of Windows Server and Hyper-V NIC teaming and SMB Multichannel, to get redundant network configurations.

NIC Teaming

Windows Server NIC Teaming was introduced in Windows Server 2012 (Codename Windows Server 8). NIC teaming, also known as Load Balancing/Failover (LBFO), allows multiple network adapters to be placed into a team for the purposes of bandwidth aggregation, and/or traffic failover to maintain connectivity in the event of a network component failure.

NIC Teaming Recommendation

For designing, the default and recommended configuration is using NIC Teaming with Switch Independent and Dynamic, and in some scenarios where you have the write switches you can use LACP and Dynamic.

Download Windows Server 2012 R2 NIC Teaming (LBFO) Deployment and Management Whitepaper

This guide describes how to deploy and manage NIC Teaming with Windows Server 2012 R2.

You can find the Whitepaper on Windows Server 2012 R2 NIC Teaming (LBFO) Deployment and Management in the Microsoft Download Center.

SMB Multichannel

Hyper-V over SMB Multichannel

If you use Hyper-V over SMB, you can use SMB Multichannel as an even better mode to distribute SMB 3.0 traffic across different network adapters, or you could use a mix of both, NIC Teaming and SMB Multichannel. Check out my blog post about Hyper-V over SMB: SMB Multichannel, SMB Direct (RDMA) and Scale-Out File Server and Storage Spaces.

Configuration with System Center Virtual Machine Manager

Logical Switch

Some months back, I also wrote some blog post about configuration of Hyper-V Converged Networking and System Center Virtual Machine Manager. This guide will help you to understand how you deploy NIC Teaming with System Center Virtual Machine Manager using the Logical Switch on Hyper-V hosts.

Using System Center 2012 SP1 – Virtual Machine Manager Logical Switch with Hyper-V

System Center Logo

This blog post is a part of a series of blog posts about System Center 2012 Virtual Machine Manager, I am writing together with Michel Luescher (Consultant from Microsoft Switzerland).

In the last post we wrote about the new networking features in System Center 2012 SP1 – Virtual Machine Manager. One of the biggest changes in SCVMM is the concept of the Logical Switch. The new Logical Switch allows to manage Hyper-V Virtual Switches including the underlying network teaming centralized from System Center Virtual Machine Manager.

In Service Pack 1 you can choose between two Virtual Switches; You can use either the new Logical Switch or you can use the Standard Virtual Switch, which is basically the “legacy” Virtual Switch with the default Hyper-V Virtual Switch functions. If you create the Virtual Switch on a Hyper-V host you can choose between the two options and this allows you to choose the Logical Switch.

Standard Switch

The Standard Virtual Switch is basically the normal Hyper-V Virtual Switch and the configuration looks exactky the same as in the Hyper-V Manager. If you add a Hyper-V Host to SCVMM and you have previously created the Virtual Switch using Hyper-V Manager or PowerShell cmdlets, this Virtual Switch will be shown as Standard Switch.

Standard SwitchIn a nutshell:

  • The Standard Switch can only be deployed on one network adapter, so if you want to use network teaming you have to create the network teaming manual on the Hyper-V host.
  • The available Logical Networks have to be added on every host on the physical network adapter. This can be a little of a management effort but I made a simple PowerShell Script which helps you to do configuration changes: SCVMM 2012: Add Logical Network to all Hyper-V Hosts in HostGroup via PowerShell
  • Existing Virtual Switches will be shown as Standard Switches in SCVMM, you have to recreate the configuration if you want to use the Logical Switch.
  • With the Standard Switch you can set the one single management vNIC which can be used by the Management OS. You can attach additional vNIC using Windows PowerShell on the Hyper-V host but not from the Virtual Machine Manager Console

Logical Switch

A Logical Switch includes Virtual Switch Extensions, Uplink Port Profiles which define the physical network adapters used by the Hyper-V Virtual Switch for example for teaming and the Virtual Adapter Port Profiles mapped to Port Classifications which are the settings for the Virtual Network Adapters of the virtual machines.

Logical SwitchIn a nutshell:

  • The Logical Switch allows you to add multiple NICs in one Virtual Switch and creates a NIC teaming based on Uplink Port Profile. The Uplink Port Port Profile includes all the information which teaming mode and algorithm has to be used.
  • The Uplink Port Profile also includes a list of available logical network sites. If you have an additional Logical Network which runs on this network adapters you can simply add this to the Uplink Port Profile.
  • You can create multiple vNICs (vEthernet Adapters) for example a Hyper-V Converged Networking setup. Port Classifications and Virtual Adapter Port Profiles bring support for Bandwidth Management and QoS.
  • Logical Switches only work with windows Server 2012 , but there is no need to stay on Windows Server 2008 R2 Hyper-V.

If you are running Windows Server 2012 Hyper-V hosts there is no reason why you should not use the Logical Switch, which adds additional functionality and centralized management to the Hyper-V Virtual Switch.

You can find the German Version of this blog post on Michel Lueschers (Consultant Microsoft Switzerland) blog.