VMQ Example Script for Intel E5-2637v0 & one vSwitch

Following configuration is for an Intel Xeon E5-2637 and Intel X520 NICs.

The Script will disable VMQ on iSCSI and Livemigration and enable and configure VMQ on converged.

CPU distribution:

2

Script:

 

@AltaroSoftware New eBook: Supercharging Hyper-V Performance

Hi everybody,

Altaro published a great new eBook “Supercharging Hyper-V Performance”.

Here’s what you can expect from this eBook:

  1. A practical guide to finding and fixing issues in storage, CPU, memory, and network components
  2. Instructions on how to use Windows Performance Monitor and PAL to monitor your virtualized environment
  3. Advice on how to plan hosts, VMs, storage, networking and management for maximum performance.

You can download it here.

Book Tipp: Introduction to Windows Server Failover Clustering

Hi everybody,

5nine Software Vice President Symon Perriman published a book with some cool best practices for configuration Windows Server Failover Clusters. 🙂

Greate stuff and great to read.

You can download it here.

Where to find logs from cluster role movement?

Hi everybody,

as you know sometimes it is neccessary to get some more information about where and when roles within a cluster were successfully moved from one node to another.

One example could be Hyper-V Livemigrations or role movements from mixed role cluster servers.

When you have errors or warnings during rolemigrations, you can see the events directly within the failover cluster manager.

2016-02-19_11-03-59

But what is if I want to see successfull role moves? Where do I find them?

Those messages are a bit hidden within the logfile structures of a Windows Server.

  1. Navigate to Applications and Services Logs\Microsoft\Windows\Failover Clustering\Operational
  2. There you can find several events dependig if you are on the role sender or receiver2016-02-19_11-07-222016-02-19_11-07-522016-02-19_11-08-14

Virtual Switches in Windows Server 2016 Hyper-V

With coming nearer to the release of Windows Server 2016, more and more details about he final server are revealed.

Today I want you give a short list about the switches which will be part of Hyper-V in Windows Server 2016.

“Classical” Switches

Switchtype Discription Source
Private Switch The private switch allows communications among the virtual machines on the host and nothing else. Even the management operating system is not allowed to participate. This switch is purely logical and does not use any physical adapter in any way. “Private” in this sense is not related to private IP addressing. You can mentally think of this as a switch that has no ability to uplink to other switches. http://www.altaro.com/hyper-v/the-hyper-v-virtual-switch-explained-part-1/
Internal Switch The internal switch is similar to the private switch with one exception: the management operating system can have a virtual adapter on this type of switch and communicate with any virtual machines that also have virtual adapters on the switch. This switch also does not have any matching to a physical adapter and therefore also cannot uplink to another switch. http://www.altaro.com/hyper-v/the-hyper-v-virtual-switch-explained-part-1/
External This switch type must be connected to a physical adapter. It allows communications between the physical network and the management operating system and virtual machines. Do not confuse this switch type with public IP addressing schemes or let its name suggest that it needs to be connected to a public-facing connection. You can use the same private IP address range for the adapters on an external virtual switch that you’re using on the physical network it’s attached to. http://www.altaro.com/hyper-v/the-hyper-v-virtual-switch-explained-part-1/

New Switches available in Windows Server 2016

Switchtype Discription Source
Externals Switch with SET SET (Switch embedded Teaming) is an alternative NIC Teaming solution that you can use in environments that include Hyper-V and the Software Defined Networking (SDN) stack in Windows Server 2016 Technical Preview. SET integrates some NIC Teaming functionality into the Hyper-V Virtual Switch.SET allows you to group between one and eight physical Ethernet network adapters into one or more software-based virtual network adapters. These virtual network adapters provide fast performance and fault tolerance in the event of a network adapter failure. SET member network adapters must all be installed in the same physical Hyper-V host to be placed in a team. https://technet.microsoft.com/en-US/library/mt403349.aspx#bkmk_sswitchembedded
NAT Mode Switch With the latest releases of the Windows 10 and Windows Server 2016 Technical Preview 4, Microsoft included a new VM Switch Type called NAT, which allows Virtual Machines to have a Internal Network and connect to the external world and internet using NAT. http://www.thomasmaurer.ch/2015/11/hyper-v-virtual-switch-using-nat-configuration/

Virtual Switches in System Center Virtual Machine Manager

Switchtype Discription
Standard Switch A Standard Switch is basicly a Hyper-V Switch shown in virtual machine manager. From the management and feature perspective there are no differences.
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.

Not really a switch but part of the Hyper-V networking stack and currently necessary in multi tenant scenarios.

Type Discription Source
Multi Tenant Gateway In Windows Server 2012 R2, the Remote Access server role includes the Routing and Remote Access Service (RRAS) role service. RRAS is integrated with Hyper-V Network Virtualization, and is able to route network traffic effectively in circumstances where there are many different customers – or tenants – who have isolated virtual networks in the same datacenter.Multi-tenancy is the ability of a cloud infrastructure to support the virtual machine workloads of multiple tenants, but isolate them from each other, while all of the workloads run on the same infrastructure. The multiple workloads of an individual tenant can interconnect and be managed remotely, but these systems do not interconnect with the workloads of other tenants, nor can other tenants remotely manage them. https://technet.microsoft.com/en-us/library/dn641937.aspx