Re: Redhat 5 Qlogic HBA discovering new targets
I think I'm getting the picture, Redhat and Qlogic dont support open- iscsi. This was starting to become obvious when I had to escalate through several engineers at Redhat because they were not aware of features of open-iscsi and wether or not they supported it. I just did a fresh load of Redhat 5 update 2, san boot over qle4060c card. I'm using the redhat qla4xxx driver right now and I installed iscsi-initiator-utils.i386 and its still not working. iscsiadm still doesnt detect any interfaces "iscsiadm -m iface". I'm more than willing to manually create all the needed files if I can get this to work. The only features I need to work are. 1) discover storage via iSCSI HBA 2) login to targets via iSCSI HBA 3) logout of targets via iSCIS HBA I dont need to modify any card settings at all. thanks Jason On Aug 18, 2:04 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > WonderBoy wrote: > > I'm currently running the Qlogic driver for the QLE4060c, should I > > be using the Redhat driver. > > open-iscsi will not work with the qlogic.com drivers. They use their own > ioctl and do not implement what is needed for open-iscsi to config it. > > You must be using the upstream kernel's qlogic driver. And like I said > before we can only discover new targets. We cannot do any other config > right now. So if below when you mentioned you need to configure the > card, if it is anything more than discovery of targets you must use the > distro drivers +qlogic.com ioctl module or qlogic.com module and then > use qlogic.com's tools with those modules. > > > > > Sorry to sound like a broken record, but does anyone know > > specfically what I need to do to setup, configure the QLE4060c card, > > using the HBA not network interface. > > > I have read through the docs several times and I can't figure out > > what I'm supposed to do. Better yet has anyone ever gotten this to > > work and can point me or even give me an export of what the config > > should look like? > > Normally people just use the qlogic.com driver and qlogic's tools, or > they use the distro driver + ioctl module on qlogic.com and qlogic's tools. > > Red hat and qlogic.com drivers do not support open-iscsi. > > > > > Is this the correct place to ask such a question? > > Normally for red hat I would make a bugzilla > here.https://bugzilla.redhat.com/, or I would use the qlogic.com > documentation, or send a question to qlogic.com. > > This question has been asked before and so if you search the list you > should find it --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Redhat 5 Qlogic HBA discovering new targets
WonderBoy wrote: > I'm currently running the Qlogic driver for the QLE4060c, should I > be using the Redhat driver. open-iscsi will not work with the qlogic.com drivers. They use their own ioctl and do not implement what is needed for open-iscsi to config it. You must be using the upstream kernel's qlogic driver. And like I said before we can only discover new targets. We cannot do any other config right now. So if below when you mentioned you need to configure the card, if it is anything more than discovery of targets you must use the distro drivers +qlogic.com ioctl module or qlogic.com module and then use qlogic.com's tools with those modules. > > Sorry to sound like a broken record, but does anyone know > specfically what I need to do to setup, configure the QLE4060c card, > using the HBA not network interface. > > I have read through the docs several times and I can't figure out > what I'm supposed to do. Better yet has anyone ever gotten this to > work and can point me or even give me an export of what the config > should look like? Normally people just use the qlogic.com driver and qlogic's tools, or they use the distro driver + ioctl module on qlogic.com and qlogic's tools. Red hat and qlogic.com drivers do not support open-iscsi. > > Is this the correct place to ask such a question? > Normally for red hat I would make a bugzilla here. https://bugzilla.redhat.com/, or I would use the qlogic.com documentation, or send a question to qlogic.com. This question has been asked before and so if you search the list you should find it --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Redhat 5 Qlogic HBA discovering new targets
I'm currently running the Qlogic driver for the QLE4060c, should I be using the Redhat driver. Sorry to sound like a broken record, but does anyone know specfically what I need to do to setup, configure the QLE4060c card, using the HBA not network interface. I have read through the docs several times and I can't figure out what I'm supposed to do. Better yet has anyone ever gotten this to work and can point me or even give me an export of what the config should look like? Is this the correct place to ask such a question? thanks everyone. Jason Hammond On Aug 18, 11:09 am, Mike Christie <[EMAIL PROTECTED]> wrote: > WonderBoy wrote: > > I just read the docs and its saying that I dont need iface files for > > hardware iscsi. Do I have to tell open iscsi to use the hardware > > adapter "qla4xxx". > > > When you run iscsiadm the first time a hardware iscsi driver like > > qla4xxx is > > loaded, iscsiadm will create default iface configs for you. The > > config > > created > > by iscsiadm for qlogic should be ok for most uses and users should not > > have > > to modify them. > > You should not have to do anything, but the RHEL 5 driver does not > export the needed settings. > > You will have to try the upstream kernel. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Redhat 5 Qlogic HBA discovering new targets
WonderBoy wrote: > I just read the docs and its saying that I dont need iface files for > hardware iscsi. Do I have to tell open iscsi to use the hardware > adapter "qla4xxx". > > When you run iscsiadm the first time a hardware iscsi driver like > qla4xxx is > loaded, iscsiadm will create default iface configs for you. The > config > created > by iscsiadm for qlogic should be ok for most uses and users should not > have > to modify them. > You should not have to do anything, but the RHEL 5 driver does not export the needed settings. You will have to try the upstream kernel. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Redhat 5 Qlogic HBA discovering new targets
I just read the docs and its saying that I dont need iface files for hardware iscsi. Do I have to tell open iscsi to use the hardware adapter "qla4xxx". When you run iscsiadm the first time a hardware iscsi driver like qla4xxx is loaded, iscsiadm will create default iface configs for you. The config created by iscsiadm for qlogic should be ok for most uses and users should not have to modify them. Running: On Aug 18, 12:39 am, WonderBoy <[EMAIL PROTECTED]> wrote: > If I do an iscsiadm -m iface i get "iscsiadm: no records found!" do > I have to create the ifaces files manually. I'm having difficult > understanding the ifaces files and how they are used. I have some > virtual hosts that can attach to storage over eth0 and eht1 as opposed > to an iSCSI hba. On those systems I dont see any ifaces files. > > Can someone explain to me what I need to do in my situation. iscsiadm > -m iface returns no records found and I'm using a Qlogic HBA qla4xxx. > > any assistance would be greatly appreciated. > > thanks > > Jason > > On Aug 15, 7:12 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > > > > > WonderBoy wrote: > > > sorry I didnt see your response, I have not tried specifing the ifaces > > > No problem. I sent it in the order I read the mails so you would have > > seen the other one first :) > > > > file. I'll do that here shortly and see if this works. > > > Ok, just one update. Below I said it is not possible on RHEL, and it > > turns out it is possible on RHEL5. So if you do > > > iscsiadm -m iface > > > you should see some thing about qla4xxx and some mac addresses. You can > > then take the ifacename for the port you want to use and run that command > > iscsiadm -m discovery -t st -p ip -I iface_name_of_qlogic_card > > > There are some hicups though. We do not yet get any error from qla4xxx > > if something fails. So if the qlogic card has in the firmware defaults > > to use CHAP or digests, but the target does not want to use them you > > will not log into anything and you will not get an error. > > > > Thanks Mike > > > > Jason > > > > On Aug 15, 2:58 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > > >> WonderBoy wrote: > > >>> I cant use the Sansurfer cli, not because it doesnt work but it stamps > > >>> the volume info "iqn, target ip, etc" on the card. In my situation > > >>> this data cant be written to the card, and this is why I'm looking > > >>> towards the open-iscsi initiator solution.. data will only be on the > > >>> os. > > >> That is not possible with the driver in RHEL. > > > >> With the upstream kernel, if you do > > > >> iscsiadm -m discovery -t st -p ip -I iface_name_of_qlogic_card > > > >> then it will do sendtargets discovery and log into all the targets and > > >> portals found. It will not store anything on the card firmware. > > > >> I think the closest you can get with iscli + qla4xxx in RHEL is just > > >> storing the discovery address on the firmware. You do not need to store > > >> the target, ip for every target you want to use. Just the discovrey > > >> address. Maybe that will help. > > > >>> The software initiator solution is what I really need to work, I have > > >>> Redhat calling be back here shortly and hopefully I'll get more > > >>> information. > > >>> On Aug 15, 2:40 pm, "Don Williams" <[EMAIL PROTECTED]> wrote: > > >>>> If you install the qlogic, iscli utility, you can use that to > > >>>> statically map > > >>>> the volumes. You'll need the complete IQN name and the IP address. > > >>>> Usually, using SANsurfer makes life easier, even if you have to run > > >>>> the X > > >>>> window to another server. Are you using RHEL v4.x or v5.x? > > >>>> What iSCSI target are you using? > > >>>> Don > > >>>> -Original Message- > > >>>> From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > > >>>> Behalf Of WonderBoy > > >>>> Sent: Friday, August 15, 2008 4:44 PM > > >>>> To: open-iscsi > > >>>> Subject: Re: Redhat 5 Qlogic HBA discovering new targets > > >>>> I can boot off of the card fine using the Redhat driver or the > > >>>> Qlogic driver, but I'm not using software initiate for b
Re: Redhat 5 Qlogic HBA discovering new targets
If I do an iscsiadm -m iface i get "iscsiadm: no records found!" do I have to create the ifaces files manually. I'm having difficult understanding the ifaces files and how they are used. I have some virtual hosts that can attach to storage over eth0 and eht1 as opposed to an iSCSI hba. On those systems I dont see any ifaces files. Can someone explain to me what I need to do in my situation. iscsiadm -m iface returns no records found and I'm using a Qlogic HBA qla4xxx. any assistance would be greatly appreciated. thanks Jason On Aug 15, 7:12 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > WonderBoy wrote: > > sorry I didnt see your response, I have not tried specifing the ifaces > > No problem. I sent it in the order I read the mails so you would have > seen the other one first :) > > > file. I'll do that here shortly and see if this works. > > Ok, just one update. Below I said it is not possible on RHEL, and it > turns out it is possible on RHEL5. So if you do > > iscsiadm -m iface > > you should see some thing about qla4xxx and some mac addresses. You can > then take the ifacename for the port you want to use and run that command > iscsiadm -m discovery -t st -p ip -I iface_name_of_qlogic_card > > There are some hicups though. We do not yet get any error from qla4xxx > if something fails. So if the qlogic card has in the firmware defaults > to use CHAP or digests, but the target does not want to use them you > will not log into anything and you will not get an error. > > > > > Thanks Mike > > > Jason > > > On Aug 15, 2:58 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > >> WonderBoy wrote: > >>> I cant use the Sansurfer cli, not because it doesnt work but it stamps > >>> the volume info "iqn, target ip, etc" on the card. In my situation > >>> this data cant be written to the card, and this is why I'm looking > >>> towards the open-iscsi initiator solution.. data will only be on the > >>> os. > >> That is not possible with the driver in RHEL. > > >> With the upstream kernel, if you do > > >> iscsiadm -m discovery -t st -p ip -I iface_name_of_qlogic_card > > >> then it will do sendtargets discovery and log into all the targets and > >> portals found. It will not store anything on the card firmware. > > >> I think the closest you can get with iscli + qla4xxx in RHEL is just > >> storing the discovery address on the firmware. You do not need to store > >> the target, ip for every target you want to use. Just the discovrey > >> address. Maybe that will help. > > >>> The software initiator solution is what I really need to work, I have > >>> Redhat calling be back here shortly and hopefully I'll get more > >>> information. > >>> On Aug 15, 2:40 pm, "Don Williams" <[EMAIL PROTECTED]> wrote: > >>>> If you install the qlogic, iscli utility, you can use that to statically > >>>> map > >>>> the volumes. You'll need the complete IQN name and the IP address. > >>>> Usually, using SANsurfer makes life easier, even if you have to run the > >>>> X > >>>> window to another server. Are you using RHEL v4.x or v5.x? > >>>> What iSCSI target are you using? > >>>> Don > >>>> -Original Message- > >>>> From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On > >>>> Behalf Of WonderBoy > >>>> Sent: Friday, August 15, 2008 4:44 PM > >>>> To: open-iscsi > >>>> Subject: Re: Redhat 5 Qlogic HBA discovering new targets > >>>> I can boot off of the card fine using the Redhat driver or the > >>>> Qlogic driver, but I'm not using software initiate for boot. > >>>> I'm looking to discover and login to additional storage that I > >>>> allocate to this server. I need the open-iscsi driver to login through > >>>> the HBA as well, I cant use front end network interfaces. I dont care > >>>> if I use the Redhat driver or the Qlogic driver for open-iscsi, I have > >>>> tried both and neither work. > >>>> I just need the iscsi client to discover my iscsi targets. Is this > >>>> even possible at this point with the version of open-iscsi that is > >>>> available. > >>>> thanks for the help > >>>> Jason > >>>> On Aug 15, 1:11 pm, Konrad Rzeszutek <[EMAIL PROTECTED]> wrote: > >>>>> On Fri, Au
