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/*”

New free eBook Microsoft System Center Building a Virtualized Network Solution, Second Edition

Hey everbody,

Microsoft offers a new free eBook written by Nigel Cain, Michel Luescher, Damian Flynn, and Alvin Morales.  You can find the book here: Download

What topics are included in this book?

The vast majority of the book is focused on architecture and design, highlighting key design decisions and providing best practice advice and guidance relating to each major feature of the solution.

  • Chapter 1: Key concepts A virtualized network solution built on Windows Server and System Center depends on a number of different features. This chapter outlines the role each of these features plays in the overall solution and how they are interconnected.
  • Chapter 2: Logical networks This chapter provides an overview of the key considerations, outlines some best practice guidance, and describes a process for identifying the set of logical networks that are needed in your environment.
  • Chapter 3: Hyper-V port profiles This chapter discusses the different types of port profiles that are used in Virtual Machine Manager, outlines why you need them and what they are used for, and provides detailed guidance on how and when to create them.
  • Chapter 4: Logical switches This chapter describes the function and purpose of logical switches, which are essentially templates that allow you to consistently apply the same settings and configuration across multiple hosts.
  • Chapter 5: Network Virtualization gateway This chapter outlines key design choices and considerations for providing cross-premises connectivity from networks at tenant sites to virtual networks dedicated (per tenant) in a service provider network.
  • Chapter 6: Deployment This chapter builds on the material discussed in previous chapters and walks through common deployment scenarios, highlighting known issues (and workarounds) relating to the deployment and use of logical switches in your environment.
  • Chapter 7: Operations Even after having carefully planned a virtual network solution, things outside of your immediate control might force changes to your virtualized network solution. This chapter walks you through some relatively common scenarios and provides recommendations, advice, and guidance for how best to deal with them.
  • Chapter 8: Diagnosing Connectivity Issues This chapter looks at how to approach a connectivity problem with a virtualized network solution, the process you should follow to troubleshoot the problem, and some actions you can take to remediate the issue and restore service.
  • Chapter 9: Cloud Platform System network architecture This chapter reviews the design and key decision points for the network architecture and virtualized network solution within the Microsoft Cloud Platform System.

To recap, this book is mainly focused on architecture and design (what is needed to design a virtualized network solution) rather than on the actual steps required to deploy it in your environment. Other than in few chapters, you will find few examples of code. This is by design. Our focus here is not to provide details of how you achieve a specific goal but rather on what you need to do to build out a solution that meets the needs of your business and provides a platform for the future.

When you have designed a solution using the guidelines documented in this book, you will be able to make effective use of some of the excellent materials and examples available in the Building Clouds blog (http://blogs.technet.com/b/privatecloud/) to assist you with both solution deployment and ongoing management.

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