Hi, I'm Joe with Dell EqualLogic.  I'm guessing that you have the two Storage1&2 NIC's setup with MPIO on the Host servers, and the MPIO policy is set?  You also didn't indicate if you are using MS MPIO or the EqualLogic HIT MPIO.  Check to see if you have four connections to the volume on the SAN (select the volume/connections tab in the EqualLogic Management GUI).  You should see all 4 connections to the volume (2 from each server).  This could also be a jumbo frame issue, a quick test for this is to disable Jumbo on the iSCSI NIC's and switch ports to see if this is causing the problem.

Let me know what you find.

Regards,

Joe

I've disabled Jumbo as you said, but nothing changed.

I used remote setup wizard to configure MPIO settings for both nodes.

I included:

subnet 10.0.1.0/255.255.255.0,

Default Load Balancing : Policy Least Queue Depht

Max sessiones per volume slice : 2

max Sessions per entire volume: 6

Minimum adapter speed: 1Gbps

use MPIO for snapshts: actve

Use IPv4: Active

How can i know if i using MS MPIO or Equalogic HIT MPIO?

Raffaele

To tell if you are using EqualLogic MPIO DSM, you would see a Tab in then iSCSI Initiator called “Dell EqualLogic MPIO”.  From your description, it sounds like you installed the EqualLogic HIT and enable MPIO (the remote setup wizard that you used to exclude the subnets from MPIO is part of the EqualLogic MPIO).

Did you see the connections from Storage 1&2 (both hosts) on the volume in the EqualLogic Group Manager GUI?

If you see all the connection on the SAN in the Group Admin, the message you see in the validation test would then be a normal message.

This is a warning message, not a failure message so the validation has passed. Multiple SAN NICs so are required so we can do MPIO and improve the iSCSI performance of the cluster.

Regards,

Joe