Category: Hyper V Page 1 of 2

VLAN, Trunk, NIC Teaming, Virtual Switch Configuration in Hyper-v Server

If you checked my posts before and especially LAB scenarios maybe you noticed I didn’t tag VLANs and reason is I didn’t want to complicate things and I know that some people have problem with understanding how it all works in comparison with physical switches and all. This post is meant to help clear that and I hope it will help in better understanding of Hyper-V Virtual Switch.

Network virtualization provides multiple virtual network infrastructures run on the same physical network with or without overlapping IP addresses. Each virtual network infrastructure operates as if they are the only virtual network running on the shared network infrastructure. Hyper-v Network Virtualization also decouples physical network from virtual network.

Read More

Nested Virtualized Windows Server 2016 Hyper-V Cluster LAB – Scenario 2

This Scenario will be lot quicker and we will be using PowerShell since Nano Server is without GUI and it will definitely reflect on footprint and size of cluster.

I recommend you read Nano Server – Deployment since I will be using that procedure for creating script that will automate creation of Nano Servers.

In this scenario we will have 3 VMs and first one same as in Scenario 1 will be VM with our Domain Controler, DHCP, DNS and we will need to setup all those services on that VM(detailed info on this procedure). This time we will also need to install Failover Cluster Manager so we can manage Nano servers since they don’t have any GUI. Second and Third will be our Nano Servers that we will create with script below but before we do it we need to mount Windows Server 2016 ISO  and copy NanoServer folder to our C: drive.

Read More

Nested Virtualized Windows Server 2016 Hyper-V Cluster LAB – Scenario 1

On Hyper V in Windows 10 we will create 4 VMs as we planned before and after VMs are created we must enable nested virtualization for our future cluster nodes.

After that we need to install Windows Server 2016 and I suggest we use VM template for faster deployment as described in post earlier. Do not forget to enable MAC address spoofing in order for network packets to be routed through two virtual switches, MAC address spoofing must be enabled on the first level of virtual switch.

First VM will be our Domain Controler, DHCP, DNS and we need to setup all those services (detailed info on this procedure). Second VM will be our SAN VM and for this we will use StarWind Virtual SAN. Third and Fourth Server will be our future Hyper V host cluster nodes and for time being they must be joined to domain and given appropriate names and IP addresses.
Network interfaces on cluster nodes will be configured later with PowerShell script since I elected to team all 4 NICs using the minimum bandwidth setting for Management, Cluster, ISCSI, VM, and LiveMigration traffic.  I highly recommend that you take a few moments to watch John Savill’s discussion on this method of teaming: Using NIC Teaming and a virtual switch for Windows Server 2012 host networking

Read More

Hyper Converged

Hyper Converged infrastructure is based on servers where disks are Direct-Attached Storage (DAS) connected internally or by using a JBOD tray. Each server (at least four to implement Storage Space Direct) has their own storage devices. So there are no shared disks or JBODs.

Hyper Converged infrastructure is based on known features as Failover Cluster, Cluster Shared Volume, and Storage Space. However, because storage devices are not shared between each node, we need something more to create a Clustered Storage Space with DAS devices. This is called Storage Space Direct. Below you can find the Storage Spaces Direct stack.

On network side, Storage Space Direct leverage at least 10G networks RDMA capable. This is because replications that occur though Software Storage Bus need low latency that RDMA provides.

More on this link: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/storage-spaces-direct-overview?f=255&MSPPError=-2147217396

Nested Virtualized Windows Server 2016 Hyper-V Cluster LAB

Prior to deployment on production I wanted to test new Windows Server 2016 Hyper V Cluster. On paper it seems it didn’t change much from Windows Server 2012 R2 but still there is fear of unknown. My goal was to test all of it on my desktop workstation since it is quite good even after 3 years of service it is still capable of doing some serious business. Main new feature that will enable me to do this is called Nested Virtualization.

Well now after everything I must say I am impressed what I was capable to achieve and this will be series of articles and step by step instructions if you are interested in doing similar setup at your home or just part of it for fun.

First things comes first 🙂

In all possible scenarios planing and preparation is half work done right there, because of that we need detail plan of our future Hyper V cluster environment and all of it parts and envision our test case.

Read More

Add Nano Server to Domain

This is procedure how to add Nano Server to domain. Basic idea behind this is to do offline join to domain. Before you venture to adding Nano Server to domain you must set network address and adequate DNS record on your DNS server.

Nano server is a headless server which you cant RDP or not a command prompt. For Nano Server management we have to use PowerShell or RSAT tools. So as a first step is to login to other server which stays in the same network and run the PowerShell and execute the following commands.

First add the server to TrustedHost List

Read More

Nano Server – Deployment

So, if you are an IT Pro you probably know that with Microsoft Server 2016 comes with something called Nano Server.

In my opinion it is the best of new thing that Server 2016 have. To see what is new in Windows Server 2016 check out this link on TechNet and if you have more time available there are a series of really good Microsoft Virtual Academy resources here.

Over the last few years the Microsoft tried to downsize their Windows Server product and answer on many issues that users had.

The first attempt to resolve these issues was in Server Core released as an installation option in Windows Server 2008. A command line only version of the Server OS that can be managed remotely and to a limited degree from a direct console This ‘server core’ did away with a lot of extraneous ‘stuff’ and meant fewer updates, smaller images and smaller, quicker installations.

But this was not enough and so the Server Product team in Microsoft went back to the drawing board and produced a deployment option now known as Nano server. This cannot be installed from the DVD or ISO, it has to be installed using PowerShell and each individual image built up to only contain the roles and services that are required for that particular server.

Read More

How to create a Hyper-V VM template

In this post I will look at creating a virtual machine (VM) template that you can use to quickly deploy new VM’s from, without having to install and patch them each time.

It is particularly useful if you are in a small Hyper-V environment and don’t have System Center Virtual Machine Manager (VMM).

The beauty of using a template for VM deployment is standardization. You deploy a known configuration which can be pre-patched which reduces time during the post deployment tasks.

Read More

Shared Nothing Live Migration

Shared Nothing Live Migration protects you from planned downtime (say you need to patch Windows on host or replace or upgrade some hardware components). See:

Shared Nothing Live Migration

For an unplanned downtime you need either VM HA (little downtime, little data loss, VM reboots) or guest VM cluster (no downtime, no data loss, VM turns to other host). See:

VMs for High Availability

Guest VM Cluster for HA

Read More

Run Hyper-V in a Virtual Machine with Nested Virtualization

Nested virtualization is a feature that allows you to run Hyper-V inside of a Hyper-V virtual machine. In other words, with nested virtualization, a Hyper-V host itself can be virtualized. Some use cases for nested virtualization would be to run a Hyper-V Container in a virtualized container host, set-up a Hyper-V lab in a virtualized environment, or to test multi-machine scenarios without the need for individual hardware. This document will detail software and hardware prerequisites, configuration steps, and limitations.

Prerequisites

  • A Hyper-V host running Windows Server 2016 or Windows 10 Anniversary Update.
  • A Hyper-V VM running Windows Server 2016 or Windows 10 Anniversary Update.
  • A Hyper-V VM with configuration version 8.0 or greater.
  • An Intel processor with VT-x and EPT technology.

Configure Nested Virtualization

  1. Create a virtual machine. See the prerequisites above for the required OS and VM versions.
  2. While the virtual machine is in the OFF state, run the following command on the physical Hyper-V host. This enables nested virtualization for the virtual machine.

  1. Start the virtual machine.
  2. Install Hyper-V within the virtual machine, just like you would for a physical server. For more information on installing Hyper-V see, Install Hyper-V.

Read More

Page 1 of 2

Powered by WordPress & Theme by Anders Norén