On 06/09/2011 02:38 AM, Seth Simons wrote: > Hi Mike, > > Thanks for the speedy reply! > > I've set the initiator name the same in the bios and in the OS. Do > they *have* to be different? I can see the logic in having each
No. For things like boot they will actually be the same. I was just trying to say that if they are different make sure that in the target you have them in any initiator ACLs you might have set up. > transport have a different name, but it seems not to be the case with > the other qlogic iscsi HBAs i'm using. > > As for Log output, there's a whole load of iscsid output which repeats > several times until timeout. I've attached the last iteration below. > > The target is an HP/Lefthand P4300, which as far as I can tell is just > a linux box with a fancy frontend and lots of SAS disks attached. It > seems to just be a wrapper around open-iscsi, but obviously I can't > tell for sure as it's locked down and fiddling with it would > invalidate the warranty. It is not forthcoming with any log output. > > I use this little snippet in the initramfs to get the initial > connection to the boot device defined in the HBA bios: > > ifconfig eth0 10.10.12.70 netmask 255.255.255.0 > modprobe iscsi_tcp > iscsistart -i `cat /sys/firmware/iscsi_boot0/initiator/initiator-name` > -t `cat /sys/firmware/iscsi_boot0/target0/target-name` -g 1 -a `cat > /sys/firmware/iscsi_boot0/target0/ip-addr` Ah so you are doing iscsi boot? Are you doing the initiator root from the initramfs with iscsi_tcp then when the system is booted starting be2iscsi and trying to use that? If do then for 2.6.39 you should just use be2iscsi in the initramfs. In there you need to do: // this module will read the boot info that was used by the bios and export it in sysfs modprobe iscsi_boot_sysfs // this will load be2iscsi modprobe be2iscsi // this will have iscsid/iscsistart read the iscsi_boot_sysfs info and have be2iscsi create sessions using that info iscsistart -b // you can run iscsistart -f to see the info in sysfs if you wanted or you can just cd to /sys/firmware/iscsi_boot_* When the system has switched to the real root and the init scripts run then you just need to start iscsid and log into any other sessions you wanted running. -- 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.
