NIC teaming and Hyper-V switch recommendations in a cluster

HI,

We’ve recently purchased four HP Gen 8 servers with a total of ten NICS to be used in a Hyper-V 2012 R2 Cluster

These will be connecting to ISCSI storage so I’ll use two of the NICs for the ISCSI storage connection.

I’m then deciding between to options.

1. Create one NIC team, one Extensible switch and create VNics for Management, Live Migration and CSV\Cluster - QOS to manage all this traffic. Then connect my VMs to the same switch.

2. Create two NIC teams, four adapters in each.  Use one team just for Management, Live Migration and CSV\Cluster VNics - QOS to manage all this traffic. Then the other team will be dedicated just for my VMs.

Is there any benefit to isolating the VMs on their own switch?

Would having two teams allow more flexibility with the teaming configurations I could use, such as using Switch Independent\Hyper-V Port mode for the VM team? (I do need to read up on the teaming modes a little more)

Thanks,