Broadcom iSCSI Boot for HP FlexFabric Adapters User Guide Abstract This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft®, Windows®, and Windows Server® are U.S.
Contents Introduction .................................................................................................................................. 5 iSCSI boot ................................................................................................................................................ 5 HP FlexFabric supported adapters for Broadcom iSCSI boot ........................................................................... 5 Broadcom iSCSI boot supported operating systems ................
Documentation feedback ............................................................................................................. 41 Index .........................................................................................................................................
Introduction iSCSI boot iSCSI boot enables a network boot of operating systems to diskless systems. With an iSCSI boot a Windows, Linux, or VMware operating system can boot from an iSCSI target machine located remotely over a standard IP network. For both Windows and Linux operating systems, iSCSI boot can be configured to boot with two distinctive paths: non-offload (also known as Microsoft Open-iSCSI Initiator) and offload (Broadcom offload iSCSI driver or HBA).
Setup iSCSI boot setup To set up an iSCSI boot: • Configuring the iSCSI target (on page 6) • Configuring iSCSI boot parameters (on page 6) • Preparing the iSCSI boot image (on page 12) • Booting (on page 19) Configuring the iSCSI target Configuring the iSCSI target varies by target vendors. For information on how to configure the iSCSI target, see the documentation provided by the vendor. To configure the iSCSI target: 1. Create an iSCSI target. 2. Create a virtual disk. 3.
Configuration options Option Description TCP/IP parameters via DHCP This option is specific to IPv4 and controls whether the iSCSI boot host software acquires the IP address information using DHCP (Enabled) or using a static IP configuration (Disabled). IP Auto-configuration This option is specific to IPv6. IP auto-configuration controls whether the iSCSI boot host software configures a stateless link-local address or a stateful address if DHCPv6 is present and used (Enabled).
iSCSI boot configuration To configure iSCSI boot, do one of the following: • Static iSCSI boot configuration (on page 8) • Dynamic iSCSI boot configuration (on page 9) Static iSCSI boot configuration For a static configuration, enter data for the system IP address, the system initiator IQN, and the target parameters obtained in "Configuring the iSCSI target (on page 6)." For information on configuration options, see "Configuration options (on page 7).
o IP Address o TCP Port o Boot LUN o iSCSI Name 8. Press ESC to return to the main menu. 9. Press ESC, and then select Exit and Save Configuration. 10. Press F4 to save your MBA configuration. 11. To configure a second iSCSI target, return to the iSCSI Boot Configuration Utility. Dynamic iSCSI boot configuration For a dynamic configuration, specify the system IP address. The target and initiator information are provided by a DHCP server.
o Target as First HDD: Disabled o LUN Busy Retry Count: 0 o IP Version: IPv6 (for IPv6, non-offload) o HBA Boot Mode: Disabled For HP FlexFabric CNA adapters, select Enabled to support offload iSCSI boot path. The HBA Boot Mode parameter cannot be changed when the adapter is in Multi-Function mode. 2. Press ESC to return to the main menu. Information on the Initiator Parameters, 1st Target Parameters, and 2nd Target Parameters screens are ignored and do not need to be cleared. 3.
• DHCP option 43, vendor-specific information (on page 11) 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:"":"":"":"":"".
DHCP iSCSI boot configuration for IPv6 The DHCPv6 server provides a number of options, including stateless or stateful IP configuration, and information to the DHCPv6 client. For iSCSI boot, HP FlexFabric adapters support these DHCP configurations: • DHCPv6 option 16, vendor class option (on page 12) • DHCPv6 option 17, vendor-specific information (on page 12) The DHCPv6 standard root path option is not available. Use option 16 or option 17 for dynamic iSCSI boot IPv6 support.
Windows Server 2008 R2 and SP2 iSCSI boot setup Windows Server 2008 R2 and Windows Server 2008 SP2 support booting and installing in either the offload or non-offload paths. The following procedure prepares the image for installation and booting in either the offload or non-offload path. The following procedure references Windows Server 2008 R2 but is common to both the Windows Server 2008 R2 and SP2. The required CD/ISO image includes Windows 2008 R2 x64 with the Broadcom drivers injected.
15. Verify that the OS and system are functional and can pass traffic by pinging a remote system IP. Windows Server 2012 iSCSI boot setup Windows Server 2012 supports booting and installing in either the offload or non-offload paths. Use a slipstream DVD with the latest Broadcom drivers injected. For more information, see "Injecting (slipstreaming) Broadcom drivers into Windows image files (on page 17)." Also, see the base topic KB974072 on the Microsoft website (http://support.microsoft.com/).
• Set up Linux iSCSI boot using remote DVD installation (on page 17) Set up Linux iSCSI boot using local hard drive installation To set up Linux iSCSI boot using local hard drive installation: 1. Install Linux OS on your local hard drive, and then verify that the open iSCSI Initiator is current. To update iSCSI Initiator, remove the existing initiator using rpm-e. 2. Be sure all run-levels of network service are on: chkconfig network on 3.
• Broadcom CNIC driver (cnic) • Broadcom iSCSI offload driver (bnx2i) • Userspace I/O driver (uio) The directory structure of the package follows. (root): • doc (documentation directory: man pages) • src: o uip (the uIP stack) o unix (iscsiuio source) To compile and install the script: 1. Untar the tarball file. 2. Run the configure script. The configure script creates makefiles and proper header files needed for the build. 3. Run make to create the binary iscsiuio. 4.
5. Test the iSCSI target connection: iscsiadm -m node -p -T -I --login Set up Linux iSCSI boot using remote DVD installation Linux iSCSI boot remote DVD installation can be set up with an offload path or a non-offload path. The remote DVD installation is supported by Red Hat 6.2 or later and SLES 11 SP2 or later. Installing through a non-offload path is also supported by SLES 11 SP2 or later.
Copy the driver packages to a working directory, inject the drivers into the Windows Image (.wim) files, and then install the applicable Windows Server version from the updated images. The file and folder names used in this procedure are examples only. Specify file and folder names for the specific slipstream project. To inject (slipstream) the drivers into Windows image files: 1. Do one of the following: a. For Windows Server 2008 R2 and SP2, install the Windows Automated Installation Kit. b.
dism /mount-wim /wimfile:.\src\sources\install.wim /index:X /mountdir:.\mnt X is a placeholder for the obtained index value. 13. Enter the following commands to add the following drivers to the currently mounted image: dism /image:.\mnt /add-driver /driver:C:\Temp\evbd\evbd.inf dism /image:.\mnt /add-driver /driver:C:\Temp\bxnd\bxnd.inf dism /image:.\mnt /add-driver /driver:C:\Temp\bxfcoe\bxfcoe.inf dism /image:.\mnt /add-driver /driver:C:\Temp\bxois\bxois.inf 14.
and duplex settings can be changed using the BACS management utility for iSCSI boot through the offload and NDIS paths. Virtual LANs VLAN tagging is not supported for iSCSI boot with the Microsoft iSCSI Software Initiator. iSCSI crash dump To use the Broadcom iSCSI Crash Dump utility, follow the installation procedure for the iSCSI Crash Dump driver ("iSCSI offload in Windows server" on page 20).
• Configure Microsoft Initiator to use Broadcom’s iSCSI offload ("Configuring Microsoft Initiator to use Broadcom iSCSI offload" on page 21) Installing Broadcom drivers and management applications To install drivers and management applications: 1. Install the Windows drivers. 2. Install BACS for Windows. Installing the Microsoft iSCSI Initiator For Windows Server 2008 and later, the iSCSI initiator is included in the box. To download the iSCSI initiator, go to the Microsoft website (http://support.
2. Configure the initiator IQN name according to your setup. To change the name, click Change. 3. Enter the initiator IQN name.
4. Open the Discovery tab, and then click Add Portal to add a target portal. 5. Enter the IP address of the target, and then click Advanced.
6. From the General tab, select the HP FlexFabric adapter from Local adapter.
7. Select the IP address for the adapter from Source IP.
8. Click OK to close Advanced settings, and then click OK to add the target portal.
9. From the Targets tab, select the target, and then click Log On to log into your iSCSI target using the iSCSI adapter. 10. Click Advanced.
11. On the General tab, select the HP FlexFabric adapter from Local adapter. 12. Click OK to close Advanced settings. 13. Click OK to close the Microsoft Initiator. 14. To format your iSCSI partition, use Disk Manager. Teaming does not support iSCSI adapters or NDIS adapters that are in the boot path. Teaming supports NDIS adapters that are not in the iSCSI boot path, but only for the SLB team type.
Troubleshooting Boot fails when switching to Broadcom iSCSI offload Possible cause: When switching iSCSI boot from the Microsoft standard path to Broadcom iSCSI offload, the boot fails to complete. Action: Install or upgrade the Broadcom Virtual Bus Device driver to 5.0.x and the OIS driver prior to switching the iSCSI boot path. Broadcom iSCSI Crash Dump utility does not capture a memory dump Possible cause: The link speed for iSCSI boot is configured for 10 Mbps or 100 Mbps, which are not supported.
IP address conflict Symptom: For static IP configurations, an IP address conflict message appears when switching from Layer 2 iSCSI boot to Broadcom iSCSI HBA. Action: Change the IP address of the network property in the OS. iSCSI target is not recognized as an installation target Possible cause: An iSCSI target is not recognized as an installation target during a Windows Server 2008 installation through an IPv6 connection. Action: No action is required. This is a known third-party issue.
System blue screen occurs when iSCSI boots Windows 2008 R2 Symptom: A system blue screen occurs when iSCSI boots Windows 2008 R2 through the adapter NDIS path with the initiator configured using a link-local IPv6 address and the target configured using a router-configured IPv6 address. Action: No action is required. This is a known Windows TCP/IP stack issue.
Frequently asked questions iSCSI offload FAQs Q: How do I assign an IP address for iSCSI offload? A: Use the Configurations tab in BACS. Q: What tools should be used to create the connection to the target? A: Use Microsoft iSCSI Software Initiator (version 2.08 or later). Q: How do I know that the connection is offloaded? A: Use Microsoft iSCSI Software Initiator. From a command line, enter iscsicli sessionlist. From the Initiator Name, an iSCSI offloaded connection displays an entry beginning with B06BDRV.
Event notifications Offload iSCSI driver The following table lists the offload iSCSI driver event log messages. Message Severity Message 1 Error Initiator failed to connect to the target. Target IP address and TCP port number are given in dump data. 2 Error Initiator could not allocate resources for an iSCSI session. 3 Error Maximum command sequence number is not serially greater than the expected command sequence number in login response.
Message Severity Message 22 Error Header digest error was detected for the given PDU. Dump data contains the header and digest. 23 Error Target sent an invalid iSCSI PDU. Dump data contains the entire iSCSI header. 24 Error Target sent an iSCSI PDU with an invalid opcode. Dump data contains the entire iSCSI header. 25 Error Data digest error was detected. Dump data contains the calculated checksum followed by the given checksum.
Message Severity Message 51 Error Target failed to respond in time to a logout request sent in response to an asynchronous message from the target. 52 Error Initiator service failed to respond in time to a request to configure IPSec resources for an iSCSI connection. 53 Error Initiator service failed to respond in time to a request to release IPSec resources allocated for an iSCSI connection. 54 Error Initiator service failed to respond in time to a request to encrypt or decrypt data.
Regulatory compliance notices Safety and regulatory compliance For safety, environmental, and regulatory information, see Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the HP website (http://www.hp.com/support/Safety-Compliance-EnterpriseProducts). Warranty information HP ProLiant and X86 Servers and Options (http://www.hp.com/support/ProLiantServers-Warranties) HP Enterprise Servers (http://www.hp.
Support and other resources Before you contact HP Be sure to have the following information available before you call HP: • Active Health System log (HP ProLiant Gen8 or later products) Download and have available an Active Health System log for 3 days before the failure was detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning User Guide on the HP website (http://www.hp.com/go/ilo/docs).
Acronyms and abbreviations BACS Broadcom Advanced Control Suite CD compact disc CHAP Challenge Handshake Authentication Protocol DHCP Dynamic Host Configuration Protocol DVD digital video disc EUI extended unique identifier FIPS Federal Information Processing Standard HBA host bus adapter HDD hard drive IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IQN iSCSI qualified name Acronyms and abbreviations 38
iSCSI Internet Small Computer System Interface ISO International Organization for Standardization LUN logical unit number MAC Media Access Control MBR multi-boot agent MTU maximum transmission unit NDIS network driver interface specification NOP no operation NVRAM nonvolatile memory OIS offload iSCSI PCI payment card industry PDU protocol data unit PXE preboot execution environment RFC request for comments Acronyms and abbreviations 39
RHEL Red Hat Enterprise Linux SLB switch-assisted load balancing SLES SUSE Linux Enterprise Server VLAN virtual local-area network WMI Windows Management Instrumentation Acronyms and abbreviations 40
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index B O blue screen event 30, 31 booting 19 booting problems 29 overview 5 C problem diagnosis 29, 32, 33 PXE (preboot execution environment) 7, 13, 14 CHAP 7, 10, 33 crash dump 19, 29 P S DHCP server 10, 11, 12 discovery protocols 21, 33 downloading files 5, 37 slipstream CD 17 support 37 supported adapters 5 supported operating systems 5 supported targets 21, 29 E T event logs 33 target connection problems 29, 30, 32, 33 target installs 13, 14 target login problems 33 teaming limitations 2