We have only tested with 2 NICs but this would depend on the initiator side to add more NICs for the MPIO.
For the Auto Failover the Primary server will need to set the volumes in Source mode and the Secondary server set them in Destination mode and you cannot mix them if using the Auto Failover. Though you can use it in such a way to mix them just using the Volume replication function only.
Ok thanks and in the case of using different Volumes instead of different Luns wil that do the trick ?
(1 volume source/destination, 1 volume independant).
Ok and last thing about the auto-failover limitation in this case (because it's becoming a little bit complicated for my understanding ).
I dont understand why i cant attach my clustered volumes with the failover virtual IP and in same time attach independant volumes (non redundant) using the physical array IPs ?
The aim is to keep some storage space seperated from synchronous tasks but keeping autofailover on clustered volumes would be great. Don't you think that would be a valuable function ?
But you can use your clustered servers like VMware's HA or MS Cluster we have videos showing this from link below and many use the DSS V6 for this setup. If you are having issues connecting from your iSCSI initiators this link below might provide some help.