Correct MPIO from host to failover IP

[enealDC]

the max number of paths on your initiator(s) will be determined by the maximum number of paths you have available on the target.
if you've dedicated two 10GBE nics for iSCSI - then I'd break the rr bond and have a virtual for each NIC. So you'll need a total of 6 IPs across two subnets, two of the IPs being the VIPs.

[techtou]

Hi!
Thanks for the advice.
I managed to get two VIPs on the SAN and two distinct connections to it from the host with MPIO successfully.
Now, I have two 1Gb NICs on the host leftover not being used and have tried to team adapters such that I get two teams on the host to connect to two VIPs with MPIO..
however that config is real buggy and host server has issues running this.

Any idea if teaming is not recommended fro host-side connectivity to SANs via iSCSI or am I not configuring this right?

I would like to be able to use 4 NIcs from the host to two VIPs on SANs.

Thanks for all your help,

D

[enealDC]

Teaming/Bonding really only works to provide redundancy UNLESS you have a very large number of client devices OR unless you IP each host so that the XOR operation results in a different patch being chosen.
I would suggest that you go ahead and use all 4 NICS as 4 distinct paths. In theory, you will then have an aggregate of 400MB of bandwidth (so long as your backend storage and replication can sustain it). In this scenario, if you have at least two nodes with two nics each, you can have two dedicated paths per host.
If you don't want to go this route, then the alternative method is to just setup each NIC pair as an active/passive bond.