Dell Intel PRO Family of Adapters User guide

Brand: Dell

Model: Intel PRO Family of Adapters

Type: User guide

Intel® Ethernet iSCSI Boot User Guide

The information below is provided by the supplier of the referenced device without independent verification by Dell and is

subject to the restrictions and disclaimers

noted below.

This manual applies to the Intel® Boot Agent. Choose any of the links below to learn more about the product.

Overview

System Requirements

Installation and Setup

Firmware Setup

iSCSI Target Configuration

DHCP Server Configuration

Microsoft* Windows* Setup

Linux Setup

iSCSI Over Data Center Bridging (DCB)

Troubleshooting

Known Issues

Support

Glossary

Intel® Ethernet Flash Firmware Utility

Dell Update Package for Intel Adapter Firmware

Software License

Information in this document is subject to change without notice.

Trademarks used in this text: Dell and the DELL logo are trademarks of Dell Computer Corporation; Intel is a trademark of

Intel Corporation in the U.S. and other countries.

* Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and

names or their products. Intel Corporation disclaims any proprietary interest in trademarks and trade names other than its

own.

Restrictions and Disclaimers

The information contained in this document, including all instructions, cautions, and regulatory approvals and certifications, is

provided by the supplier and has not been independently verified or tested by Dell. Dell cannot be responsible for damage

caused as a result of either following or failing to follow these instructions.

All statements or claims regarding the properties, capabilities, speeds or qualifications of the part referenced in this document

are made by the supplier and not by Dell. Dell specifically disclaims knowledge of the accuracy, completeness or

substantiation for any such statements. All questions or comments relating to such statements or claims should be directed to

the supplier.

Export Regulations

Customer acknowledges that these Products, which may include technology and software, are subject to the customs and

export control laws and regulations of the United States ("U.S.") and may also be subject to the customs and export laws and

regulations of the country in which the Products are manufactured and/or received. Customer agrees to abide by those laws

and regulations. Further, under U.S. law, the Products may not be sold, leased or otherwise transferred to restricted end users

or to restricted countries. In addition, the Products may not be sold, leased or otherwise transferred to, or utilized by an end

user engaged in activities related to weapons of mass destruction, including without limitation, activities related to the design,

development, production or use of nuclear weapons, materials, or facilities, missiles or the support of missile projects, and

chemical or biological weapons.

Last revised: 29 April 2014

Back to Contents Page

Overview: Intel® Ethernet iSCSI Boot User Guide

Intel® Ethernet iSCSI Boot is designed for the Gigabit and 10 Gigabit family of PCI Express Server Adapters. Intel® Ethernet

iSCSI Boot provides the capability to boot from a remote iSCSI disk volume located on an iSCSI-based Storage Area Network

(SAN). This guide covers hardware and software installation, setup procedures, and troubleshooting tips for installing and

booting the system using these adapters.

iSCSI Over Data Center Bridging (DCB)

Intel® Ethernet adapters support iSCSI software initiators that are native to the underlying operating system. In the case of

Windows, the Microsoft iSCSI Software Initiator, enables connection of a Windows host to an external iSCSI storage array

using an Intel Ethernet adapter. For Windows Server 2008 and Windows Server 2012, the iSCSI initiator is included inbox.

In the case of Open Source distributions, virtually all distributions include support for an Open iSCSI Software Initiator and

Intel® Ethernet adapters will support them. Please consult your distribution documentation for additional configuration details

on their particular Open iSCSI initiator.

Intel® 82599-based and X540-based 10 gigabit adapters support iSCSI within a Data Center Bridging cloud. Used in

conjunction with switches and targets that support the iSCSI/DCB application TLV, this solution can provide guaranteed

minimum bandwidth for iSCSI traffic between the host and target. This solution enables storage administrators to segment

iSCSI traffic from LAN traffic, similar to how they can currently segment FCoE from LAN traffic. Previously, iSCSI traffic within

a DCB supported environment was treated as LAN traffic by switch vendors. Please consult your switch and target vendors to

ensure that they support the iSCSI/DCB application TLV.

iSCSI Over DCB

Quick Installation Procedures

For information on system requirements, see System Requirements.

To install and prepare a system for iSCSI Boot follow the procedure below.

1. Install Intel® iSCSI Boot-capable adapters in the system. For a list of supported adapters, see Supported Intel®

Network Adapters.

2. Install the latest iSCSI Boot firmware using the Dell Update Package for Intel Adapter Firmware

The command "BOOTUTIL -UP -ALL" programs the firmware on the flash ROM of all iSCSI Boot-capable adapters in the

system. See iSCSI DOS Utility

section for details.

3. Connect the adapter(s) in the iSCSI initiator system to a network with the iSCSI target

disk.

4. Follow the Firmware Setup

instructions to configure the Intel® Ethernet iSCSI Boot firmware to boot from a pre-

configured iSCSI target

disk.

5. To set up the initiator system to boot from a remote iSCSI disk using Microsoft* Windows*, follow the steps in Windows

Setup or Linux Setup.

6. After following the above steps if you are having problems, refer to Troubleshooting

NOTE: For the following adapters, iSCSI is enabled through the uEFI environment.

Intel® Ethernet 10G 2P X540-t Adapter

Intel® Ethernet 10G 2P X520 Adapter

Intel® Ethernet 10G 4P X540/I350 rNDC

Intel® Ethernet 10G 4P X520/I350 rNDC

Intel® Ethernet 10G 2P X520-k bNDC

Intel® Gigabit 4P X540/I350 rNDC

Intel® Gigabit 4P X520/I350 rNDC

Intel® Gigabit 4P I350 bNDC

To do this:

1. Go to System Setup.

2. Choose a port and go to configuration.

3. Specify the boot protocol: PXE, FCoE, iSCSI Primary, or iSCSI Secondary.

NOTE: The following adapters do not support the FCoE boot protocol:

Intel® Gigabit ET Dual Port Server Adapter

Intel® Gigabit ET Quad Port Server Adapter

Intel® Ethernet X520 10GbE Dual Port KX4 Mezz

Intel® Ethernet Server Adapter X520-T2

Intel® Gigabit 4P X520/I350 rNDC

Intel® Gigabit 4P X540/I350 rNDC

Intel® Gigabit 4P I350-t Mezz

Intel® Gigabit 2P I350-t Adapter

Intel® Gigabit 4P I350-t Adapter

Intel® Gigabit 4P I350-t rNDC

Intel® Gigabit 4P I350 bNDC

Intel® Gigabit 2P I350 LOM

Please read all restrictions and disclaimers

Back to Contents Page

System Requirements: Intel® Ethernet iSCSI Boot User Guide

System Hardware Compatibility for Network Adapters

Supported Intel® Network Adapters

Supported 32-bit Operating Systems

Platform Requirements for Intel® 64 Architecture (Intel® 64)

System Hardware Compatibility for Network Adapters

Before installing Intel Gigabit Server Adapters and Intel® iSCSI Boot firmware, check your system for the following minimum

configuration requirements.

One of the following slot types, depending on your adapter: A PCI Express slot (v1.0a or newer), 1x, 4x, 8x or 16x

The latest BIOS for your computer

Supported Intel® Network Adapters

Intel® 10 Gigabit Network Adapters

Intel® 10 Gigabit AT Server Adapter

Intel® 10 Gigabit XF SR Server Adapter

Intel® 10 Gigabit AF DA Dual Port Server Adapter

Intel® Ethernet X520 10GbE Dual Port KX4 Mezz

Intel® Ethernet X520 10GbE Dual Port KX4-KR Mezz

Intel® Ethernet Server Adapter X520-2

Intel® Ethernet 10G 2P X540-t Adapter

Intel® Ethernet 10G 2P X520 Adapter

Intel® Ethernet 10G 4P X540/I350 rNDC

Intel® Ethernet 10G 4P X520/I350 rNDC

Intel® Ethernet 10G 2P X520-k bNDC

Intel Gigabit Network Adapters and Devices

Intel® PRO/1000 PT Server Adapter

Intel® PRO/1000 PT Dual Port Server Adapter

Intel® PRO/1000 PF Server Adapter

Intel® Gigabit ET Dual Port Server Adapter

Intel® Gigabit ET Quad Port Server Adapter

Intel® Gigabit ET Quad Port Mezzanine Card

Intel® Gigabit 2P I350-t Adapter

Intel® Gigabit 4P I350-t Adapter

Intel® Gigabit 4P I350-t rNDC

Intel® Gigabit 4P X540/I350 rNDC

Intel® Gigabit 4P X520/I350 rNDC

Intel® Gigabit 4P I350-t Mezz

Intel® Gigabit 2P I350-t LOM

Intel® Gigabit 4P I350 bNDC

Intel® Gigabit 2P I350 LOM

NOTE: When using iSCSI Remote Boot with an Intel networking adapter, a Brocade Host Bus Adapter (HBA) must not

be installed in the system.

Supported 32-bit Operating Systems

Intel® Ethernet iSCSI Boot is supported on remote booting of the following IA-32 operating systems:

Microsoft Windows Server 2008 x86

Platform Requirements for Intel® 64 Architecture (Intel® 64)

Intel® Ethernet iSCSI Boot is supported on remote booting of the following Intel® 64 operating systems:

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2

RHEL6.5

SLES11 SP3

A platform that supports Intel® 64 will run in either 64-bit mode or 32-bit compatibility mode. In order for it to run in 64-bit

mode, the following requirements must be met:

The Intel® 64 system must have a 64-bit BIOS.

A 64-bit operating systems must be installed.

The installer for the adapter drivers will only list the drivers that are compatible with the currently running operating system.

If the system is running in compatibility mode, only IA-32 drivers will be available.

If the system is running in 64-bit mode, only Intel® 64 drivers will be available.

Please read all restrictions and disclaimers

Back to Contents Page

Installation and Setup: Intel® Ethernet iSCSI Boot User Guide

This section provides instructions on how to install and set up Intel® iSCSI Boot components. The first step after hardware

preparation is to program Intel® Ethernet iSCSI Boot firmware on an iSCSI Boot-capable adapter. See the Installing Firmware

section below.

The default iSCSI Boot configuration uses DHCP. If you are using Static IP, it is necessary to set up the firmware for static IP

configurations. See the section for Firmware Setup

For Microsoft Windows environment, follow the detailed instructions in Microsoft* Windows Setup

For Linux environment, follow the detailed instructions in Linux Setup

Installing Firmware

In order to enable Intel® Ethernet iSCSI Boot, the firmware should be loaded as Option ROM while booting the BIOS in the

system. "Intel® iSCSI Boot" followed by the firmware version number is displayed if the firmware is installed correctly.

The flash on Intel PCI Express adapters is loaded with several sets of firmware, including iSCSI Boot and PXE. To enable iSCSI

Boot you must run BootUtil to select the iSCSI Boot firmware. You may reconfigure the adapter flash firmware as needed,

switching to PXE for example, by running the BootUtil again and selecting a different firmware option.

If you are installing or upgrading Intel® Ethernet iSCSI Boot firmware on the Intel PRO/1000 PT/PF Single/Dual Port Server

Adapter or an Intel 10 Gigabit server adapter, BootUtil

is a DOS utility software used to install the firmware. BootUtil is not

intended as a utility for LAN on Motherboard (LOM) implementations. If you are using an Intel® iSCSI Boot-capable OEM

server system, please refer to instructions provided from the OEM to enable Intel® iSCSI Boot.

NOTE: For the following adapters, iSCSI can be enabled through the uEFI environment.

Intel® Ethernet 10G 2P X540-t Adapter

Intel® Ethernet 10G 2P X520 Adapter

Intel® Ethernet 10G 4P X540/I350 rNDC

Intel® Ethernet 10G 4P X520/I350 rNDC

Intel® Ethernet 10G 2P X520-k bNDC

Intel® Gigabit 4P X540/I350 rNDC

Intel® Gigabit 4P X520/I350 rNDC

Intel® Gigabit 4P I350 bNDC

To do this:

1. Go to System Setup.

2. Choose a port and go to configuration.

3. Specify the boot protocol: PXE, FCoE, iSCSI Primary, or iSCSI Secondary.

NOTE: The following adapters do not support the FCoE boot protocol:

Intel® Gigabit ET Dual Port Server Adapter

Intel® Gigabit ET Quad Port Server Adapter

Intel® Ethernet X520 10GbE Dual Port KX4 Mezz

Intel® Ethernet Server Adapter X520-T2

Intel® Gigabit 4P X520/I350 rNDC

Intel® Gigabit 4P X540/I350 rNDC

Intel® Gigabit 4P I350-t Mezz

Intel® Gigabit 2P I350-t Adapter

Intel® Gigabit 4P I350-t Adapter

Intel® Gigabit 4P I350-t rNDC

Intel® Gigabit 4P I350 bNDC

Intel® Gigabit 2P I350 LOM

NOTE: If you are updating firmware from version 13.x, you must first update to version 14.0.12 before updating to

firmware version 14.5.x or later.

Please read all restrictions and disclaimers.

Back to Contents Page

Firmware Setup: Intel® Ethernet iSCSI Boot User Guide

Intel® iSCSI Boot Port Selection Menu

Intel® iSCSI Boot Port Specific Menu

Intel® iSCSI Boot Configuration Menu

iSCSI CHAP Configuration

Intel® Ethernet iSCSI Boot features a setup menu which allows two network ports in one system to be enabled as iSCSI Boot

devices. To configure Intel® iSCSI Boot, power-on or reset the system and press the Ctrl-D key when the message "Press

<Ctrl-D> to run setup..." is displayed. After pressing the Ctrl-D key, you will be taken to the Intel® iSCSI Boot Port

Selection Setup Menu.

NOTE: When booting an operating system from a local disk, Intel® Ethernet iSCSI Boot should be disabled for all

network ports.

Intel® Ethernet iSCSI Boot Port Selection Menu

The first screen of the Intel® iSCSI Boot Setup Menu displays a list of Intel iSCSI Boot-capable adapters. For each adapter port

the associated MAC address, PCI device ID, PCI bus/device/function location, and a field indicating Intel® Ethernet iSCSI Boot

status are displayed. Up to 16 iSCSI Boot-capable ports can be displayed within the Port Selection Menu, 4 at a time in a

scrollable list. If there are more Intel® iSCSI Boot-capable adapters, these are not listed in the setup menu. The usage of this

menu is described below:

One network port in the system can be selected as the primary boot port by pressing the 'P' key when highlighted. The

primary boot port will be the first port used by Intel® iSCSI Boot to connect to the iSCSI target. Only one port may be

selected as a primary boot port.

One network port in the system can be selected as the secondary boot port by pressing the 'S' key when highlighted.

The secondary boot port will only be used to connect to the iSCSI target disk if the primary boot port fails to establish a

connection. Only one port may be selected as a secondary boot port.

Pressing the 'D' key with a network port highlighted will disable iSCSI Boot on that port.

Pressing the 'B' key with a network port highlighted will blink an LED on that port.

Pressing the Esc key exits the Port Selection Menu.

Pressing the Enter key enters the iSCSI Boot Port Specific Setup Menu for that port.

NOTES:

It is possible to end up with two primary adapters if a formerly configured primary adapter is added back to the

system with a new primary adapter configured. Either disable one of the adapters or change one to be a

secondary adapter.

When configuring primary and secondary ports, each may have different target parameters. Thus, if the iSCSI

primary target fails to connect to its target, the secondary port will try to connect to its target.

Intel® iSCSI Boot Port Specific Setup Menu

The port specific iSCSI setup menu has four options:

iSCSI Boot Configuration - Selecting this option will take you to the Intel® iSCSI Boot Configuration Setup Menu. This

menu is described in detail in the section below and will allow you to configure the iSCSI parameters for the selected

network port.

CHAP Configuration - Selecting this option will take you to the CHAP configuration screen. The CHAP Configuration

Menu is described in detail in the section below.

Discard Changes and Exit - Selecting this option will discard all changes made in the iSCSI Boot Configuration and

CHAP Configuration setup screens, and return back to the Intel® iSCSI Boot Port Selection Menu.

Save Changes and Exit - Selecting this option will save all changes made in the iSCSI Boot Configuration and CHAP

Configuration setup screens. After selecting this option, you will return to the Intel® iSCSI Boot Port Selection Menu.

Intel® iSCSI Boot Configuration Menu

The iSCSI Boot Configuration Menu allows you to configure the iSCSI Boot and Internet Protocol (IP) parameters for a specific

port. The iSCSI settings can be configured manually or retrieved dynamically from a DHCP server. Listed below are the

options in the Intel® iSCSI Boot Configuration Menu:

Use Dynamic IP Configuration (DHCP) - Selecting this checkbox will cause iSCSI Boot to attempt to get the client IP

address, subnet mask, and gateway IP address from a DHCP server. If this checkbox is enabled, these fields will not be

visible.

Initiator Name - Enter the iSCSI initiator name to be used by Intel iSCSI Boot when connecting to an iSCSI target. The

value entered in this field is global and used by all iSCSI Boot enabled ports in the system. This field may be left blank

if the "Use DHCP For Target Configuration" checkbox is enabled. For information on how to retrieve the iSCSI

initiator name dynamically from a DHCP server see the section "DHCP Server Configuration"

Initiator IP - Enter the client IP address to be used for this port as static IP configuration in this field. This IP address

will be used by the port during the entire iSCSI session. This option is visible if DHCP is not enabled.

Subnet Mask - Enter the IP subnet-mask in this field. This should be the IP subnet mask used on the network which

the selected port will be connecting to for iSCSI. This option is visible if DHCP is not enabled.

Gateway IP - Enter the IP address of the network gateway in this field. This field is necessary if the iSCSI target is

located on a different sub-network than the selected Intel iSCSI Boot port. This option is visible if DHCP is not enabled.

Use DHCP for iSCSI Target Information - Selecting this checkbox will cause Intel iSCSI Boot to attempt to gather

the iSCSI target's IP address, IP port number, iSCSI target name, and iSCSI LUN ID from a DHCP server on the

network. For information on how to configure the iSCSI target parameters using DHCP see the section "DHCP Server

Configuration". When this checkbox is enabled, these fields will not be visible.

Target Name - Enter the IQN name of the iSCSI target in this field. This option is visible if DHCP for iSCSI target is not

enabled.

NOTE: Target IQNs can differ for primary and secondary ports.

Target IP - Enter the target IP address of the iSCSI target in this field. This option is visible if DHCP for iSCSI target is

not enabled.

Target Port - TCP Port Number. This option is visible if DHCP for the iSCSI target is not enabled.

Boot LUN - Enter the LUN ID of the boot disk on the iSCSI target in this field. This option is visible if DHCP for iSCSI

target is not enabled.

NOTE: The Boot LUNs may differ for the primary and secondary ports since the primary and secondary ports

may have different targets.

iSCSI CHAP Configuration

Intel® iSCSI Boot supports one-way CHAP MD5 authentication with an iSCSI target. Intel® iSCSI Boot uses the "MD5 Message

Digest Algorithm" developed by RSA Data Security, Inc. The iSCSI CHAP Configuration menu has the following options to

enable CHAP authentication:

Use CHAP - Selecting this checkbox will enable CHAP authentication for this port. CHAP allows the target to

authenticate the initiator. After enabling CHAP authentication, a user name and target password must be entered.

User Name - Enter the CHAP user name in this field. This must be the same as the CHAP user name configured on the

iSCSI target.

Target Secret - Enter the CHAP password in this field. This must be the same as the CHAP password configured on the

iSCSI target and must be between 12 and 16 characters in length. This password cannot be the same as the Initiator

Secret.

Use Mutual CHAP - Selecting this checkbox will enable Mutual CHAP authentication for this port. Mutual CHAP allows

the initiator to authenticate the target. After enabling Mutual CHAP authentication, an initiator password must be

entered. Mutual CHAP can only be selected if Use CHAP is selected.

Initiator Secret - Enter the Mutual CHAP password in this field. This password must also be configured on the iSCSI

target and must be between 12 and 16 characters in length. This password cannot be the same as the Target Secret.

The CHAP Authentication feature of this product requires the following acknowledgements:

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software

written by Tim Hudson ([email protected]

This product includes software developed by the OpenSSL Project for use in the Open SSL Toolkit

(http://www.openssl.org

Intel PROSet for Windows Device Manager

Many of the functions of the Intel® iSCSI Boot Port Selection Setup Menu can also be configured or revised using Intel PROSet

for Windows Device Manager. See the Intel® Network Adapters User Guide for instruction on installing and using Intel PROSet

for Windows Device Manager.

VLAN ID

The VLAN ID field was grayed out in the iSCSI Boot firmware screen because the Microsoft* iSCSI Boot Initiator does not

support VLANs.

Please read all restrictions and disclaimers.

Back to Contents Page

iSCSI Target Configuration: Intel® Ethernet iSCSI Boot User

Guide

For specific information on configuring your iSCSI target system and disk volume, refer to instructions provided by the third-

party vendor. Listed below are the basic steps necessary to set up Intel® Ethernet iSCSI Boot to work with most iSCSI target

systems. The specific steps will vary from one vendor to another.

NOTE: In order to be able to support iSCSI Boot, the target needs to be able to support multiple sessions from the

same initiator. Both the iSCSI Boot firmware initiator and the OS High Initiator need to establish an iSCSI session at

the same time. Both these initiators use the same Initiator Name and IP Address to connect and access the OS disk but

these two initiators will establish a different iSCSI session. In order for the target to support iSCSI Boot, the target

must be capable of supporting multiple sessions and client logins.

1. Configure a disk volume on your iSCSI target system. Note the LUN ID of this volume for use when configuring in Intel®

Ethernet iSCSI Boot firmware setup.

2. Note the iSCSI Qualified Name (IQN) of the iSCSI target. This value will be used as the iSCSI target name when

configuring in Intel® iSCSI Boot firmware setup. The IQN will typically look like:

iqn.1986-03.com.intel:target1

3. Configure the iSCSI target system to accept the iSCSI connection from the iSCSI initiator. This usually requires listing

the initiator's IQN name or MAC address for permitting the initiator to access to the disk volume. See the Firmware

Setup for information on how to set the iSCSI initiator name.

4. One-way authentication protocol can be enabled optionally for secure communications. Challenge-Handshake

Authentication Protocol (CHAP) is enabled by configuring username/password on iSCSI target system. For setting up

CHAP on the iSCSI initiator, refer to Firmware Setup

for information.

To configure your iSCSI hardware target, consult your product documentation.

Booting from Targets Larger than 2TB

You can connect and boot from a target LUN that is larger than 2 Terabytes with the following restrictions:

The block size on the target must be 512 bytes.

The following operating systems are supported:

VMware* ESX 5.0, or later

Red Hat* Enterprise Linux* 6.3, or later

SUSE* Enterprise Linux 11SP2, or later

Microsoft* Windows Server* 2012, or later

You may be able to access data only within the first 2 TB.

NOTE: The Crash Dump driver does not support target LUNs larger than 2TB.

Please read all restrictions and disclaimers

Back to Contents Page

DHCP Server Configuration: Intel® Ethernet iSCSI Boot User

Guide

If you are using Dynamic Host Configuration Protocol (DHCP), the DHCP server needs to be configured to provide the iSCSI

Boot configurations to the iSCSI initiator. It is necessary to set up the DHCP server to specify Root Path option 17 and Host

Name option 12 in responding iSCSI target information back to the iSCSI initiator. DHCP option 3, router list may be

necessary, depending on the network configuration.

NOTE: Conflict detection should be enabled on the DHCP server.

DHCP Root Path Option 17:

The iSCSI root path option configuration string uses the following format:

ISCSI:<server name or IP address>:<protocol>:<port>:<LUN>:<targetname>

Examples:

iscsi:192.168.0.20:6:3260:0:iqn.1986-03.com.intel:target1

Server name: iSCSI server name or valid IPv4 address literal. Example: 192.168.0.20.

Protocol: Transport protocol used by ISCSI. Default is TCP (6). No other protocols are currently

supported.

Port: Port number of the iSCSI target. A default value of 3260 will be used if this field is left blank.

LUN: LUN ID configured on iSCSI target system. The LUN value entered should be in hexadecimal. For

example, an LUN ID of 64 (decimal) would be configured as 40 (hexadecimal). Default is zero.

Target name: iSCSI target name to uniquely identify an iSCSI target in IQN format.

Example: iqn.1986-03.com.intel:target1

DHCP Host Name Option 12:

Configure option 12 with the hostname of the iSCSI initiator.

DHCP Option 3, Router List:

Configure option 3 with the gateway or router IP address, if the iSCSI initiator and iSCSI target are on different subnets.

Please read all restrictions and disclaimers

Back to Contents Page

Microsoft Windows* Setup for Intel® Ethernet iSCSI Boot:

Intel® Ethernet iSCSI Boot User Guide

Microsoft* Windows* Intel iSCSI/DCB Installation & Configuration

iSCSI Over DCB

Configuration for Intel® Ethernet iSCSI Boot

Microsoft* Windows* Intel iSCSI/DCB Installation & Configuration

Adapter Requirements

This feature is only supported on X520 and X540-based adapters.

Installation

At the initial Intel Software installation screen, select the iSCSI/DCB checkbox. The installation process will install the

relevant DCB service and the iSCSI/DCB application TLV.

Configuration

1. From Windows Device Manager, expand Networking Adapters and highlight the appropriate adapter (such as

Intel® Ethernet Server Adapter X520). Right click on the Intel adapter and select Properties.

2. In the Property Page, select the Data Center Tab.

3. Data Center Bridging features can be set at either the switch or the adapter. Unless there is a compelling reason not to,

we recommend using the switch settings. By selecting switch settings, the iSCSI traffic class and the minimum

bandwidth guarantees are defined by the DCB settings in the DCB capable switch. Essentially you can push the DCB

settings for a single switch to a number of hosts rather than attempting to configure every host. To have the adapter

define the traffic class and bandwidth, uncheck the switch settings and set the appropriate traffic (0-7) and the

percentage of bandwidth that you wish to allocate for iSCSI traffic. The Data Center Tab provides feedback as to the

DCB state, operational or non- operational, as well as providing additional details should it be non-operational. It is

worth noting that DCB requires negotiation between the adapter and its link partner, typically a switch. If the switch is

not DCB capable, the DCB handshake will fail but the iSCSI connection will not be lost.

iSCSI Over Data Center Bridging (DCB)

iSCSI installation will include the installation of the iSCSI DCB Agent (iscsidcb.exe), which is a user mode service.

Hardware Support: iSCSI Over DCB is supported by all FCoE-capable adapters.

Software Support: Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 SP2, Windows Server 2008 SP2

(with Hyper-V Role), Windows Server 2008 R2, Windows Server 2008 R2 (with Hyper-V Role).

NOTE: DCB does not install in a VM. iSCSI over DCB is only supported in the base OS. An iSCSI initiator running in a VM

will not benefit from DCB Ethernet enhancements.

iSCSI Over DCB Configuration

iSCSI Over DCB is configured from the Data Center tab of Intel® PROSet for Windows* Device Manager.

iSCSI bandwidth (after boot up) is configured through DCB, if DCB is installed.

When in local mode, the raising or lowering of FCoE or iSCSI bandwidth percentage will lower or raise the LAN

bandwidth settings respectively.

FCoE/iSCSI cannot co-exist on the same user priority.

The Bandwidth percentages for LAN, FCOE (if installed) and iSCSI (if installed) must add up to 100%.

Using iSCSI over DCB with ANS Teaming

The Intel® iSCSI Agent is responsible for maintaining all packet filters for the purpose of priority tagging iSCSI traffic flowing

over DCB-enabled adapters. The iSCSI Agent will create and maintain a traffic filter for an ANS Team if at least one member

of the team has an "Operational" DCB status. However, if any adapter on the team does not have an “Operational” DCB

status, the iSCSI Agent will log an error in the Windows Event Log for that adapter. These error messages are to notify the

administrator of configuration issues that need to be addressed, but do not affect the tagging or flow of iSCSI traffic for that

team, unless it explicitly states that the TC Filter has been removed.

Microsoft* Windows* Configuration for Intel® Ethernet iSCSI Boot

Requirements

Installing Windows Server 2008 and Server 2012

Crash Dump Support

Requirements

1. Follow installation steps to install the Intel® Ethernet iSCSI Boot-capable adapters with Intel iSCSI Boot firmware

support.

2. Create a disk target (LUN) on an available iSCSI target system. Configure this LUN to be accessible to the MAC address

of the adapter of the host being booted.

3. Make sure the iSCSI initiator system starts the iSCSI Boot firmware. The firmware should be configured properly, be

able to connect to iSCSI target, and detect the boot disk.

4. Obtain the latest version of the Microsoft* iSCSI Software Initiator with integrated software boot support from here

5. To set up Windows Server 2008 boot system, following the steps in Installing Windows Server 2008

6. To enable crash dump support, follow the steps in Crash Dump Support

7. For information on iSCSI Over DCB, read iSCSI Over DCB

Installing Windows Server 2008 and Server 2012

Installing from Microsoft Media

NOTE: Windows Server 2008 and Server 2012 natively support installation to an iSCSI target without a local disk and

also natively supports OS iSCSI boot.

NOTE: In Windows Server 2008, by default the Dell Update Package (DUP) does not install the DCB component of the

Intel driver due to the requirement of a Microsoft initiated reboot. To install the DCB (iSCSI) component,

1. Go to the Control Panel and select Add/Remove Programs.

2. Select the Intel Network Connections program and click the Modify button.

3. Select the option to install DCB (iSCSI).

1. Install Windows Server 2008 or Server 2012.

2. Select an iSCSI LUN on the "Where do you want to install Windows?" screen. The Windows Server installation media

supports the network controller by default. Continue to complete the OS installation.

3. If no iSCSI LUN is listed on the "Where do you want to install Windows?" screen, click "Load Driver" to install the

network drivers for the network controllers. The network drivers are located on the Intel Network Driver CD or can be

downloaded at http://www.intel.com/support/network/sb/CS-006120.htm

to USB media. If an iSCSI LUN is listed,

continue to complete the OS installation.

4. For 10 gigabit network controllers, after performing step 3 above if the iSCSI LUN is not seen, then proceed with the

following from the driver selection window.

a. Create the WINPE INF driver directory.

i. Create a temporary directory (for example, f:\temp\winpe on the USB media).

ii. Copy all files from the appropriate directory on the CD to the temporary directory. Do NOT copy the INF

files from the directory to the temporary directory.

iii. Extract the INF files from the same directory as in step ii above to the temporary directory.

b. Press shift+F10 to bring up the Windows PE command line.

c. Enter "drvload <path>" where <path> is the path to the WinPE inf.

d. Close the driver selection window by clicking the X on the upper right side of the window. It automatically restarts

from the initial installation screen with the network driver installed. Continue to complete the OS installation.

WDS Installation of Windows Server 2008 and Server 2012

Microsoft provides WDS, Windows Deployment Services, for acquiring an installation image remotely. One network adapter is

assigned for PXE Option ROM in order to pull the install image, and another adapter to iSCSI Option ROM for Windows Server

2008 or Server 2012 installation destination. You may need to prepare a custom boot image based on the MS TechNet article

Windows Deployment Services.

Setting up WDS

1. Prepare the WDS environment and the custom boot image based on the MS TechNet article.

2. Inject the network driver and INF from the appropriate directory to the custom boot image. To determine which

directory to copy the files from, see Determining the Windows Drivers Directory for Installing Windows Server 2008

NOTE: Windows Server* 2012 R2 uses NDIS 6.4, Windows Server 2012 uses NDIS 6.3, Windows Server 2008 R2 uses

NDIS 6.2, and Windows Server 2008 SP1 or SP2 uses NDIS 6.1.

Setting Up the System

1. Install an adapter flashed with Intel® Boot Agent, or configure the LOM in your system to enable PXE.

2. Install an adapter flashed with the iSCSI Option ROM.

3. Boot the system.

4. Enter the BIOS setup menu and set the PXE adapter as the primary boot device.

5. Reboot the system.

6. Enter the iSCSI Setup screen via CTRL-D, and enable the primary port. Enable the Secondary port if required by your

configuration. Enter any static settings if you are not using DHCP. For more information on options in the iSCSI Setup

screen click here

NOTE: If you want to strictly use DHCP, you will need to enable Option 60 for PXE, as well as options 12 and

option 17 for iSCSI in the DHCP server.

7. Reboot the machine.

8. Ensure that the iSCSI Option ROM connects to the iSCSI LUN, and the PXE Option ROM connects to the WDS server.

Performing an Installation

1. Boot the system via PXE to your WDS Server, ensuring that the iSCSI Option ROM has made a connection to your

target.

2. Choose the Windows Server 2008 or Server 2012 boot image you modified with the network drivers.

3. Select an iSCSI LUN on the “Where do you want to install Windows?” screen. Continue to complete the OS Installation.

If no iSCSI LUN is listed on the “Where do you want to install Windows?” screen:

A. Inject the other INF discussed in Step 2 of the Setting UP WDS section above into your custom boot image on

your WDS server. Reboot, and attempt the install again.

B. Manually load the network drivers:

i. Using the "setup -a" command, extract the drivers from the Dell Driver Update Package. If an iSCSI LUN is

listed from step three, above, continue to complete the OS installation.

ii. On another system, create the WINPE INF driver directory on a removable media.

1. Create a temporary directory (for example, F:\temp\winpe on the USB media).

2. Copy all files from the PROXGB\Win32\NDISxx (or PROXGB\Winx64\NDISxx) directory to the

temporary directory. NDISxx indicates the NDIS version. Do NOT copy the INF files from NDISxx

directory to the temporary directory.

3. Extract the .INF files from PROXGB\Win32\NDISxx\WinPE\*.zip to the temporary directory.

iii. Reboot, and follow the above instructions until you get to the "Where do you want to install Windows?"

iv. Press Shift+F10 to bring up the Windows PE command line and connect the removal media to the system.

v. Enter "drvload <path>" where <path> is the location of the temporary directory you created in Step A,

above.

vi. Press "Refresh" on the "Where do you want to install Windows?" screen.

vii. The iSCSI LUN will be listed after the refresh completes. Continue to complete the install.

Crash Dump Support

To ensure a full memory dump,

Set the page file size equal to or greater than the amount of RAM installed on your system necessary for a full memory

dump.

Ensure that the amount of free space on your hard disk is able to handle the amount of RAM installed on your system.

A full memory dump may not be created if these requirements are not met.

Microsoft Windows Server 2008 and Server 2012

Crash dump file generation is supported for iSCSI-booted Windows Server 2008 x86/x64 or Server 2012 x86/x64 by the Intel

iSCSI Crash Dump Driver. A hot fix is available for crash dump file generation using Intel 10 Gigabit Ethernet at:

http://support.microsoft.com/kb/970312

NOTE: This hot fix is not necessary for Intel 1 Gigabit Ethernet.

To set up crash dump support, follow these steps:

1. Set up Windows iSCSI Boot as described in earlier documentation.

2. Install Intel PROSet for Windows Device Manager by Autorun from the Intel Network Driver CD if this has not yet been

done.

3. Open Intel PROSet for Windows Device Manager and select the Boot Options Tab.

4. From Settings select ISCSI Remote Boot Crash Dump and the Value Enabled and click OK.

Platforms Booted by uEFI iSCSI Native Initiator

Starting with version 2.2.0.0, the iSCSI crash dump driver gained the ability to support platforms booted using the native uEFI

iSCSI initiator over supported Intel Network Adapters. This support is available on Windows Server 2008 or later and only on

64-bit architecture. Any hot fixes listed in Crash Dump Support for Microsoft Windows Server 2008 must also be applied.

Since network adapters on uEFI platforms may not provide legacy iSCSI option rom, the boot options tab in DMIX may not

provide the setting to enable the iSCSI crash dump driver. If this is the case, the following registry entry has to be created:

HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\

<InstanceID>\Parameters

DumpMiniport REG_SZ iscsdump.sys

Please read all restrictions and disclaimers

Back to Contents Page

Linux Installation Setup for Intel® Ethernet iSCSI Boot: Intel®

Ethernet iSCSI Boot User Guide

Open-iSCSI Initiator Installation

Open-iSCSI Initiator Configuration

DCBx Software Configuration

Installation of Intel® Ethernet iSCSI Boot

Open-iSCSI Initiator Installation

1. Install the Open-iSCSI initiator utilities.

#yum -y install iscsi-initiator-utils

Open-iSCSI Initiator Configuration

1. Refer to www.open-iscsi.org/docs/README.

2. Configure your iSCSI array to allow access.

examine /etc/iscsi/initiatorname.iscsi for the Linux host initiator name

Update your volume manager with this host initiator name.

3. Set iscsi to start on boot.

#chkconfig iscscd on

#chkconfig iscsi on

4. Start iSCSI service (192.168.x.x is the IP Address of your target).

#iscsiadm -n discovery -t s -p 192.168.x.x

Observe the target names returned by iscsi discovery.

5. Log onto the target (-m XXX -T is XXX -l XXX -).

iscsiadm -m node -T iqn.2123-01.com:yada:yada: -p 192.168.2.124 -l

DCBx Software Configuration

Data Center Bridging Exchange (DCBx) provides services to establish a dropless Ethernet fabric to both FCoE and iSCSI. Most

FCoE and many iSCSI network configurations will require DCBx to be installed and configured. Instructions for configuring

DCBx are here.

Installation of Intel® Ethernet iSCSI Boot

This section describes how to install Linux onto a hard drive so that the disk is bootable using an Intel® iSCSI Boot-capable

adapter. There are two methods to accomplish this:

Install directly to a hard drive in an iSCSI storage array (Remote Install).

Install to a local disk drive and transfer this disk drive or OS image to an iSCSI Target (Local Install).

For more information on SCSI device enumeration, refer to Appendix A

at the end of this document.

The following operating systems support iSCSI Boot.

SUSE* Linux Enterprise Server 11

Red Hat* Enterprise Linux

SUSE* Linux Enterprise Server 10

NOTE: Currently, only SLES11 SP3 is supported. SLES provides native support for iSCSI remote booting and installing.

This means that there are no additional steps outside of the installer that are necessary to install to an iSCSI target

using an Intel Gigabit PCI Express Server Adapter. Please refer to the SLES10 documentation for instructions on how to

install to an iSCSI LU.

Red Hat Enterprise Linux

NOTE:Currently, only Red Hat Enterprise Linux 6.5 is supported. RHEL provides native support for Intel® iSCSI Boot

and installing. This means that there are no additional steps outside of the installer that are necessary to install to an

iSCSI target using an Intel Gigabit PCI Express Server Adapter. Please refer to the RHEL6.5 documentation for

instructions on how to install to an iSCSI LU.

Appendix A: Device Enumeration

The iSCSI LUs are discovered as SCSI device nodes. The enumeration of SCSI devices is dynamic. The SCSI subsystem creates

device nodes in the order that they are discovered, starting with /dev/sda and incrementing alphabetically. In the case of

iSCSI LU enumeration, local SCSI devices such as disks or USB devices affect this process. If a device node is created for a

USB device before iSCSI discovery occurs the USB device will be represented by /dev/sda and the iSCSI LUs will begin with

/dev/sdb. However, if you were to reboot this system without the USB device the iSCSI LUs will begin with /dev/sda. It is

important to configure grub correctly to point to the correct device node in order to boot from an iSCSI hard drive.

It is often the case when installing to an iSCSI LU that a device driven by the SCSI subsystem is used for the install media. For

example, using a USB flash drive for the Driver Update Media (DUM). As stated above this will affect how grub should be

configured when installing.

Here is an example of how iSCSI device node mappings might differ between installation and booting. In this example the user

is using a USB flash drive as a DUM. Because this device is being used to copy files onto the system, it is present before iSCSI

discovery occurs. However, when booting from the iSCSI Boot Disk, no USB flash drive is necessary and therefore it is not

attached.

Remote Installation:

USB flash drive or USB floppy /dev/sda

LUN 0 /dev/sdb

LUN 1 /dev/sdc

Booting:

LUN 0 /dev/sda

LUN 1 /dev/sdb

If the USB device is attached after booting, it will be enumerated as such: USB flash drive or USB floppy /dev/sdc.

It is also possible that there are other USB devices on the system; it is the user's responsibility determine whether these will

interfere with the device node mapping during boot.

Appendix B: Local Install on an IDE Device

After performing a Local Install on an IDE device the user will need to modify grub so that when booting the root partition is

identified as a SCSI device. When installing to a local IDE disk drive the device node used will be of the form /dev/hdX, but

when this volume is exposed by the iSCSI target the initiator will see the hard drive as a SCSI device and it will be

represented as /dev/sdX. This change must be made in the grub configuration file. This type of problem exposes the necessity

that the user fully understands the concepts described in this document, as specifics may vary greatly.

Appendix C: Unusually Long Boot Time

In some cases, if booting the system takes an unusually long time, you may try commenting the following line in the file

/etc/init.d/iptables:

$IPTABLES-restore $OPT $IPTABLES_DATA

if [ $? -eq 0 ]; then

success; echo

else

failure; echo; return 1

This may be required as the command may be resetting the connection.

Appendix D: Crash Dump for Linux

SUSE Linux Enterprise Server: Netdump utility can be used to dump the disk image when the system crashes.

Please read all restrictions and disclaimers

Back to Contents Page

Page is loading ...

Dell Intel PRO Family of Adapters User guide

Dell Intel PRO Family of Adapters User guide

Dell Intel PRO Family of Adapters User guide

Related papers

Other documents