none
Adding third node to Hyper-V failover cluster

    Question

  • The post http://social.technet.microsoft.com/Forums/en/winserverhyperv/thread/86ba2313-8bd8-42fd-adfd-b89af38695fe answered some questions, but a couple issues I remain unclear on are:

    Currently, we are using a crossover cable for server-to-server communications.  The TCP/IP (V4) on these NICs are set to DHCP (with no DHCP server).  We plan to add a VLAN on our switch, and connect the nodes to that VLAN.  Can we continue DHCP (with no DHCP server) and let the cluster sort itself out, or should we assign IPs manually?

    Once we've edited the zones for our SAN switches, and presented the LUNs containing our VMs to the new node as well as the currently presented nodes, am I correct in thinking that Clustered Shared Volumes will sort itself out, or are there configuration steps we need to perform?  I am concerned about the volume numbers staying in sync with the other nodes, especially.

    Wednesday, July 20, 2011 3:01 PM

Answers

  • Hi,

    I do assume you do use standard file server cluster without Hyper-V or CSV use.

    when you add a 3rd node the high level steps to take are:

    1. Prepare 3rd node (OS, Patchlevel, driver update) + Install FC role

    2. configure networks depending on other cluster node network configuration

    3. configure storage (FC/ISCSI) and present LUNs from cluster also to 3rd new node

    4. validate your cluster (see down below for more details)

    5. Join new node to cluster

    6. reconfigure quorum settings (if required)

    7. additional application level required steps (a.e. SQL installation...)

    NOTE: these is only an high level overview!

    more detailed informations around adding an node to an existing cluster can you find here:

    Add a Server to a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc730998.aspx

    Creating a Failover Cluster or Adding a Cluster Node
    http://technet.microsoft.com/en-us/library/cc730647.aspx

    Validate a New or Existing Failover Cluster
    http://technet.microsoft.com/en-us/library/cc772450.aspx

    Prepare Hardware Before Validating a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc770723.aspx

    when you follow these guidelines your failover should work without any issues. Use validation as a troubleshooting tool to cross-check your own configuration ->

    Use Validation Tests for Troubleshooting a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc770807.aspx

    Hope that helps.

    Regards

    Ramazan


    Ramazan Can [MVP Cluster] http://ramazancan.wordpress.com/ ##This posting is provided "AS IS" with no warranties, and confers no rights##
    Monday, July 25, 2011 8:27 PM

All replies

  • Hi,

     

    The TCP/IP (V4) on these NICs are set to DHCP (with no DHCP server).

     

    >> If there isn’t a DHCP server, how did the NICs get IP addresses?

     

    By the way, if you have CSV configured properly on the previous two nodes, you will find that the CSV is available on the new node after you add it to the existing cluster.

     

     

    Best Regards,

    Vincent Hu

     

    Thursday, July 21, 2011 3:53 AM
  • Automatic private addressing
    Thanks- Joe
    Friday, July 22, 2011 7:20 PM
  • I'm not sure that the statement about the shared volumes is totally true.  We have a two node failover cluster running WS08 (not R2) as a file server.  We wanted to add a third node, so I presented all 12 disks to the new server, and joined the node to the cluster.  When I tried to move the application to that node one of the volumes would not mount.  Looking at Disk Manager, I saw that the new node did not see that there was a volume on that disk.  All the others were fine, just this one.

    For the moment we have given up on this one new node, but before I take the time to try again, I'd like to know what I could do to mitigate this issue if it happens again, and if there is anything I can do short of failling the cluster over to check whether the pre-existing volumes are going to be recognized

    Certainly, any new volumes once the third node is a member are trivial.

     

    Thanks!


    • Edited by MNscripter Monday, July 25, 2011 3:51 PM improper terminology used
    Monday, July 25, 2011 3:46 PM
  • Hi,

    I do assume you do use standard file server cluster without Hyper-V or CSV use.

    when you add a 3rd node the high level steps to take are:

    1. Prepare 3rd node (OS, Patchlevel, driver update) + Install FC role

    2. configure networks depending on other cluster node network configuration

    3. configure storage (FC/ISCSI) and present LUNs from cluster also to 3rd new node

    4. validate your cluster (see down below for more details)

    5. Join new node to cluster

    6. reconfigure quorum settings (if required)

    7. additional application level required steps (a.e. SQL installation...)

    NOTE: these is only an high level overview!

    more detailed informations around adding an node to an existing cluster can you find here:

    Add a Server to a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc730998.aspx

    Creating a Failover Cluster or Adding a Cluster Node
    http://technet.microsoft.com/en-us/library/cc730647.aspx

    Validate a New or Existing Failover Cluster
    http://technet.microsoft.com/en-us/library/cc772450.aspx

    Prepare Hardware Before Validating a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc770723.aspx

    when you follow these guidelines your failover should work without any issues. Use validation as a troubleshooting tool to cross-check your own configuration ->

    Use Validation Tests for Troubleshooting a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc770807.aspx

    Hope that helps.

    Regards

    Ramazan


    Ramazan Can [MVP Cluster] http://ramazancan.wordpress.com/ ##This posting is provided "AS IS" with no warranties, and confers no rights##
    Monday, July 25, 2011 8:27 PM
  • Hi, I have a similar problem. I must add 3rd to existing cluster, but I have difficulty on how to present the LUNs to the node. The storage is MSA 2000

    In point 3:

    3. configure storage (FC/ISCSI) and present LUNs from cluster also to 3rd new node

    From MSA Menu I tried to map the LUN as ReadOnly, and from new node in Disk Management I see Disk 1 "ReadOnly". Is this correct to make pass 4 and 5

    4. validate your cluster (see down below for more details)

    5. Join new node to cluster

    ?

    Or I must map as ReadWrite ? Becaus as ReadWrite I see in Disk Management Disk1 as "Online".

    But in this case if I reboot 3rd node BEFORE add it to cluster, Windows don't start because it try to map volume that are used by other two node

    Thursday, August 04, 2011 9:55 AM