Hyper-V|W2k12R2|4x1GB|2xFC

Hyper-V Cluster Network configuration with following parameters:

The following configuration leverages 4x 1GB Ethernet and 2x Fibre channel connections. The storage can be connected via Fibre Channel with MPIO. The configurations uses physical configuration and software defined / converged network for Hyper-V.


 Pro’s and Con’s of that solution

 Pro Con
– High Bandwidth for VM- Good Bandwidth for Storage
– Fault redundant
– Can be used in switch independent or LACP (with stacked switches) teaming mode
– Fibrechannel ist most common SAN technology
– Limited Bandwidth for Livemigration
– a lot of technologies involved

 Switches

Switch name Bandwidth Switchtyp
1GBE SW01 1 GBit/s physical stacked or independed
1GBE SW02 1 GBit/s physical stacked or independed
FC SW01 4/8 GB FC/s physical stacked or independed
FC SW02 4/8 GB FC/s physical stacked or independed
SoftSW01 1 GBit/s Software defined / converged
SoftSW02 1 GBit/s Software defined / converged

 Neccessary Networks

Networkname VLAN IP Network (IPv4) Connected to Switch
Management 100 10.11.100.0/24 SoftSW01
Cluster 101 10.11.101.0/24  SoftSW01
Livemigration 450 10.11.45.0/24  SoftSW01
Virtual Machines 200 – x 10.11.x.x/x  SoftSW02

 Possible rearview Server

NIC17


 Schematic representation

NIC14 NIC15

Switch Port Configuration

NIC16  

Bandwidth Configuration vNICs

vNIC min. Bandwidth Weight PowerShell Command
Management 20%
Cluster 10%
Livemigration 40%

QoS Configuration Switch

Networkname Priority
Management medium
Cluster high
Livemigration medium
VMs dependig on VM Workload

 

How to upgrade SCVMM from 2012 R2 to 2016

Hi,

today I want to provide you a quick end dirty step by step guide how to upgrade you SCVMM from 2012 R2 to 2016.

The procedure is pretty much the same like in 2012 or 2012 R2.

Single Node:

  1. Uninstall SCVMM 2012 R2 and keep your database
  2. Install all needed requirements for SCVMM 2016 on your server which are noticed in the requirements* during the installation wizard
  3. Connect the “old” SCVMM 2012 R2 database
  4. Run all updates and your done

Cluster:

  1. Uninstall SCVMM 2012 R2 from all of your nodes and keep your database
  2. delete the cluster role of the old VMM (if you want to keep the name you need to set it new)
  3. Install all needed requirements for SCVMM 2016 on your server’s which are noticed in the requirements* during the installation wizard
  4. Create a new cluster role with the old name and IP
  5. Connect the “old” SCVMM 2012 R2 database
  6. Run all updates and your done

*You will require

That’s all 🙂

How to fix same SMBIOS ID on different Hosts

Today one post about things I see sometimes in the field.

Today I want to show you how to fix the issue when you get servers and clients with the same SMBIOS ID. Normally that would be an issue but as soon as you try to management them with System Center Virtual Machine Manager or Configuration Manager it will become one. Both tools use the SMBIOS ID to create a primary key in their databases to identify the system.

2015-11-29_14-02-03

 

Currently I only know the following trick to fix the issue and that one would be extremly annoying on many clients or servers but it actually work.

First you need two tools.

1: Rufus – To create a bootable USB Stick

2: AMIDMI – With that tool you can overright the SMBIOS ID

Now create the Bootstick with Rufus and copy the AMIDMI file on the stick.

Reboot your from the stick.

Navigate to the folder with your AMIDMI file and run the command amidmi /u

Afterwards you can reboot the system and start Windows again.

 

When you are working with Virtual Machine Manager, you need to remove the host from your management consolte and add it again. After the host is discovered again, you can see the new SMBIOS ID.

2015-11-29_14-02-50

 

I currently saw these issues with following motherboard vendors:

  1. ASRock (Client & Rack)
  2. ASUS (Client)
  3. SuperMicro (Server & ARM)
  4. Fujisu (Server)

You install Hyper-V & VMM from the green? Please do it in the right order.

Hi everybody,

today another story I see most of the days when I do Healthcheck on customer site.

One of the first things I found was a new VMM installation on top of a new Microsoft Hyper-V Cluster. The issue was, that the cluster was installed first and every thing was running on Hyper-V converged network and standard Hyper-V Switches. There was no VMM network configured or the host made compliant within VMM.

Why is that so bad? It’s bad because VMM uses it’s own kind of switches (logical switches) and needs some additional configurations to manage the hosts in the best possible way.

When I ask guy’s why they do it in that way, I normally get the answer “how should I configure the host when no VMM is in place before he install the cluster?”.

So now my answer and how you can do it in the right way.

  1. Install a Hyper-V Host as Standalone host
  2. Configure and install the VMs for VMM and SQL Server (if needed) on the standalone host
  3. Performe the ful VMM configuration
  4. Install the other Hyper-V Hosts and roll out the VMM configuration to that hosts
  5. Cluster the Hyper-V Hosts
  6. Migrate your SQL DB and VMM with shared nothing livemigration to the new Hyper-V Cluster
  7. Reconfigure the standalone Hyper-V Host with VMM and add it to the cluster
  8. Run the cluster validation again

That’s all and it will cost you the same amount of time.

PowerShell Script to move Hyper-V Hosts to special OU and add them to group

Hi,

as another part of my deployment scripts, I developed a small script that does following tasks.

  1. Moves all Hosts with *SVR-HV* from Computers to Hyper-V OU
  2. Creates Group for Hosts
  3. Adds Hosts to group