BIOS Integrated iscsi Boot for PRIMERGY Servers. Installation and Configuration

Transcription

1 BIOS Integrated iscsi Boot for PRIMERGY Servers Installation and Configuration Edition November 2008

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2000 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2000. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright 2008 Fujitsu Siemens Computers GmbH. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

3 Contents 1 Introduction iscsi Boot with Windows 2003 Server Installation Overview System Requirements Preparing an Operating System Image Performing the Initial Windows Installation Installing the Microsoft iscsi Boot Software Initiator Configuring the Microsoft iscsi Software Initiator Transferring the Operating System Image to the iscsi Target Start Set Initiator Node Name Connect to iscsi Target Select Source Disk Select Destination Disk Prepare Disk Activating Option ROM Scan Configuring the Controller for iscsi Boot Static iscsi Boot Configuration Dynamic iscsi Boot Configuration Configuring a Secondary Controller Completing the Controller Configuration Performing an iscsi Boot iscsi Boot with Windows 2008 Server Installation Overview System Requirements System BIOS Settings Configuring the Controller for iscsi Boot Static iscsi Boot Configuration BIOS Integrated iscsi Boot

4 Contents Dynamic iscsi Boot Configuration Completing the Controller Configuration Installing Windows 2008 on an iscsi Target Completing the Controller Configuration Configuring an MPIO Connection iscsi Boot with SuSE Linux Enterprise Server Installation Overview System Requirements Activating Option ROM Scan Configuring the Controller for iscsi Boot Static iscsi Boot Configuration Dynamic iscsi Boot Configuration Completing the Controller Configuration Installing Linux on an iscsi Target Configuring a DHCP Server to Support iscsi Boot DHCP Options Configuring the DHCP Server to Support DHCP Option Configuring the DHCP Server to Support DHCP Option Configuring iscsi Crash Dump Installation with NetXtreme I Installation with NetXtreme II Troubleshooting Glossary BIOS Integrated iscsi Boot

5 1 Introduction The purpose of this document is to outline the steps necessary to support iscsi boot with PRIMERGY servers under Windows and Linux. These steps include configuring the system and the network controller to perform iscsi boot, along with the steps necessary to configure a DHCP server to support dynamic iscsi boot configuration. For the iscsi target configuration, this manual only provides general information, see page 7. Figure 1: iscsi connection Overview of the iscsi boot process At power up the iscsi boot DOS initiator driver is executed from a binary image residing on the NVRAM of the network controller. The binary image contains the iscsi boot DOS initiator code, an iscsi boot configuration file, and a configuration file editor. The configuration file allows for the flexibility of obtaining iscsi boot parameters statically (via the configuration file itself), or dynamically (via a DHCP server). If the dynamic method is utilized, the DHCP server will publish all of its supported options including option 17 and option 43 which provide a root path to the iscsi target where the W2K3 operating system image is stored. BIOS Integrated iscsi Boot 5

6 Introduction The iscsi boot software hooks into the system INT 13H handler so that it can redirect disk access requests transparently from the real-mode operation to remote disk via the iscsi protocol. The iscsi boot program downloads the operating system image (using an iscsi session) from an iscsi target and starts the standard boot process. iscsi boot configurations with Broadcom NetXtreme controllers Three key pieces of information are required to perform an iscsi boot: 1. An IP address (along with the associated net mask and default gateway) for the client system 2. The address of an iscsi target 3. An iscsi initiator name The Broadcom iscsi boot solution is able to use two different mechanisms to obtain appropriate configuration information to perform an iscsi boot; a static configuration and a dynamic configuration. In the static configuration the client system is configured with a static IP address (including net mask and gateway), an assigned initiator IQN (to identify the NetXtreme controller as an iscsi initiator) and 1 or 2 iscsi target IQNs. These values are programmed into the NVRAM associated with the controller and can only be changed through a special setup program (similar to the program used to configure the MBA). With a dynamic configuration, the controller will acquire its IP address, initiator IQN, and target IQN using DHCP. It is also possible to support a combination of these static and dynamic configurations as shown below: Static IP address, static initiator IQN, and static target IQN Dynamic IP address, static initiator IQN, and static target IQN (up to 2 targets) Dynamic IP address, dynamic Initiator IQN (DHCP Option 43), and dynamic target IQN (DHCP Option 43, up to 2 targets) Dynamic IP address, static initiator IQN, and dynamic target IQN (DHCP Option 17, up to 1 target) 6 BIOS Integrated iscsi Boot

7 Configuring the iscsi Target Configuring the iscsi target Configuration of the iscsi target varies by the iscsi target vendor and is beyond the scope of this document. The general steps include: Creating an iscsi target Associating an iscsi initiator with the iscsi target Recording the iscsi target name, TCP port number, iscsi LUN, and authentication details Refer to the iscsi target vendor s documentation for the specific steps associated with the selected iscsi target device. After the target has been configured the following information should be collected from the target: The iscsi target IQN The iscsi target IP address The iscsi target TCP port number The iscsi target CHAP ID & secret Structure of the rest of this manual The exact configuration process of a PRIMERGY server for iscsi depends on the operating system. Chapter 2 describes how to configure your server for iscsi boot under Windows Chapter 3 describes how to configure your server for iscsi boot under Windows Chapter 4 describes how to configure your server for iscsi boot under SuSE Linux 10. Chapter 5 describes how to set up a DHCP server to support iscsi boot. The required settings are explained using examples of a DHCP server under Windows 2003 Server. Chapter 6 describes how to configure crash dump functinality for servers under Windows Server 2003 and 2008 which are started via iscsi boot. Chapter 7 provides information for troubleshooting. BIOS Integrated iscsi Boot 7

8 References References RFC 3720, Internet Small Computer Systems Interface (iscsi), RFC 4173, Bootstrapping Clients using the Internet Small Computer System Interface (iscsi) Protocol, 8 BIOS Integrated iscsi Boot

9 2 iscsi Boot with Windows 2003 Server 2.1 Installation Overview Configuring a system to support iscsi boot under Windows 2003 consists of the following steps: Configuring a second iscsi target (for general information, see page 7. For further information, please see the documentation provided by the iscsi target manufacturer.) Preparing an Operating System Image (see page 10) Performing the Initial Windows Installation (see page 10) Installing the Microsoft iscsi Boot Software Initiator (see page 10) Configuring the Microsoft iscsi Software Initiator (see page 17) Transferring the Operating System Image to the iscsi Target (see page 23) Activating Option ROM Scan (see page 33) Configuring the Controller for iscsi Boot (see page 37) Performing an iscsi Boot (see page 54) Each of these steps will be discussed in detail, with appropriate examples, throughout the remainder of this chapter. 2.2 System Requirements The iscsi boot configuration described in this document requires Broadcom NetXtreme controllers and Windows Server 2003 with at least Service Pack 1 with WindowsServer2003-KB HotFix or Service Pack 2. BIOS Integrated iscsi Boot 9

10 Preparing an OS Image iscsi Boot with Windows Preparing an Operating System Image Because the NetXtreme Ethernet controller does not natively emulate a storage controller, the initial installation of the Windows operating system must be performed in two stages. In the first stage, the OS is installed to a local hard drive on the system. After the OS has been completely installed, an image of the local drive must be transferred to the iscsi target for use in subsequent boots Performing the Initial Windows Installation Before beginning, verify that the desired version of Windows supports iscsi boot, see section System Requirements on page 9. Proceed to install Windows to a local hard drive. When partitioning the local hard drive, make sure that the Windows boot drive (normally C:) is partitioned to a size less than or equal to the size of the iscsi target to be used. (Depending on the method used to copy an image of the local hard drive to the iscsi target this may or may not be an actual requirement.) Proceed to install Windows with the desired options. V CAUTION! The order of the following steps is important. The NetXtreme device driver must be installed before the Microsoft iscsi Boot Software initiator is installed. Install the appropriate Broadcom NetXtreme device drivers. If you use Windows 2003 Server with Service Pack 1 instead of Service Pack 2, install the KB HotFix for iscsi support. You will find the HotFix on the ServerStart DVD 1 under PROGRAMS/GENERAL/MS/iSCSI SW Initiator Boot Version Installing the Microsoft iscsi Boot Software Initiator You will find the Microsoft iscsi Boot Software initiator on the ServerStart DVD 1 under PROGRAMS/GENERAL/MS/iSCSI SW Initiator Boot Version. The images on the following pages show the installation steps. 10 BIOS Integrated iscsi Boot

11 iscsi Boot with Windows 2003 Preparing an OS Image During the installation of the Microsoft iscsi Boot Software initiator, be sure to specify that iscsi boot support is required and specify that the appropriate Broadcom NetXtreme device driver is to be used. I The Initiator Node Name of the Microsoft iscsi Boot Software initiator corresponds to the iscsi name to be used by the NetXtreme controller. Start the Microsoft iscsi initiator wizard. I In the network controller MBA setup, you can configure a secondary controller for iscsi to allow a multi-path connection to an iscsi target, see page 49. In this case, you must enable the option Microsoft MPIO Multipathing Support for iscsi in the Microsoft Software Initiator for the multi-path configuration to take effect. BIOS Integrated iscsi Boot 11

12 Preparing an OS Image iscsi Boot with Windows 2003 Set the installation options and click Next to continue. I By configuring a secondary controller via the MBA setup you can configure a multi-path connection to an iscsi target, see page 49. For the multi-path configuration to become effective, MPIO installation with Microsoft iscsi Software Initiator is required. 12 BIOS Integrated iscsi Boot

13 iscsi Boot with Windows 2003 Preparing an OS Image Activate the Configure iscsi Network Boot Support checkbox and select the desired network interface driver. Then click Next to continue. BIOS Integrated iscsi Boot 13

14 Preparing an OS Image iscsi Boot with Windows 2003 Accept the license agreement and click Next to continue 14 BIOS Integrated iscsi Boot

15 iscsi Boot with Windows 2003 Preparing an OS Image The setup inspects your current configuration and updates your files. After this is done, the dialog box is closed automatically. BIOS Integrated iscsi Boot 15

16 Preparing an OS Image iscsi Boot with Windows 2003 Click Finish to close the wizard. 16 BIOS Integrated iscsi Boot

17 iscsi Boot with Windows 2003 Preparing an OS Image Configuring the Microsoft iscsi Software Initiator To open a connection to the Microsoft iscsi Boot Software initiator follow the steps shown in the pictures below. Please refer to the help file for the Microsoft iscsi Boot Software initiator for details on connecting to and logging in to an iscsi target. Open the Microsoft iscsi initiator and select the Discovery tab. BIOS Integrated iscsi Boot 17

18 Preparing an OS Image iscsi Boot with Windows 2003 Click Add to open the following dialog box. 18 BIOS Integrated iscsi Boot

19 iscsi Boot with Windows 2003 Preparing an OS Image Enter the IP address and the port of the target portal and click OK. BIOS Integrated iscsi Boot 19

20 Preparing an OS Image iscsi Boot with Windows 2003 Select the Targets tab. 20 BIOS Integrated iscsi Boot

21 iscsi Boot with Windows 2003 Preparing an OS Image Click LogOn to open the following dialog box. BIOS Integrated iscsi Boot 21

22 Preparing an OS Image iscsi Boot with Windows 2003 In case of a multi-path configuration, activate the Automatically restore... and the Enable multi-path checkboxes. Otherwise, the default is not activated. Log on to the target by clicking OK. 22 BIOS Integrated iscsi Boot

23 iscsi Boot with Windows 2003 Transferring the OS Image Quit the Microsoft iscsi initiator by clicking OK. 2.4 Transferring the Operating System Image to the iscsi Target Transferring a Windows operating system image from the local hard drive to the iscsi target can be performed via the iscsi Boot Wizard.The graphical user interface of the iscsi Boot Wizard is described in this section. I Only the first (active) partition (not a GlobalFash partition) is copied. The Challenge Handshake Authentication Protocol (CHAP) is not supported. BIOS Integrated iscsi Boot 23

24 Transferring the OS Image iscsi Boot with Windows Start You start the iscsi Boot Wizard from the ServerStart DVD. Boot the server from the ServerStart DVD. When the boot process is finished the ServerStart entry menu is displayed. In the list, select the country variant of the attached keyboard and your preferred language for the user interface. Under ServerStart mode select the option Standard mode. Click Continue. You will now be prompted to accept the Microsoft End User License Agreement (EULA). Click Accept. The ServerStart welcome screen opens. Under Please Select the ServerStart Mode, select the option Guided / Expert Installation. The main menu of the ServerStart Expert mode opens. Under Further Functions click Tools. On the Tools menu click System Configuration Utilities. 24 BIOS Integrated iscsi Boot

25 iscsi Boot with Windows 2003 Transferring the OS Image Figure 2: ServerStart starting the iscsi Boot Wizard After you have started the Wizard, the Initiator Service is started (if this has not already been done by ServerStart) and the Wizard s start window is displayed. After you have clicked the Next button in the start window, the first processing window Set Initiator Node Name is opened. BIOS Integrated iscsi Boot 25

26 Transferring the OS Image iscsi Boot with Windows Set Initiator Node Name In this window you specify the Initiator Node Name. This name consists of iqn com.microsoft: and a unique system name. Figure 3: Set Initiator Node Name window The input field is pre-filled with a name which is generated automatically by ServerStart. If this automatically generated name is not the same as the name entered on the iscsi Target, you must modify it here to permit the iscsi Target to be accessed. 26 BIOS Integrated iscsi Boot

27 iscsi Boot with Windows 2003 Transferring the OS Image Connect to iscsi Target In this window you specify the IP address and the port number of the iscsi Target and set up the connection to it. Figure 4: Connect to iscsi Target window After you have entered the IP address and the port number (default: 3260) and then clicked on the Refresh button, the iscsi Target is displayed in the lower list. I When you enter further IP addresses and click on the Refresh button after each entry is made, multiple iscsi Targets are displayed in the list. After you have selected the/an iscsi Target in this list and clicked on the Login button, the connection to the iscsi Target is set up. BIOS Integrated iscsi Boot 27

28 Transferring the OS Image iscsi Boot with Windows Select Source Disk In this window you specify the source disk (local disk) on which the operating system which is to be copied was installed. Figure 5: Select Source Disk window reading the hard disk configuration After you have switched to this window, initially the current disk configuration is read in. This procedure can take some time. 28 BIOS Integrated iscsi Boot

29 iscsi Boot with Windows 2003 Transferring the OS Image Figure 6: Select Source Disk window selecting the source disk After the disk configuration has been read in, both the local disk (Disk 0 in the example) and the iscsi Target LUN (Disk 1 in the example) are displayed under Select Source Disk. I If the iscsi Target LUN is not displayed, you can start reading in the disk configuration again by clicking the Rescan button. After you have selected the local disk, its partitioning is displayed in the lower list. BIOS Integrated iscsi Boot 29

30 Transferring the OS Image iscsi Boot with Windows Select Destination Disk In this window you specify the destination disk (iscsi Target LUN) to which the operating system is to be copied. Figure 7: Select Destination Disk window selecting the target disk After you have selected the iscsi Target LUN, its partitioning is displayed in the lower list. I If the iscsi Target LUN has not yet been partitioned and formatted, this field is empty. 30 BIOS Integrated iscsi Boot

31 iscsi Boot with Windows 2003 Transferring the OS Image Prepare Disk In this window you start the transfer of the operating system by clicking the Prepare button. Figure 8: Prepare Disk window After you have clicked the Prepare button, a security prompt appears in which you must confirm that you want to perform the transfer: BIOS Integrated iscsi Boot 31

32 Transferring the OS Image iscsi Boot with Windows 2003 If the iscsi Target LUN has already been partitioned and formatted, an additional security prompt appears: I You are recommended to repartition and reformat the iscsi Target LUN (if necessary after you have backed up the existing data), otherwise unwanted collisions with the data on the disk can occur. Execution of the various Prepare actions is displayed in the message boxes. A progress display appears during the actual copy operation. How long the copy operation takes depends on the LAN structure and the volume of data to be copied. Generally it takes at least five minutes. After the copy operation has been completed, the iscsi target volume is assigned the label iscsi_boot. 32 BIOS Integrated iscsi Boot

33 iscsi Boot with Windows 2003 Activating Option ROM Scan 2.5 Activating Option ROM Scan Verify in the system BIOS that option ROM scan is activated for the NetXtreme controller you want to configure for iscsi boot. This setting is required for entering the MBA setup of the controller as well as for performing an iscsi boot later on. I It is recommended to activate option ROM scan only for the one controller you want to use for iscsi boot. This will prevent confusion about the sequence of MBA setups. How to activate option ROM scan for a network controller depends on the BIOS setup of your system. Examples are shown below for RX300 S3 and BX620 S3. RX300 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 9: PRIMERGY RX300 S3 BIOS setup Advanced menu Select Peripheral Configuration and press Ú to enter the submenu. BIOS Integrated iscsi Boot 33

34 Activating Option ROM Scan iscsi Boot with Windows 2003 Figure 10: PRIMERGY RX300 S3 BIOS setup Peripheral Configuration menu Select the LAN Remote Boot entry of the LAN controller that you want to configure for iscsi boot. Set the parameter for this channel to iscsi. I If the iscsi option for LAN Remote Boot is not available in your BIOS Setup, change the value to PXE instead. Use the À key to change to the Exit menu, save the changes and exit the BIOS Setup. 34 BIOS Integrated iscsi Boot

35 iscsi Boot with Windows 2003 Activating Option ROM Scan BX620 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 11: PRIMERGY BX620 S3 BIOS setup Advanced menu Select PCI Configuration and press Ú to enter the submenu. BIOS Integrated iscsi Boot 35

36 Activating Option ROM Scan iscsi Boot with Windows 2003 Figure 12: PRIMERGY BX620 S3 BIOS setup PCI Configuration menu Select the Onboard Lan <n> OPROM entry of the LAN controller that you want to configure for iscsi boot. Set the value to Enabled. Press {F10} to save the changes and exit the BIOS Setup. 36 BIOS Integrated iscsi Boot

37 iscsi Boot with Windows 2003 Configuring the Controller 2.6 Configuring the Controller for iscsi Boot Once the option ROM scan for the network controller port to be used for iscsi boot has been activated the next step is to configure it for either a static configuration or a dynamic configuration. This involves selecting iscsi as the boot protocol for the MBA and then setting the appropriate iscsi boot configuration options. Figure 13: MBA banner and setup prompt Start the server and press {Ctrl}-[S] when the MBA setup prompt for the controller to be configured is displayed. I The first line of this screen shows the MBA version of the controller. BIOS Integrated iscsi Boot 37

38 Configuring the Controller iscsi Boot with Windows 2003 Figure 14: MBA Configuration Menu Use the  or À keys to change the Boot Protocol option to iscsi. Press the {Ctrl}-[K] key to enter the iscsi Configuration Utility. 38 BIOS Integrated iscsi Boot

39 iscsi Boot with Windows 2003 Configuring the Controller Figure 15: Device List The Device List menu lists the server s network controllers. The controller for which the MBA setup was called is marked with a *. Select the controller that is marked with the * and press Ú. BIOS Integrated iscsi Boot 39

40 Configuring the Controller iscsi Boot with Windows 2003 Figure 16: iscsi Configuration Utility Enter the General Parameters configuration option. 40 BIOS Integrated iscsi Boot

41 iscsi Boot with Windows 2003 Configuring the Controller Figure 17: iscsi configuration screen with General Parameters With this menu, you set up the controller for a dynamic or static configuration. With a dynamic configuration, the IP parameters and the iscsi parameters can be taken from a DHCP server. With a static configuration, you must define these parameters in the MBA setup. The following table explains all the parameters you can set in the General Parameters menu. Option TCP/IP parameters via DHCP iscsi parameters via DHCP CHAP Authentication Description Controls whether the iscsi boot host software acquires the IP address information using DHCP (Enabled) or use a static IP configuration (Disabled). Controls whether the iscsi boot host software acquires its iscsi target parameters using DHCP (Enabled) or through a static configuration (Disabled). Controls whether the iscsi boot host software uses CHAP authentication when connecting to the iscsi target. If CHAP Authentication is enabled, the CHAP ID and CHAP Secret are entered through the iscsi Initiator Parameters Configuration screen. BIOS Integrated iscsi Boot 41

42 Configuring the Controller iscsi Boot with Windows 2003 Option Boot to iscsi target DHCP Vendor ID Link Up Delay Time Use TCP Timestamp Target as First HDD LUN Busy Retry Count Windows HBA Boot Mode Description Controls whether the iscsi boot host software attempts to boot from the iscsi target after successfully connecting to it. When the option is enabled, the iscsi boot host software immediately attempts to boot form the iscsi target. Otherwise, if it is disabled, the iscsi boot host software does not attempt to boot from the iscsi target and control returns to the system BIOS so that the next boot device may be used. This option is always set to Enabled. Controls how the iscsi boot host software interprets the Vendor Class ID field used during DHCP. If the Vendor Class ID field in the DHCP Offer packet matches the value in the field, the iscsi boot host software looks into the DHCP Option 43 fields for the required iscsi boot extensions. If DHCP is disabled, this value does not need to be set. Controls how long the iscsi boot host software waits, in seconds, after an Ethernet link is established before sending any data over the network. The valid values are 0 to 255. As an example, a user may need to set a value for this option if a network protocol, such as Spanning Tree, is enabled on the switch interface to the client system. Controls if the TCP Timestamp option is enabled or disabled. Allows specifying that the iscsi target drive will appear as the first hard drive in the system. Controls the number of connection retries the iscsi Boot initiator will attempt if the iscsi target LUN is busy. Set to disable when the host OS is configured for software initiator mode and to enable for HBA mode. This option is not supported with PRIMERGY servers. The following section describes the process for a static configuration using an example. You will find an example of a dynamic configuration in section on page 47. For information on configuring the DHCP server, see chapter Configuring a DHCP Server to Support iscsi Boot on page BIOS Integrated iscsi Boot

43 iscsi Boot with Windows 2003 Configuring the Controller Static iscsi Boot Configuration In a static configuration, the user must enter data for the system s IP address, the system s initiator IQN, and the target IQN. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Disabled iscsi parameters via DHCP Disabled CHAP Authentication Disabled Boot to iscsi target Enabled DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Disabled LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled I You can also combine static and dynamic elements in a configuration. You can use the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP to specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. For more information on dynamic configuration, see section Dynamic iscsi Boot Configuration on page 47 and chapter Configuring a DHCP Server to Support iscsi Boot on page 115. In this example both the TCP/IP parameters and the iscsi parameters are statically assigned. Exit the General Parameters menu by pressing [Esc] and, back in the Main Menu, open the Initiator Parameters menu. BIOS Integrated iscsi Boot 43

44 Configuring the Controller iscsi Boot with Windows 2003 Figure 18: iscsi configuration screen Initiator Parameters Set an appropriate value for IP Address, Subnet Mask, Default Gateway, Primary DNS, Secondary DNS and iscsi Name. I The iscsi Name must be identical with the Initiator Node Name of the Microsoft Software iscsi initiator, see section Preparing an Operating System Image on page 10. If you have enabled the CHAP Authentication option in the General Parameters menu, enter the appropriate CHAP ID and CHAP Secret. Exit the Initiator Parameters screen by pressing [Esc] and, back in the Main Menu, open the 1st Target Parameters menu. 44 BIOS Integrated iscsi Boot

45 iscsi Boot with Windows 2003 Configuring the Controller Figure 19: iscsi configuration screen with 1st Target Parameters Set the Connect option to Enabled to connect the client to the iscsi target when booting. Set the IP Address, TCP Port, Boot LUN, and iscsi Name options according to the values used when configuring the iscsi target (see section Configuring the iscsi target on page 7 for more details). Press [Esc] to return to the Main Menu. BIOS Integrated iscsi Boot 45

46 Configuring the Controller iscsi Boot with Windows 2003 Configuring a second iscsi target Figure 20: iscsi Configuration Utility The submenu 2nd Target Parameters allows you to configure a second iscsi target. This ensures higher availability during the system s boot phase: If the connection to the first target fails, the server is booted from the second target. Select the menu item 2nd Target Parameters and press Ú. The remaining process is the same as for the configuration of the first iscsi target, see page 43 (static configuration) or page 47 (dynamic configuration). 46 BIOS Integrated iscsi Boot

47 iscsi Boot with Windows 2003 Configuring the Controller Dynamic iscsi Boot Configuration For a dynamic configuration, you only have to specify that the IP address and target /initiator information of the system are provided via DHCP, see chapter Configuring a DHCP Server to Support iscsi Boot on page 115. If you use DHCP option 17, the parameters of the iscsi target are provided by the DHCP server and the iscsi initiator name from the MBA setup is used. If no iscsi initiator name was specified in the MBA setup, the controller generates the following initiator name: iqn com.broadcom iscsiboot, where the string is replaced with the controller s MAC address. In the case of DHCP option 43, all the parameter settings for the iscsi initiator, for the first and the second target, are provided by the DHCP server. Any settings in the MBA setup are ignored. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Enabled iscsi parameters via DHCP Enabled CHAP Authentication Disabled Boot to iscsi target Enabled DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Disabled LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled I Using the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP, you can also combine static and dynamic configurations. You can specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. For more information on static configuration see section Static iscsi Boot Configuration on page 43. BIOS Integrated iscsi Boot 47

48 Configuring the Controller iscsi Boot with Windows 2003 In this example both the TCP/IP parameters and the iscsi parameters are dynamically assigned. Press [Esc] to return to the Main Menu. 48 BIOS Integrated iscsi Boot

49 iscsi Boot with Windows 2003 Configuring the Controller Configuring a Secondary Controller By configuring a secondary controller you can configure a multi-path connection (MPIO connection) to an iscsi target. This increases the availability of the server during the boot phase and at runtime. If the connection to the iscsi target through the primary controller fails, the secondary controller takes over its function. I For the configuration of a secondary controller for iscsi to become effective, you must install MPIO with Microsoft Software Initiator, see page 12. The Microsoft iscsi Software Initiator automatically uses the configuration of the secondary controller that you set in the MBA setup. You configure the secondary controller in a similar way to that described in the sections Static iscsi Boot Configuration on page 43 and Dynamic iscsi Boot Configuration on page 47. Figure 21: iscsi Configuration Utility - Main Menu Select the menu item Secondary Device Parameters and press Ú. BIOS Integrated iscsi Boot 49

50 Configuring the Controller iscsi Boot with Windows 2003 Figure 22: iscsi Configuration Utility - Secondary Device Parameters Select the Secondary Device field and press Ú to open the Device List submenu. 50 BIOS Integrated iscsi Boot

51 iscsi Boot with Windows 2003 Configuring the Controller Figure 23: iscsi Configuration Utility - Device List Select the controller you want to configure and press Ú to return to the Secondary Device Parameters menu. The MAC address of the selected controller is automatically used as the value of the Secondary Device. BIOS Integrated iscsi Boot 51

52 Configuring the Controller iscsi Boot with Windows 2003 Figure 24: iscsi Configuration Utility - Secondary Device Parameters Set the parameter Multipath I/O Mode to Enabled or Disabled to define how the configuration parameters for the secondary controller are to be set. Enabled You only have to set the TCP/IP parameters for the secondary controller. The iscsi parameters are automatically inherited from the primary controller. Disabled You must set all the parameters for the secondary controller specifically. Select Configure Secondary: Invoke to open the submenu for configuring the the secondary controller. Proceed exactly as described for configuring the primary controller, see page 43 (static configuration) or page 47 (dynamic configuration). I If Multipath I/O Mode is set to Enabled, you only have to set the TCP/IP parameters: If DHCP is enabled: DHCP Vendor ID Link Up Delay Time 52 BIOS Integrated iscsi Boot

53 iscsi Boot with Windows 2003 Configuring the Controller If DHCP is disabled: IP address Subnet Mask Default Gateway Primary DNS Secondary DNS The configuration of the secondary controller is automatically transferred to the Microsoft iscsi Software Initiator Completing the Controller Configuration Figure 25: iscsi Configuration Utility - Main Menu In the Main Menu of the iscsi Setup, press [Esc] to complete the iscsi configuration and to return to the MBA Configuration Menu. In the MBA Configuration Menu, press [F4] to save the configuration. BIOS Integrated iscsi Boot 53

54 Performing an iscsi Boot iscsi Boot with Windows Performing an iscsi Boot Now that the system has been prepared for an iscsi boot and the operating system has been transferred to the iscsi target, the last step is to perform the actual boot. Verify in the system BIOS that the NetXtreme controller which is configured for iscsi boot is at the top of the boot order. Examples are shown below for the RX300 S3 and BX620 S3 BIOS setup menus. RX300 S3 Enter the BIOS Setup menu and select the Main menu. Figure 26: PRIMERGY RX300 S3 BIOS setup Main menu Select Boot Options and press Ú to enter the Boot Options submenu. 54 BIOS Integrated iscsi Boot

55 iscsi Boot with Windows 2003 Performing an iscsi Boot Figure 27: PRIMERGY RX300 S3 BIOS setup Boot Options menu In the Boot Options submenu select Boot Sequence and press Ú to enter the Boot Sequence submenu. BIOS Integrated iscsi Boot 55

56 Performing an iscsi Boot iscsi Boot with Windows 2003 Figure 28: PRIMERGY RX300 S3 BIOS setup Boot Sequence menu In the Boot Sequence submenu select the network controller (MBA) which is configured for iscsi boot and move it to the top-most position of the priority list. Use the À key to change to the Exit menu, save the changes and exit the BIOS Setup. 56 BIOS Integrated iscsi Boot

57 iscsi Boot with Windows 2003 Performing an iscsi Boot BX620 S3 Enter the BIOS Setup menu and select the Boot menu. Figure 29: PRIMERGY BX620 S3 BIOS setup Boot menu In the Boot Settings menu select the Boot Device Priority menu. BIOS Integrated iscsi Boot 57

58 Performing an iscsi Boot iscsi Boot with Windows 2003 Figure 30: PRIMERGY BX620 S3 BIOS setup Boot Device Priority menu In the Boot Device Priority menu select the network controller (Network:MBA) which is configured for iscsi boot and move it to top-most position of the priority list. Press {F10} to save the changes and exit the BIOS Setup. 58 BIOS Integrated iscsi Boot

59 iscsi Boot with Windows 2003 Performing an iscsi Boot If all goes well the system should boot to Windows over the network and operate as if it were a local disk drive. The following screen should be shown briefly as the iscsi boot driver connects to the iscsi target. Figure 31: iscsi Boot driver logging in the iscsi target If you encounter any problems, see the chapter Troubleshooting on page 127. BIOS Integrated iscsi Boot 59

60

61 3 iscsi Boot with Windows 2008 Server This chapter describes how to configure a system to support iscsi boot under Windows Unlike with Windows 2003, you can install Windows 2008 directly to the iscsi target. 3.1 Installation Overview Configuring a system to support iscsi boot under Windows 2008 consists of the following steps: Configuring the iscsi target (for general information, see page 7. For further information, please see the documentation provided by the iscsi target manufacturer.) System BIOS Settings (see page 62) Configuring the Controller for iscsi Boot (see page 68) Installing Windows 2008 on an iscsi Target (see page 80) Configuring an MPIO Connection (see page 86) Each of these steps will be discussed in detail, with appropriate examples, throughout the remainder of this chapter. 3.2 System Requirements The iscsi boot configuration described in this document requires Broadcom NetXtreme controllers and Windows Server BIOS Integrated iscsi Boot 61

62 System BIOS Settings iscsi Boot with Windows System BIOS Settings Verify in the system BIOS that option ROM scan is activated for the NetXtreme controller you want to configure for iscsi boot. This setting is required for entering the MBA setup of the controller as well as for performing an iscsi boot later on. I It is recommended that you activate option ROM scan only for the one controller you want to use for iscsi boot. This will prevent confusion about the sequence of MBA setups. Verify in the system BIOS that the NetXtreme controller configured for iscsi boot is at the top of the boot sequence ahead of the DVD drive. Before making this setting, you must restart the server. The restart is necessary to ensure that the NetXtreme controller for which option ROM scan was activated is recognized by the system BIOS as a possible boot drive. How you make these settings depends on the BIOS setup of your system. Examples are shown below for the RX300 S3 and BX620 S3. 62 BIOS Integrated iscsi Boot

63 iscsi Boot with Windows 2008 System BIOS Settings RX300 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 32: PRIMERGY RX300 S3 BIOS setup Advanced menu Select Peripheral Configuration and press Ú to enter the submenu. BIOS Integrated iscsi Boot 63

64 System BIOS Settings iscsi Boot with Windows 2008 Figure 33: PRIMERGY RX300 S3 BIOS setup Peripheral Configuration menu Select the LAN Remote Boot entry of the LAN controller that you want to configure for iscsi boot. Set the parameter for this channel to iscsi. Use the À key to change to the Exit menu, save the changes and exit the BIOS Setup. Restart the server. Enter the BIOS Setup menu. In the Main menu select Boot Options Boot Sequence. 64 BIOS Integrated iscsi Boot

65 iscsi Boot with Windows 2008 System BIOS Settings Figure 34: PRIMERGY RX300 S3 BIOS setup Boot Sequence menu Arrange the boot sequence such that the NetXtreme controller configured for iscsi boot is at the top ahead of the DVD drive. Use the À key to change to the Exit menu, save the changes and exit the BIOS Setup. BIOS Integrated iscsi Boot 65

66 System BIOS Settings iscsi Boot with Windows 2008 BX620 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 35: PRIMERGY BX620 S3 BIOS setup Advanced menu Select PCI Configuration and press Ú to enter the submenu. 66 BIOS Integrated iscsi Boot

67 iscsi Boot with Windows 2008 System BIOS Settings Figure 36: PRIMERGY BX620 S3 BIOS setup PCI Configuration menu Select the Onboard Lan <n> OPROM entry of the LAN controller that you want to configure for iscsi boot. Set the value to Enabled. Press {F10} to save the changes and exit the BIOS Setup. Restart the server. Enter the BIOS Setup menu. Use the À key to change to the Boot menu. Arrange the boot sequence such that the NetXtreme controller configured for iscsi boot is at the top ahead of the DVD drive. Press {F10} to save the changes and exit the BIOS Setup. BIOS Integrated iscsi Boot 67

68 Configuring the Controller iscsi Boot with Windows Configuring the Controller for iscsi Boot Once the option ROM scan for the network controller port to be used for iscsi boot has been activated, the next step is to configure it for either a static or a dynamic configuration. This involves selecting iscsi as the boot protocol for the MBA and then setting the appropriate iscsi boot configuration options. Figure 37: MBA banner and setup prompt Start the server and press {Ctrl}-[S] when you see the MBA setup prompt for the controller to be configured. I The first line of this screen shows the MBA version of the controller. 68 BIOS Integrated iscsi Boot

69 iscsi Boot with Windows 2008 Configuring the Controller Figure 38: MBA Configuration Menu Make sure that the Boot Protocol parameter is set to iscsi. Press the {Ctrl}-[K] key to enter the iscsi Configuration Utility. BIOS Integrated iscsi Boot 69

70 Configuring the Controller iscsi Boot with Windows 2008 Figure 39: Device List The Device List menu lists the server s network controllers. The controller for which the MBA setup was called is marked with a *. Select the controller marked with the * and press Ú. 70 BIOS Integrated iscsi Boot

71 iscsi Boot with Windows 2008 Configuring the Controller Figure 40: iscsi Configuration Utility - Main Menu Open the General Parameters submenu. BIOS Integrated iscsi Boot 71

72 Configuring the Controller iscsi Boot with Windows 2008 Figure 41: iscsi configuration screen with General Parameters With this menu, you set up the controller for a dynamic or static configuration. With a dynamic configuration, the IP parameters and the iscsi parameters can be taken from a DHCP server. With a static configuration, you must define these parameters in the MBA setup. The following table explains all the parameters you can set in the General Parameters menu. TCP/IP parameters via DHCP Controls whether the iscsi boot host software acquires the IP address information using DHCP (Enabled) or uses a static IP configuration (Disabled). iscsi parameters via DHCP Controls whether the iscsi boot host software acquires its iscsi target parameters using DHCP (Enabled) or through a static configuration (Disabled). CHAP Authentication Controls whether the iscsi boot host software uses CHAP authentication when connecting to the iscsi target. If CHAP Authentication is enabled, the CHAP ID and CHAP Secret are entered in the iscsi Initiator Parameters Configuration screen. 72 BIOS Integrated iscsi Boot

73 iscsi Boot with Windows 2008 Configuring the Controller Boot to iscsi target Controls whether the iscsi boot host software attempts to boot from the iscsi target after successfully connecting to it. When this option is enabled, the iscsi boot host software immediately attempts to boot from the iscsi target. Otherwise, if it is disabled, the iscsi boot host software does not attempt to boot from the iscsi target and control returns to the system BIOS so that the next boot device may be used. I This option must be set to Disabled before the Windows 2008 installation and to Enabled after the Windows 2008 installation. DHCP Vendor ID Controls how the iscsi boot host software interprets the Vendor Class ID field used during DHCP. If the Vendor Class ID field in the DHCP Offer packet matches the value in the field, the iscsi boot host software searches the DHCP Option 43 fields for the required iscsi boot extensions. If DHCP is disabled, this value does not need to be set. Link Up Delay Time Controls how long the iscsi boot host software waits, in seconds, after an Ethernet link is established before sending any data over the network. The valid values are 0 through 255. As an example, a user may need to set a value for this option if a network protocol, such as Spanning Tree, is enabled on the switch interface to the client system. Use TCP Timestamp Controls whether the TCP Timestamp option is enabled or disabled. Target as First HDD Allows you to specify that the iscsi target drive will appear as the first hard drive in the system. I This option must be set to Enabled before the Windows 2008 installation and to Disabled after the Windows 2008 installation. LUN Busy Retry Count Controls the number of connection retries the iscsi Boot initiator will attempt if the iscsi target LUN is busy. Windows HBA Boot Mode Set to Disabled when the host OS is configured for software initiator mode and to Enabled for HBA mode. This option is not supported with PRIMERGY servers. BIOS Integrated iscsi Boot 73

74 Configuring the Controller iscsi Boot with Windows 2008 The following section describes the process for a static configuration using an example. You will find an example of a dynamic configuration in section on page 77. For how to configure the DHCP server, see chapter Configuring a DHCP Server to Support iscsi Boot on page Static iscsi Boot Configuration In a static configuration, the user must enter data for the system s IP address, the system s initiator IQN, and the target IQN. This section describes the settings you must make before the Windows setup so that Windows is installed on the iscsi target. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Disabled iscsi parameters via DHCP Disabled CHAP Authentication Disabled Boot to iscsi target Disabled (must be set to Enabled after the Windows 2008 installation, see page 72) DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Enabled (must be set to Disabled after the Windows 2008 installation, see page 72) LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled I You can also combine static and dynamic elements in a configuration. You can use the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP to specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. 74 BIOS Integrated iscsi Boot

75 iscsi Boot with Windows 2008 Configuring the Controller For more information on dynamic configuration, see section Dynamic iscsi Boot Configuration on page 77 and chapter Configuring a DHCP Server to Support iscsi Boot on page 115. In this example both the TCP/IP parameters and the iscsi parameters are statically assigned. Exit the General Parameters menu by pressing [Esc] and, back in the Main Menu, open the Initiator Parameters menu. Figure 42: iscsi configuration screen Initiator Parameters Set an appropriate value for IP Address, Subnet Mask, Default Gateway, Primary DNS, Secondary DNS and iscsi Name. If you have enabled the CHAP Authentication option in the General Parameters menu, enter the appropriate CHAP ID and CHAP Secret. Exit the Initiator Parameters screen by pressing [Esc] and, back in the Main Menu, open the 1st Target Parameters menu. BIOS Integrated iscsi Boot 75

76 Configuring the Controller iscsi Boot with Windows 2008 Figure 43: iscsi Configuration Utility - 1st Target Parameters Set the Connect option to Enabled to connect the client to the iscsi target when booting. This setting ensures that Windows 2008 can be installed directly on the iscsi target, see Installing Windows 2008 on an iscsi Target on page 80. Set the IP Address, TCP Port, Boot LUN, and iscsi Name options according to the values used when configuring the iscsi target (see section Configuring the iscsi target on page 7 for more details). Press [Esc] to return to the Main Menu. The submenu 2nd Target Parameters allows you to configure a second iscsi target. This ensures higher availability during the system s boot phase: If the connection to the first target fails, the server is booted from the second target. Select the menu item 2nd Target Parameters and press Ú. The remaining process is the same as for the configuration of the first iscsi target, see page 74 (static configuration) or page 77 (dynamic configuration). 76 BIOS Integrated iscsi Boot

77 iscsi Boot with Windows 2008 Configuring the Controller Dynamic iscsi Boot Configuration For a dynamic configuration, you only have to specify that the IP address and target /initiator information of the system are provided via DHCP, see chapter Configuring a DHCP Server to Support iscsi Boot on page 115. If you use DHCP option 17, the parameters of the iscsi target are provided by the DHCP server and the iscsi initiator name from the MBA setup is used. If no iscsi initiator name was specified in the MBA setup, the controller generates the following initiator name: iqn com.broadcom iscsiboot, where the string is replaced with the controller s MAC address. In the case of DHCP option 43, all the parameter settings for the iscsi initiator, for the first and the second target, are provided by the DHCP server. Any settings in the MBA setup are ignored. This section describes the settings you must make before the Windows setup so that Windows is installed on the iscsi target. You will need to change some of the parameters once Windows is installed. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Enabled iscsi parameters via DHCP Enabled CHAP Authentication Disabled Boot to iscsi target Disabled (must be set to Enabled after the Windows 2008 installation, see page 72) DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Enabled (must be set to Disabled after the Windows 2008 installation, see page 72) LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled BIOS Integrated iscsi Boot 77

78 Configuring the Controller iscsi Boot with Windows 2008 I Using the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP, you can also combine static and dynamic configurations. You can specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. For more information on static configuration see section Static iscsi Boot Configuration on page 74. In this example both the TCP/IP parameters and the iscsi parameters are dynamically assigned. Press [Esc] to return to the Main Menu. 78 BIOS Integrated iscsi Boot

79 iscsi Boot with Windows 2008 Configuring the Controller Completing the Controller Configuration Figure 44: iscsi Configuration Utility - Main Menu In the Main Menu of the iscsi Setup, press [Esc] to complete the iscsi configuration and to return to the MBA Configuration Menu. In the MBA Configuration Menu, press [F4] to save the configuration. Then press [Esc] to exit the MBA setup. BIOS Integrated iscsi Boot 79

80 Installing Windows on an iscsi Target iscsi Boot with Windows Installing Windows 2008 on an iscsi Target Insert the operating system DVD in the DVD drive and switch on the server. Figure 45: Starting the Windows installation The system connects to the iscsi target and boots from the second drive in the boot sequence, which you defined in the system BIOS, see page 62. This should be the DVD drive with the installation medium. Once the boot process is completed, the entry menu of the Windows setup is displayed. Select the interface language, time zone and currency as well as the country variant of the connected keyboard. Click Next. The Windows Server 2008 welcome screen is displayed. Click Install Now. 80 BIOS Integrated iscsi Boot

81 iscsi Boot with Windows 2008 Installing Windows on an iscsi Target Figure 46: Selecting the Windows Server variant Select Windows Server 2008 Enterprise (Full Installation) for your system architecture. Click Next. You are now prompted to accept the Microsoft End User License Agreement (EULA). Click Accept. The screen for selecting the installation type is displayed. Select the option Custom (advanced). BIOS Integrated iscsi Boot 81

82 Installing Windows on an iscsi Target iscsi Boot with Windows 2008 In the following screen, the LUN released for the server on the iscsi target is shown as the installation destination. Figure 47: Selecting the installation destination Select the installation destination. I If no iscsi target LUN is displayed in this menu, there are two possible reasons: The iscsi parameters in the controller s MBA setup do not match the corresponding parameters in the configuration of the iscsi target. In this case you will need to check the iscsi parameters in the controller s MBA setup, see page 68, and restart the Windows setup. A controller of type Broadcom NetXtreme II is installed in your server. In this case you must additionally install the Virtual Bus driver and the NDIS driver for the controller. The current driver package (BCM5708S) is available at To install the drivers, proceed as follows: 82 BIOS Integrated iscsi Boot

83 iscsi Boot with Windows 2008 Installing Windows on an iscsi Target Copy the Virtual Bus and NDIS drivers onto a USB stick or a diskette. Click Load Driver, navigate to the storage location of the Virtual Bus driver, and install it. Click Load Driver again, navigate to the storage location of the NDIS driver, and install it. If the iscsi target LUN is not displayed, click Refresh in the Where do you want to install Windows? screen. To proceed, select the iscsi target LUN on which you want to install Windows. Click Next to continue in the standard Windows setup. Figure 48: Installing Windows I During the installation process, Windows Setup will trigger a restart. This may cause the server to crash. If so, you will need to start it manually and, in the boot phase, set the iscsi configuration of the NetXtreme controller for routine operation, see section 3.6. BIOS Integrated iscsi Boot 83

84 Completing the controller configuration iscsi Boot with Windows Completing the Controller Configuration After installing Windows Server 2008 on the iscsi target, you must adjust the iscsi configuration of the NetXtreme controller for routine operation. Start the server. Press {Ctrl}-[S] when you see the MBA setup prompt for the controller to be configured. Press {Ctrl}-[K] to open the iscsi configuration menu. In the Device List menu, select the controller marked with a * and press Ú to open the Main Menu of the iscsi configuration. Open the General Parameters submenu. Figure 49: iscsi Configuration Utility - General Parameters Set the parameter Boot to iscsi Target to Enabled. Set the parameter Target as First HDD to Disabled. Press [Esc] to exit the General Parameters menu and return to the Main Menu. In the Main Menu of the iscsi setup, press [Esc] to complete the iscsi configuration and return to the MBA Configuration Menu. 84 BIOS Integrated iscsi Boot

85 iscsi Boot with Windows 2008 Completing the controller configuration In the MBA Configuration Menu, press [F4] to save the configuration. Press [Esc] to exit the MBA setup. The server startup continues and Windows is loaded from the iscsi target. BIOS Integrated iscsi Boot 85

86 Configuring an MPIO connection iscsi Boot with Windows Configuring an MPIO Connection Under Windows 2008 you can configure a multipath connection (MPIO connection) to an iscsi target at operating system level. With MPIO you increase the availability of the server during the boot phase and during routine operation. If the connection to the iscsi target via the primary controller fails, the secondary controller takes over its function. To set up a multipath connection, proceed as follows: Start the Windows Server Manager. Figure 50: Windows 2008 Server Manager Open the Features menu and click Add Features. 86 BIOS Integrated iscsi Boot

87 iscsi Boot with Windows 2008 Configuring an MPIO connection Figure 51: Windows 2008 Server Manager Select Multipath I/O and click Next. The Confirm Installation Selections menu is displayed. BIOS Integrated iscsi Boot 87

88 Configuring an MPIO connection iscsi Boot with Windows 2008 Following the Windows restart, you can configure the MPIO connection with the program Start Programs Administrative Tools MPIO. Figure 52: Windows 2008 MPIO Properties Open the Discover Multi-Paths tab. Select the option Add support for iscsi devices. For the rest of the MPIO configuration procedure, please follow the instructions in the Windows 2008 Help. 88 BIOS Integrated iscsi Boot

89 4 iscsi Boot with SuSE Linux Enterprise Server Installation Overview The following steps are necessary to configure a system to support iscsi boot processes under SuSE Linux: Configuring the iscsi target (for general information, see page 7. For further information, please see the documentation provided by the iscsi target manufacturer.) Activating Option ROM Scan (see page 90) Configuring the Controller for iscsi Boot (see page 94). Installing Linux on an iscsi Target (see page 107) All these steps are described in detail in this document with appropriate examples. 4.2 System Requirements The iscsi boot configuration described in this chapter requires Broadcom NetXtreme controllers and SuSE Linux Enterprise Server 10 with Service Pack 2 (SLES 10 SP2). BIOS Integrated iscsi Boot 89

90 Activating the Option ROM Scan iscsi Boot with SLES Activating Option ROM Scan Verify in the system BIOS that option ROM scan is activated for the NetXtreme controller you want to configure for iscsi boot. This setting is required for entering the MBA setup of the controller as well as for performing an iscsi boot later on. I It is recommended to activate option ROM scan only for the one controller you want to use for iscsi boot. This will prevent confusion about the sequence of MBA setups. How to activate option ROM scan for a network controller depends on the BIOS setup of your system. Examples are shown below for RX300 S3 and BX620 S3. RX300 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 53: PRIMERGY RX300 S3 BIOS setup Advanced menu Select Peripheral Configuration and press Ú to enter the submenu. 90 BIOS Integrated iscsi Boot

91 iscsi Boot with SLES 10 Activating the Option ROM Scan Figure 54: PRIMERGY RX300 S3 BIOS setup Peripheral Configuration menu Select the LAN Remote Boot entry of the LAN controller that you want to configure for iscsi boot. Set the parameter for this channel to iscsi. I If the iscsi option for LAN Remote Boot is not available in your BIOS Setup, change the value to PXE instead. Check the settings in the menu Main Boot Options. Make sure that the NetXtreme controller configured for the iscsi boot process is second in the starting order after the DVD drive. Use the Ú key to change to the Exit menu, save the changes and exit the BIOS Setup. BIOS Integrated iscsi Boot 91

92 Activating the Option ROM Scan iscsi Boot with SLES 10 BX620 S3 Enter the BIOS Setup menu and select the Advanced menu. Figure 55: PRIMERGY BX620 S3 BIOS setup Advanced menu Select PCI Configuration and press Ú to enter the submenu. 92 BIOS Integrated iscsi Boot

93 iscsi Boot with SLES 10 Activating the Option ROM Scan Figure 56: PRIMERGY BX620 S3 BIOS setup PCI Configuration menu Select the Onboard Lan <n> OPROM entry of the LAN controller that you want to configure for iscsi boot. Set the value to Enabled. Check the settings in the BIOS Setup menu Boot. Make sure that the NetXtreme controller configured for the iscsi boot process is second in the starting order after the DVD drive. Press {F10} to save the changes and exit the BIOS Setup. BIOS Integrated iscsi Boot 93

94 Configuring the Controller iscsi Boot with SLES Configuring the Controller for iscsi Boot Once the option ROM scan for the network controller port to be used for iscsi boot has been activated the next step is to configure it for either a static configuration or a dynamic configuration. This involves selecting iscsi as the boot protocol for the MBA and then setting the appropriate iscsi boot configuration options. Figure 57: MBA banner and setup prompt Start the server and press {Ctrl}-[S] when the MBA setup prompt for the controller to be configured is displayed. I The first line of this screen shows the MBA version of the controller. 94 BIOS Integrated iscsi Boot

95 iscsi Boot with SLES 10 Configuring the Controller Figure 58: MBA Configuration Menu Use the  or À keys to change the Boot Protocol option to iscsi. Press the {Ctrl}-[K] key to enter the iscsi Configuration Utility. BIOS Integrated iscsi Boot 95

96 Configuring the Controller iscsi Boot with SLES 10 Figure 59: Device List The Device List menu lists the server s network controllers. The controller for which the MBA setup was called is marked with a *. Select the controller that is marked with the * and press Ú. 96 BIOS Integrated iscsi Boot

97 iscsi Boot with SLES 10 Configuring the Controller Figure 60: iscsi Configuration Utility Enter the General Parameters configuration option. BIOS Integrated iscsi Boot 97

98 Configuring the Controller iscsi Boot with SLES 10 Figure 61: iscsi configuration screen with General Parameters With this menu, you set up the controller for a dynamic or static configuration. With a dynamic configuration, the IP parameters and the iscsi parameters can be taken from a DHCP server. With a static configuration, you must define these parameters in the MBA setup. The following table explains all the parameters you can set in the General Parameters menu. Option TCP/IP parameters via DHCP iscsi parameters via DHCP CHAP Authentication Description Controls whether the iscsi boot host software acquires the IP address information using DHCP (Enabled) or use a static IP configuration (Disabled). Controls whether the iscsi boot host software acquires its iscsi target parameters using DHCP (Enabled) or through a static configuration (Disabled). Controls whether the iscsi boot host software uses CHAP authentication when connecting to the iscsi target. If CHAP Authentication is enabled, the CHAP ID and CHAP Secret are entered through the iscsi Initiator Parameters Configuration screen. 98 BIOS Integrated iscsi Boot

99 iscsi Boot with SLES 10 Configuring the Controller Option Boot to iscsi target DHCP Vendor ID Link Up Delay Time Use TCP Timestamp Target as First HDD LUN Busy Retry Count Windows HBA Boot Mode Description Controls whether the iscsi boot host software attempts to boot from the iscsi target after successfully connecting to it. When the option is enabled, the iscsi boot host software immediately attempts to boot form the iscsi target. Otherwise, if it is disabled, the iscsi boot host software does not attempt to boot from the iscsi target and control returns to the system BIOS so that the next boot device may be used. This option is always set to Enabled. Controls how the iscsi boot host software interprets the Vendor Class ID field used during DHCP. If the Vendor Class ID field in the DHCP Offer packet matches the value in the field, the iscsi boot host software looks into the DHCP Option 43 fields for the required iscsi boot extensions. If DHCP is disabled, this value does not need to be set. Controls how long the iscsi boot host software waits, in seconds, after an Ethernet link is established before sending any data over the network. The valid values are 0 to 255. As an example, a user may need to set a value for this option if a network protocol, such as Spanning Tree, is enabled on the switch interface to the client system. Controls if the TCP Timestamp option is enabled or disabled. Allows you to specify that the iscsi target drive will appear as the first hard drive in the system. If the server has local hard disk drives, Target as First HDD must be set to Enabled. Controls the number of connection retries the iscsi Boot initiator will attempt if the iscsi target LUN is busy. Set to disable when the host OS is configured for software initiator mode and to enable for HBA mode. This option is not supported with PRIMERGY servers. The following section describes the process for a static configuration using an example. You will find an example of a dynamic configuration in section on page 104. For information on configuring the DHCP server, see chapter Configuring a DHCP Server to Support iscsi Boot on page 115. BIOS Integrated iscsi Boot 99

100 Configuring the Controller iscsi Boot with SLES Static iscsi Boot Configuration In a static configuration, the user must enter data for the system s IP address, the system s initiator IQN, and the target IQN. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Disabled iscsi parameters via DHCP Disabled CHAP Authentication Disabled Boot to iscsi target Enabled DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Disabled 1 LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled 1 If there are local hard disks, Target as First HDD must be set to Enabled. I You can also combine static and dynamic elements in a configuration. You can use the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP to specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. For more information on dynamic configuration, see section Dynamic iscsi Boot Configuration on page 104 and chapter Configuring a DHCP Server to Support iscsi Boot on page 115. In this example both the TCP/IP parameters and the iscsi parameters are statically assigned. Exit the General Parameters menu by pressing [Esc] and, back in the Main Menu, open the Initiator Parameters menu. 100 BIOS Integrated iscsi Boot

101 iscsi Boot with SLES 10 Configuring the Controller Figure 62: iscsi configuration screen Initiator Parameters Set an appropriate value for IP Address, Subnet Mask, Default Gateway, Primary DNS, Secondary DNS and iscsi Name. I The iscsi Name must be identical with the Initiator Name defined in the Linux setup, see section Installing Linux on an iscsi Target on page 107. If you have enabled the CHAP Authentication option in the General Parameters menu, enter the appropriate CHAP ID and CHAP Secret. Exit the Initiator Parameters screen by pressing [Esc] and, back in the Main Menu, open the 1st Target Parameters menu. BIOS Integrated iscsi Boot 101

102 Configuring the Controller iscsi Boot with SLES 10 Figure 63: iscsi configuration screen with 1st Target Parameters Set the Connect option to Enabled to connect the client to the iscsi target when booting. Set the IP Address, TCP Port, Boot LUN, and iscsi Name options according to the values used when configuring the iscsi target (see section Configuring the iscsi target on page 7 for more details). Press [Esc] to return to the Main Menu. 102 BIOS Integrated iscsi Boot

103 iscsi Boot with SLES 10 Configuring the Controller Configuring a second iscsi target Figure 64: iscsi Configuration Utility The submenu 2nd Target Parameters allows you to configure a second iscsi target. This ensures higher availability during the system s boot phase: If the connection to the first target fails, the server is booted from the second target. Select the menu item 2nd Target Parameters and press Ú. The remaining process is the same as for the configuration of the first iscsi target, see page 100 (static configuration) or page 104 (dynamic configuration). BIOS Integrated iscsi Boot 103

104 Configuring the Controller iscsi Boot with SLES Dynamic iscsi Boot Configuration For a dynamic configuration, you only have to specify that the IP address and target /initiator information of the system are provided via DHCP, see chapter Configuring a DHCP Server to Support iscsi Boot on page 115. If you use DHCP option 17, the parameters of the iscsi target are provided by the DHCP server and the iscsi initiator name from the MBA setup is used. If no iscsi initiator name was specified in the MBA setup, the controller generates the following initiator name: iqn com.broadcom iscsiboot, where the string is replaced with the controller s MAC address. In the case of DHCP option 43, all the parameter settings for the iscsi initiator, for the first and the second target, are provided by the DHCP server. Any settings in the MBA setup are ignored. Set the parameters in the General Parameters menu as follows: TCP/IP parameters via DHCP Enabled iscsi parameters via DHCP Enabled CHAP Authentication Disabled Boot to iscsi target Enabled DHCP Vendor ID BRCM ISAN Link Up Delay Time 0 Use TCP Timestamp Disabled Target as First HDD Disabled 1 LUN Busy Retry Count 0 Windows HBA Boot Mode Disabled 1 If there are local hard disks, Target as First HDD must be set to Enabled. I You can also combine static and dynamic elements in a configuration. You can use the parameters TCP/IP parameters via DHCP and iscsi parameters via DHCP to specify that only the iscsi parameters are to be statically configured, while the TCP/IP parameters are obtained via DHCP or vice versa. 104 BIOS Integrated iscsi Boot

105 iscsi Boot with SLES 10 Configuring the Controller For more information on dynamic configuration, see section Dynamic iscsi Boot Configuration on page 104 and chapter Configuring a DHCP Server to Support iscsi Boot on page 115. In this example both the TCP/IP parameters and the iscsi parameters are dynamically assigned. Press [Esc] to return to the Main Menu. BIOS Integrated iscsi Boot 105

106 Configuring the Controller iscsi Boot with SLES Completing the Controller Configuration Figure 65: iscsi Configuration Utility - Main Menu In the Main Menu of the iscsi Setup, press [Esc] to complete the iscsi configuration and to return to the MBA Configuration Menu. In the MBA Configuration Menu, press [F4] to save the configuration. 106 BIOS Integrated iscsi Boot

107 iscsi Boot with SLES 10 Installing Linux on an iscsi Target 4.5 Installing Linux on an iscsi Target I Before you begin the installation, bear in mind the following: For an operating system setup via network (NFS/FTP), the iscsi target and the server to be installed must be in the same LAN segment. During installation of the operating system, only one LAN port is active. By default this is eth0. The boot option netsetup=1 does allow another LAN port to be selected during installation, but there is only ever one LAN port active! If the server has one or more local hard disk drives, the parameter Target as first HDD in the iscsi Setup menu General Parameters must be set to Enabled, see section Configuring the Controller for iscsi Boot on page 94. BIOS Integrated iscsi Boot 107

108 Installing Linux on an iscsi Target iscsi Boot with SLES 10 Start the operating system setup for SLES 10 SP2 from the installation medium. Figure 66: Starting SuSE Linux installation Enter the following parameter as a boot option: withiscsi=1 Follow the instructions of the installation program until you get to the iscsi Initiator Overview menu. 108 BIOS Integrated iscsi Boot

109 iscsi Boot with SLES 10 Installing Linux on an iscsi Target Figure 67: iscsi Initiator Overview Service tab In the Initiator Name field, enter the IQN name of the iscsi initiator. I The Initiator Name must be identical with the iscsi Name you defined in the controller configuration, see page 94 Open the Connected Targets tab. BIOS Integrated iscsi Boot 109

110 Installing Linux on an iscsi Target iscsi Boot with SLES 10 Figure 68: iscsi Initiator Overview Connected Targets tab Click Add to add the target on which you want to install the operating system. 110 BIOS Integrated iscsi Boot

111 iscsi Boot with SLES 10 Installing Linux on an iscsi Target Figure 69: iscsi Initiator Discovery Adding the target Enter the IP address of the target. Click Next. BIOS Integrated iscsi Boot 111

112 Installing Linux on an iscsi Target iscsi Boot with SLES 10 Figure 70: iscsi Initiator Discovery (Connected = False) Select the target. Click Connect to connect to the target. 112 BIOS Integrated iscsi Boot

113 iscsi Boot with SLES 10 Installing Linux on an iscsi Target The Connected column displays the value True for the selected target. Figure 71: iscsi Initiator Discovery (Connected = True) Click Next to return to the iscsi Initiator Overview menu. BIOS Integrated iscsi Boot 113

114 Installing Linux on an iscsi Target iscsi Boot with SLES 10 Figure 72: iscsi Initiator Overview Connected Targets tab Click the Toggle Start Up button to change the Start Up parameter from manual to automatic. This ensures that the system is automatically connected to the target on startup. Click Next to proceed in the standard Linux setup. The operating system is installed on the target. Once the Linux setup is complete, the server can be booted from the target. 114 BIOS Integrated iscsi Boot

115 5 Configuring a DHCP Server to Support iscsi Boot 5.1 DHCP Options The DHCP protocol includes a number of options which provide configuration information to the DHCP client. Common examples of such options include the IP address of the DNS server (option 6), the default lease time for the IP address being assigned (option 51), and so forth. For iscsi boot, two different DHCP configurations are supported by the NetXtreme controller. DHCP Option 17, Root Path The first configuration uses DHCP option 17 (or the root path) to pass the iscsi target information to the iscsi client. The format of the root path option is defined in RFC 4173 as follows: iscsi:servername:protocol:port:lun:targetname The parameters are defined as follows: iscsi servername protocol port LUN targetname A literal string The IP address or FQDN of the iscsi target The IP protocol used to access the iscsi target. Currently only TCP is supported, so the protocol is 6. The port number associated with the protocol. The standard port number for iscsi is The Logical Unit Number to use on the iscsi target The target name in either IQN or EUI format (for details of both IQN and EUI formats, refer to RFC 3720). An example of an IQN name would be iqn com.broadcom:iscsitarget. Using the root path option the DHCP server can assign a single iscsi target to a DHCP client. BIOS Integrated iscsi Boot 115

116 DHCP Option 17 Configuring a DHCP Server DHCP Option 43, Vendor Specific Information The second configuration uses DHCP option 43 (or Vendor Specific Information) to provide more configuration options to the iscsi client. In this configuration, three additional sub-options are provided which assign the initiator IQN to the iscsi boot client (something which must be statically configured when using DHCP option 17) along with two iscsi target IQNs which can be used to boot. The format for the iscsi target IQN is the same as that of DHCP option 17 above, while the iscsi initiator IQN is simply the initiator s IQN. Using DHCP option 43 requires a little more configuration than DHCP option 17 but provides a richer environment and provides more configuration options to the IT administrator. Broadcom recommends that customers use DHCP option 43 when performing dynamic iscsi boot configuration. 5.2 Configuring the DHCP Server to Support DHCP Option 17 Since some DHCP servers are not currently configured to support iscsi boot out-of-the-box, the following discussion will provide the information necessary to properly configure a Windows 2003 Server to support iscsi boot. Assumptions For the purposes of this example, the following configuration is assumed: The DHCP server IP address is The DHCP server will distribute addresses to for iscsi clients The iscsi target server IP address is The iscsi target TCP port number is 3260 The iscsi target server IQN is iqn com.broadcom:iscsi-target The iscsi client MAC address is 00:10:18:01:02: BIOS Integrated iscsi Boot

117 Configuring a DHCP Server DHCP Option 17 Configuring the Microsoft Windows 2003 DHCP Server By default Microsoft Windows does not support iscsi boot out-of-the-box. The Windows DHCP server must be configured to add the additional DHCP options required by iscsi boot. The following steps are applicable to Microsoft Windows Server Open a command prompt on the DHCP server to be configured. 2. Create a new scope for the iscsi DHCP clients: C:\>netsh dhcp server add scope iscsi Clients 3. Add a range of IP addresses for the DHCP server to give to the iscsi clients: C:\>netsh dhcp server scope add iprange Create a reservation for a client system with the MAC address 00:10:18:01:02:03 to receive the IP address : C:\>netsh dhcp server scope add reservedip Broadcom iscsi Client Broadcom iscsi Client 5. Set the iscsi target (target IP address , TCP port 3260, LUN 1, IQN iqn com.broadcom:iscsi-target): C:\>netsh dhcp server scope set reservedoptionvalue string iscsi: :6:3260:1:iqn com.broadcom:iscsi- target BIOS Integrated iscsi Boot 117

118 DHCP Option 17 Configuring a DHCP Server Finally, if the DHCP server has not already been authorized to assign IP addresses, authorize it. The final result should appear as follows in the DHCP manager: 118 BIOS Integrated iscsi Boot

119 Configuring a DHCP Server DHCP Option Configuring the DHCP Server to Support DHCP Option 43 Since some DHCP servers are not currently configured to support iscsi boot out-of-the- box, the following will provide the information necessary to properly configure a Windows 2003 Server to support iscsi boot. Assumptions For the purposes of this example, the following configuration is assumed: The DHCP server IP address is The DHCP server will distribute addresses to for iscsi clients The iscsi target server IP address is The iscsi target TCP port number is 3260 The iscsi target server IQN is iqn com.broadcom:iscsi-target The iscsi client MAC address is 00:10:18:01:02:03 The iscsi initiator IQN is iqn com.broadcom: Configuring the Microsoft Windows 2003 DHCP Server By default Microsoft Windows does not support iscsi boot out-of-the-box. The Windows DHCP server must be configured to add the additional DHCP options required by iscsi boot. The following steps are applicable to Microsoft Windows Server 2003: V CAUTION! When entering the following commands, please note that the string BRCM ISAN is case-sensitive. 1. Open a command prompt on the DHCP server to be configured. 2. Create a new vendor class called BRCM ISAN: C:\>netsh dhcp server add class BRCM ISAN Broadcom iscsi DHCP Options BRCM ISAN 1 BIOS Integrated iscsi Boot 119

120 DHCP Option 43 Configuring a DHCP Server 3. Create sub-options 201 to 203 for the new vendor class: C:\>netsh dhcp server add optiondef 201 Primary Boot Target IQN and Boot Parameters string 0 vendor= BRCM ISAN comment= Primary iscsi boot target and associated boot parameters C:\>netsh dhcp server add optiondef 202 Secondary Boot Target IQN and Boot Parameters string 0 vendor= BRCM ISAN comment= Secondary iscsi boot target and associated boot parameters C:\>netsh dhcp server add optiondef 203 Initiator IQN string 0 vendor= BRCM ISAN comment= InitiatorIQN 4. Create a new scope for the iscsi DHCP clients: C:\>netsh dhcp server add scope iscsi Clients 5. Add a range of IP addresses for the DHCP server to give to the iscsi clients: C:\>netsh dhcp server scope add iprange Add option 60 and set option 60 for the scope created in the previous step: C:\>netsh dhcp server add optiondef 60 ClassID string 0 C:\>netsh dhcp server scope set optionvalue 60 string BRCM ISAN 7. Create a reservation for a client system with the MAC address 00:10:18:01:02:03 to receive the IP address : C:\>netsh dhcp server scope add reservedip Broadcom iscsi Client Broadcom iscsi Client 8. Set the iscsi target (target IP address , TCP port 3260, LUN 1, IQN iqn com.broadcom:iscsi-target): C:\>netsh dhcp server scope set reservedoptionvalue string vendor= BRCM ISAN iscsi: :6:3260:1:iqn com.broadcom:iscsi-target 9. Set the iscsi initiator (IQN iqn com.broadcom: ): C:\>netsh dhcp server scope set reservedoptionvalue string vendor= BRCM ISAN iqn com.broadcom: BIOS Integrated iscsi Boot

121 Configuring a DHCP Server DHCP Option 43 Finally, if the DHCP server has not already been authorized to assign IP addresses, authorize it. The final result should appear as follows in the DHCP manager: Alternatively, the configuration can be displayed with the dump command as follows: C:\>netsh dhcp server dump BIOS Integrated iscsi Boot 121

122

123 6 Configuring iscsi Crash Dump Under Windows Server 2003 and 2008, you can install crash dump functionality for servers which are started via iscsi boot. This ensures that, if the system crashes, the crash dump file is stored on the iscsi target LUN from which the server was booted. iscsi Crash Dump is implemented via a special driver, which is included in the relevant Broadcom NetXtreme driver package. How you install iscsi Crash Dump depends on the type of Broadcom NetXtreme controller configured for iscsi boot. System requirements The following are required for the installation of iscsi Crash Dump: For Windows Server 2003 you need hotfix KB For controllers of type Broadcom NetXtreme I, iscsi Crash Dump is only supported as of Broadcom software kit and only for certain server models. For more information, see the Release Notes for the relevant server. For controllers of type Broadcom NetXtreme II, iscsi Crash Dump is released without restrictions. For NetXtreme I and NetXtreme II, the configuration of iscsi boot must be completed and the server must have been started from the iscsi target. 6.1 Installation with NetXtreme I To install iscsi Crash Dump for Broadcom NetXtreme I, proceed as follows. Make sure that the current drivers and management tools for the Broadcom NetXtreme I Controller are installed. The current driver package for your server is available from the Fujitsu Siemens Computers download portal Open the Windows Control Panel and start the Broadcom Advanced Control Suite 3 (BACS 3). BIOS Integrated iscsi Boot 123

124 Installation with NetXtreme I Configuring iscsi Crash Dump Bild 73: Broadcom Advanced Control Suite 3 (BACS 3) Open the Configurations tab. In the iscsi Boot Configurations window, set the iscsi Crash Dump parameter to Enable. Click Apply to apply the setting and exit BACS 3. You must now restart the server to activate the iscsi Crash Dump functionality. 124 BIOS Integrated iscsi Boot

125 Configuring iscsi Crash Dump Installation with NetXtreme II 6.2 Installation with NetXtreme II To install iscsi Crash Dump for Broadcom NetXtreme II Controllers, proceed as follows. Download the current Broadcom driver package (BCM5708S) for your server from the Fujitsu Siemens Computers download portal Unzip the ZIP archive and copy the files to a memory stick. Start the setup program on the memory stick. The Windows welcome screen is displayed. Click Next. While the setup program prepares the installation, the progress is displayed. Then the Program Maintenance menu appears. Select Modify and click Next. The Custom Setup menu is displayed. Bild 74: Broadcom NetXtreme II Custom Setup Select iscsi Crash Dump Driver for the installation. Click Next. BIOS Integrated iscsi Boot 125

126 Installation with NetXtreme II Configuring iscsi Crash Dump The Ready to Modify the Program menu is displayed. Click Install. The iscsi Crash Dump driver is installed. Once the installation is complete, you must restart the server to activate the iscsi Crash Dump functionality. 126 BIOS Integrated iscsi Boot

127 7 Troubleshooting The following troubleshooting tips are useful for iscsi boot. The system boots to the local hard drive and not the iscsi target. Verify the boot order specified by the system BIOS, placing the MBA agent or Broadcom Ethernet Controller as the first bootable device. The system performs a PXE or RPL boot instead of an iscsi boot. Enter the MBA configuration screen ({CTRL}-[S]) and make sure that iscsi is the selected boot protocol. The iscsi boot driver cannot acquire an IP address. Make sure that the system is connected to the network and can contact the DHCP server. After moving the Windows operating system image to the iscsi target, Windows does not boot successfully from the iscsi target or generates unexpected stop messages. Make sure that the iscsi target is the same size or larger than the partition used on the local hard drive. Try to transfer the image again and watch for any errors that might indicate that the destination drive is too small. The iscsi boot driver cannot log in to the iscsi target. If using a static configuration, make sure the iscsi initiator and target names are correct. If using CHAP, verify the username/password on both the iscsi initiator and target. If using a dynamic configuration, verify that the DHCP lease is using the correct MAC address, that the iscsi initiator and/or target information are correct. Install a packet capture utility and verify that the DHCP offers to the iscsi client contain the appropriate initiator/target names. Make sure the desired iscsi target is correctly configured for the client. Install a packet capture utility and verify that the client is attempting to log-in to the iscsi target. The Windows operating system was configured for a dynamic IP address when it was first installed but is shown as supporting a static IP address when booting over iscsi. This is normal behavior. When the operating system takes over from the iscsi boot host driver it will inherit all the configured options in use, including IP address, iscsi target IQN, and iscsi initiator IQN. This is necessary to ensure a smooth transition from real-mode to protected mode operation. BIOS Integrated iscsi Boot 127

128

129 Glossary CHAP Challenge Handshake Authentication Protocol. An authentication protocol in which the authentication agent (typically a network server) sends the client program a random value that is used only once. DHCP Dynamic Host Configuration Protocol. A protocol for assigning dynamic IP addresses to devices on a network. FQDN Fully Qualified Domain Name. An internet address which consists of a hostname and a domain name of the form IQN iscsi Qualified Name. A naming convention supported by iscsi to uniquely identify an iscsi initiator or target. iscsi Initiator A client device that connects to the iscsi service offered by an iscsi target. Similar in concept to a SCSI controller that plugs into a PC system. iscsi Target A server device that offers the iscsi service to an iscsi initiator. Similar in concept to a SCSI drive used in a PC system. MBA PXE Multiple Boot Agent. A host CPU application, implemented as an IBM PC option ROM, that controls the protocol used to perform a network boot for NetXtreme controllers. Pre-Boot execution Environment. An environment to bootstrap computers using a network interface card rather than using local media. UNDI Universal Network Device Interface. An application programming interface (or API) for network interface cards. Most commonly associated with PXE. BIOS Integrated iscsi Boot 129

130

131 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009