[ILUG] FW: Further SAN issues with RHEL4 & Equalogic SAN

[Brian O'Mahony]

Well I do have a ticket open with Dell on why CHAPs (with an Equalogic SAN) just doesn't seem to work with rhel4u6. No matter what I try, if chaps is enabled, it fails to authenticate, with the SAN throwing up "Initiator tried to bypass the security phase but we cannot."

I have currently just set the volume to allow connection from the specific IPs on the two interfaces on that box. Just boggling me why CHAP doesn't work.

If I get a chance next week im going to test it on SPARC solaris / HPUX / AIX / zLINUX and find out if its just a Linux issue.

The tech mentioned he was going to speak to equalogic for me. :)

B

-----Original Message-----
From: Conor Wynne [mailto:mariconor at gmail.com] 
Sent: 08 December 2009 15:37
To: Brian O'Mahony
Cc: conor_d_wynne at dell.com; Irish Linux Users Group
Subject: Re: [ILUG] FW: Further SAN issues with RHEL4 & Equalogic SAN

No worries mate,

I suspected the issue was related to a delay in initialising yer networking.
I'm happy to help you, and other luggers, with dell kit / iSCSI / FC SANs.

It's Xmas after all!

Brian O'Mahony wrote:
> Actually as a matter of interest, as it was my first time mucking with iSCSI SAN volumes on redhat, I decided to use the LVM gui (something I personally abhor but needed to show someone that the volume was visible etc). That's why I didn't think of changing the FS type.
>
> Thanks again
> B
>
> -----Original Message-----
> From: Brian O'Mahony
> Sent: 08 December 2009 13:45
> To: 'Conor Wynne'
> Cc: conor_d_wynne at dell.com; Irish Linux Users Group
> Subject: RE: [ILUG] FW: Further SAN issues with RHEL4 & Equalogic SAN
>
> Conor
>
> It was a stupid error on my part, sorry. I had the mount points set to default, and as such they were loading before the interfaces were fully up.
>
> Once I changed them to _netdev, I started getting login errors, but eventually they logged in as the interface came up. Everything was reosey after that.
>
> Thanks for the offer of opening a case, but I got it sorted now!
>
> :D
>
> Brian
>
> -----Original Message-----
> From: Conor Wynne [mailto:mariconor at gmail.com]
> Sent: 08 December 2009 13:17
> To: Brian O'Mahony
> Cc: conor_d_wynne at dell.com; Irish Linux Users Group
> Subject: Re: [ILUG] FW: Further SAN issues with RHEL4 & Equalogic SAN
>
> Hiya brian,
>
> I can help you sort this out - send me your service TAG and I'll log a case for you. if you could send me a "sosreport" that would be very useful.
> or keep it on list and I'll help you anyway. Whichever suits. My work address is in CC.
>
> Later
> Conor.
>
> Brian O'Mahony wrote:
>   
>> Im having further issues with the test box I have connected to the SAN.
>>
>> I have assigned 500Gb of space to my PE2850. I have the SAN on a 
>> separate network, and after installing the iSCSI initiator, I can see 
>> the device
>>
>> *********************************************************************
>> *
>> ********* SFNet iSCSI Driver Version ...4:0.1.11-6(03-Aug-2007)
>> *******************************************************************************
>> TARGET NAME             : iqn.2001-05.com.equallogic:0-8a0906-8d303fd04-a63000007cf4b151-dubsangrp01volcc
>> TARGET ALIAS            : DubSanGrp01VolCC
>> HOST ID                 : 7
>> BUS ID                  : 0
>> TARGET ID               : 0
>> TARGET ADDRESS          : 10.10.10.20:3260,1
>> SESSION STATUS          : ESTABLISHED AT Mon Dec  7 14:16:19 GMT 2009
>> SESSION ID              : ISID 00023d000001 TSIH bd
>>
>> I then put a volume group (called SAN) of the full 500Gb on the device, and created a 90Gb logical volume, which I was able to write with an ext3 FS and mounted it.
>>
>> When I rebooted the system hung on boot saying it could not find /dev/SAN/cc_san_lv01, I edited the fstab, and brought the system up. Sure enough /dev/SAN was missing. I created a second volume, cc_san_lv02, and once again on reboot the /dev/SAN is gone.
>>
>> Why is it getting dropped on reboot?
>>
>> B
>>
>>
>> The information in this email is confidential and may be legally privileged.
>> It is intended solely for the addressee. Access to this email by 
>> anyone else is unauthorized. If you are not the intended recipient, 
>> any disclosure, copying, distribution or any action taken or omitted 
>> to be taken in reliance on it, is prohibited and may be unlawful. If 
>> you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
>>   
>>     
>
>
>
>
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by 
> anyone else is unauthorized. If you are not the intended recipient, 
> any disclosure, copying, distribution or any action taken or omitted 
> to be taken in reliance on it, is prohibited and may be unlawful. If 
> you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
>
>   




The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.