Results for category "HyperV3"

Adding a node to existing Windows Server 2012 R2 Hyper-V Cluster

I started working with Windows Server 2012 R2 cluster few weeks back. At the initial time, due to the lack of time – I started with a three node cluster and later made it as a four node cluster and now adding one more node. I thought of making a post on how to safely add a node to an existing production cluster.

I personally don’t encourage changing the Tyre while driving the car :D, however sometime the situation may demand it.

Before start

  • Ensure that the new server is on same patch level with other cluster nodes
  • Ensure that the server is on the same Firmware level with other cluster nodes
  • Ensure that Fail-over Cluster feature is installed
  • Ensure that Hyper-V role is installed and the Virtual Switch is configured with same name and settings as of other cluster nodes
  • Ideally, All cluster nodes should be identical – So I assume the new server is also having the same hardware as other cluster members
  • Ensure the Multipath software has installed as of other cluster nodes
  • Ensure that the Network interfaces are configured properly to meet the requirement for Hyper-V
  • Ensure that NICs dedicated for Live Migration, CSV, Heartbeat etc are able to ping to the respective IPs in other cluster nodes
  • Add an additional SAN disk of smaller size to be used along with validation test
  • Ensure SAN disks are visible in Disk Management of the new server. Just check, Don’t try to make it online.

    Check if DISKS are visible in Disk Management

    Check if DISKS are visible in Disk Management


I would definitely go through the validation tests every time I create/add nodes to the cluster. This will give us the confidence that everything is configured and working as expected before the activity starts. Since we are trying to add an additional node to the existing cluster, We should understand that validation test may interrupt the VMs hosted on other nodes as the CSV disks may go offline as part of the test. For this reason, I did assigned one more temporary disk and made it as a CSV so that we can select only this specific disk while performing the validation.

Go to Failover Cluster Manager – Nodes

Right click on Nodes and Select “Add Nodes”

Add node

Add node



Click next on the “Before you begin” page after reading :D.

On the “Select Server” page, Key In the server name and click on Add. Ideally, adding the node shouldn’t take more than ten seconds.

Adding the new node

Adding the new node


On the “Validation Warning” Screen, We need to choose the right option specific to running validation test. As I mentioned earlier, I prefer to run all test with a spare disk form storage which don’t have any production data. So select Yes.

Validation Warning

Validation Warning


Clicking Next will Switch on the Validation Configuration Wizard

The account used for running validation wizard should be a local administrator on all nodes.


Validation Wizard - Before Begin

Validation Wizard – Before Begin

The next screen is “Testing Options”. I prefer to run all tests. If you are re-running after identifying some issues, Its Ok to choose only that failed module by select “Run only tests I select”.


Testing Options

Testing Options

The next screen is important. We need to choose the right SAN disk which will be used for validation test. I already added a 1 TB disk and made it as a CSV disk – Name CSV-4. Chose the right disk and click on next.

Select the Storage which will be used for Validation test

Select the Storage which will be used for Validation test



In the Confirmation page, Have a look on the specific tests which are going to perform on each modules and click on NEXT



Click Next to start the Validation tests.

Validation Test in Progress

Validation Test in Progress


Once done, You can review the result by clicking “View Report”.

If any of the test got failed, the Wizard assumes that something is not correct, hence shouldn’t proceed with the next step with the blessing of wizard. However, Once you click on finish, You will go back to “Add Node Wizard”  where you will get Option to Run Validation test again or proceed without Validation test.


Validation Wizard - Result Summary

Validation Wizard – Result Summary

In my case, I am using NICs with trunking for HyperV Data traffic,  So while creating the Virtual switch – I haven’t assigned any IP to this interface which the validation wizard claims that its not good. As I am sure that this error is not going to make an issue, I am proceeding with the next Option.



In the next screen, Review the node to be added and click on NEXT.

Wait for the successful confirmation and that’s it.




Windows Server 2012 R2 – Shared Nothing Live Migration

Last week, We got the first Windows Server 2012 R2 Hyper-V Cluster up. Now, its the time for migrating some low priority payloads to test the performance and stability.

I used Shared nothing live migration on majority of the cases. I am happy to say that its a smooth and silent move.

Before starting shared nothing live migraiton

  • Kerberos or Credential Security Support Provider (CredSSP) to authenticate the Live Migration is configured – Check this link.
  •  Network for Live Migration is configured and able to communicate

On Windows Server 2012 which is the source, Go to Failover Cluster Manager -> Cluster Name -> Networks

Right Click on Networks and Choose Live Migration setting.

Windwos Server 2012 - Hyper V Live Migration Network Configuration

Windows Server 2012 – Hyper V Live Migration Network Configuration


  • Ensure that the right network card is selected with right preference for Live migration
  • The same setting needs to be checked on the Windows Server 2012 R2 cluster too.

Windows Server 2012 R2 - Hyper V Live Migration Network Configuration

  • Ensure the communication between source server and destination server over the Live Migration network
  • Remove the VM from cluster high availability is configured
  • From Hyper-V Manager of source server, Right Click on the VM and choose Move

Selecting Move Option

  • In the Choose Move Type, Select “Move Virtual Machine”


Update – This post is not completed. For some reason, the rest of the post was missing after I published it. Let me re-create for you. Please check this page later.


Windows Server 2012 inplace upgrade to Windows 2012 R2

Getting ready for the Windows 2012 R2 release. I was searching for the inplace upgrade procedures but couldn’t see any blog or technet writeup if its supported or how should we get this done.

As expected, Windows  Server 2012 can be upgraded to Windows Server 2012 R2. ie inplace upgrade is supported. I just tested with a standalone HyperV node with the in place upgrade and successfully completed Windows 2012 R2 installation.





The compatibility check will detect the applications and report in case of any issues.  I had few VMs which was running at the time of upgrade. And thus the compatibility report clearly says that Virtual machines are ON and needs to turned off before starting the upgrade.


After turning off the VMs, I was able to proceed with the next step.




And thats all. In approximately 30 minutes, the server got upgraded. HyperV service was all fine and VMs are perfectly running.




Oracle Enterprise Linux on HyperV

One of the major limitation  I am having now is the VMs with non supported gust OS. Some of the tweaks which is found on the net works but however, not confident to try it out on production machines. With Windows Server 2012 R2, I see that Hyper-V will be improving its support specific to Linux VMs.

Yesterday, Microsoft and Oracle made announcements their joint partnership.

Customers should expect all Oracle products will be supported on Hyper-V as well as Azure soon.

Cheers !



Windows Server 2012 R2 and Network Virtualization

Seems Microsoft heard the voice of customers.

Though network virtualization was introduced with Windows Server 2012, I really don’t think that any of the customer could adopt it and make a production network virtualized. The main road block was network virtualization gateway. As I mentioned in one of my previous post, lot many main stream networking giants are coming up with network virtualization gateway appliance for Hyper-V. But that could be an additional investment and may not be an easy option for everyone.

Even, We had unofficial information that Windows 2012 R2 will fix-up these mess. And seems its true. Windows Server 2012 R2 is coming up with an inbuilt gateway which is capable of Multi-tenant multi-site VPN gateway, NAT gateway for internet access and forwarding gateway for within the Datacenter.

Cheers !


F5 Big IP Announced NVGRE Support

F5 announced their road map on supporting network visualization for Hyper-V.

F5® BIG-IP® hardware will support NVGRE gateway functionality beginning the first quarter of calendar year 2014. Integration with Windows Azure is currently available on F5’s BIG-IP solutions.

For me, this seems to be an important move as one of the mainstream vendor will be coming soon to support the network visualization initiatives. Lets hope for the best !






Network Virtualization with SCVMM 2012 Sp1 – Some key points before start

I was running around this topic for the last few months. Once we had Windows 2012 HyperV Clusters, the next target was to try out network virtualization. Unfortunately, SCVMM 2012 Sp1 was not ready at that time. Recently, we got that. We did attempted and few points which I understood now is

  • For enabling communication between a Network Virtualized subnet and a non network virtualized subnet, A Virtualization Gateway needs to be in the middle
  • Virtualization Gateway devices are still under development and major network vendors are getting ready for release
  • Microsoft is coming up with Software-based NV Gateway which will be fully integrated with SCVMM
  • F5 is also coming with Network Virtualization gateway – but time lines are not confirmed

To my knowledge, the whole stuff is amazing but its complicated. Lack of documentation and information makes it complicated and I expect to see more official documentation coming up for NV in the coming days.

If you have any further information to add on, Please comment. I am open for a discussion.



Installing HyperV3 – Pre-Check

In the last six months, I did installed multiple HyperV clusters. One important issue which I faced in the initial days is outdated firmwares. This may not be specific to HyperV3, but this will become an issue once you enable HyperV3. I had issues while enabling HyperV role, sometimes while creating a cluster.

We are crossing 6+ months with Windows Server 2012. Most of the vendors has released the new firmwares for Windows Server 2012. I had issues where the specific driver was only available for Windows 2008 R2, where we cannot update it from a Windows 2012 OS. Installation will throw an error which says that incompatible OS.

Update Firmware

Update Firmware error

Its always better to check each components and get the latest firmware and drivers prior to the HyperV configurations. If Windows 2012 is supported, you can try using bootable ISO images if possible.

Another important aspect of firmware update is due to the support for latest features like SR-IOV and ODX. The hardware may be having this feature but until the firmwares are updated to the latest one, we may not be able to use this.