Assigning NIC in Hyper-V R2

According to Netapp we should assign a NIC for CLUSTER on a dedicated network and another NIC for LIVE MIGRATION on a dedicated Network.  In other hands, most of the time the configuration Ithat seems to be recommanded  does have only one NIC for both (CLUSTER NIC is the same as LIVE MIGRATION)

What is your advice ?  I can have as many NIC as I need (10 or 12) on the servers.  But I found this information only on the netapp web site.  thanks



BP #1: Network Configuration in Hyper-V Environments

There are two important best practices to mention when it comes to network configuration:

    * Be sure to provide the right number of physical network adapters on Hyper-V servers.
    * Take advantage of the new network features that Hyper-V R2 supports if at all possible.

Physical network adapters. Failure to configure enough network connections can make it appear as though you have a storage problem, particularly when using iSCSI. Smaller environments require a minimum of two or three network adapters, while larger environments require at least four or five. You may require far more. Here’s why:

    * Management. Microsoft recommends a dedicated network adapter for Hyper-V server management.
    * Virtual machines. Virtual network configurations of the external type require a minimum of one network adapter.
    * IP storage. Microsoft recommends that IP storage communication have a dedicated network, so one adapter is required and two or more are necessary to support multipathing.
    * Windows failover cluster. Windows® failover cluster requires a private network.
    * Live migration. This new Hyper-V R2 feature supports the migration of running virtual machines between Hyper-V servers. Microsoft recommends configuring a dedicated physical network adapter for live migration traffic.
    * Cluster shared volumes. Microsoft recommends a dedicated network to support the communications traffic created by this new Hyper-V R2 feature.