How to fix non compliant NICs with no logical network connectivity in VMM

Hi everybody,

today again a blogpost out of my heading “I need to remind my self because I love to forget this”.

I want to show you how you need to configure Network Adapters which are not used in a virtual switch for Hyper-V. That network adapters could be used for example with Storage like iSCSI, SMB3 or other things.

At first you will get a warning from Virtual Machine Manager that your host is not compliant.

2015-10-09_17-37-52

Like you see in my example below.

2015-10-09_12-15-23

 

Now there are two options to get the NICs compliant. The first way, which we don’t want to use with Storage Adapters is, to move them into a virtual switch.

The second one, which I prefer when working with storage adapter, is ti define the connection within the hardware profile of the server. For that you go into the properties of your Hyper-V Hosts in VMM and select hardware. Scroll down until you reached the network adapter you want to configure. Now you should see the logical network connectivity.

2015-10-09_17-39-46

There you check the logical networks, your host has connection with and press ok.

2015-10-09_12-16-44

So that’s all. Now your Networkadapter is shown as compliant in VMM.

2015-10-09_17-38-42

How to fix VMM error 20553

Hi,

today I want you to provide you some GPO Templates, which could help you to fix following error in VMM:

Error (20553)
The Windows Remote Management (WinRM) client on the VMM server cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer **.

WinRM: URL: ** , Verb: [ENUMERATE], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_ComputerSystemProduct], Filter: []

Unknown error (0x803381a3)

Recommended Action
Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer. For example, for a target computer name myserver.domain.com, the SPN can be one of the following: WSMAN/myserver.domain.com OR WSMAN/*.domain.com OR WSMAN/*

Thanks to¬†Radhika Gupta for his blog on TechNet which gave me the final solution¬†ūüôā

In my case I needed to create two GPOs.

The first deployed on the Hyper-V Hosts to enable WinRM with CreedSSP

Computer Configuration\Administrative template\Windows Components\Windows Remote Management (WinRM)\WinRM Service\[Allow CredSSP authentication] = true

The first deployed on the VMM Hosts to enable WinRM with CreedSSP and Credentials Delegation

Computer Configuration\Administrative template\Windows Components\Windows Remote Management (WinRM)\WinRM Service\[Allow CredSSP authentication] = true

Computer Configuration\Administrative Templates\System\Credentials Delegation\[AllowFreshCredentials ] = “WSMAN/*”

Hyper-V|W2k12R2|8x1GB|2x10GB

Hyper-V Cluster Network configuration with following parameters:

The following configuration leverages 8x 1GB Ethernet NICs and LOM (LAN on Motherboard) and 2x 10GB Ethernet NICs. The storage can be connected via iSCSI with MPIO or SMB 3.x.x without RDMA. The configurations uses physical configuration and software defined / converged network for Hyper-V.


¬†Pro’s and Con’s of that solution

 Pro Con
РGood Bandwidth for VM
– Good Bandwidth for Storage
– Separated NICs for Livemigration, Cluster and Management
– Full fault redundant
– Can be used in switch independent or LACP (with stacked switches) teaming mode
– Only one Hardware Technology is used
– Network becomes limited by a large number of VMs
– Combination between Hardware Defined and Software Defined Network is sometimes hardly to understand

 Switches

1GBE SW01 1 GBit/s physical stacked or independed
1GBE SW02 1 GBit/s physical stacked or independed
10GBE SW01 10 GBit/s physical stacked or independed
10GBE SW02 10 GBit/s physical stacked or independed
SoftSW01 10 GBit/s Software defined / converged
SoftSW02 10 GBit/s Software defined / converged

 Neccessary Networks

Networkname VLAN IP Network (IPv4) Connected to Switch
Management 10 10.11.10.0/24 SoftSW01
Cluster 11 10.11.11.0/24  SoftSW01
Livemigration 45 10.11.45.0/24 1GBE SW01 / 1GBE SW02
With iSCSI РStorage 40 10.11.40.0/24 10GBE SW01 / 10GBE SW02
With SMB РStorage 5051 10.11.50.0/2410.11.51.0/24 10GBE SW0110GBE SW02
Virtual Machines 200 Рx 10.11.x.x/x 1GBE SW01 / 1GBE SW02

 Possible rearview Server


 Schematic representation


Switch Port Configuration

   

Bandwidth Configuration vNICs

vNIC min. Bandwidth Weight PowerShell Command
Management 10%
Cluster 5%

QoS Configuration Switch

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

 

New free eBook Microsoft System Center Data Protection for the Hybrid Cloud

Hey everbody,

Microsoft offers a new free eBook written by Shreesh Dubey, Vijay Tandra Sistla, Shivam Garg, and Aashish Ramdas. Within the book you can read some really usefull things, how to Backup your Microsoft Hybrid cloud.

You can find the book here: Download

HyperV|W2k12R2|3x1GB

Done use that configuration in production! It’s only for lab use!

This configuration is very similar to the 4x 10Gb Ethernet config but not useable for production.

Hyper-V Cluster Network configuration with following parameters:

The following configuration leverages 3x 1GB Ethernet NICs and LOM (LAN on Motherboard). The storage can be connected via iSCSI with MPIO or SMB 3.x.x without RDMA. The configurations uses physical configuration and software defined / converged network for Hyper-V.


¬†Pro’s and Con’s of that solution

 Pro Con
–¬†Easy to build and good for lab use
– enougth bandwidth for test workloads
– fully converged
–¬†limited bandwidth
– no production use
– cheap to build

 Switches

1GBE SW01 1 GBit/s physical stacked or independed
1GBE SW02 1 GBit/s physical stacked or independed
SoftSW01 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
Storage 400 10.11.40.0/24 SoftSW01
Virtual Machines 200 – x 10.11.x.x/x SoftSW01

 Possible rearview Server


 Schematic representation


Switch Port Configuration


Bandwidth Configuration vNICs

vNIC min. Bandwidth Weight PowerShell Command
Management 10%
Cluster 5%
iSCSI 30%
Livemigration 30%

QoS Configuration Switch

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