To keep the connection count from getting out of hand, the default settings of MEM produce this result.  If a path fails MEM will initiate new ones on a different port.  MEM will choose different NICs for different volumes.  More, smaller volumes are preferred over a few very large volumes.   You can override these settings.  You would need to up the volume sessions and the member sessions.  The MEM guide has info on how to change these values.   Just make sure you are not nearing you max connections on the group/pool.   Especially if you plan on adding more volumes and more arrays in the future.   Regards, 
Hi, I've just installed the MPIO drivers for an EQL PS6500E onto a VMWare ESXi4.1 cluster and used the EQL script to set up the iSCSI links.  PS6500E has 4 uplinks to a Powerconnect switch stack and each VM host has 4 gig links to the switches. Added some datastores from the EQL box and noticed this (screengrab from vSphere client) [IMAGE] What worries me is that each iSCSI volume has only 2 paths to it instead of 4 as I might have expected. I'm concerned in case a switch failed (we have 2, stacked, with redundant paths). Should I be worried enough to put in a support call or, if a switch fails, will the MPIO driver "do magic" to ensure paths are replaced. ** Before anyone asks - the 4 target IPs are 10.223.10.11,12,13,14 and other volumes do use the other target IPs so I believe all paths are operational.  TIA  Tim
ESX and MPIO to PS6500E