Good evening,  It's not quite that straightforward, since volumes can span more members  you would end up with more connections to that volume per member. The size of the volume in relation to the size of each member is important.  By default a volume will span up to 3 members unless the volume won't fix within those three members.  In which case additional members would have to be used.  So per volume you could have an asymmetric connection count.   I..e 15TB volumes would cover more members than 1TB volumes.  Also in a pool with more than three members, the default of 3 members still holds.  So again not all members will be used for every volume.  Which will result is more connections on some members.  But yes if you have 8 members in a pool the 1024 pool limit would restrict how many connections.  But an additional piece of info is that if you are using the HIT kit for Windows, Linux or MEM for ESX the number of connections per volumes goes way up.  Since each iscsi port on the host will directly connect to a member that has data for that volume.  This improves performance and lowers latency but quickly uses pool connections.  It's very common for ESX servers with 4x NICs to use HUNDREDS of connections per SERVER.     So connection management must consider all these issues.  If I were really concerned about connection count I would break up 16 members in two (or more groups)  with multiple pools.   Regards, 
I know you can have 4096 connections per Group so i'm assuming this is max, so if you had 16 member in group you should only get 256 iSCSi connections per member correct ? provided that you had them separated by 4 pools , so my other question is max number of members per pool is 8 so if you had 8 members in pool and the max iSCSi connection per pool is 1024 would it decrease this to 128 per member and if so if indeed you can have 4 Pools and put 4 members in each pool equal 16 members would this decrease the iSCSi connections to 256 iSCSi per Member.
iSCSi Conntions question | Equallogic