Virtualization: Network card settings for Hyper V Cluster
The table below illustrate the network settings for each of the five NICs on the cluster nodes (Yes, No, Optional). This shows the configuration based on Microsoft recommended Best Practices.
Setting |
Management |
Heartbeat |
Live Migration |
Production |
Storage |
Client for Microsoft Networks |
Y |
N |
Y |
N |
N |
File and Printer Sharing |
Y |
N |
Y |
N |
N |
Microsoft Virtual Network Switch Protocol |
N |
N |
N |
Y |
N |
Internet Protocol Version 6 |
O |
O |
O |
N |
O |
Internet Protocol Version 4 |
Y |
Y |
Y |
N |
Y |
Link-Layer Topology Discovery Mapper I/O Driver |
Y |
N |
Y |
N |
N |
Link-Layer Topology Discovery Responder |
Y |
N |
Y |
N |
N |
Comments
Anonymous
January 01, 2003
Hi, Considering that CSV traffic flows through "Heartbeat" network, are there any settings to be configured for it? -I tried configuring "Heartbeat" network as above, Errors started logging in cluster event viewer that "STATUS_BAD_NETWORK_PATH to CSV1" EVENT ID 5120 , and after enabling back F&P Sharing and Client for MS N/w's it stopped reporting any errors or If we have a dedicated NIC for CSV, How about the settings for CSV NIC? ThanksAnonymous
March 18, 2011
I agree with ashok, because we had the same problem. You should only disable SMB (File and Printer Sharing and Client for MS Networks) on the iSCSI network, and the Virtual network (Production). See last sentence below: TechNet: In the properties for all adapters that carry cluster communication, make sure that Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks are enabled to support Server Message Block (SMB), which is required for CSV. Only one network will be the preferred network for CSV communication, but enabling these settings on multiple networks helps the cluster respond to failures.Anonymous
March 11, 2013
IPv6 should be enabled: technet.microsoft.com/.../cc987595.aspx