vpnsol123
asked on
Hyper V Cluster Failover NIC Question
I am setting up a lab environment following the basis on this article:
http://www.msserverpro.com/implementing-windows-server-2012-hyper-v-failover-clustering/
My question pertains to the NIC setup.
My Storage Arrays have only SFP+10 GB ports. My host machines have 4 One GB cards. Ideally I'd like 4 Ten GB SFP+ ports on the host machines - and I can obtain new NICs for them but would the heartbeat nic really need a 10GB connection? Obviously the storage NIC on the host would need 10GB SFP+ to communicate to the storage arrays - where the VMs will reside. Is there a way I can utilize some of the 1GB NIC cards for some of the 4 NICs (vEthernet, Production, Storage, Heartbeat) and 10GB for others and not have performance degredation? Which need to be on the 10GB connection to take advantage of performance?
http://www.msserverpro.com/implementing-windows-server-2012-hyper-v-failover-clustering/
My question pertains to the NIC setup.
My Storage Arrays have only SFP+10 GB ports. My host machines have 4 One GB cards. Ideally I'd like 4 Ten GB SFP+ ports on the host machines - and I can obtain new NICs for them but would the heartbeat nic really need a 10GB connection? Obviously the storage NIC on the host would need 10GB SFP+ to communicate to the storage arrays - where the VMs will reside. Is there a way I can utilize some of the 1GB NIC cards for some of the 4 NICs (vEthernet, Production, Storage, Heartbeat) and 10GB for others and not have performance degredation? Which need to be on the 10GB connection to take advantage of performance?
A 10 Mb NIC is sufficient for the heartbeat, no data goes over thet crossover cable.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No heartbeat network is required (John Marlin).
You can use Switch Embedded Teaming to set up your network paths and use two dedicate ports, one per physical network adapter, for your iSCSI traffic if that's how things are set up.
Two switches and MPIO should be considered as a best practice to eliminate any single point of failure in the setup.
You can use Switch Embedded Teaming to set up your network paths and use two dedicate ports, one per physical network adapter, for your iSCSI traffic if that's how things are set up.
Two switches and MPIO should be considered as a best practice to eliminate any single point of failure in the setup.