Re: Issues with intel firmware initiator, ibft and 2-way chap
On Friday 20 March 2009 13:12:43 Hans de Goede wrote: Sorry for the long delay. Here is a reminder of what this what about, when doing 2 way chap, booting from an intel server nic with ibft, there is no way to specify the reverse username. And the ibft info in sysfs contains a garbage string for the reverse username. As requested here is a dump of the ibft table. Notice the string consisting of a single capital S followed by a 0xff character, that is what gets shown as the reverse username in sysfs. Definitely a bug in the Intel firmware. The iBFT reverse username entry contains a valid string descriptor pointing to the S0xff string. Michael --~--~-~--~~~---~--~~ 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: iscsi boot without ibft but using ibft sysfs code
On Wednesday 25 February 2009 22:47:12 Konrad Rzeszutek wrote: This is nice because the tools only have to look in one place, but I am not sure if this type of stuff can also go under the /sys/firmware dir. True. Would have to change the parent tree. Maybe to to /sys/boot' (or /sys/iscsi_boot?) We're still talking about information extracted from the firmware, whether via the iBFT or via vendor-specific mechanisms; /sys/firmware sounds appropriate to me at least. Michael --~--~-~--~~~---~--~~ 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: [RFC]-Sysfs attributes of /sys/firmware/ibft files
On Tuesday 24 February 2009 07:57:32 shyam_i...@dell.com wrote: (I don't see why you would want to modify the iBFT anyway, but that's a separate issue.) Part of it is out of lazyness and I guess sysadmins will agree. I don't want the system to reboot to reconfigure the target IP addresses and iqn's when I know they have changed while I am booted into OS. The other thing is if I have an iSNS server configured I can just issue the change through sysfs especially if my NIC doesn't talk iSNS. It sounds as though you're expecting that making changes to the iBFT would cause the iSCSI initiator to change its configuration. I don't think this is going to be the case; it definitely won't happen in the case of gPXE. Michael --~--~-~--~~~---~--~~ 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: Issues with intel firmware initiator, ibft and 2-way chap
On Monday 02 February 2009 19:12:25 Konrad Rzeszutek wrote: A year ago that was the problem - you got something like this: konrad@/data/git/ibft$ hexdump intel_nic.bin 000 4269 5446 029c 0001 4e49 4554 004c 010 * 030 * 290 29c Where the iBFT NIC and target structure are filled with 0xFF. The checksum of that table is non-zero, so anything scanning for it should ignore it anyway. If the ibft module treats it as a valid table, then it's a bug. Michael --~--~-~--~~~---~--~~ 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: Booting using open-iscsi from gpxe?
On Sun, 6 Apr 2008 [EMAIL PROTECTED] wrote: Can I boot a linux machine using open-iscsi and gpxe? I'd like to do do something similar to how I would setup on a windows machine described here http://www.etherboot.org/wiki/sanboot/winnt_iscsi?s=iscsi%20windows Yes, you can. The gPXE boot from SAN tutorial starts at http://www.etherboot.org/wiki/sanboot/ and either the Fedora or CentOS instructions are personally[*] guaranteed to work, and will use open-iscsi. In the general case, if you're not following one of the tutorials, you'll need an initrd that supports iSCSI boot including obtaining parameters from the iBFT. Install grub/lilo in the usual way on the disk, then make the disk image available via iSCSI and point gPXE at it. Michael [*] I'm the gPXE lead developer, btw. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
