Seft-backup-001-iscsi


http://stuff.mit.edu/afs/athena/dept/cron/documentation/dell-server-admin/en/Broadcom/NetXtreme/iscsibt.htm#wp388493

iscsi很简单，在Windows server 2012里面集成了这个功能。通过添加role去添加。然后加一个iscsi盘。客户端用iSCSI initiator 联上去，通过GHOST上传image。然后就可以过iscsi boot进image.

Back to Contents Page

iSCSI Boot: Broadcom NetXtreme 57XX User Guide

Overview


Supported
Operating Systems


Windows
iSCSI Boot Setup


Other
Considerations


Troubleshooting

Overview

Broadcom NetXtreme Gigabit Ethernet adapters support iSCSI boot to enable network boot of operating systems to diskless systems. The iSCSI boot allows a Windows operating system boot from an iSCSI target machine located remotely over a standard
IP network.

Supported Operating Systems

The Broadcom NetXtreme Gigabit Ethernet adapters support iSCSI boot on the following operating systems:

Windows Server 2003 32-bit SP1 and SP2

Windows Server 2003 64-bit SP1 and SP2

Windows iSCSI Boot Setup

The Windows iSCSI boot setup consists of:

Configuring the iSCSI Target

Configuring the iSCSI Boot Parameters

Preparing the Image on the Local Hard Drive

Transferring the OS Image to the iSCSI Target

Booting

Configuring the iSCSI Target

Configuring the iSCSI target varies by target vendors. For information on configuring the iSCSI target, refer to the documentation provided by the vendor. The general steps include:

Create an iSCSI target.

Create a virtual disk.

Map the virtual disk to the iSCSI target created in step 1.

Associate an iSCSI initiator with the iSCSI target.

Record the iSCSI target name, TCP port number, iSCSI Logical Unit Number (LUN), initiator Internet Qualified Name (IQN), and CHAP authentication details.

After configuring the iSCSI target, obtain the following:

Target IQN

Target IP address

Target TCP port number

Target LUN

Initiator IQN

CHAP ID and secret

Configuring the iSCSI Boot Parameters

Configure the Broadcom iSCSI boot software for either static or dynamic configuration. Refer toTable 1
for configuration options available from the General Parameters screen.

Table 1: Configuration Options

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 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). The static information is entered through the iSCSI Initiator Parameters Configuration screen.
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 through 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 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 generally set to disabled when booting from a CD to install the iSCSI target and then later set to enabled after the installation is completed.
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 available on NetXtreme adapters.

MBA Boot Protocol Configuration

To configure the boot protocol

Restart your system.

From the PXE banner, select CTRL+S. The MBA Configuration Menu appears (seeBroadcom
Boot Agent).

From the MBA Configuration Menu, use the UP ARROW orDOWN ARROW to move to the
Boot Protocol option. Use theLEFT ARROW or
RIGHT ARROW to change theBoot Protocol option to
iSCSI.

Select CTRL+K to access the iSCSI Configuration Utility.


NOTE: If iSCSI boot firmware is not programmed in the NetXtreme network adapter, selectingCTRL+K
will not have any effect.

Static iSCSI Boot Configuration

In a static configuration, you must enter data for the system's IP address, the system's initiator IQN, and the target parameters obtained inConfiguring
the iSCSI Target. For information on configuration options, see
Table 1.

To configure the iSCSI boot parameters using static configuration

From the MBA Configuration Menu, select
CTRL+K.

From the Main menu, select
General Parameters.

From the General Parameters screen, set the following:

TCP/IP parameters via DHCP: Disabled

iSCSI parameters via DHCP: Disabled

CHAP Authentication: Disabled

Boot to iSCSI target: Disabled

DHCP Vendor ID: BRCM ISAN

Link Up Delay Time: 0

Use TCP Timestamp: Enabled (for some targets such as the Dell/EMC AX100i, it is necessary to enableUse TCP Timestamp)

Target as First HDD: Disabled

LUN Busy Retry Count: 0

Windows HBA Boot Mode: Disabled

Select ESC to return to the
Main menu.

From the Main menu, select
Initiator Parameters.

From the Initiator Parameters screen, type values for the following:

IP Address

Subnet Mask

Default Gateway

Primary DNS

Secondary DNS

iSCSI Name (corresponds to the iSCSI initiator name to be used by the client system)


NOTE: Verify IP address. Invalid and duplicate IP addresses are ignored, silently.

Select ESC to return to the
Main menu.

From the Main menu, select
1st Target Parameters.


NOTE: Configuring a second target is not supported.

From the 1st Target Parameters screen, enable
Connect to connect to the iSCSI target. Type values for the following using the values used when configuring the iSCSI target:

IP Address

TCP Port

Boot LUN

iSCSI Name

Select ESC to return to the
Main menu.

A second iSCSI boot adapter can be configured for redundancy in the event the primary adapter fails to boot. To configure the secondary device parameters, selectSecondary Device Parameters
from the Main menu (see
Configure Parameters for a Secondary Adapter). Otherwise, go to step 12.

Select ESC and select Exit and Save Configuration.

Select F4 to save your MBA configuration.

Dynamic iSCSI Boot Configuration

In a dynamic configuration, you only need to specify that the system's IP address and target/initiator information are provided by DHCP (seeConfiguring
the DHCP Server to Support iSCSI Boot). With the exception of the initiator iSCSI name, any settings on the Initiator Parameters, 1st Target Parameters, or 2nd Target Parameters screens are ignored and do not need to be cleared. For information on configuration
options, see
Table 1.

If DHCP Option 17 is used, the target information is provided by the DHCP server, and the initiator iSCSI name is retrieved from the value programmed from the Initiator Parameters screen. If no value was selected, then the controller defaults
to the name:

iqn.1995-05.com.broadcom.<11.22.33.44.55.66>.iscsiboot

where the string

11.22.33.44.55.66

corresponds to the controller's MAC address.

If DHCP option 43 is used, then any settings on the Initiator Parameters, 1st Target Parameters, or 2nd Target Parameters screens are ignored and do not need to be cleared.

To configure the iSCSI boot parameters using dynamic configuration

From the MBA Configuration Menu, select
CTRL+K.

From the Main menu, select
General Parameters.

From the General Parameters screen, set the following:

TCP/IP parameters via DHCP: Enabled

iSCSI parameters via DHCP: Enabled

CHAP Authentication: Disabled

Boot to iSCSI target: Disabled

DHCP Vendor ID: BRCM ISAN

Link Up Delay Time: 0

Use TCP Timestamp: Enabled (for some targets such as the Dell/EMC AX100i, it is necessary to enableUse TCP Timestamp)

Target as First HDD: Disabled

LUN Busy Retry Count: 0

Windows HBA Boot Mode: Disabled

Select ESC to return to the
Main menu.


NOTE: Information on theInitiator Parameters and
1st Target Parameters screens are ignored and do not need to be cleared.

A second iSCSI boot adapter can be configured for redundancy in the event the primary adapter fails to boot. To configure the secondary device parameters, selectSecondary Device Parameters
from the Main menu (see
Configure Parameters for a Secondary Adapter). Otherwise, go to step 12.

Select Exit and Save Configurations.

Configure Parameters for a Secondary Adapter

A second iSCSI boot adapter can be configured for redundancy in the event the primary adapter fails to boot.

To configure the iSCSI boot parameters for a secondary adapter

From the MBA Configuration Menu, select
CTRL+K.

From the Main menu, select
Secondary Device Parameters.

From the Secondary Device Parameters screen, selectSecondary Device.

From the Device List, select the adapter that will be used as the secondary adapter.

From the Secondary Device Parameters screen, setMultipath I/O Mode
to Enabled (or Disabled if MPIO mode is not required).

Select Invoke to configure the secondary adapter.

Configure the secondary adapter parameters similar to the primary adapter parameters as shown in eitherStatic
iSCSI Boot Configuration or
Dynamic iSCSI Boot Configuration.


NOTE: The IP addresses for the primary and secondary adapters must be in two different subnets.

Select ESC and select Exit and Save Configuration.

Select F4 to save your MBA configuration.

Preparing the Image on the Local Hard Drive

When the software initiator mode operating system installation is used, the Windows operating system install must be performed in two stages. In the first stage, the OS is installed to a local hard drive on the system. In the second stage 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.

Initial Windows Install

Install Windows 2003 32-bit or Windows 2003 64-bit OS on the local hard drive.

Install the Broadcom drivers using the Setup installer.


NOTE: Do not install the drivers through Windows Plug-and-Play (PnP). Failure to install the drivers through the Setup
installer might blue screen your system.

Install Microsoft iSCSI Software Initiator (version 2.04 or later). To download from Microsoft, go tohttp://www.microsoft.com/downloads/details.aspx?FamilyID=c9ff2d21-fae2-40af-997a-70432f171311&DisplayLang=en.

Select support for Multipath I/O (MPIO), if needed. Refer to Microsoft's Initiator documentation for more information on MPIO.

Select the iSCSI boot option.

Select the Broadcom adapter as the iSCSI boot device.


NOTES:

Do not manually create connections to the iSCSI target for iSCSI boot adapters.

If the image is used on other hardware, Sysprep is required.

It is recommended to always run iscsibcg.exe /verify /fix at a command prompt before restarting the system. For information on configuring the iscsibcg utility to run automatically when a system shuts down, seehttp://support.microsoft.com/kb/934235.

Transferring the OS Image to the iSCSI Target

Create a new FAT32 partition on the local hard drive using the disk management console.

Boot to a bootable device such as a diskette drive, media, or USB key and run a disk imaging software, such as Symantec Ghost.

Clone the OS partition to the FAT32 partition (partition to image).

Place the iSCSI boot adapter before the hard drive in the boot menu.

Reboot the host and boot into the OS in the local hard drive.

Launch Windows compatible coning software, such as Ghost32, and write the image in the FAT32 partition to the remote LUN.

Booting

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

Reboot the server.

Select CTRL+S and CTRL+K.

From the Main menu, select
General Parameters and configure the Boot to iSCSI target option toEnabled.

If CHAP authentication is needed, enable CHAP authentication after determining that booting is successful (seeEnabling
CHAP Authentication).

Enabling CHAP Authentication

To enable CHAP authentication

From the MBA Configuration Menu, select
CTRL+K.

From the Main menu, select
General Parameters.

From the General Parameters screen, set
CHAP Authentication to Enabled.

From the Initiator Parameters screen, type values for the following:

CHAP ID

CHAP Secret (if authentication is required, and must be 12 characters in length or longer)

Select ESC to return to the
Main menu.

From the Main menu, select
1st Target Parameters.

From the 1st Target Parameters screen, type values for the following using the values used when configuring the iSCSI target:

CHAP ID (optional if two-way CHAP)

CHAP Secret (optional if two-way CHAP, and must be 12 characters in length or longer)

Select ESC to return to the
Main menu.

Select ESC and select Exit and Save Configuration.

Configuring the DHCP Server to Support iSCSI Boot

The DHCP server is an optional component and it is only necessary if you will be doing a dynamic iSCSI Boot configuration setup (seeDynamic
iSCSI Boot Configuration).

DHCP iSCSI Boot Configurations

The DHCP protocol includes a number of options that provide configuration information to the DHCP client. For iSCSI boot, Broadcom adapters support the following DHCP configurations:

DHCP Option 17, Root Path

DHCP Option 43, Vendor-Specific Information

DHCP Option 17, Root Path

Option 17 is used to pass the iSCSI target information to the iSCSI client.

The format of the root path as defined in IETC RFC 4173 is:

"iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>

The parameters are defined below.

Table 2: DHCP Option 17 Parameter Definition

Parameter	Definition
"iscsi:"	A literal string
<servername>	The IP address or FQDN of the iSCSI target
":"	Separator
<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 (refer to RFC 3720 for details on both IQN and EUI formats). An example IQN name would be "iqn.1995-05.com.broadcom:iscsi-target".

DHCP Option 43, Vendor-Specific Information

DHCP option 43 (vendor-specific information) provides more configuration options to the iSCSI client than DHCP option 17. In this configuration, three additional suboptions are provided that assign the initiator IQN to the iSCSI boot client
along with two iSCSI target IQNs that can be used for booting. The format for the iSCSI target IQN is the same as that of DHCP option 17, while the iSCSI initiator IQN is simply the initiator's IQN.

The suboptions are listed below.

Table 3: DHCP Option 43 Suboption Definition

Suboption	Definition
201	First iSCSI target information in the standard root path format "iscsi:"<servername>":"<protocol>":"<port>":"<LUN>":"<targetname>
203	iSCSI initiator IQN

Using DHCP option 43 requires more configuration than DHCP option 17, but it provides a richer environment and provides more configuration options. Broadcom recommends that customers use DHCP option 43 when performing dynamic iSCSI boot configuration.

Configuring the DHCP Server

Configure the DHCP server to support option 17 or option 43.


NOTE: If using Option 43, you also need to configure Option 60. The value of Option 60 should match the DHCP Vendor
ID value. The DHCP Vendor ID value is BRCM ISAN, as shown in
General Parameters of the iSCSI Boot Configuration menu.

Other Considerations

There are several other factors that should be considered when configuring a system for iSCSI boot.

Locally Administered Address

A user-defined MAC address assigned through the Locally Administered Address property of the BACS Advanced tab is not supported on iSCSI boot-enabled devices.

Virtual LANs

Virtual LAN (VLAN) tagging is not supported for iSCSI boot with the Microsoft iSCSI Software Initiator.

Teaming

The use of any form of teaming (Smart Load Balancing, Generic Trunking, or Link Aggregation) with iSCSI boot is not supported.

Troubleshooting

The following troubleshooting tips are useful for iSCSI boot.

Problem: If a Windows 2003-based system is booted with an MPIO configuration in the first boot, the interface booted without a cable attached will not be functional since the IP address of the interface
will be statically configured to a value of 0. This problem only occurs if the TCP/IP parameters are configured as DHCP. in other words, it will not occur if the IP addresses are statically configured in the iSCSI configuration program.

Solution: Perform the first boot with both cables attached and ensure that both interfaces are able to acquire IP addresses.

Problem: The iSCSI configuration utility will not run.

Solution. Ensure that the iSCSI Boot firmware is installed in the NVRAM.

Problem: When using a DHCP server, the DNS server entries are overwritten by the values provided by the DHCP server. This occurs even if the locally provided values are valid and the DHCP server provides no DNS
server information. When the DHCP server provides no DNS server information, both the primary and secondary DNS server values are set to 0.0.0.0.

Solution. When the Windows OS takes over, the Microsoft iSCSI initiator retrieves the iSCSI Initiator parameters and configures the appropriate registries statically. It will overwrite whatever is configured. Since the DHCP daemon
runs in the Windows environment as a user process, all TCP/IP parameters have to be statically configured before the stack comes up in the iSCSI Boot environment.

Problem: A system blue screen occurs when installing the Broadcom drivers through Windows Plug-and-Play (PnP).

Solution. Install the drivers through the Setup installer.

Please read all
Restrictions and Disclaimers.

Back to Contents Page