<div>
You are on the right track. Put host NICs into a switch independent team. Configure the switch ports for trunking, and use VLAN tagging to separate out the traffic. It works very well, and is exactly what I do. <br />
<br />
I see a switch port count problem, as you can't connect all of your host NICs and the EqualLogic to the same switch. The switch is also a single point of failure. EqualLogic recommends two switches. <br />
<br />
I have essentially the same setup, though I have two switches and I use only four NICs on each host. Because my hosts have fewer NICs, I run iSCSI through the NIC team, and each host has two vNICs attached to the iSCSI VLAN. In your case, I would use two to four NICs in a team for the host and guests, and two to four NICs dedicated to the host iSCSI.
</div>


<div>
Here's a tip: you don't need to create separate live migration or cluster heartbeat networks. Hyper-V can use the management and iSCSI networks for heartbeat, and the management network for live migration. Any live migration will be limited to a single NIC at a time due to the nature of how TCP interacts with switch independent teams.
</div>


<div>
With your setup we would do the following:<br />
Team 0: Port 0 on two Gigabit NICs: Production/Management (2-ports)<br />
Team 1: Port 1 two Gigabit NICs: Dedicated vSwitch (2-ports)<br />
Port 2 on each NIC: iSCSI<br />
Port 3 on each NIC: Live Migration 1 &amp;&nbsp;2<br />
10GbE Port: Live Migration 0<br />
<br />
Having the 10GbE for Live Migration makes things go quite quickly. We would have a minimum of two x540-T2 NICs in each node for a total of four 10GbE ports per node plus two 10GbE switches for redundancy. That gives us four 10GbE Live Migration streams.<br />
<br />
In your setting you get one 10GbE stream and two Gigabit streams.<br />
<br />
Edit: We don't do iSCSI so I missed that originally. Two 10GbE NICs and two 10GbE switches would be the route to go for storage.<br />
<br />
NOTE: Cluster does not require any other dedicated networks.
</div>


<div>
Hi kevinhsieh / Philip,<br />
<br />
Apologies for the late response we had a surprise audit so its been a little crazy. Thank you for your suggestions I just need a little time today to go through each one so please bear with me
</div>


<div>
Hi kevinhsieh,<br />
<br />
Sorry for the delay I have included a basic map of the network to help. Before I start I do know none of the switch config is ideal but a combination of what I have been left with and funds is forcing me to look at redundancy down the line. Our SANs are on a separate storage network which consists of 2 switches (will be merged into the rest of the network at a later date hence the separate storage VLAN). Note cluster 2 is unused at the moment and once the whole network is moved to it we will reconfigure cluster 1 as another hyper-v cluster and look at doing failover between the two. To get it straight in my head my interpretation of your design is I should configure all 1GB NICs on each of the 3 cluster nodes as Hyper-V port switch independent teams with the 10GB NIC connecting each node to the SAN. Then on the switch I should configure each port as its own trunk tagged with the Management, Migration, Heartbeat &amp;&nbsp;Servers VLANs with a 10GB trunk carrying all VLANs back to the core switch. Then in Hyper-V I should enable management to share the adapter (for team of 1GB NICs) and Tag the servers VLAN on each VM's VNIC. where I am struggling a bit is how will the cluster see the heartbeat and migration VLANs and where will I go to configure those?<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/03_w11/1085842/C--Users-mgrundy-Downloads-NewVLANsT.png" target="_blank" class="file-inline" title="Network Map (30 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>C--Users-mgrundy-Downloads-NewVLANsT.png</a>
</div>


C--Users-mgrundy-Downloads-NewVLANsT.png

<div>
Sorry quick update forgot to remove the Mi &amp;&nbsp;H VLANs show between Storage SW 1 &amp;&nbsp;2. please ignore those
</div>


<div>
Hi Philip, I think I have a better understanding of your idea of having different teams for different VLANs but it does prove problematic if VLANs are added. still not sure where you go to point a cluster at &quot;this is a heartbeat NIC &amp;&nbsp;this is a migration NIC&quot; but I am sure that will present itself in the setup.
</div>


<div>
Live Migration paths can be defined via PoSh or in Failover Cluster Manager. They can be ordered according to preference.<br />
<br />
Teaming = No SPF (Single Point of Failure)<br />
<br />
That's the goal of a cluster. To reduce the possibility of downtime via redundancies.<br />
<br />
The vSwitch should be dedicated. Meaning not shared with the host OS.<br />
<br />
iSCSI paths should be dedicated ports. Either VLAN them or segment them off to be on their own. Two paths should be had with a minimum of two switches and two NICs.<br />
<br />
If the VMs require VLAN pathways that gets defined in the VM's properties. The vSwitch takes care of the rest. The switches need only be trunked for that VLAN at the port(s) the vSwitch is connected to.<br />
<br />
Our approach to clusters is KISS. We keep things as simple as possible. This helps big time if something goes awry and we need to troubleshoot a problem. The more complex the environment the more room there is for mistakes and/or problems IMNSHO.
</div>


<div>
Hi Philip, That does make a lot of sense. So in my case per node:<br />
1 x 10GB NIC -&gt; VSwitch1 -&gt; used to connect the SAN<br />
2 x 1GB NICs -&gt; Team1 -&gt; VSwitch2 -&gt; Used for Heartbeat<br />
2 x 1GB NICs -&gt; Team2 -&gt; VSwitch3 -&gt; Used for Migration<br />
4 x 1GB NICs -&gt; Team3 -&gt; VSwitch4 -&gt; Used for Management, Servers VLANs ect and shared with Host OS<br />
I gather for this configuration you would recommend creating trunks on the switch (Tagging all VLANs?) and selecting switch dependant teaming mode and Hyper-V port load balancing? (Maybe address hash balancing for heartbeat &amp;&nbsp;migration?)
</div>


<div>
<div class="content wysiwyg-content">
Hi all,<br />
I will try and made this as short as possible and to the point as I realise this question has a very broad scope. I am looking to move from a 3 node VMware 5.5 cluster to a 3 node Windows 2012 R2 cluster. We have recently reworked out networks VLAN structure in preparation for this and other expansion projects. The network is a standard star topology with VLANs as follows<br />
VLAN ID 1 – Management<br />
VLAN ID 2 –Heartbeat (for use by cluster)<br />
VLAN ID 3 – Migration (for use by cluster)<br />
VLAN ID 4 – Storage (for use by cluster)<br />
VLAN ID 5 – Servers<br />
Other VLAN ID’s for client machines<br />
VLAN ID 49 – Current VMWare servers<br />
Our new 3 cluster nodes have 8 x 1GB Ethernet NIC’s &amp;&nbsp;1 x 10GB Ethernet NIC’s per node. I have an HP 2920 24 port switch with 2 x 10GB modules in the back (for connection to the core switch). We also have 2 x Dell equallogic SANs for storage. After the move the current VMWare cluster will be turned into another 3 node Hyper-V cluster and I would like to be able to failover machines from one cluster to another. At the moment the SANs are on their own physical network but I would like to integrate them at a later date hence VLAN ID 4. I am coming unstuck at the network setup. My current thinking is to team the 8 x 1GB NICs from the server to the switch and trunk all the VLANs to the team. This will provide maximum redundancy although I don’t think I will be able to use switch independent teaming as I will be sending multiple VLANs through each port. I am also unsure how I will go about setting up the migration and heartbeat VLANs for the cluster. I have a decent basic knowledge of switching and Hyper-V but very new to clustering. Could anyone guide me down the right path for this kind of setup?<br />
If you need any more information please ask and as always thanks in advance
</div>
</div>


Hi all,
I will try and made this as short as possible and to the point as I realise this question has a very broad scope. I am looking to move from a 3 node VMware 5.5 cluster to a 3 node Windows 2012 R2 cluster. We have recently reworked out networks VLAN structure in preparation for this and other expansion projects. The network is a standard star topology with VLANs as follows
VLAN ID 1 – Management
VLAN ID 2 –Heartbeat (for use by cluster)
VLAN ID 3 – Migration (for use by cluster)
VLAN ID 4 – Storage (for use by cluster)
VLAN ID 5 – Servers
Other VLAN ID’s for client machines
VLAN ID 49 – Current VMWare servers
Our new 3 cluster nodes have 8 x 1GB Ethernet NIC’s & 1 x 10GB Ethernet NIC’s per node. I have an HP 2920 24 port switch with 2 x 10GB modules in the back (for connection to the core switch). We also have 2 x Dell equallogic SANs for storage. After the move the current VMWare cluster will be turned into another 3 node Hyper-V cluster and I would like to be able to failover machines from one cluster to another. At the moment the SANs are on their own physical network but I would like to integrate them at a later date hence VLAN ID 4. I am coming unstuck at the network setup. My current thinking is to team the 8 x 1GB NICs from the server to the switch and trunk all the VLANs to the team. This will provide maximum redundancy although I don’t think I will be able to use switch independent teaming as I will be sending multiple VLANs through each port. I am also unsure how I will go about setting up the migration and heartbeat VLANs for the cluster. I have a decent basic knowledge of switching and Hyper-V but very new to clustering. Could anyone guide me down the right path for this kind of setup?
If you need any more information please ask and as always thanks in advance

Hyper-v Cluster Network setup

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Since 1984, Dell has been delivering technology to fit your life.
Dell is in Enterprise, Home Office and Consumer sectors of the market, supplying a broad range of customizable desktops, laptops, notebooks, servers, storage, and network devices.