On Tue, Nov 20, 2007 at 10:04:10AM -0500, Tom Sightler wrote: > On Tue, 2007-11-20 at 10:33 +0200, Pasi Kärkkäinen wrote: > > > I think you need to load ioctl module for qla4xxx called "qisioctl". The > > qlogic vendor driver includes this functionality "out of the box". > > Thanks for the info Pasi. I actually already had the qisioctl module > installed, but it wasn't working. It turns out that on this machine > there seems to be some conflict between the iqlremote agent and the > qisioctl module. >
Ok. Which version of qisioctl are you using? Which iSCSI SANsurfer (iqlremote) version? Maybe it's some version conflict.. make sure you have latest version of SANsurfer. Qlogic guys are reading open-iscsi mailinglist, so maybe you can also ask from there.. > When I use the Qlogic qla4xxx driver I can run the iqlremote agent which > allows me to configure the HBA via the SANsurfer GUI interface. I can > also use the iscli command line interface. > > When I use the stock RHEL5.1 qla4xxx driver with qisioctl I can use the > iscli interface as well. If I attempt to start the iqlremote server, > the service starts and seems to be attempting to work, but SANsurfer > will not correctly connect to the device and it even interferes with the > operation of iscli with the symptom of randomly failing to allow access > to one or two of the iscsi ports (this machine has 4). > > This sounds like it is probably a problem with qisioctl so I'll take it > up with Qlogic. > Yep. Please let us know what you find out :) > In the meantime, when running with the stock qla4xxx driver we have not > been able to reproduce the corruption. > That's good to hear. -- Pasi _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
