Posts Tagged ‘Integration Services’

Hyper-V 2016 Tp5: Hyper-V Manager Console new features

April 28, 2016 Leave a comment

Here are some important information and improvements Microsoft released for Hyper-V Manager in Tp5:

  • Alternate credentials support. You can now use a different set of credentials in Hyper-V Manager when you connect to another Windows Server 2016 TP5 or Windows 10 remote host. You can also save these credentials to make it easier to log on again.
  • Previous version management: the New Hyper-V Manager will allow you to manage versions manage computers running Hyper-V on Windows Server 2012/R2 and Windows 8.x client version.
  • Updated management protocolHyper-V Manager has been updated to communicate with remote Hyper-V hosts using the WS-MAN protocol, which permits CredSSP, Kerberos or NTLM authentication. When you use CredSSP to connect to a remote Hyper-V host, you can do a live migration without enabling constrained delegation in Active Directory. The WS-MAN-based infrastructure also makes it easier to enable a host for remote management. WS-MAN connects over port 80, which is open by default.
  • No more Integration services for Windows Virtual Machines. Updates to integration services for Windows guests are distributed through Windows Update. For service providers and hosting companies, this puts the control of applying updates into the hands of the tenants who own the virtual machines. Customers (tenants Administrators) can now update their Windows virtual machines with all updates, including the integration services, using a single method.
  • Integration services for Linux and FreeBSD Virtual Machines. Hyper-V supports both emulated and Hyper-V-specific devices for Linux and FreeBSD virtual machines. Linux Integration Services (LIS) or FreeBSD Integration Services (BIS) , the collection of drivers that are required to run Hyper-V-specific devices, has been added to the Linux kernel and is updated for new releases, but Linux distributions based on older kernels may not have the latest enhancements or fixes. Microsoft provides a download containing installable LIS drivers for some Linux installations based on these older kernels.
    Note: As some Linux distributions include versions of LIS, make sure you install the latest downloadable version of LIS, if applicable, for your installation.



Red Hat RHEL 5.9 now includes the Hyper-V Linux Integration Services built-in

January 10, 2013 Leave a comment

Red Hat announced the release of RHEL 5.9 which includes the Hyper-V Linux Integration Services built-in.

New Virtualization Capabilities and Flexibility in Multi-vendor Environments. Red Hat Enterprise Linux 5.9 enhances the operating system’s usability in multi-vendor environments by introducing Microsoft Hyper-V drivers for improved performance. This enhances the usability of Red Hat Enterprise Linux 5 for guests in heterogeneous, multi-vendor virtualized environments and provides improved flexibility and interoperability for enterprises.

To download Red Hat Enterprise Linux 5.9 visit here

Hyper-v: Detailed step by step installing RedHat 6.1 VM in expert mode with the new Linux Integration Services 3.1

August 18, 2011 16 comments

Microsoft released the a new Linux Integration Services, fully tested against RHEL 6.0, RHEL 6.1, and CentOS 6.0

To Create a RedHat 6 VM

1. Open Hyper-V Manager: Click Start, point to Administrative Tools, and then click
Hyper-V Manager.
2. Create a new virtual machine where you will install Linux: In the Actions menu, click New, and then click Virtual Machine.

Note: if you do not Add a legacy network adapter a this point, the virtual machine will not have network support, until you install the Linux Integration Services.

3. Specify the Linux installation media: Right-click the virtual machine that you created, and then click Settings. In IDE Controller, specify one of the following:
a. An image file in ISO format that contains the files required for installation
b. A physical CD/DVD drive that contains the installation media
4. Turn on the virtual machine: Right-click the virtual machine that you created, and then click Connect.
To Install Redhat Linux 6.1

1. After a short delay, the Welcome to Red Hat Linux 6.1! screen appears. Press <Tab>

2.At the prompt, add the text: append expert and then press <Enter>

3. Press <OK> to check the installation media or <SKIP> to not test check in the next screen

4. Click Next to continue

5. The Choose a Language screen appears. This screen asks you to select the lan­guage to be used during the installation process.  Use the up-or down-arrow key to select alanguage (the system highlights your choice). Click Next

6.The Keyboard Type screen appears asking you to select a keyboard type.  Use the up- or down-arrow key to select a keyboard type (the system highlights your choice). Click Next

7. At the “Devices” screen select Basic Storage Devices to install Red Hat Enterprise Linux on the following storage devices: hard drives or solid-state drives connected directly to the local system

8. As you selected Basic Storage Devices, anaconda automatically detects the local storage attached to the system and does not require further input.Click Next.

9. Enter the Hostname for your server, select OK

10 If you added the Legacy Network at the creation of the VM, then click Configure Network . At the “Network Configuration” window,  Specify an IP address/gateway. Otherwise, skip this task. You can setup the network later, after installing the Linux Integration Services

Use the IPv4 Settings tab to configure the IPv4 parameters for the previously selected network connection.  Select Start automatically to start the connection automatically when the system boots.

11.Click Next

12. At the “Time Zone Selection” window, highlight the correct time zone. Click Next

13.For Root Password, type and confirm the password. Click Next

14. If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive

15. Select the type of installation would you like and then click Next.

Note: If you chose one of the automatic partitioning options (first 4 options) and selected Review, you can either accept the current partition settings (click Next), or modify the setup manually in the partitioning screen. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you by anaconda appear. You can make modifications to these partitions if they do not meet your needs.

If you chose to create a custom layout, you must tell the installation program where to install Red Hat Enterprise Linux. This is done by defining mount points for one or more disk partitions in which Red Hat Enterprise Linux is installed. You may also need to create and/or delete partitions at this time

Unless you have a reason for doing otherwise, I recommend that you create the following partitions for x86, AMD64, and Intel
64 systems:

swap partition

/boot partition

/ partition

Advice on Partitions:

  • A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, use the  recommended:
 Amount of RAM in the System  Recommended Amount of Swap Space
4GB of RAM or less a minimum of 2GB of swap space
4GB to 16GB of RAM a minimum of 4GB of swap space
16GB to 64GB of RAM a minimum of 8GB of swap space
64GB to 256GB of RAM a minimum of 16GB of swap space
  • The /var directory holds content for a number of applications. It also is used to store downloaded update packages on a temporary basis. Ensure that the partition containing the /var directory has enough space to download pending updates and hold your other content.
  • The /usr directory holds the majority of software content on a Red Hat Enterprise Linux system. For an installation of the default set of software, allocate at least 4 GB of space.
    If you are a software developer or plan to use your Red Hat Enterprise Linux system to learn software development skills, you may want to at least double this allocation.
  • Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other partitions to reallocate storage

16. After finishing creating the partitions, Click Next. The installer prompts you to confirm the  partitioning options that you selected. Click Write changes to disk to allow the installer to partition your hard drive and install Red Hat Enterprise Linux

17.Allow the  installation process to complete. The Package Installation Defaults screen appears and details the default package set for the Red Hat Enterprise Linux installation

If you select Basic Server, this option will provide a basic installation of Red Hat Enterprise Linux for use on a server.

18. Select Customize now to specify the software packages for your final system in more detail. This option causes the installation process to display an additional customization screen when you select Next.  The following screens shows the customized packages selected

Note : The packages that you select are not permanent. After you boot your system, use the Add/Remove Software tool to either install new
software or remove installed packages. To run this tool, from the main menu, select System -> Administration -> Add/Remove Software

19. Click Next to continue the installation. The installer checks your selection, and automatically adds any extra packages required to use the software you selected. The installation process will start. At this point there is nothing left for you to do until all the packages have been installed.

20. Installation Complete: Red Hat Enterprise Linux installation is now complete. select Reboot to restart your Virtual Machine

Now it’s time for the first-boot configuration.

21. First Boot lets you configure your environment at the beginning. Click Forward to proceed

22. Accept the License and Click Forward to proceed

23. Setting up software updates.  Select whether to register the system immediately with Red Hat Network. To register the system, select Yes, I’d like to register now, and click Forward.
Note : it can be registered with the RedHat Entitlement Service later using the Red Hat Subscription Manager tools

24. Create User to use as a regular non-administrative use. Enter a user name and your full name, and then enter your chosen password. Type your password once more in the Confirm Password box to ensure that it is correct.
Note: If you do not create at least one user account in this step, you will not be able to log in to the RedHat Enterprise Linux graphical environment

25. Click Forward to proceed

26. Date and Time. Use this screen to adjust the date and time of the system clock.

27. Click Forward to proceed

28. Kdump. Use this screen to select whether or not to use the Kdump kernel crash dumping mechanism on this system. Note that if you
select this option, you will need to reserve memory for Kdump and that this memory will not be available for any other purpose.

29 Click Finish to proceed.
Done installation and configuration of RedHat Linux 6.1 completed. Not let’s configure the Linux Integration Services.

To install Linux Integration Services Version 3.1

Important Note:  There is an issue where the SCVMM 2008 Service can crash with VMs running Linux Integration Components v3.1 for Hyper-V.
Disabling the KVP daemon on the Linux virtual machine will prevent the SCVMM service crash. The command to make this change must be run as root.

#/sbin/chkconfig –level 35 hv_kvp_daemon off

This will prevent the KVP service from auto starting while retaining all other functionality of hv_utils. hv_utils provides integrated shutdown, key value pair data exchange, and heartbeat features. More info :

1. Log on to the virtual machine.
2. In Hyper-V Manager, configure LinuxIC v30.ISO (located in the directory where you extracted the downloaded files) as a physical CD/DVD drive on the virtual machine.

3. Open a Terminal Console ( command line )

4. As the root user, mount the CD in the virtual machine by issuing the following command at a shell prompt:
 #mount /dev/cdrom  /media

4. As the root user, run the following command to install the synthetic drivers. A reboot is required after installation.

For 64-bit versions:
# yum install /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64
# yum install /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64
# reboot

or if you prefer to use rpm:

# rpm –ivh /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64.rpm
# rpm –ivh /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64.rpm
# reboot

For 32-bit versions:
# yum install /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686
 #yum install /media/x86/microsoft-hyper-v-rhel6-60.1.i686
# reboot


# rpm –ivh /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686.rpm
# rpm –ivh /media/x86/microsoft-hyper-v-rhel6-60.1.i686.rpm
# reboot


DONE! You should now have RedHat 6.1 running as VM on Hyper-V.


After Linux Integration Services are installed on the virtual machine, Key Value Pair exchange  functionality is activated. This allows the virtual machine to provide the following information  to the virtualization server:

  •  Fully Qualified Domain Name of the virtual machine
  •  Version of the Linux Integration Services that are installed
  •  IP Addresses (both IPv4 and IPv6) for all Ethernet adapters in the virtual machine
  •  OS Build information, including the distribution and kernel version
  •  Processor architecture (x86 or x86-64)

The data can be viewed using the Hyper-V WMI provider, and accessed via Windows  PowerShell. Instructions for viewing Key Value Pair exchange data are available at these  websites:

Hyper-V : Supported Server Guest Operating Systems. Updated May 2011

May 16, 2011 Leave a comment


 The following tables list the Server guest operating systems that are supported for use on a virtual machine as a guest operating system.

Server guest operating system Editions Virtual processors
Windows Server 2008 R2 with Service Pack 1 Standard, Enterprise, Datacenter, and Web editions 1, 2, or 4
Windows Server 2008 R2 Standard, Enterprise, Datacenter, and Windows Web Server 2008 R2 1, 2, or 4
Windows Server 2008 Standard, Standard without Hyper-V, Enterprise, Enterprise without Hyper-V, Datacenter, Datacenter without Hyper-V, Windows Web Server 2008, and HPC Edition 1, 2, or 4
Windows Server 2003 R2 with Service Pack 2 Standard, Enterprise, Datacenter, and Web 1 or 2
Windows Home Server 2011 Standard 1
Windows Storage Server 2008 R2 Essentials 1
Windows Small Business Server 2011 Essentials 1 or 2
Windows Small Business Server 2011 Standard 1, 2, or 4
Windows Server 2003 R2 x64 Edition with Service Pack 2 Standard, Enterprise, and Datacenter 1 or 2
Windows Server 2003 with Service Pack 2 Standard, Enterprise, Datacenter, and Web 1 or 2
Windows Server 2003 x64 Edition with Service Pack 2 Standard, Enterprise, and Datacenter 1 or 2
CentOS 5.2 through 5.6 (NEW)  x86 edition and x64 edition 1, 2, or 4
Red Hat Enterprise Linux 5.6 x86 edition and x64 edition 1, 2, or 4
Red Hat Enterprise Linux 5.5 x86 edition and x64 edition 1, 2, or 4
Red Hat Enterprise Linux 5.4 x86 edition and x64 edition 1, 2, or 4
Red Hat Enterprise Linux 5.3 x86 edition and x64 edition 1, 2, or 4
Red Hat Enterprise Linux 5.2 x86 edition and x64 edition 1, 2, or 4
SUSE Linux Enterprise Server 11 with Service Pack 1 x86 edition and x64 edition 1, 2, or 4
SUSE Linux Enterprise Server 10 with Service Pack 4 x86 edition and x64 edition 1, 2, or 4

 Note: Support for Windows 2000 Server and Windows XP with Service Pack 2 (x86) ended on July 13, 2010

Source :

Everything you wanted to know about Time Synchronization in Hyper-V, but were afraid to ask

November 22, 2010 Leave a comment


keeping time inside of virtual machines, how Hyper-V tackles these ?

Check out here in Ben Armstrong, Microsoft Virtualization Program Manager :

Debian on Hyper-V with 4 vCPU support and syntetic network.

November 2, 2010 2 comments

When Microsoft says that does not support all linux distributions, does not mean that a particular distribution will not work on Hyper-V.

It’s easy to get a DEBIAN running on Hyper-V. It took me more time to install Debian than to add the Hyper-V integration services components, thanks to Yusuf Ozturk , who created the kernel updates, ready to deploy on Debian.

Here are the steps:

1. Download Debian 5.06 (lenny)  from  (full CD/DVD sets – CD 1 )
2. Create a VM with 1 Legacy Network ( we will add the synthetic one, later ) and 4 processors
3. Install Debian using the ISO.
4. After installation finished, logon

5. Using a Terminal session, typed the following commands

# apt-get update


# aptitude update
# wget -c
# wget -c

# dpkg -i linux-image-2.6.36-hyperv_2.6.36-hyperv-10.00.Custom_amd64.deb linux-headers-2.6.36-hyperv_2.6.36-hyperv-10.00.Custom_amd64.deb
# echo -e “hv_vmbus\nhv_storvsc\nhv_blkvsc\nhv_netvsc” >> /etc/initramfs-tools/modules
# update-initramfs –u –k 2.6.36-hyperv
6. Shutdown the Virtual Machine
7. Added synthetic Network
8. Start the VM

Now you have a Debian distribution running on Hyper-V, with 4 processors, synthetic network and also integrated shutdown is available. Simple as that!

Workaround for Pluggable Time Source support for RHEL 5.x 64-bit Hyper-V guests

October 29, 2010 Leave a comment

When installed in a supported Linux virtual machine running on Hyper-V, the Linux Integration Components provide:

• Driver support for synthetic devices: The Linux integration components include support for both the synthetic network controller and synthetic storage controller that have been developed specifically for Hyper-V. These components take advantage of the new high-speed bus, VMBus, which was developed for Hyper-V.

• Fastpath Boot Support: Boot devices now take advantage of the storage VSC to provide enhanced performance.

• Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.

• Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager, using the “Shut Down” command.

• Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.

• Heartbeat: Allows the host to detect whether the guest is running and responsive.

• Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest.

Although this version of the integration services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 / 5.3 / 5.4 / 5.5, Red Hat Enterprise Linux 5 x64 editions do not support using the Pluggable Time Source component.

However, you can use the existing timesync component with the adjtimex RPM package, to compensate for time drift:

If using the x64 version of Red Hat Enterprise Linux, follow these additional instructions:

 1.   Attach the Red Hat Enterprise Linux ISO that was used for installation in the virtual machine, and mount it using the following commands at a shell prompt:

# mkdir /mnt/cdrom

# mount /dev/cdrom /mnt/cdrom

2.   Install the adjtimex RPM for more accurate time keeping in the virtual machine:

# rpm –ivh /mnt/cdrom/Server/adjtimex-1.20-2.1.x86_64.rpm


To install the Linux IC.

After the ISO is “available”.
Firstly, install the Required Components via Command Line

Red Hat updates

# yum install kernel-devel

# yum groupinstall “development tools”

# yum update 

Restart the VM and then, insert the LinuxIC iso into the DVD drive and copy the contents to /opt/linuxic directory.
Run the commands below, to install the IC:  

 # mount /dev/cdrom /mnt

# mkdir /opt/linux_is

# cp –r /mnt/* /opt/linux_is

# cd /opt/linux_is

# make

# make install 

To verify that the Linux ICs are working.

# /sbin/lsmod | grep vsc

# modinfo vmbus

To verify the Synthetic Ethernet adapter is working

# ifconfig seth0
Note:  Article also published by myself at
My thanks to Sumesh P - MSFT, who helped with the tip.

New version of the Linux Integration Services for Hyper-V

September 27, 2010 1 comment

A new version (2.1) of the Linux Integration Services for Hyper-V have just been made available.

This new version has some significant improvements:  

  • Driver support for synthetic devices: Linux Integration Services supports the synthetic network controller and the synthetic storage controller that were developed specifically for Hyper-V.
  • Fastpath Boot Support for Hyper-V: Boot devices take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
  • Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.
  • Integrated Shutdown: Virtual machines running Linux can be gracefully shut down from either Hyper-V Manager or System Center Virtual Machine Manager.
  • Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.
  • Heartbeat: Allows the host to detect whether the guest is running and responsive. 
  • Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest. 

This version of the integration services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 / 5.3 / 5.4 / 5.5.



Hyper-V R2 : Storage/Network Design for High Availability

March 1, 2010 1 comment

By converting your physical servers to virtual ones, you immediately get extra capabilities that make them less likely to go down and easier to bring back up when they do:

  • · Snapshots enable you to go back in time when a software update or configuration change blows up an otherwise healthy server.
  • · Virtual hard disks consolidate the thousands of files that comprise a Windows server into a single file for backups, which significantly improves the reliability of those backups.
  • · Volume Shadow Copy Service (VSS) support, which is natively available in Hyper-V, means that applications return from a restore with zero loss of data and immediately ready for operation.
  • · Migration capabilities improve planned downtime activities by providing a mechanism for relocating the processing of virtual machines to new hosts with little to no disruption in service.
  • · Failover clustering means that the loss of a virtual host automatically moves virtual machines to new locations where they can continue doing their job.

What’s become much more critical is that the servers/application/services to keep on working.

To Provide High Availability, we need to design properly our environment. With the right combinations of technology, you can inexpensively increase the availability of your environment.

The best practices are based on the following design principles:

  • · Redundant hardware to eliminate a single point of failure
  • · Load balancing and failover for iSCSI and network traffic
  • · Redundant paths for the cluster, Cluster Shared Volume (CSV), and live migration traffic
  • · Separation of each traffic type for security and availability
  • · Ease of use and implementation

Remember: Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter must be used for the physical computers. These servers must run the same version of Windows Server 2008 R2, including the same type of installation. That is, both servers must be either a full installation or a Server Core installation

Also, Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware-enforced Data Execution Prevention (DEP). Specifically, you must enable the Intel XD bit (execute disable bit) or AMD NX bit (no execute bit).


Server-class equipment. The use of equipment that is not listed in the Windows catalog can impact supportability and may not best meet the needs of your virtual machines. Moving to tested and supported server-class equipment will ensure full support in the case of a problem. ). The Windows Server catalog is available at the Microsoft Web site

iSCSI Storage
I would recommend Dell Equalogic, Compellent, IBM NetApp, EMC, but you should evaluate others vendors.

iSCSI Software

If you need to use software-based iSCSI, look carefully at the features available. Microsoft clustering requires iSCSI to support SCSI Primary Commands-3, specifically the support of Persistent Reservations. Most for-cost iSCSI software currently supports this capability, but there is very little support for it in most open source software packages.

One inexpensive and easy-to-use software package is the StarWind iSCSI Target from StarWind Software. There is a free version of StarWind iSCSI target allowing multiple connections. You cannot get it filling automatic form on their site. You have to ask for free NFR unlock key manuallyNetwork
How about the network configuration? Here is my proposal and this is what I am using in terms of NICs/Ports:1 management2 private: 1 for cluster private/CSV primary, 1 for live migration primary2 for network (in teaming)2 for iSCSI2 Dedicated (NIC/Ports) for the Network traffic configured as teaming.The failover cluster should be disabled from managing this network.
Provided by establishing the Hyper-V virtual switch on a network team. The team can provide load balancing, link aggregation, and failover capabilities to the virtual network
NIC teaming is the process of grouping together several physical NICs into one single logical NIC, which can be used for network fault tolerance and transmit load balance. The process of grouping NICs is called teaming. Teaming has two purposes:• Fault Tolerance: By teaming more than one physical NIC to a logical NIC, high availability is maximized. Even if one NIC fails, the network connection does not cease and continues to operate on other NICs.• Load Balancing: Balancing the network traffic load on a server can enhance the functionality of the server and the network. Load balancing within network interconnect controller (NIC) teams enables distributing traffic amongst the members of a NIC team so that traffic is routed among all available paths.2 Dedicated (NIC/Ports) for the CSV. (Minimum 1Gb). I personally recommend 10Gb. One a 2 nodes you can use cross-over, but if you plan to use more, than you need a switch. If you choose 10GB it means that your switch needs to be 10GB.
A feature of failover clusters called Cluster Shared Volumes is specifically designed to enhance the availability and manageability of virtual machines. Cluster Shared Volumes are volumes in a failover cluster that multiple nodes can read from and write to at the same time. This feature enables multiple nodes to concurrently access a single shared volume.CSV will provide many benefits, including easier storage management, greater resiliency to failures, the ability to store many VMs on a single LUN and have them fail over individually, and most notably, CSV provides the infrastructure to support and enhance live migration of Hyper-V virtual machines.Cluster private traffic will flow over the private network with the lowest cluster metric (typically has value of 1000). To view the cluster network metrics that have been assigned, run the following PowerShell command:
To view the cluster network metric settings, run the following Power Shell commands:Import-Module FailoverClusters
Get-ClusterNetwork | ft Name, Metric, AutoMetricIf the automatically assigned metrics are not the desired values, then the following Power Shell commands can be executed to manually set the metric values:Get-ClusterNetwork | ft Name, Metric, AutoMetricNote the name of the networks that you want to set the values on (used for next command)$cn = Get-ClusterNetwork “<cluster network name>”
$cn.Metric = <value>Cluster private/CSV should have a value of 1000
Live migration should have a value of 11002 Dedicated (NIC/Ports) for the iSCSI traffic.( Minimum 1Gb). I personally recommend 10Gb ( the difference in price will be about 10% more).Btw, remember: If you choose 10GB it means that your switch needs to be 10GB, also the Storage.
The mass-storage device controllers that are dedicated to the cluster storage should be identical. They should also use the same firmware version.Isolating iSCSI traffic to its own network path isolates that traffic to its own network segment, ensuring its full availability as network conditions change.A multipath I/O software needs to be installed on the Hyper-V hosts to manage the disks properly. This is done by first enabling Hyper-V-based MPIO support which is not installed by default.Also, Enable Jumbo frames on the two interfaces identified for iSCSI1 (NIC/Port) for the Management. External management applications (SCVMM, DMC, Backup/Restore, etc) communicate with the cluster through this network.Resuming :hyper-r2-host-ha