Default networking for hyper-v cluster

David,
I do not have screenshots at this time, but you're correct on your assumptions about the 10GigE, and the 1GigE adapters are usually disconnected after the setup has been completed:

PS C:Usersf3rm1n> Get-NetLbfoTeam
Name : NetAdapterTeamMembers : {Ethernet 2, Ethernet 3}TeamNics : NetAdapterTeamTeamingMode : SwitchIndependentLoadBalancingAlgorithm : Dynamic

PS C:Usersf3rm1n> Get-NetLbfoTeamMember

Name : Ethernet 2InterfaceDescription : Intel(R) 82599 10 Gigabit Dual Port Network ConnectionTeam : NetAdapterTeamAdministrativeMode : ActiveOperationalStatus : ActiveTransmitLinkSpeed(Gbps) : 10ReceiveLinkSpeed(Gbps) : 10FailureReason : NoFailure

Name : Ethernet 3InterfaceDescription : Intel(R) 82599 10 Gigabit Dual Port Network Connection #2Team : NetAdapterTeamAdministrativeMode : ActiveOperationalStatus : ActiveTransmitLinkSpeed(Gbps) : 10ReceiveLinkSpeed(Gbps) : 10FailureReason : NoFailure

Thanks for the reply. I'm just really trying to picture how it hangs together in my head.

we would normally have a VLAN for management, and also a VLAN for the virtual servers etc. So I assume I would use the "converged networking" design similar to this http://charbelnemnom.com/2014/05/create-a-converged-network-fabric-in-vmm-2012-r2/ . Do we separate out the cluster heatbeats too?

Does the CVM go on its own VLAN too, as in do i need to separate the storage traffic over a VLAN as well?

Thanks, I see now what you mean; I personally have seen only one deployment using more than a couple logical networks, but if planned correctly, it should work fine.
Regarding the CVM traffic (I/O) goes over the Internal switch unless the local CVM has a problem, in that case traffic is re-routed over to another CVM, so host Management and CVM eth0 would fall under the same VLAN

CVMs adn Hosts are usually always recommened on the same VLAN for communication purposes. Once imaged, you use the VMNetworkAdapterVlan commands to set the proper VLAN for them as you need and then set can set LACP team bond and remove and disable your 1Gbs, ect if not being used from a Hyper-V standpoint. The scripts will do the 1Gb part for you but if adding to existing cluster, just easier to do it manually using the powershell commands..