BIOS Integrated iSCSI Boot for PRIMERGY Serversmanuals.ts.fujitsu.com/file/3522/iscsi-boot-bcm-en.pdfGesellschft für Technik-Dokumentation mbH 2008 Pfad: H:\windows\_projekte\iSCSI_boot\Handbuch\2008-11\InArbeit\iscs

$Page 1: BIOS Integrated iSCSI Boot for PRIMERGY Serversmanuals.ts.fujitsu.com/file/3522/iscsi-boot-bcm-en.pdfGesellschft für Technik-Dokumentation mbH 2008 Pfad: H:\windows\_projekte\iSCSI_boot\Handbuch\2008-11\InArbeit\iscs$
BIOS Integrated iSCSI Boot for PRIMERGY Servers Installation and Configuration

Edition November 2008

iscsi-boot-bcm.buc Seite 1 Dienstag, 4. November 2008 5:52 17

Comments… Suggestions… Corrections…The User Documentation Department would like toknow your opinion of this manual. Your feedback helpsus optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail to [email protected].

Certified documentation according to DIN EN ISO 9001:2000To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2000.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

008

P

fad:

H:\w

ind

ows\

_pro

jekt

e\iS

CS

I_b

oot\H

and

buch

\200

8-11

\InA

rbei

t\is

csi-

boot

-bcm

-en\

iscs

i-boo

t-bc

m.v

or

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.


mailto:[email protected]

http://www.cognitas.de

BIOS Integrated iSCSI Boot

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 iSCSI Boot with Windows 2003 Server . . . . . . . . . . . . . 9

2.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . 9

2.3 Preparing an Operating System Image . . . . . . . . . . . . 102.3.1 Performing the Initial Windows Installation . . . . . . . . . . . 102.3.2 Installing the Microsoft iSCSI Boot Software Initiator . . . . . . 102.3.3 Configuring the Microsoft iSCSI Software Initiator . . . . . . . . 17

2.4 Transferring the Operating System Image to the iSCSI Target . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.4.1 Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.4.2 Set Initiator Node Name . . . . . . . . . . . . . . . . . . . . . 262.4.3 Connect to iSCSI Target . . . . . . . . . . . . . . . . . . . . . 272.4.4 Select Source Disk . . . . . . . . . . . . . . . . . . . . . . . 282.4.5 Select Destination Disk . . . . . . . . . . . . . . . . . . . . . 302.4.6 Prepare Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.5 Activating Option ROM Scan . . . . . . . . . . . . . . . . . 33

2.6 Configuring the Controller for iSCSI Boot . . . . . . . . . . 372.6.1 Static iSCSI Boot Configuration . . . . . . . . . . . . . . . . . 432.6.2 Dynamic iSCSI Boot Configuration . . . . . . . . . . . . . . . 472.6.3 Configuring a Secondary Controller . . . . . . . . . . . . . . . 492.6.4 Completing the Controller Configuration . . . . . . . . . . . . . 53

2.7 Performing an iSCSI Boot . . . . . . . . . . . . . . . . . . . 54

3 iSCSI Boot with Windows 2008 Server . . . . . . . . . . . . 61

3.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . 61

3.2 System Requirements . . . . . . . . . . . . . . . . . . . . . 61

3.3 System BIOS Settings . . . . . . . . . . . . . . . . . . . . . 62

3.4 Configuring the Controller for iSCSI Boot . . . . . . . . . . 683.4.1 Static iSCSI Boot Configuration . . . . . . . . . . . . . . . . . 74


BIOS Integrated iSCSI Boot

Contents

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik-

Do

kum

enta

tion

mbH

200

8 P

fad

: H:\w

indo

ws\

_pro

jekt

e\iS

CS

I_bo

ot\H

andb

uch\

2008

-11

\InA

rbe

it\is

csi-b

oot-

bcm

-en

\iscs

i-bo

ot-

bcm

.ivz

3.4.2 Dynamic iSCSI Boot Configuration . . . . . . . . . . . . . . . . 773.4.3 Completing the Controller Configuration . . . . . . . . . . . . . 79

3.5 Installing Windows 2008 on an iSCSI Target . . . . . . . . . 80

3.6 Completing the Controller Configuration . . . . . . . . . . . 84

3.7 Configuring an MPIO Connection . . . . . . . . . . . . . . . 86

4 iSCSI Boot with SuSE Linux Enterprise Server 10 . . . . . . 89

4.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . 89

4.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . 89

4.3 Activating Option ROM Scan . . . . . . . . . . . . . . . . . . 90

4.4 Configuring the Controller for iSCSI Boot . . . . . . . . . . 944.4.1 Static iSCSI Boot Configuration . . . . . . . . . . . . . . . . 1004.4.2 Dynamic iSCSI Boot Configuration . . . . . . . . . . . . . . . 1044.4.3 Completing the Controller Configuration . . . . . . . . . . . . 106

4.5 Installing Linux on an iSCSI Target . . . . . . . . . . . . . . 107

5 Configuring a DHCP Server to Support iSCSI Boot . . . . 115

5.1 DHCP Options . . . . . . . . . . . . . . . . . . . . . . . . . 115

5.2 Configuring the DHCP Server to Support DHCP Option 17 116

5.3 Configuring the DHCP Server to Support DHCP Option 43 119

6 Configuring iSCSI Crash Dump . . . . . . . . . . . . . . . 123

6.1 Installation with NetXtreme I . . . . . . . . . . . . . . . . . 123

6.2 Installation with NetXtreme II . . . . . . . . . . . . . . . . 125

7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 127

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129


BIOS Integrated iSCSI Boot 5

1 IntroductionThe 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 configu-ration 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.


6 BIOS Integrated iSCSI Boot

Introduction

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

01

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 config-urations 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)



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 2003.

Chapter 3 describes how to configure your server for iSCSI boot under Windows 2008.

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.



References

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

01

References

RFC 3720, “Internet Small Computer Systems Interface (iSCSI)”, http://www.ietf.org/rfc/rfc3720.txt

RFC 4173, “Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol”, http://www.ietf.org/rfc/rfc4173.txt


http://www.ietf.org/rfc/rfc3720.txt

http://www.ietf.org/rfc/rfc4173.txt


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-KB902113 HotFix or

– Service Pack 2.



Preparing an OS Image iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.3 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.

2.3.1 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 KB902113 HotFix for iSCSI support.

You will find the HotFix on the ServerStart DVD 1 under PROGRAMS/GENERAL/MS/iSCSI SW Initiator Boot Version.

2.3.2 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.



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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê 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 instal-lation with Microsoft iSCSI Software Initiator is required.




Ê Activate the Configure iSCSI Network Boot Support checkbox and select the desired network interface driver. Then click Next to continue.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê Accept the license agreement and click Next to continue




The setup inspects your current configuration and updates your files. After this is done, the dialog box is closed automatically.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê Click Finish to close the wizard.




2.3.3 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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê Click Add to open the following dialog box.




Ê Enter the IP address and the port of the target portal and click OK.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê Select the Targets tab.




Ê Click LogOn to open the following dialog box.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Ê 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.



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.



Transferring the OS Image iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.4.1 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.




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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.4.2 Set Initiator Node Name

In this window you specify the Initiator Node Name. This name consists of iqn.1991-05.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.




2.4.3 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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.4.4 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.




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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.4.5 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.




2.4.6 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:




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.



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.



Activating Option ROM Scan iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.



iSCSI Boot with Windows 2003 Activating Option ROM Scan

BX620 S3


Figure 11: PRIMERGY BX620 S3 BIOS setup “Advanced” menu

Ê Select PCI Configuration and press Ú to enter the submenu.



Activating Option ROM Scan iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.



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 config-uration 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.



Configuring the Controller iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.




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 Ú.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Figure 16: “iSCSI Configuration Utility”

Ê Enter the General Parameters configuration option.




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 Description

TCP/IP parameters via DHCP

Controls whether the iSCSI boot host software acquires the IP address information using DHCP (Enabled) or use a static IP config-uration (Disabled).

iSCSI parameters via DHCP

Controls whether the iSCSI boot host software acquires its iSCSI target parameters using DHCP (Enabled) or through a static config-uration (Disabled).

CHAP Authentication Controls whether the iSCSI boot host software uses CHAP authen-tication 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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

The following section describes the process for a static configuration using an example.

You will find an example of a dynamic configuration in section 2.6.2 on page 47. For information on configuring the DHCP server, see chapter “Configuring a DHCP Server to Support iSCSI Boot” on page 115.

Boot to iSCSI target 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.

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 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.

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 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.

Use TCP Timestamp Controls if the TCP Timestamp option is enabled or disabled.

Target as First HDD Allows specifying that the iSCSI target drive will appear as the first hard drive in the system.

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 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.

Option Description




2.6.1 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:

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.

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




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.




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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Configuring a second iSCSI target


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).




2.6.2 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.1995-05.com.broadcom.11.22.33.44.55.66.iscsiboot, where the string 11.22.33.44.55.66 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.


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.

TCP/IP parameters via DHCP Enabled

iSCSI parameters via DHCP Enabled






Target as First HDD Disabled






© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

In this example both the TCP/IP parameters and the iSCSI parameters are dynamically assigned.





2.6.3 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 configu-ration 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 Ú.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

Figure 22: iSCSI Configuration Utility - “Secondary Device Parameters”

Ê Select the Secondary Device field and press Ú to open the Device List submenu.




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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.

EnabledYou only have to set the TCP/IP parameters for the secondary controller. The iSCSI parameters are automatically inherited from the primary controller.

DisabledYou must set all the parameters for the secondary controller specifi-cally.

Ê 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




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.

2.6.4 Completing the Controller Configuration


Ê 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.



Performing an iSCSI Boot iSCSI Boot with Windows 2003

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

2.7 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.



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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.





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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02

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.





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.


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

02



3 iSCSI Boot with Windows 2008 Server

This chapter describes how to configure a system to support iSCSI boot under Windows 2008. Unlike with Windows 2003, you can install Windows 2008 directly to the iSCSI target.


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.


The iSCSI boot configuration described in this document requires Broadcom NetXtreme controllers and Windows Server 2008.



System BIOS Settings iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

3.3 System BIOS Settings


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.



iSCSI Boot with Windows 2008 System BIOS Settings

RX300 S3







© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

Figure 33: PRIMERGY RX300 S3 BIOS setup “Peripheral Configuration“ menu




Ê Restart the server.

Ê Enter the BIOS Setup menu.

Ê In the Main menu select Boot Options – Boot Sequence.




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.





© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

BX620 S3







Figure 36: PRIMERGY BX620 S3 BIOS setup “PCI Configuration“ menu




Ê 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.





© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03


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.


Ê Start the server and press {Ctrl}-[S] when you see the MBA setup prompt for the controller to be configured.





Figure 38: “MBA Configuration Menu“

Ê Make sure that the Boot Protocol parameter is set to iSCSI.





© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

Figure 39: “Device List“


Ê Select the controller marked with the * and press Ú.




Figure 40: iSCSI Configuration Utility - “Main Menu“

Ê Open the General Parameters submenu.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03




Controls whether the iSCSI boot host software acquires the IP address information using DHCP (Enabled) or uses 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).

CHAP Authentication

Controls whether the iSCSI boot host software uses CHAP authenti-cation 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.




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 exten-sions. 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.


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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03


You will find an example of a dynamic configuration in section 3.4.2 on page 77. For how to configure the DHCP server, see chapter “Configuring a DHCP Server to Support iSCSI Boot” on page 115.



This section describes the settings you must make before the Windows setup so that Windows is installed on the iSCSI target.






Boot to iSCSI target Disabled (must be set to Enabled after the Windows 2008 installation, see page 72)




Target as First HDD Enabled (must be set to Disabled after the Windows 2008 installation, see page 72)
















© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

Figure 43: iSCSI Configuration Utility - “1st Target Parameters“


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.













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.





Boot to iSCSI target Disabled (must be set to Enabled after the Windows 2008 installation, see page 72)




Target as First HDD Enabled (must be set to Disabled after the Windows 2008 installation, see page 72)






© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

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 the MBA Configuration Menu, press [F4] to save the configuration. Then press [Esc] to exit the MBA setup.



Installing Windows on an iSCSI Target iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

3.5 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.



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 archi-tecture.

Ê 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).



Installing Windows on an iSCSI Target iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

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 athttp://www.fujitsu-siemens.com/support/downloads.html.

To install the drivers, proceed as follows:


http://www.fujitsu-siemens.com/support/downloads.html


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.



Completing the controller configuration iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

3.6 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.



iSCSI Boot with Windows 2008 Completing the controller configuration


Ê Press [Esc] to exit the MBA setup.

The server startup continues and Windows is loaded from the iSCSI target.



Configuring an MPIO connection iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

3.7 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.



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.



Configuring an MPIO connection iSCSI Boot with Windows 2008

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

03

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.



4 iSCSI Boot with SuSE Linux Enterprise Server 10


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.


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).



Activating the Option ROM Scan iSCSI Boot with SLES 10

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

4.3 Activating Option ROM Scan


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






iSCSI Boot with SLES 10 Activating the Option ROM Scan

Figure 54: PRIMERGY RX300 S3 BIOS setup “Peripheral Configuration” menu



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.



Activating the Option ROM Scan iSCSI Boot with SLES 10

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

BX620 S3






iSCSI Boot with SLES 10 Activating the Option ROM Scan

Figure 56: PRIMERGY BX620 S3 BIOS setup “PCI Configuration” menu



Ê 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.




Configuring the Controller iSCSI Boot with SLES 10

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04


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 config-uration or a dynamic configuration. This involves selecting iSCSI as the boot protocol for the MBA and then setting the appropriate iSCSI boot configuration options.


Ê Start the server and press {Ctrl}-[S] when the MBA setup prompt for the controller to be configured is displayed.




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.





© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

Figure 59: “Device List”


Ê Select the controller that is marked with the * and press Ú.





Ê Enter the General Parameters configuration option.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04



Option Description


Controls whether the iSCSI boot host software acquires the IP address information using DHCP (Enabled) or use a static IP config-uration (Disabled).


Controls whether the iSCSI boot host software acquires its iSCSI target parameters using DHCP (Enabled) or through a static config-uration (Disabled).

CHAP Authentication Controls whether the iSCSI boot host software uses CHAP authen-tication 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.





You will find an example of a dynamic configuration in section 4.4.2 on page 104. For information on configuring the DHCP server, see chapter “Configuring a DHCP Server to Support iSCSI Boot” on page 115.

Boot to iSCSI target 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.

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 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.

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 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.

Use TCP Timestamp Controls if 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. If the server has local hard disk drives, Target as First HDD must be set to Enabled.

LUN Busy Retry Count 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.

Option Description




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04





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.










Target as First HDD Disabled1

1 If there are local hard disks, Target as First HDD must be set to Enabled.








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.






© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

Figure 63: iSCSI configuration screen with “1st Target Parameters”







Configuring a second iSCSI target








© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04














Target as First HDD Disabled1

1 If there are local hard disks, Target as First HDD must be set to Enabled.












© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04







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.



Installing Linux on an iSCSI Target iSCSI Boot with SLES 10

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

Ê 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.




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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

Figure 68: iSCSI Initiator Overview – Connected Targets tab

Ê Click Add to add the target on which you want to install the operating system.




Figure 69: iSCSI Initiator Discovery – Adding the target

Ê Enter the IP address of the target.

Ê Click Next.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

Figure 70: iSCSI Initiator Discovery (Connected = False)

Ê Select the target.

Ê Click Connect to connect to the 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.




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

04

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.



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:

Using the root path option the DHCP server can assign a single iSCSI target to a DHCP client.

iscsi A literal string

servername The IP address or FQDN of the iSCSI target

protocol The IP protocol used to access the iSCSI target. Currently only TCP is supported, so the protocol is 6.

port The port number associated with the protocol. The standard port number for iSCSI is 3260.

LUN The Logical Unit Number to use on the iSCSI target

targetname 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.1995-05.com.broadcom:iscsi-target.



DHCP Option 17 Configuring a DHCP Server

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

05

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 192.168.10.1

– The DHCP server will distribute addresses 192.168.10.100 to 192.168.10.254 for iSCSI clients

– The iSCSI target server IP address is 192.168.10.2

– The iSCSI target TCP port number is 3260

– The iSCSI target server IQN is iqn.1995-05.com.broadcom:iscsi-target

– The iSCSI client MAC address is 00:10:18:01:02:03



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 2003.

1. 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 192.168.10.1 add scope 192.168.10.0 255.255.255.0 “iSCSI Clients“

3. Add a range of IP addresses for the DHCP server to give to the iSCSI clients:

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 add iprange 192.168.10.100 192.168.10.254

4. Create a reservation for a client system with the MAC address 00:10:18:01:02:03 to receive the IP address 192.168.10.100:

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 add reservedip 192.168.10.100 001018010203 “Broadcom iSCSI Client“ “Broadcom iSCSI Client“

5. Set the iSCSI target (target IP address 192.168.10.2, TCP port 3260, LUN 1, IQN iqn.1995-05.com.broadcom:iscsi-target):

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 set reservedoptionvalue 192.168.10.100 17 string “iscsi:192.168.10.2:6:3260:1:iqn.1995-05.com.broadcom:iscsi- target“




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

05

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:




5.3 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 192.168.10.1

– The DHCP server will distribute addresses 192.168.10.100 to 192.168.10.254 for iSCSI clients

– The iSCSI target server IP address is 192.168.10.2

– The iSCSI target TCP port number is 3260

– The iSCSI target server IQN is iqn.1995-05.com.broadcom:iscsi-target

– The iSCSI client MAC address is 00:10:18:01:02:03

– The iSCSI initiator IQN is iqn.1995-05.com.broadcom:001018010203

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 192.168.10.1 add class „BRCM ISAN“ „Broadcom iSCSI DHCP Options“ „BRCM ISAN“ 1




© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

05

3. Create sub-options 201 to 203 for the new vendor class:

C:\>netsh dhcp server 192.168.10.1 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 192.168.10.1 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 192.168.10.1 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 192.168.10.1 add scope 192.168.10.0 255.255.255.0 “iSCSI Clients“

5. Add a range of IP addresses for the DHCP server to give to the iSCSI clients:

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 add iprange 192.168.10.100 192.168.10.254

6. Add option 60 and set option 60 for the scope created in the previous step:

C:\>netsh dhcp server 192.168.10.1 add optiondef 60 ClassID string 0C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 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 192.168.10.100:

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 add reservedip 192.168.10.100 001018010203 “Broadcom iSCSI Client“ “Broadcom iSCSI Client“

8. Set the iSCSI target (target IP address 192.168.10.2, TCP port 3260, LUN 1, IQN iqn.1995-05.com.broadcom:iscsi-target):

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 set reservedoptionvalue 192.168.10.100 201 string vendor=“BRCM ISAN“ “iscsi:192.168.10.2:6:3260:1:iqn.199505.com.broadcom:iscsi-target“

9. Set the iSCSI initiator (IQN iqn.1995-05.com.broadcom:001018010203):

C:\>netsh dhcp server 192.168.10.1 scope 192.168.10.0 set reservedoptionvalue 192.168.10.100 203 string vendor=“BRCM ISAN“ “iqn.1995-05.com.broadcom:001018010203“




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 192.168.10.1 dump


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

05



6 Configuring iSCSI Crash DumpUnder 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 KB939875.

– For controllers of type Broadcom NetXtreme I, iSCSI Crash Dump is only supported as of Broadcom software kit 11.4.3 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 http://www.fujitsu-siemens.com/support/downloads.html.

Ê Open the Windows Control Panel and start the Broadcom Advanced Control Suite 3 (BACS 3).




Installation with NetXtreme I Configuring iSCSI Crash Dump

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

06

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.



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 http://www.fujitsu-siemens.com/support/downloads.html.

Ê 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.




Installation with NetXtreme II Configuring iSCSI Crash Dump

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

06

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.



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.


© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

ent

atio

n m

bH 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte

\iSC

SI_

boo

t\Han

dbuc

h\20

08-1

1\In

Arb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-

boo

t-bc

m.k

07



GlossaryCHAP

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.

DHCPDynamic Host Configuration Protocol. A protocol for assigning dynamic IP addresses to devices on a network.

FQDNFully Qualified Domain Name. An internet address which consists of a hostname and a domain name of the form www.broadcom.com.

IQNiSCSI Qualified Name. A naming convention supported by iSCSI to uniquely identify an iSCSI initiator or target.

iSCSI InitiatorA 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 TargetA server device that offers the iSCSI service to an iSCSI initiator. Similar in concept to a SCSI drive used in a PC system.

MBAMultiple 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.

PXEPre-Boot eXecution Environment. An environment to bootstrap computers using a network interface card rather than using local media.

UNDIUniversal Network Device Interface. An application programming interface (or API) for network interface cards. Most commonly associated with PXE.


© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

ume

ntat

ion

mb

H 2

008

P

fad:

H:\

win

dow

s\_p

roje

kte\

iSC

SI_

boo

t\Han

dbu

ch\2

008-

11\I

nArb

eit\

iscs

i-bo

ot-b

cm-e

n\is

csi-b

oot-

bcm

.mix


Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

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 So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

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 seit-dem 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 Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009

Documents

BIOS Integrated iSCSI Boot for PRIMERGY Serversmanuals.ts.fujitsu.com/file/3522/iscsi-boot-bcm-en.pdfGesellschft für Technik-Dokumentation mbH 2008 Pfad: H:\windows\_projekte\iSCSI_boot\Handbuch\2008-11\InArbeit\iscs