iSCSI stuff in Busybox on Linux

1. Notes/Warnings
1. This works with Intel I350 Gbit NICs, as on a Supermicro X9DRT motherboard, which uses the igb (1Gbit) or ixgbe (10Gbit) module as the NIC device driver, and the iscsi_ibft module for iscsi boot. You'll have to change the module names if using Broadcom or other chips.
2. Once booted, you're in a Busybox environment... some commands will be limited or may not work the way in which you are accustomed on a full Linux system.
3. As a best practice, use all lower-case named target and initiator names (some firmwares may silently convert case).
4. WARNING: If you do not have your LUNs properly masked, do not specify the installation target correctly, and so forth, you may destroy your data. Know what you are doing, and use at your own risk.
2. Connect up the Intel NICs
3. Configure the iscsi target to allow access from this initiator (hint: this is done on your SAN), and mask out other LUNs to be NOT visible to this initiator
4. Boot off the CD and enter the busybox command environment
5. Manually configure the ip address and enable the interfaces, and verify connectivity
1. ifconfig eth0 inet 10.10.10.15 netmask 255.255.255.0 up
2. route add default gw 10.10.10.1
3. ping 10.10.10.1; ping www.google.com
4. At this point you can enable ssh to access this from a different computer over the network, if you need to:
1. ssh-keygen -f /etc/ssh_host_rsa_key -t rsa  (use an empty passphrase)
2. ssh-keygen -f /etc/ssh_host_dsa_key -t dsa (use an empty passphrase)
3. /usr/sbin/sshd
4. echo "root:supersecret" | chpasswd
5. (now, copy the hashed password for root from /etc/passwd to /etc/shadow
6. Prepare iscsi:
1. mkdir /etc/iscsi
2. echo "InitiatorName=iqn.2014-01.local:hostname" > /etc/iscsi/initiatorname.iscsi (replace the initiator name and/or hostname as appropriate)
3. echo "node.startup = automatic" > /etc/iscsi/iscsid.conf
4. echo "node.session.initial_logon_retry_max = 60" >> /etc/iscsi/iscsid.conf
5. modprobe iscsi_ibft
6. modprobe scsi_transport_iscsi
7. modprobe iscsi_tcp
8. iscsid -c /etc/iscsi/iscsid.conf -i /etc/iscsi/initiatorname.iscsi -f &
7. detect iscsi targets (where 10.10.10.20 is the IP address of the iSCSI SAN target) (only do this if you are not going to use the ibft boot stuff from an OS installer)
1. iscsiadm -m discovery -t sendtargets -p 10.10.10.20
2. iscsiadm -m node -l
8. set up multipath (if you have multiple paths)
1. modprobe dm-multipath
2. multipath -l -r
3. multipath -l -r (verify that the paths exist and are recognized...)
9. At this point, you can use the multipath device to access your iSCSI LUNs as needed.
10. If you want to run an OS installer, at this point start the installer
1. (in CentOS or XenServer installation media, append --use_ibft)
2. (use --mpath if you have set up multipath)
3. (use --network_device=eth0 , or the correct iSCSI network device, if needed)