Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Windows 2012 single node Hyper-V cluster

Unanswered Windows 2012 single node Hyper-V cluster

  • Sunday, January 27, 2013 4:12 PM
     
     
    Sign In to Vote
    0

    Hi

    Because we have a limited budget, but urgently need to consolidate some old servers we are going with one new HP Proliant server with Windows 2012 server installed and on top of it Hyper-V role in a single node cluster mode. We decided to go with a single node cluster installation because in a few months we will implement (add) another two proliant server with SAN to existing cluster to have fully HA environment, but right now single server with DAS is our only option.

    My question is, what is best practice to install Hyper-V as a single node cluster ? Are there any step-by-step guides or other informations ?

    Also is it better to configure node as a workgroup (stand alone server) or a member of an AD domain ?

    New server has 4 NICs. On Windows 2008 R2 cluster we used NIC in the following scenario:

    - 1 NIC for Hyper-V management in LAN environment

    - 1 NIC for virtual switch (for VM) in LAN environment

    - 1 NIC for live migration (different subnet)

    - 1 NIC for CSV (different subnet).

    Now on Windows 2012 there is NIC teaming option build-in. Is it better to configure NIC in scenario like we did on 2008 cluster, or do we team all NIC together and configure different VLANs  (1 for management, 1 for VM, 1 for live migration, 1 for CSV)

    Any help or clues are gladly appreciated.

    Thank you in advance

    Mike

     

All Replies

  • Sunday, January 27, 2013 11:57 PM
     
     
    Sign In to Vote
    0

    Clusters require domains.

    No need to start with a single node cluster.  You indicate that you will be receiving a pair of servers in the future with a SAN.  Just put up your single server today and Live Migrate them from the single server to the cluster when you get it built.  Then you can add the third node into the cluster when you have moved everything off it.

    With four NICs and no teaming, you can easily run into a situation where something goes down at the worst possible time.  Teaming will help minimize that.  You could either create one 4-NIC team and use VLANs, or you could come up with other combinations that fit your needs.

    .:|:.:|:. tim

     
  • Monday, January 28, 2013 11:31 AM
     
     
    Sign In to Vote
    0

    Hi

    Thanks. OK, we'll go with a single server installtion in a workgroup and no cluster mode and P2V existing physical server on it.

    When we get additional hardware, we'll install 2 node cluster with SAN storage, and do migration from 'non cluster' node to a cluster, and then add 'single hyper-v node' as a third node to a cluster ? 

    Did I get this right, is this right scenario ? As I know, Hyper-V 3.0 support 'share nothing migration' so as I see we can do a live 'online' migration from a single hyper-v node with DAS to a new 2-node cluster on SAN with almost zero downtime, and the re-configure blank single hyper-v node to a cluster ?

    OK, so it is better to do a Windows 2012 NIC teaming all  4 NICs, and then configure VLAN for use on single hyper-v host?

    How many VLANs do we need ? I suppose only one a single hyper-v host (since there will be no CSV or Live Migration)

    - 1 for Management and VMnetwork switch (both in our company LAN network) ?

    Thanks again

    Regards,

    Mikea