none
Hyper-V Management and Cluster Failover Management

    Question

  • Maybe I'm thinking about this all wrong, but when using Hyper-V in a standalone environment you can use Hyper-V Manager. When joining it in a cluster you use Failover Cluster Manager for cluster management. Is there a way to use both of these on 1 NIC or do I need a seperate NIC for both, or is it recommended to not use Hyper-V Manager after joining a cluster? Also, if there a way to tell Hyper-V which NIC to use for the Failover Cluster Management?
    Monday, April 18, 2011 1:22 PM

Answers

All replies

  • Hi.

    I will try to explain this as easy as I can.

    When you join your Hyper-V hosts to a cluster, you should do the most of the administration from the FCM. If you use Hyper-V manager, you would still need to update the configuration/changes in failover cluster manager afterwards.

    Check this post: http://kristiannese.blogspot.com/2010/10/failover-cluster-manager-scvmm-and.html

    When it comes to NICs, this is maybe the most important component in your cluster environment.

    You should have 1 NIC dedicated to host management, 1 NIC dedicated for external virtual network for your VMs, 1 NIC dedicated for Live migration, 1 (or more) NICs dedicated for CSV/iSCSI, and even 1 dedicated NIC for cluster communication. But you can actually create a test cluster with only a single NIC.

    Some more reading: http://kristiannese.blogspot.com/search/label/networking

    http://kristiannese.blogspot.com/2011/01/failover-cluster-for-use-with-hyper-v.html

    http://kristiannese.blogspot.com/2010/11/failover-clustering-and-domain.html

     

     


    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
    Monday, April 18, 2011 1:32 PM
  • Thank Kristian,

    Mark As Answer

    I already understood the NIC information, as far as what is needed for the different Hyper-V functions, I was just unsure weather I would need to use both Hyper-V Manager and Failover Cluster Manager. Thanks for the info.

    Monday, April 18, 2011 1:39 PM
  • The management NIC on a production host or cluster should be separate from other functions such as NICs attaced to virtual switches, cluster heartbeat and live migration.  I have seen folks combine the cluster heartbeat and live migration NICs, but if you can separate them out to separate physical NICs it will keep you out of trouble.  In a cluster all of this is defined in your cluster setup for which physical NIC are for cluster use, The rest can be setup with Hyper-V manager or SCVMM for VM access.  The management NIC is just that whether it is a standalone or clustered  host.  It is used for things like RDP, or Hyper-V manager, SCVMM, Failover Cluster Administrator etc...

     

    As far as manament, you can use Hyper-V manager to do most administrative functions like modifying VM properties and connecting.  Without VMM, you will not be able to live migration VMs without the use of Failover Cluster Administrator and Hyper-V manager cannot do this.  For smaller environments, the combination of these tools should work fine, but as  you grow, the addition of VMM will save you lots of time taking out the complexity of managing with multiple tools.

     

     

    Rob McShinsky (http://www.VirtuallyAware.com


    http://www.VirtuallyAware.com
    Monday, April 18, 2011 1:44 PM