Becoming a “New Yorker Author”

1. Create a new file called boot.open-iscsi with the content shown below.

2. Copy the file you just created to /etc/init.d/ folder and overwrite the existing one.

Content of the new boot.open-iscsi file:

#!/bin/bash

# Should-Start: boot.multipath

# Required-Stop:

# Should-Stop: $null

# Default-Start: B

# Default-Stop:

# Short-Description: iSCSI initiator daemon root-fs support

# Description: Starts the iSCSI initiator daemon if the

# root-filesystem is on an iSCSI device

# This service is run right after booting. So all targets activated

# during mkinitrd run should not be removed when the open-iscsi

Bro a d c o m Co rp o r a ti o n

Document INGSRVT78-CDUM100-R iSCSI Boot Page 91

# service is stopped.

#

iscsi_load_iscsiuio() {

TRANSPORT=`$ISCSIADM -m session 2> /dev/null | grep "bnx2i"`

if [ "$TRANSPORT" ] ; then

STARTUP=`$ISCSIADM -m node -p $ip -T $target 2> /dev/null | grep "node.conn\[0\].startup"

| cut -d' ' -f3`

if [ "$STARTUP" -a "$STARTUP" != "onboot" ] ; then

$ISCSIADM -m node -p $ip -T $target -o update -n node.conn[0].startup -v onboot fi

done }

# Reset status of this service rc_reset

# We only need to start this for root on iSCSI if ! grep -q iscsi_tcp /proc/modules ; then if ! grep -q bnx2i /proc/modules ; then

echo -n "Starting iSCSI initiator for the root device: "

iscsi_load_iscsiuio

echo -n "Checking for iSCSI initiator service: "

if checkproc $DAEMON ; then

Bro a d c o m C o rp o r a ti o n

Page 92 iSCSI Boot Document INGSRVT78-CDUM100-R

exit 1

;;

esac rc_exit

Injecting (Slipstreaming) Broadcom Drivers into Windows Image Files

To inject Broadcom drivers into the Windows image files, you must obtain the following correct Broadcom driver packages for the applicable Windows Server version (2008 R2, 2008 SP2, 2012, or 2012 R2).

• bxvbd

Then, you place these driver packages to a working directory. For example, copy the driver packages to the following directories:

Finally, you inject these drivers into the Windows Image (WIM) files and install the applicable Windows Server version from the updated images.

The detailed steps are provided below:

1. For Windows Server 2008 R2 and SP2, install the Windows Automated Installation Kit (AIK).

—or—

For Windows Server 2012 and 2012 R2, install the Windows Assessment and Deployment Kit (ADK).

2. Use the following commands to create a temporary directory and set it as the current directory for all later steps:

md C:\Temp\x cd /d C:\Temp\x

3. Use the following commands to create two subdirectories:

md src md mnt

4. Use the following command to copy the original DVD into the src subdirectory.

xcopy N:\ .\src /e /c /i /f /h /k /y /q

Note that in this example, the installation DVD is in the N: drive.

5. Open a Deployment and Imaging Tools command prompt in elevated mode. Then, set c:\Temp\x as the current directory.

NOTE: The file and folder names used in this procedure are examples only. You can specify your own file and folder names for your slipstream project.

Bro a d c o m Co rp o r a ti o n

Document INGSRVT78-CDUM100-R iSCSI Boot Page 93

Note that you will use this command prompt window in all subsequent steps.

6. Enter the following commands:

attrib -r .\src\sources\boot.wim attrib -r .\src\sources\install.wim

7. Enter run the following command to mount the boot.wim image:

dism /mount-wim /wimfile:.\src\sources\boot.wim /index:2 /mountdir:.\mnt Note that you must always use “2” for the index value.

8. Enter the following commands to add the below drivers to the currently mounted image:

dism /image:.\mnt /add-driver /driver:C:\Temp\evbd\evbd.inf 9. Enter the following command to unmount the boot.wim image:

dism /unmount-wim /mountdir:.\mnt /commit

10. Enter the following command to determine the index of the desired SKU in the install.wim image:

dism /get-wiminfo /wimfile:.\src\sources\install.wim

For example, in Windows Server 2012, index 2 is identified as “Windows Server 2012 SERVERSTANDARD.”

11. Enter the following command to mount the install.wim image:

dism /mount-wim /wimfile:.\src\sources\install.wim /index:X /mountdir:.\mnt Note that X is a placeholder for the index value that you obtained in step 10.

12. Enter the following commands to add these drivers to the currently mounted image:

dism /image:.\mnt /add-driver /driver:C:\Temp\evbd\evbd.inf 13. Enter the following command to unmount the install.wim image:

dism /unmount-wim /mountdir:.\mnt /commit 14. Enter the following command to create an .iso file:

oscdimg -e -h -m -n -lslipstream -bootdata:2#p0,e,b"c:\Program Files\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com"#pEF,e,b"c:\Program Files\Windows AIK\Tools\PETools\amd64\boot\efisys.bin" c:\temp\x\src c:\temp\Win20xxMOD.iso

Note that Platform is a placeholder for the architecture of the operating system that you want to install, such as amd64 or x86. Also, xx in the file names is a placeholder for the Windows Server OS version (2012, 2008R2, 2008SP2.) 15. Using a DVD-burning application, burn the .iso file you created to a DVD.

16. Use the DVD that you created in step 15 to install the applicable Windows Server version.

Bro a d c o m C o rp o r a ti o n

Page 94 iSCSI Boot Document INGSRVT78-CDUM100-R

Booting

After that the system has been prepared for an iSCSI boot and the operating system is present on the iSCSI target, the last step is to perform the actual boot. The system will boot to Windows or Linux over the network and operate as if it were a local disk drive.

1. Reboot the server.

2. Select CTRL+S.

3. To boot through an offload path, set the HBA Boot Mode to Enabled. To boot through a non-offload path, set the HBA Boot Mode to Disabled. (Note: This parameter cannot be changed when the adapter is in Multi-Function mode.) If CHAP authentication is needed, enable CHAP authentication after determining that booting is successful (see Enabling CHAP Authentication).