locked
Windows Server 2012 R2 Failover Cluster - Network(Production + Management) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    The our exist setup have one cluster for two Nodes, each node have 4 network interface make two NIC as teaming finally we have for each nodes Two network teaming name [ Management & Production]

    Cluster network:

    Assigned  "Management" 10.10.8.0/21 as cluster network only.

    VLAN setting for Teaming:

    "Management" assigned to VLAN ID:10

    "Production"     assinged to VLAN ID: default   ( have multi Vlan's like [20,21,30,31,110,120,40,26,27,24])

    All our VM's machines connect to "Production" network  in this case if "Production" come down interface that mean all VM's on one node will be stay in the same node without any task of fail-over clustering which mean they doesn't have any connectivity network and it will work as local VM's in one node.

    Now my request how can I add the "production" network to be second NIC in cluster network and the same time all VM's which work with different VLAN's likes [20,21,30,31,.......]?

    Please if need any more information ?

    Thank you.

    Hasanain Ghanem

    Monday, September 21, 2015 3:26 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The our exist system have one cluster for two Nodes, each node have 4 network interface make two NIC as teaming finally we have for each nodes Two network teaming name [ Management & Production]

    Cluster network:

    Assigned  "Management" 10.10.8.0/21 as cluster network only.

    Teaming VLAN setting  :

    "Management" assigned to VLAN ID:10

    "Production"     assigned to VLAN ID: default   ( have multi Vlan's like [20,21,30,31,110,120,40,26,27,24])

    All our VM's machines connect to "Production" network  in this case if "Production"  interface come down  that mean all VM's  will be stay in the same node without any task of fail-over clustering which mean they doesn't have any connectivity network traffic and it will work as local VM's in one node.

    Now my request how can I add the "production" network to be second NIC in cluster network and the same time all VM's which connect to " Production" can work with different VLAN's likes [20,21,30,31,.......] in the our network?

    Please if need any more information ?

    Thank you.

    Hasanain Ghanem

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ali, 

    when you are working with Hyper-V it is more efficiant to work with converged network (software definded network). 

    Which means, you build virtual NICs on top of you Teams. 

    So that means you can use 2 NICs for you VMs and Tag all VLANs for the VMs on that Team. On the second team you can build virtual NICs for Hyper-V Management, Cluster Heartbeat and Livemigration. For the second Team you need to Tag the VLANs that you are using for Management, Cluster and Livemigration to that Team. 

    I would suggest to read some of these blogs to get a better understanding. 

    Network Recommendations for a Hyper-V Cluster in Windows Server 2012 

    Building A Converged Fabric with Windows Server 2012 PowerShell

    Configuring the Virtual Network using Converged Networks

    create-a-converged-network-fabric-in-vmm-2012-r2 <- only if you have VMM

    How to pass DHCP / PXE through to a virtual machine

    Differences in Cluster Traffic with different workloads
    Why you should have a network for cluster heartbeat only!

    How to configure cluster traffic priority on a windows server

    That Network configuration could help you understanding how it works. It is not exactly yours but matches in most parts. 

    Hyper-V|W2k12R2|4x1GB|2x10GB|2xFC

    Edit: Network isn't that common when it comes to Failover Clustering with Hyper-v and Scale out Fileserver or other services running on top of the Failover Cluster Feature

    I hope that helps. 

    Kind regards, Flo


    Monday, September 21, 2015 4:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hasanian,

    how can I add the "production" network to be second NIC in cluster

    You have two NIC "production" (teamed) and "Management"(teamed). You want another NIC to be added into cluster? In this case, you need to have additional NIC installed on the server.

    and the same time all VM's which connect to " Production" can work with different VLAN's likes

    Are you using hyper-v service to manage VM's on it? Or yet to build? If yes, you need to create virtual switch (attach to production NIC) and assign all the VM's to it. In order for VM's in different vlan to work on the same hyper-v cluster,  you must configure your switch port / router so that all required VLANs' can communicate each other. Then create VM's and assign the required IP, configure VLAN tagging in VM's settings.

    -Umesh.S.K


    • Edited by Umesh S K Monday, September 21, 2015 4:23 PM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Florian,

    I appreciate that, i will read these blogs and we  will see if we can resolve it then i will update you. 

    Best Regards,

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh,

    first thank you.

    Server1 have 4 NIC - create Teaming 2 NIC named: "Production"  and 2 NIC named:"Management"

    Now Server1 have two network teaming "production" & " Management"


    - also create Virtual Switch " vProduction" and "vManagement".

    * vProduction keep it without IP address static # because  i assigned all VM's with different Vlans to connect with "Production".

    * vManagement assigned with IP static  10.10.8.1.

    when we do Validation Configure Cluster add only 10.10.8.0 and assigned cluster network 10.10.8.50.

    Now if i do test Fail over cluster and switch off for only "Management" the VM's client move from Server1 to Server2 it work fine.

    but, if i switch off "Production" the All VM's in the Server1 will disconnect with our network and i can not reach them so that i need to do some things with "Production" to be assigned same " Management" in cluster network and the same time can VM's machine connect with " Production" to work in the our network.

    Windows server 2012 R2 Datacenter hyper-v both nodes.

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "when you are working with Hyper-V it is more efficiant to work with converged network (software definded network). 

    Which means, you build virtual NICs on top of you Teams. "

    Depends on your hardware solution.  If using Cisco's UCS environment, it is much easier and quicker to define fabric failover.  Define it once in the fabric, and every machine coming on board automatically has built-in NIC failover.  Since we now default to 20 Gbps NICs, it is very, very rare that anyone needs more than that as throughput that would require teaming.  If so, we also support 40 Gbps NICs.

    . : | : . : | : . tim

    • Proposed as answer by Alex Lv Tuesday, September 29, 2015 6:18 AM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 10:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hasanian,

     vProduction keep it without IP address static

    Can you assign static IP to this vProduction NIC and see if it works? Also, is production and management network are on same subnet? If yes, cluster will ignore one of the NIC and this could cause VM's not to failover when you remove vProduction since it is not recognized in cluster.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Tuesday, September 22, 2015 8:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Actually we have setup network configuration  like this: "vManagement"  use only  for management servers cluster network.

    and "vProduction" use only for production servers. no cluster network.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster network same vManagement and  assign VM's production servers to allow multi different Vlans via vProduction?

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Wednesday, September 23, 2015 10:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Actually we have setup network configuration  like this: "vManagement"  use only  for management servers cluster network.

    and "vProduction" use only for production servers. no cluster network.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster network same vManagement and  assign VM's production servers to allow multi different Vlans via vProduction?

    Thank you.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster networksame vManagement

    You mean,  you want to have both vProduction and vManagement to have IP on the same subnet? If yes, your cluster will ignore one of the interface as it is not supported to have two or more interfaces on same subnet.

    -Umesh.S.K

    • Proposed as answer by Alex Lv Tuesday, September 29, 2015 6:18 AM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Friday, September 25, 2015 1:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh.S.K

    I mean I want to have both vProduction and vManagement to have IP on different subnet.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Wednesday, September 30, 2015 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes, can have both in different subnet. However, ensure your switch / router are properly configured in your network for communication between different subnets.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Thursday, October 1, 2015 10:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Fine, but I have vProduction  interface this will route more than different VLAN's.

    my request  I need to configure vProduction like this:

    - I configured virtual switch in the hypuer-v manager for vProduction IP static address: 10.10.2.50.

    I have 25 virtual machine in the Hyper-v manager they have static IP address with different VLAN's.

    example:

    VM1 Static IP address:192.168.1.40

    VM2 Static IP address:192.168.50.66

    VM3 Static IP address:10.25.25.100

    VM4 Static IP address:10.100.10.50

    VM5, VM6 VM7,..... so on,,,

    all VM's was assigned of network setting in the hyper-v manager to vProdcution interface, which mean any virtual machine work as production server they have to choose only "vProdcution" in their network setting.

    my question is it can "vProduction" have static IP address and same time can route other IP address with different Vlan's?????

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Thursday, October 1, 2015 11:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I miss my last reply before two days. -_-!?

    any way.

    Thank you Umesh.

    yes it is fine if i have different subnet but however I need to configure vproduction with this setup.

    vproduction have ip static :10.10.88.1

    and i have 80 virtual machines and these VM's have different subnet like

    1- VM ip static 192.168.11.11

    2- VM ip static 10.12.13.14

    3- VM ip static 20.20.10.2

    4- VM ip static 10.20.20.1

    5- VM, ....., so on

    all these 80 virtual machines have network setting in hyper-v manager they select "vproduction" interface

    so that i ask, it could be if vproduction have ip static :10.10.88.1 and same time can route others different sbunet for 80 virtual machines????

    Thank you

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 7:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ali,

    Since all the VM's vNIC will be assigned to vProduction, it should work.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 9:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh S K,

    it should be work if if if vProduction assigned to dynamic not static IP address.

     but i need to assign vProduction with IP static for culster network and work with different vlan's VM.

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 1:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    there are no respond to this case and also Microsoft site they didn't help us any more just give me some links related to our scenario but still we didn't solve or configure in correct way.

    thank you to all of you and good luck

    closed this post please.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, October 19, 2015 6:11 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    The our exist system have one cluster for two Nodes, each node have 4 network interface make two NIC as teaming finally we have for each nodes Two network teaming name [ Management & Production]

    Cluster network:

    Assigned  "Management" 10.10.8.0/21 as cluster network only.

    Teaming VLAN setting  :

    "Management" assigned to VLAN ID:10

    "Production"     assigned to VLAN ID: default   ( have multi Vlan's like [20,21,30,31,110,120,40,26,27,24])

    All our VM's machines connect to "Production" network  in this case if "Production"  interface come down  that mean all VM's  will be stay in the same node without any task of fail-over clustering which mean they doesn't have any connectivity network traffic and it will work as local VM's in one node.

    Now my request how can I add the "production" network to be second NIC in cluster network and the same time all VM's which connect to " Production" can work with different VLAN's likes [20,21,30,31,.......] in the our network?

    Please if need any more information ?

    Thank you.

    Hasanain Ghanem

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ali, 

    when you are working with Hyper-V it is more efficiant to work with converged network (software definded network). 

    Which means, you build virtual NICs on top of you Teams. 

    So that means you can use 2 NICs for you VMs and Tag all VLANs for the VMs on that Team. On the second team you can build virtual NICs for Hyper-V Management, Cluster Heartbeat and Livemigration. For the second Team you need to Tag the VLANs that you are using for Management, Cluster and Livemigration to that Team. 

    I would suggest to read some of these blogs to get a better understanding. 

    Network Recommendations for a Hyper-V Cluster in Windows Server 2012 

    Building A Converged Fabric with Windows Server 2012 PowerShell

    Configuring the Virtual Network using Converged Networks

    create-a-converged-network-fabric-in-vmm-2012-r2 <- only if you have VMM

    How to pass DHCP / PXE through to a virtual machine

    Differences in Cluster Traffic with different workloads
    Why you should have a network for cluster heartbeat only!

    How to configure cluster traffic priority on a windows server

    That Network configuration could help you understanding how it works. It is not exactly yours but matches in most parts. 

    Hyper-V|W2k12R2|4x1GB|2x10GB|2xFC

    Edit: Network isn't that common when it comes to Failover Clustering with Hyper-v and Scale out Fileserver or other services running on top of the Failover Cluster Feature

    I hope that helps. 

    Kind regards, Flo


    Monday, September 21, 2015 4:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hasanian,

    how can I add the "production" network to be second NIC in cluster

    You have two NIC "production" (teamed) and "Management"(teamed). You want another NIC to be added into cluster? In this case, you need to have additional NIC installed on the server.

    and the same time all VM's which connect to " Production" can work with different VLAN's likes

    Are you using hyper-v service to manage VM's on it? Or yet to build? If yes, you need to create virtual switch (attach to production NIC) and assign all the VM's to it. In order for VM's in different vlan to work on the same hyper-v cluster,  you must configure your switch port / router so that all required VLANs' can communicate each other. Then create VM's and assign the required IP, configure VLAN tagging in VM's settings.

    -Umesh.S.K


    • Edited by Umesh S K Monday, September 21, 2015 4:23 PM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Florian,

    I appreciate that, i will read these blogs and we  will see if we can resolve it then i will update you. 

    Best Regards,

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh,

    first thank you.

    Server1 have 4 NIC - create Teaming 2 NIC named: "Production"  and 2 NIC named:"Management"

    Now Server1 have two network teaming "production" & " Management"


    - also create Virtual Switch " vProduction" and "vManagement".

    * vProduction keep it without IP address static # because  i assigned all VM's with different Vlans to connect with "Production".

    * vManagement assigned with IP static  10.10.8.1.

    when we do Validation Configure Cluster add only 10.10.8.0 and assigned cluster network 10.10.8.50.

    Now if i do test Fail over cluster and switch off for only "Management" the VM's client move from Server1 to Server2 it work fine.

    but, if i switch off "Production" the All VM's in the Server1 will disconnect with our network and i can not reach them so that i need to do some things with "Production" to be assigned same " Management" in cluster network and the same time can VM's machine connect with " Production" to work in the our network.

    Windows server 2012 R2 Datacenter hyper-v both nodes.

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 4:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    "when you are working with Hyper-V it is more efficiant to work with converged network (software definded network). 

    Which means, you build virtual NICs on top of you Teams. "

    Depends on your hardware solution.  If using Cisco's UCS environment, it is much easier and quicker to define fabric failover.  Define it once in the fabric, and every machine coming on board automatically has built-in NIC failover.  Since we now default to 20 Gbps NICs, it is very, very rare that anyone needs more than that as throughput that would require teaming.  If so, we also support 40 Gbps NICs.

    . : | : . : | : . tim

    • Proposed as answer by Alex Lv Tuesday, September 29, 2015 6:18 AM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, September 21, 2015 10:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Hasanian,

     vProduction keep it without IP address static

    Can you assign static IP to this vProduction NIC and see if it works? Also, is production and management network are on same subnet? If yes, cluster will ignore one of the NIC and this could cause VM's not to failover when you remove vProduction since it is not recognized in cluster.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Tuesday, September 22, 2015 8:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Actually we have setup network configuration  like this: "vManagement"  use only  for management servers cluster network.

    and "vProduction" use only for production servers. no cluster network.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster network same vManagement and  assign VM's production servers to allow multi different Vlans via vProduction?

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Wednesday, September 23, 2015 10:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Actually we have setup network configuration  like this: "vManagement"  use only  for management servers cluster network.

    and "vProduction" use only for production servers. no cluster network.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster network same vManagement and  assign VM's production servers to allow multi different Vlans via vProduction?

    Thank you.

    I am asking now is it possible  to create "vProduction" to assign IP static for cluster networksame vManagement

    You mean,  you want to have both vProduction and vManagement to have IP on the same subnet? If yes, your cluster will ignore one of the interface as it is not supported to have two or more interfaces on same subnet.

    -Umesh.S.K

    • Proposed as answer by Alex Lv Tuesday, September 29, 2015 6:18 AM
    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Friday, September 25, 2015 1:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh.S.K

    I mean I want to have both vProduction and vManagement to have IP on different subnet.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Wednesday, September 30, 2015 4:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes, can have both in different subnet. However, ensure your switch / router are properly configured in your network for communication between different subnets.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Thursday, October 1, 2015 10:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Fine, but I have vProduction  interface this will route more than different VLAN's.

    my request  I need to configure vProduction like this:

    - I configured virtual switch in the hypuer-v manager for vProduction IP static address: 10.10.2.50.

    I have 25 virtual machine in the Hyper-v manager they have static IP address with different VLAN's.

    example:

    VM1 Static IP address:192.168.1.40

    VM2 Static IP address:192.168.50.66

    VM3 Static IP address:10.25.25.100

    VM4 Static IP address:10.100.10.50

    VM5, VM6 VM7,..... so on,,,

    all VM's was assigned of network setting in the hyper-v manager to vProdcution interface, which mean any virtual machine work as production server they have to choose only "vProdcution" in their network setting.

    my question is it can "vProduction" have static IP address and same time can route other IP address with different Vlan's?????

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Thursday, October 1, 2015 11:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    I miss my last reply before two days. -_-!?

    any way.

    Thank you Umesh.

    yes it is fine if i have different subnet but however I need to configure vproduction with this setup.

    vproduction have ip static :10.10.88.1

    and i have 80 virtual machines and these VM's have different subnet like

    1- VM ip static 192.168.11.11

    2- VM ip static 10.12.13.14

    3- VM ip static 20.20.10.2

    4- VM ip static 10.20.20.1

    5- VM, ....., so on

    all these 80 virtual machines have network setting in hyper-v manager they select "vproduction" interface

    so that i ask, it could be if vproduction have ip static :10.10.88.1 and same time can route others different sbunet for 80 virtual machines????

    Thank you

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 7:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ali,

    Since all the VM's vNIC will be assigned to vProduction, it should work.

    -Umesh.S.K

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 9:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh S K,

    it should be work if if if vProduction assigned to dynamic not static IP address.

     but i need to assign vProduction with IP static for culster network and work with different vlan's VM.

    Thank you.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Sunday, October 4, 2015 1:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    Just I need to setup vProduction with IP address static for cluster network + and  other virtual machines which have different vlan's  they can access via vProduction to network internal & external.

    Thank you.

    Thursday, October 8, 2015 4:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    there are no respond to this case and also Microsoft site they didn't help us any more just give me some links related to our scenario but still we didn't solve or configure in correct way.

    thank you to all of you and good luck

    closed this post please.

    • Marked as answer by ALI HASANAIN Monday, October 19, 2015 6:44 AM
    Monday, October 19, 2015 6:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Umesh S K,

    it should be work if if if vProduction assigned to dynamic not static IP address.

     but i need to assign vProduction with IP static for culster network and work with different vlan's VM.

    Thank you.

    Hi Ali,

    You can assign static IP to vProduction switch and work with VM's which are on different VLAN. In multi homed servers, you need to have only one gateway IP mentioned, and all other adapters should not have gateway. Ensure you have proper routing added in the hyper-v host. Also, ensure your VM are tagged to correct VLAN.

    -Umesh.S.K

    Monday, October 19, 2015 11:06 AM