So your connection limit is 1024 / per for a total of 4096 connections.  Your PR limit is 96 connections per volume.  So with 8 nodes you should have no issues.  2x NICs times 8x NODES = 16, times 2x members/pool = 32.     Obviously for the single member pools, that's just times 1x.   So the formula is NICs x NODES x MEMBERS the volume data is striped across.   That can be different from the members  per pool.   By default, the array will only use 3x members to stripe data over.  Unless forced to use more because of volume size.   To make life a lot easier, use CHAP for the ACL instead of IP or IQN names.   There is also a MS KB that needs to be installed to address a bug in the Cluster Validation program.  It's in the release notes I believe.  I'm about 99% sure it's KB978562  support.microsoft.com/.../978562  Regards,  -don 
Hi, I have a group that consists of 4 units, 6010, 6510, 6510, 6510e, all 10gig connections two per unit. The group is made up of three pools, SAS-Fast (6010), SAS 2-6510's and SATA 6510e. I want to build an 8 node Hyper V cluster, and each server has two iSCSI NIC's, so if I present a volume to the cluster it would have 8 nodes or 16 iSCSI IP's trying to mount it. What is the limit of nodes/connections I can apply to a volume or pool or group? Thanks,
Max # of connections per volume/pool/group