https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c Jiaying ren changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jren@novell.com AssignedTo|bnc-team-screening@forge.pr |hare@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c3 --- Comment #3 from Vasu Chandrasekhara 2012-11-20 09:51:53 UTC --- Hi Lee, not quite, but moving the target could also be a problem in the current implementation. The issue is that with modern iscsi NICs, the initrd should not persist iscsi initiator & target information. That information should be read from the iBFT dynamically. (If gpxe - http://etherboot.org/wiki/sanboot - is used and iBFT is not possible, of course persisting the iscsi info in the inird makes sense.) This way, you have a "neutral" Linux OS image residing on an arbitrary LUN and then you can program your iSCSI capable NIC (e.g. in the BIOS or UEFI) to point to that LUN. The issue above, which I am pointing to, is that the iBFT is dynamically read in boot-ibft.sh, but not acted upon in boot-network.sh. Ideally, the only parameters which needs to be passed in the boot parameter for an iscsi boot of Linux is: ibft_availabe (this could imply root_iscsi). Best, Vasu -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c5 Vasu Chandrasekhara changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|vasu.chandrasekhara@gmail.c | |om | --- Comment #5 from Vasu Chandrasekhara 2012-11-21 15:25:32 UTC --- Hi Lee, understood. 1. Get Server A with IP a to iSCSI boot from the iSCSI Target LUN T. 2. Shut Server A down. 3. Unmask LUN T from Server A, Mask to Server B. 4. Start Server B with IP b to iSCSI boot from the iSCSI Target LUN T. In this test scenario the NICs must support iBFT and the IP & iSCSI configuration must be programmed into the nvram of the NIC. Best, Vasu -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c7 --- Comment #7 from Vasu Chandrasekhara 2012-12-03 20:09:34 UTC --- Hi Lee, correct. Just to be more precise, Server B should not be in the same network realm as Server A (e.g. Server A has 10.10.10.10/24 and Server B has something like 10.20.10.17/24 and are not on the same wire). That ensures in the testcase, that any config parameter persisted in the initrd is detected. Best, Vasu -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c9 --- Comment #9 from Lee Duncan 2012-12-05 11:42:12 PST --- Created an attachment (id=515863) --> (http://bugzilla.novell.com/attachment.cgi?id=515863) Modify initrd to handle iBFT/iSCSI more dynamically Please cd to /lib/mkinitrd and apply this patch, which changes two files in the "scripts" subdirectory. Then run "mkinitrd -v" (saving the output, in case there is a problem), then rebooting using the new initrd. This patch is from bug 755642 ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785818 https://bugzilla.novell.com/show_bug.cgi?id=785818#c11 Vasu Chandrasekhara changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #11 from Vasu Chandrasekhara 2012-12-10 14:23:10 UTC --- This bug can be closed as duplicate. (I am not authorized to see the original bug report, but from the diff attachment I conclude that this is the same change that I am proposing, except that I also needed to set the "static_ips=$ip" variable) Thanks, Vasu P.S. I can also not set the status to resolved duplicate of 755642 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.