Hi,
I'm running a similar configuration (HP/Serverengines UNAs) and ran
into similar problems. The only configuration I could get to work even
sometimes was using mainline kernel 3.0.0 and compiled iscsi userland,
whatever the latest version was ~3 months ago.
HP have told me that you're not supp
oh and IIRC the P4000 series (former LeftHand Networks boxes) have
'odd' behaviour with multipathing
On 11 October 2011 08:36, Seth Tunstall wrote:
> Hi,
>
> I'm running a similar configuration (HP/Serverengines UNAs) and ran
> into similar problems. The only configuration I could get to work eve
On 10/11/2011 05:05 AM, Mike Christie wrote:
On 10/07/2011 09:09 AM, Hannes Reinecke wrote:
We only need to run configure in open-isns if either the
configure script or Makefile.in has changed. Otherwise
it's perfectly okay just to call a plain 'make' here.
Signed-off-by: Hannes Reinecke
diff
Hi Mike/all,
I am working on a part of user space 1 of TODO list, which precisely says-
the functions that were run (FUNCTION)
the iSCSI packets that were sent/receieved (PDUS)
print out extended iscsi login error information (LOGIN_ERRS)
i) I have written log_debug to retrieve all functions nam
On 09/22/2011 12:02 AM, coec wrote:
> Hi all
>
> I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with
> iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades
> talking to a P4500 14.4TB Virt SAN (two clustered P4500 boxes).
>
> As the blade has two FlexHBA (iSCSI) in
On Wed, Oct 12, 2011 at 5:05 AM, Mike Christie wrote:
> On 09/22/2011 12:02 AM, coec wrote:
>> Hi all
>>
>> I'm using RHEL 6.1 (fully patched, 2.6.32-131.12.1.el6.x86_64 with
>> iscsi-initiator-utils-6.2.0.872-21.el6.x86_64) on HP BL460c G7 blades
>> talking to a P4500 14.4TB Virt SAN (two cluster
On 10/11/2011 08:24 PM, Colin Coe wrote:
>>
>> Do you actually have a LUN with that value 4194304?
>>
>> Maybe the LeftHand target needs some blacklist entry in the scsi mid
>> layer to scan for devices properly.
>>
>
> No, this LUN was the first one created. I don't know where the
> 4194304 came