RE: Need help with multipath and iscsi in CentOS 5.4
Hi Kyle. For your configuration do you have a LUN in the storage group assigned to your server? If so, the LUN is presented to both SPs (service processors) but only owned by one. If your storage group for the server has been configured for the default mode the LUN is presented in PNR mode; therefore, only one SP owns it and can be used for the IO. In order to use the LUN thru the other SP the LUN needs to be trespassed to that SP. If the storage group for the server is configured for ALUA mode then you can read and write thru both SPs without a trespass command. If there are no LUNs assigned in a storage group for your server, then the LUN that is presented to the server is a LUNZ and you will not be able to access it. You indicate below that you are able to fdisk one of the SCSI devices but not all four. If you are configured in the manner you described you should be able to access it thru the two NICs that attached to the SP that owns the LUN. Regards, Wayne. EMC Corp -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:52 PM To: open-iscsi@googlegroups.com Subject: Re: Need help with multipath and iscsi in CentOS 5.4 Kyle Schmitt wrote: I'm cross-posting here from linux-iscsi-users since I've seen no linux-scsi-users would be for centos 4. Centos 5 uses a different initiator, but you are the right place finally :) traffic in the weeks since I posted this. Hi, I needed a little help or advice with my setup. I'm trying to configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box. Very short version: One server with two NICs for iSCSI sees storage on EMC. Storage shows up as four discs, but only one works. So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. When I setup multiple connections I have problems... I created two interfaces, and assigned each one to a NIC iscsiadm -m iface -I iface0 --op=new iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth2 iscsiadm -m iface -I iface1 --op=new iscsiadm -m iface -I iface1 --op=update -n iface.net_ifacename -v eth3 Each interface saw two paths to their storage, four total, so far so good. I logged all four of them them in with: iscsiadm -m node -T long ugly string here -l I could see I was connected to all four via iscsiadm-m session At this point, I thought I was set, I had four new devices /dev/sdb /dev/sdc /dev/sdd /dev/sde Ignoring multipath at this point for now, here's where the problem started. I have all four devices, but I can only communicate through one of them: /dev/sdc. As a quick test I tried to fdisk all four partitions, to see if I saw the same thing in each place, and only /dev/sdc works. What do you mean by works? Can you dd it, or fdisk it? Turning on multipath, I got a multipathed device consisting of sdb sdc sdd and sde, but sdb sdd and sde are failed with a message of checker msg is emc_clariion_checker: Logical Unit is unbound or LUNZ Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Could you send the /var/log/messages for when you run the login command so I can see the disk info? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RE: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
Is CHAP configured on the array? -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:54 PM To: open-iscsi@googlegroups.com Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011) avora wrote: I do not see ping/nop timeout message in the logs (probably that's why changing the noop timeouts did not work). Simply starting the session does not cause these errors. On starting the second session, I start a daemon that does SCSI commands like INQUIRY on all the paths. After that I see these messages, and the daemon gets stuck for a very long time waiting for SCSI commands to finish. At the backend I have EMC CLARiiON. # iscsiadm -m node -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091100683.a2 Portal: 192.168.10.1:3260,1 Iface Name: iface0 Target: iqn.1992-04.com.emc:cx.ckm00091100683.b2 Portal: 192.168.12.1:3260,3 Iface Name: iface1 Does the same path always fail? If you log into one can you use it, then if you logout and log into the other does that other one then work? Is there any info the clarrion logs? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RE: multipath iSCSI installs
Hi Malahal. There is a BZ for SLES. https://bugzilla.novell.com/show_bug.cgi?id=436463 I, too, have not been able to get RHEL 5.3 to install either. Regards, Wayne. -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of mala...@us.ibm.com Sent: Wednesday, April 01, 2009 8:13 AM To: open-iscsi@googlegroups.com Subject: multipath iSCSI installs Hi all, I am trying to install RHEL5.3 on an iSCSI disk with two paths. I booted with mapth option but the installer picked up only a single path. Is this the expected behavior when I use iBFT? The install went fine on a single path. I was trying to convert the single path to multi-path by running mkinitrd. RHEL was unable to boot (panics) with the new initrd image. The only difference between the old initrd image and the new one is that the old initrd image was using iBFT method and the new image was trying to use the values from the existing session(s) at initrd creation time. For some reason the latter method doesn't work. Is this a known bug? I also tried installing SLES10 and SLES11. I believe they recommend installing on a single path and then converting to multipath. I have found that SLES11's initrd image can only find one path even after including multipath support into the initrd image. It creates a dm-multipath device with a single path and later converts to dm-multipath device with two paths later when it runs scripts in /etc/init.d. SLES10's behavior might be same, but I didn't analyse. Does anyone know if SLES11's initrd image can find more than one iSCSI path? Thanks, Malahal. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: Correct qisioctl module version for RHEL 5.2 kernel qla4xxx driver
Hi Pasi. The correct IOCTL module should be included in the latest SANsurfer package. Regards, Wayne. -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Pasi Kärkkäinen Sent: Wednesday, July 09, 2008 5:46 AM To: open-iscsi@googlegroups.com Cc: [EMAIL PROTECTED] Subject: Correct qisioctl module version for RHEL 5.2 kernel qla4xxx driver Hello! What's the correct/recommended qisioctl module version for RHEL 5.2 default in-kernel qla4xxx driver? I'd like to use Qlogic iSCSI Sansurfer.. -- Pasi --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
