On 04/28/2012 11:26 PM, Mark Lehrer wrote: >> I am trying to better understand iSCSI boot. Towards that end, I'm >> trying to understand how, during iSCSI boot, the system gets the >> interface attributes. > > Of course this will depend on what hardware & driver you use. > > I had an email exchange with Qlogic a few months ago about their driver > situation (for the 4062C anyway). IIRC the driver that is in the > standard Linus kernel didn't fully integrage with iscsiadm (or SAN > surfer) as well as the one that you can download from their site. I > thought it would at least let iscsiadm show the session info though.
The qla4xxx driver in Linus's tree now supports open-iscsi (the open-iscsi tools in the open-iscsi git tree). So the next open-iscsi.org release will support qla4xxx. You can setup the networking, do discovery and login to targets like you do with software iscsi. I think the iscsi iface networking setup is still a little awkward for qla4xxx/be2iscsi, so I have been trying to fix that up before doing a release. Also I am waiting on some testing. But the current iscsiadm should at least show the qla4xxx sessions in older kernels. > > I believe they were trying to get the fully functional version into the > vanilla kernel for RH 6.2; but I haven't yet tried it out. > The iscsiadm and qla4xxx in RHEL 6.2 should work together. Qlogic and I backported open-iscsi.org code and kernel.org kernel code to the RHEL kernel and iscsi tools in 6.2. -- 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?hl=en.
