QLogic iscsi Boot for HPE FlexFabric Adapters User Guide

Transcription

1 QLogic iscsi Boot for HPE FlexFabric Adapters User Guide Abstract This document is for the person who installs, administers, and troubleshoots servers and storage systems. Hewlett Packard Enterprise assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels. Part Number: R November 2015 Edition: 3

2 Copyright 2013, 2015 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

3 Contents Introduction... 5 iscsi boot overview... 5 FlexFabric supported adapters for QLogic iscsi boot... 5 QLogic iscsi boot supported operating systems... 5 Downloading files... 6 Setup... 7 iscsi boot setup... 7 Configuring the iscsi target... 7 Configuring iscsi boot parameters... 7 Preparing the iscsi boot image Booting Other iscsi boot considerations iscsi offload in Windows server iscsi offload limitations Configuring iscsi offload Troubleshooting Boot fails when switching to QLogic iscsi offload QLogic iscsi Crash Dump utility does not capture a memory dump HBA offload miniport BXOIS does not load Inbox driver does not update Installing Windows on an iscsi target fails IP address conflict iscsi target is not recognized as an installation target iscsi configuration utility does not run NDIS miniports with Code 31 yellow-bang after L2 iscsi boot installation System blue screen appears after setting iscsi boot LUN to System blue screen occurs when installing through Windows Plug-and-Play System blue screen occurs when iscsi boots Windows 2008 R Frequently asked questions iscsi offload FAQs Event notifications Offload iscsi driver Warranty and regulatory information Warranty information Regulatory information Safety and regulatory compliance Belarus Kazakhstan Russia marking Turkey RoHS material content declaration Ukraine RoHS material content declaration Support and other resources Accessing Hewlett Packard Enterprise Support Information to collect Accessing updates Websites Customer Self Repair Remote support Acronyms and abbreviations Documentation feedback Contents 3

4 Index Contents 4

5 Introduction iscsi boot overview 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 (QLogic offload iscsi driver or HBA). The iscsi configuration utility configures the path with the HBA Boot Mode option located on the General Parameters screen. For more information on all General Parameters screen configuration options, see "Configuring iscsi boot parameters (on page 7)." iscsi boot for offload path is not supported with VMware. FlexFabric supported adapters for QLogic iscsi boot The following HPE FlexFabric adapters support iscsi boot: FlexFabric 10Gb 2-port 534M Adapter FlexFabric 10Gb 2-port 534FLR-SFP+ Adapter FlexFabric 10Gb 2-port 534FLB Adapter StoreFabric CN1100R 2-port CNA Adapter FlexFabric 20Gb 2-port 630M Adapter FlexFabric 20Gb 2-port 630 FLB Adapter FlexFabric 10Gb 2-port 536FLB Adapter QLogic iscsi boot supported operating systems The HPE FlexFabric adapters support iscsi boot on these operating systems: Windows Server 2008 SP2 and later Windows 2012 and later Linux RHEL 5.8 and later Linux RHEL 6.2 and later SLES 11 SP2 and later VMware ESXi 5.1 or later (offload path is not supported) IMPORTANT: iscsi secure boot is not supported for SLES 11 SP3, SLES 12, or RHEL 7. Introduction 5

6 Downloading files 1. Go to the Hewlett Packard Enterprise website ( 2. Select Support & Drivers, and then select Drivers & Software. 3. Type the adapter name in the For product box, and then click Go. For example, type HPE FlexFabric. 4. Download the drivers, firmware, or documentation as needed. Introduction 6

7 Setup iscsi boot setup To set up an iscsi boot: Configuring the iscsi target (on page 7) Configuring iscsi boot parameters (on page 7) Preparing the iscsi boot image (on page 13) 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. Map the virtual disk to the new iscsi target. 4. Associate an iscsi initiator with the iscsi target. 5. While configuring the iscsi target, record this information: o Target name o Target IQN o Target IP address o Target TCP port number o Target LUN o Initiator IQN o CHAP ID and secret Configuring iscsi boot parameters Configure the iscsi boot software for either static or dynamic configuration. For the configuration options and IPv4 and IPv6 parameters that are available in the General Parameters screen, see "Configuration options (on page 7)." The availability of IPv6 iscsi boot is platform and device dependent. Configuration options Option TCP/IP parameters via DHCP Description 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). Setup 7

8 Option Description IP Auto-configuration iscsi parameters via DHCP CHAP Authentication DHCP Vendor ID Link Up Delay Time Use TCP Timestamp Target as First HDD 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). Router solicit packets are sent out up to three times with 4 second intervals in between each retry. Or, use a static IP configuration (Disabled). This option controls whether the iscsi boot host software acquires the iscsi target parameters using DHCP (Enabled) or through a static configuration (Disabled). The static information is entered through the iscsi Initiator Parameters Configuration screen. This option 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. This option 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. This option 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. For example, set a value for this option if a network protocol such as Spanning Tree is enabled on the switch interface to the client system. This option controls if the TCP Timestamp option is enabled or disabled. This option specifies whether the iscsi target drive appears as the first hard drive in the system. FlexFabric adapters do not support this feature. LUN Busy Retry Count This option controls the number of connection retries the iscsi boot initiator attempts if the iscsi target LUN is busy. IP Version This option is specific to IPv6 and toggles between the IPv4 and IPv6 protocols. All IP settings are lost when switching from one protocol version to the other. HBA Boot Mode Set this option to disable when the host OS is configured for software initiator mode and to enable for HBA mode. This option is available on HPE FlexFabric adapters. The parameter cannot be changed when the adapter is in Multi-Function mode. MBA boot protocol configuration To configure the boot protocol: 1. Restart your system. 2. At the PXE banner, press CTRL+S. The MBA Configuration Menu appears. 3. From the MBA Configuration Menu, use the up or down arrows to move to the Boot Protocol option. Use the left or right arrows to change the Boot Protocol option to iscsi. 4. Select iscsi Boot Configuration from the main menu. If iscsi boot firmware is not programmed in the HPE FlexFabric adapter, selecting iscsi Boot Configuration does not have any effect. iscsi boot configuration To configure iscsi boot, do one of the following: Static iscsi boot configuration (on page 9) Dynamic iscsi boot configuration (on page 10) Setup 8

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 7)." For information on configuration options, see "Configuration options (on page 7)." To configure the iscsi boot parameters using static configuration: 1. From the General Parameters Menu screen, configure these options: o o o o o TCP/IP parameters via DHCP: Disabled (for IPv4) IP Autoconfiguration: Disabled (for IPv6, non-offload) iscsi parameters via DHCP: Disabled CHAP Authentication: Disabled DHCP Vendor ID: BRCM ISAN o Link Up Delay Time: 0 o o Use TCP Timestamp: Enabled Target as First HDD: Disabled o LUN Busy Retry Count: 0 o o IP Version: IPv6 (for IPv6, non-offload) HBA Boot Mode: Disabled For 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. 3. From the main menu, select Initiator Parameters. 4. From the Initiator Parameters screen, configure these values: o o o o o o IP Address (unspecified IPv4 and IPv6 addresses should be " " and "::", respectively) Subnet Mask Prefix Default Gateway Primary DNS Secondary DNS SCSI Name (corresponds to the iscsi initiator name used by the client system) IMPORTANT: Check that the IP address is correct. There is no automatic error-checking performed against the IP address to find duplicates or incorrect segment or network assignments. 5. Press ESC to return to the main menu. 6. From the main menu, select 1st Target Parameters. 7. From the 1st Target Parameters screen, enable Connect to connect to the iscsi target. Enter values for these options using the values used when configuring the iscsi target: 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. Setup 9

10 Dynamic iscsi boot configuration For a dynamic configuration, specify the system IP address. The target and initiator information are provided by a DHCP server. For more information, see the IPv4 and IPv6 configurations in "Configuring the DHCP Server to Support iscsi Boot (on page 11)." For IPv4, 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 IPv6, with the exception of the CHAP ID and Secret, 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 "Configuration options (on page 7)." IMPORTANT: When using a DHCP server, the DNS server entries are overwritten by the values provided by the DHCP server. Overwriting the DNS server entries with the values provided by the DHCP server 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 When the Windows OS takes over, the Microsoft iscsi initiator retrieves the iscsi initiator parameters and configures the appropriate registries statically. iscsi initiator overwrites whatever is configured. Because 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. 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 following name: iqn com.broadcom.< >.iscsiboot where the string corresponds to the controller MAC address. If DHCP option 43 (IPv4 only) 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: 1. From the General Parameters Menu screen, configure these options: o TCP/IP parameters via DHCP: Enabled (for IPv4) o IP Autoconfiguration: Enabled (for IPv6, non-offload) o iscsi parameters via DHCP: Enabled o CHAP Authentication: Disabled o DHCP Vendor ID: BRCM ISAN o Link Up Delay Time: 0 o Use TCP Timestamp: Enabled 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 HPE 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. Press Exit, and then select Save Configurations. Setup 10

11 Enabling CHAP authentication Ensure that CHAP authentication is enabled on the target. To enable CHAP authentication: 1. From the General Parameters screen, set CHAP Authentication to Enabled. 2. From the Initiator Parameters screen, enter values for these options: o o CHAP ID (up to 128 bytes) CHAP Secret (if authentication is required) The CHAP Secret must be 12 characters in length or longer. 3. Press ESC to return to the main menu. 4. From the main menu, select 1st Target Parameters. 5. From the 1st Target Parameters screen, enter the same values as the configured iscsi target: o o CHAP ID (optional if two-way CHAP) CHAP Secret (optional if two-way CHAP) The CHAP Secret must be 12 characters in length or longer. 6. Press ESC to return to the main menu. 7. Press ESC, and then select Exit and Save Configuration. Configuring the DHCP server to support iscsi boot The DHCP server is an optional component that is only necessary for a dynamic iscsi Boot configuration setup. See "Dynamic iscsi Boot Configuration (on page 10)" for more information. Configuring the DHCP server to support iscsi boot is different for IPv4 and IPv6. To configure the DHCP server to support iscsi boot, do one of the following: DHCP iscsi boot configurations for IPv4 (on page 11) DHCP iscsi boot configuration for IPv6 (on page 12) DHCP iscsi boot configurations for IPv4 The DHCP protocol includes a number of options that provide configuration information to the DHCP client. For iscsi boot, adapters support these DHCP configurations: DHCP option 17, root path (on page 11) DHCP option 43, vendor-specific information (on page 12) 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>". Parameter "iscsi" Definition 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 Setup 11

12 Parameter <LUN> <targetname> Definition The Logical Unit Number to use on the iscsi target The value of the LUN must be represented in hexadecimal format. Configure a LUN with an ID of 64 as 40 within the option 17 parameter on the DHCP server. The target name in either IQN or EUI format. See the RFC 3720 for details on both IQN and EUI formats. An example IQN name is iqn 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 sub-options 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 IQN. DHCP option 43 is supported on IPv4 only. The sub-options are listed in DHCP option 43 sub-option definitions. Using DHCP option 43 requires more configuration than DHCP option 17, but it provides more configuration options suitable for a dynamic iscsi boot configuration. Sub-option Definition 201 First iscsi target information in the standard root path format: "iscsi:"<servername>":"<protocol>":"<port>":"<lun>":"<targetname>" 202 Second issue target information in the standard root path format: "iscsi:"<servername>":"<protocol>":"<port>":"<lun>":"<targetname>" 203 iscsi initiator IQN Configuring the DHCP server Configure the DHCP server to support option 17 or option 43. For option 43, also configure option 60. Match the value of option 60 to the DHCP Vendor ID value. The DHCP Vendor ID value is BRCM ISAN, as shown in General Parameters of the iscsi Boot Configuration menu. 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, HPE FlexFabric adapters support these DHCP configurations: DHCPv6 option 16, vendor class option (on page 12) DHCPv6 option 17, vendor-specific information (on page 13) The DHCPv6 standard root path option is not available. Use option 16 or option 17 for dynamic iscsi boot IPv6 support. DHCPv6 option 16, vendor class option DHCPv6 option 16 (vendor class option) must be present and must contain a string that matches the configured DHCP Vendor ID parameter. The DHCP Vendor ID value is BRCM ISAN, as shown in General Parameters of the iscsi Boot Configuration menu. The content of option 16 should be <2-byte length> <DHCP Vendor ID>. Setup 12

13 DHCPv6 option 17, vendor-specific information DHCPv6 option 17 (vendor-specific information) provides more configuration options to the iscsi client. In this configuration, three additional sub-options are provided that assign the initiator IQN to the iscsi boot client along with two iscsi target IQNs that are used for booting. Sub-option Definition 201 First iscsi target information in the standard root path format: "iscsi:"[<servername>]":"<protocol>":"<port>":"<lun>":"<targetname>" 202 Second iscsi target information in the standard root path format: "iscsi:"[<servername>]":"<protocol>":"<port>":"<lun>":"<targetname>" 203 iscsi initiator IQN Brackets [ ] are required for the IPv6 addresses. The content of option 17 is <2-byte Option Number > <2-byte length> <data>. Configuring the DHCPv6 server Configure the DHCP server to support option 16 and option 17. The format of DHCPv6 option 16 and option 17 are fully defined in RFC Preparing the iscsi boot image To prepare the iscsi boot image: Windows Server 2008 R2 and SP2 iscsi boot setup (on page 13) Windows Server 2012 iscsi boot setup (on page 14) Linux iscsi boot setup (on page 15) Injecting (slipstreaming) QLogic drivers into Windows image files (on page 18) 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 the non-offload paths. The following procedure prepares the image for installation and booting in either the offload or the non-offload path. The following procedure references Windows Server 2008 R2, but it is common to both the Windows Server 2008 R2 and SP2. The required CD/ISO image includes Windows 2008 R2 x64 with the QLogic drivers injected. For more information, see "Injecting (slipstreaming) QLogic drivers into Windows image files (on page 18)." Also, see the knowledge base topic KB on the Microsoft website ( The Microsoft procedure injects only the QLogic 10/20GbE Multi-Function Drivers for Windows. For best performance, inject all of the drivers, including the QLogic 1Gb Multi-Function Driver for Windows. The drivers become available after extracting the QLogic10/20Gb Multi-Function adapter installer. The Bindview.exe software is required (for Windows Server 2008 R2 only). For more information, see the knowledge base topic KB on the Microsoft website ( To set up Windows Server 2008 R2 and SP2 iscsi boot: 1. Remove any local hard drives on the system to be booted (the remote system). If the system includes an embedded smart array controller, disable the controller if it is not in use. 2. Load the latest QLogic MBA and iscsi boot images onto NVRAM of the adapter. Setup 13

14 3. Configure the iscsi target to allow a connection from the remote device. Be sure that the target has sufficient disk space to hold the new OS installation. 4. Boot the remote system. The PXE banner appears. 5. Press Ctrl+S to enter the PXE menu. 6. At the PXE menu, set Boot Protocol to iscsi. 7. Enter the iscsi target parameters. 8. Set the HBA Boot Mode to Enabled or Disabled. The parameter cannot be changed when the adapter is in Multi-Function mode. 9. Save the settings, and then reboot the system. The remote system connects to the iscsi target, and then boots from the DVDROM device. 10. Boot to DVD, and then begin the installation. 11. Answer all of the installation questions appropriately. When the Where do you want to install Windows? window appears, the target drive is visible. This is a drive connected via the iscsi boot protocol that is located in the remote iscsi target. 12. Select Next to proceed with Windows 2008 R2 installation. A few minutes after the Windows 2008 R2 DVD installation process starts, the system reboots. After the reboot, the Windows 2008 R2 installation routine resumes and completes the installation. 13. After the system restarts, verify that the remote system boots to the desktop. 14. After Windows 2008 R2 boots, load all of the drivers, and then run Bindview.exe. a. Select All Services. b. The binding paths are listed under Windows Filtering Platform Lightweight Filter. Right-click and disable the binding paths, and then exit the application. 15. Verify that the OS and the system are functional and can pass traffic by pinging a remote system IP address. 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 QLogic drivers injected. For more information, see "Injecting (slipstreaming) QLogic drivers into Windows image files (on page 18)." Also, see the base topic KB on the Microsoft website ( The Microsoft procedure injects only the QLogic 10/20GbE Multifunction Drivers for Windows. For best performance, inject all drivers including the QLogic 1Gb Multifunction Driver for Windows. The following procedure prepares the image for installation and booting in either the offload or non-offload path. To set up Windows Server 2012 iscsi boot: 1. Remove any local hard drives on the system to be booted (the remote system). 2. Load the latest QLogic MBA and iscsi boot images onto NVRAM of the adapter. 3. Configure the iscsi target to allow a connection from the remote device. Be sure that the target has sufficient disk space to hold the new OS installation. 4. Boot the remote system. The PXE banner displays 5. Press Ctrl+S to enter the PXE menu. 6. In the PXE menu, set Boot Protocol to iscsi. 7. Enter the iscsi target parameters. Setup 14

15 8. Set HBA Boot Mode to Enabled or Disabled. The parameter cannot be changed when the adapter is in Multi-Function mode. 9. Save the settings, and then reboot the system. The remote system connects to the iscsi target and then boots from the DVDROM device. 10. Boot to DVD, and then begin the installation. 11. Answer the installation questions appropriately. When the Where do you want to install Windows? window appears, the target drive is visible. This is a drive connected via the iscsi boot protocol that is located in the remote iscsi target. 12. Select Next to proceed with Windows 2012 installation. A few minutes after the Windows 2012 DVD installation process starts, the system reboots. After the reboot, the Windows 2012 installation routine resumes and completes the installation. 13. After the system restarts, verify that the remote system boots to the desktop. 14. After Windows 2012 boots to the OS, run the driver installer to complete the drivers and application installation. Linux iscsi boot setup Linux iscsi boot is supported on Red Hat Enterprise Linux 5.9 and later and SUSE Linux Enterprise Server 11 SP2 and later in both the offload and non-offload paths. To set up Linux iscsi boot, do one of the following: Set up Linux iscsi boot using local hard drive installation (on page 15) 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. Be sure the 2, 3, and 5 run-levels of iscsi service are on: chkconfig -level 235 iscsi on 4. (Optional) Install iscsiuio ("Running the iscsiuio configuration script" on page 16). 5. (Optional) Install the linux-nx2 package. 6. Install the bibt package. 7. Remove all ifcfg-eth* files. 8. Reboot the system. 9. Configure one port of the network adapter to connect to the iscsi target. 10. Connect to the iscsi target. 11. Run the DD command to copy the local hard drive to the iscsi target. 12. When the DD command is complete, execute the sync command twice, log out, and then log in to the iscsi target again. 13. Run the fsck command on all partitions created on the iscsi target. The initial installation is complete. To complete the setup, create new customized initrd images for new and updated components. To create initrd images for new and updated components: 1. On the /OPT/bcm/bibt folder, run the iscsi_setup.sh script to create the initrd images. Option 0 creates a non-offload image and option 1 creates an offload image. Setup 15

16 2. Mount the /boot partition on the iscsi target. 3. Copy the newly created initrd images from the local hard drive to the mounted partition. 4. On the mounted partition, edit the grub menu to point to the new initrd images. 5. Unmount the /boot partition on the iscsi target. 6. To enable CHAP for Red Hat, modify the CHAP section of the iscsid.conf file on the iscsi target. Optionally, edit the iscsid.conf file with one- or two-way CHAP information. 7. Power down system, and then disconnect the local hard drive. The iscsi target is ready to iscsi boot. 8. Configure iscsi boot parameters, including CHAP parameters as appropriate. For more information, see "Configuring the iscsi target (on page 7)." 9. Boot to the iscsi boot image, and then select one of the new images (non-offload or offload). The image should correspond to the iscsi Boot Parameters section. If HBA Boot Mode is enabled in the iscsi boot parameters, boot the offload image. SLES 11 does not support offload. Running the iscsiuio configuration script As an optional step for a local hard drive setup of Linux iscsi boot, run the iscsiuio script version b or later. Linux kernel dependencies include the following: QLogic CNIC driver (cnic) QLogic 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. Uncompress the tar 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. Run make install to place the binaries in the appropriate installation location. The default location is /sbin. The network interface configuration files are driven by the iscsid iface files. The configuration data is parsed by iscsid and passed to the uip stack when the connection is established. To run iscsiadm commands to create and set the configuration with the iface files: 1. Create the iface file: iscsiadm -m iface -I <iface name> --op=new 2. Discover the targets associated with the new iface: iscsiadm -m discovery -t st -p <iscsi target IP address> -I <iface name> 3. To update the iface file, do one of the following: o For a static IPv4 address: Setup 16

17 o iscsiadm -m iface -I <iface name> --op=update --name=iface.ipaddress --value=<static IPv4 address ie: > For a DHCP address: iscsiadm -m iface -I <iface name> --op=update --name=iface.ipaddress --value= Enter required values for the iface file. o o To specify the bnx2i as the transport: iscsiadm -m iface -I <iface name> --op=update --name=iface.transport_name --value=bnx2i To specify the network interface for offload: i. Specify the physical network interface name (for example, eth0, eth1, eth2, and so on): iscsiadm -m iface -I <iface name> --op=update --name=iface.net_ifacename --value=<network interface name> ii. Specify the iscsi MAC address of the iscsi HBA: iscsiadm -m iface -I <iface name> --op=update --name=iface.hwaddress --value=<mac address of the iscsi HBA> 5. Test the iscsi target connection: iscsiadm -m node -p <iscsi target IP address> -T <target name> -I <iface name> --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. After completing the remote DVD installation, the system can be set up to boot from either path. Remote Linux boot setup with an offload path To set up a Linux iscsi boot using remote DVD installation and an offload path: 1. For driver updates, obtain the latest QLogic Linux driver CD. 2. Configure iscsi boot parameters for a DVD direct installation to target. 3. To install through a non-offload or through an offload path, set the HBA Boot Mode in the NVRAM Configuration to one of the following: o Select Disabled for a non-offload path. o Select Enabled for an offload path. Installation through the offload path is supported for RHEL 6.2 and SLES 11 SP2 and later. The HBA Boot Mode cannot be changed when the adapter is in Multi-Function mode. 4. Reboot the system. The system connects to the iscsi target, and then the system boots from the CD/DVD drive. 5. Follow the corresponding OS instructions. a. For Red Hat 6.2 and later, enter linux dd at the boot prompt, and then press the Enter key. Or, use the in-box drivers. b. For SLES11 SP2 and later, enter linux dd at the boot prompt, and then press the Enter key. Or, use the in-box drivers. 6. Load the CD driver, and then follow the instructions to update the driver. 7. At the networking device prompt, choose the network adapter port, and then click OK. 8. At the configure TCP/IP prompt, configure the IP address acquisition, and then click OK. For a static IP address, enter the IP information for the iscsi initiator. Indicate first priority for DHCP IP addresses and secondary priority for static IP addresses. 9. For Red Hat, skip the media testing. Setup 17

18 10. Remove the CD/DVD after the installation is complete and all files are copied. The system reboots. 11. Modify the iscsid.conf to enable CHAP. 12. Reboot the system, and then configure the CHAP parameters for the system. Be sure that CHAP is enabled in the option ROM and storage box. Injecting (slipstreaming) QLogic drivers into Windows image files Obtain the QLogic10/20GbE Multifunction Driver for Windows. 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. For Windows Server 2012, install the Windows Assessment and Deployment Kit. 2. Enter the following commands to create a temporary directory, and then set it as the current directory for all later steps: o md C:\Temp\x o cd /d C:\Temp\x 3. Enter the following commands to create two subdirectories: o md src o md mnt 4. Enter the following command to copy the original DVD into the src subdirectory: xcopy N:\.\src /e /c /i /f /h /k /y /q In this example, the installation DVD is in the N: drive. 5. Open a Deployment and Imaging Tools command prompt in elevated mode. Perform the rest of the procedure in the Deployment and Imaging Tools command prompt window. 6. Set c:\temp\x as the current directory. 7. Enter the following commands: o attrib -r.\src\sources\boot.wim o attrib -r.\src\sources\install.wim 8. Enter the following command to mount the boot.wim image: dism /mount-wim /wimfile:.\src\sources\boot.wim /index:2 /mountdir:.\mnt Always use 2 for the index value. 9. 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 The command to extract all drivers at one time is dism /image:.\mnt /add-driver /driver:c:\temp\driver /recurse /forceunsigned. 10. Enter the following command to unmount the boot.wim image: dism /unmount-wim /mountdir:.\mnt /commit Setup 18

19 Booting 11. Enter the following command to determine the index of the SKU you want in the install.wim image: dism /get-wiminfo /wimfile:.\src\sources\install.wim For example, in Windows Server 2012, index 2 is identified as "Windows Server 2012 SERVERSTANDARD." 12. Enter the following command to mount the install.wim image: 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. Enter the following command to unmount the install.wim image: dism /unmount-wim /mountdir:.\mnt /commit 15. Enter the following command to create an.iso file: oscdimg -e -h -m -n -lslipstream -bootdata:2#p0,e,b"c:\program Files\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com"#pEF,e,b"c:\Program Files\Windows AIK\Tools\PETools\amd64\boot\efisys.bin" c:\temp\x\src c:\temp\win20xxmod.iso Platform is a placeholder for the architecture of the operating system that is being installed, such as amd64 or x86. Also, xx in the file names is a placeholder for the Windows Server OS version (2012, 2008R2, or 2008SP2.) 16. (Optional) Using a DVD-burning application, burn the.iso file you created to a DVD. 17. (Optional) Use the DVD that you created to install the applicable Windows Server version. After the system has been prepared for an iscsi boot and the operating system is present on the iscsi target, boot the system. The system boots to Windows or Linux over the network and operate like a local disk drive. To boot the system: 1. Reboot the server. 2. Press CTRL+S. 3. Do one of the following: o To boot through an offload path, set the HBA Boot Mode to Enabled. o To boot through a non-offload path, set the HBA Boot Mode to Disabled. The HBA Boot Mode parameter cannot be changed when the adapter is in Multi-Function mode. If CHAP authentication is needed, enable CHAP authentication after determining that booting is successful. See "Enabling CHAP authentication (on page 11)" for more information. Other iscsi boot considerations There are several other factors to consider when configuring a system for iscsi boot. Changing the speed and duplex settings in Windows environments Setup 19

20 Changing the speed and duplex settings on the boot port using Windows Device Manager when performing iscsi boot through the offload path is not supported. Booting through the NDIS path is supported. Use the BACS management utility to change the speed and duplex settings or use CNU 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 utility To use the QLogic iscsi Crash Dump utility, follow the installation procedure for the iscsi Crash Dump driver. iscsi offload in Windows server iscsi offload is a technology that offloads iscsi protocol processing overhead from host processors to the iscsi host bus adapter to increase network performance and throughput while optimizing server processor utilization. iscsi offload limitations The following limitations are known for iscsi offload: The bnx2i driver for iscsi does not operate on a standalone PCI device. The driver shares the same PCI device with the networking driver (bnx2 and bnx2x). The networking driver alone supports layer 2 networking traffic. Offloaded iscsi operations require both the networking driver and the bnx2i driver. iscsi operations are interrupted when the networking driver brings down or resets the device. This scenario requires proper handling by the networking and bnx2i drivers, as well as the user space iscsid daemon that keeps track of all iscsi sessions. Offloaded iscsi connections take up system and on-chip resources that must be freed up before the device can be reset. Running iscsid in user space can be unpredictable because it is slow to disconnect and reconnect iscsi sessions during network resets, especially for a large number of connections. iscsi sessions might not recover when the networking device is repeatedly reset. To mitigate the effect of the limitations: Minimize administrator-administered network device resets, such as MTU change, ring size change, device shutdown, hot-unplug, and so forth, while there are active offloaded iscsi sessions running on the shared device. Link-related changes do not require device resets and can be performed at any time. Install the latest open-iscsi utilities by upgrading your Red Hat Network subscription. Configuring iscsi offload Configure the HPE FlexFabric adapter to offload iscsi processing from the host processor. To set up the QLogic iscsi offload feature: Installing QLogic drivers and management applications (on page 21) Installing the Microsoft iscsi Initiator (on page 21) Configuring QLogic iscsi using BACS (on page 21) Configuring Microsoft Initiator to use QLogic iscsi offload (on page 21) Setup 20

21 Installing QLogic drivers and management applications To install drivers and management applications: 1. Install the Windows drivers. 2. Install BACS or CNU 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 ( search the downloads for the iscsi initiator, and then use the direct link for your specific system. Configuring QLogic iscsi using BACS Use BACS to manage network adapters and advanced features. To configure iscsi using BACS: 1. Open BACS. 2. Select the HPE FlexFabric adapter. If the C-NIC iscsi adapter is not present, select the Virtual Bus Device, and then select iscsi Offload Engine from the Resource Reservations area of the Configuration tab to enable iscsi offload. 3. Open the Configuration tab. DHCP is the default for IP address assignment. A static IP address can be assigned (optional). The IP address assignment method cannot be changed if the adapter was used for boot. 4. Select Apply, and then close BACS. Configuring Microsoft Initiator to use QLogic iscsi offload After configuring the IP address, use Microsoft Initiator to configure and add a connection to the iscsi target using iscsi adapter. For more details on Microsoft Initiator, see the Microsoft documentation. To configure the Microsoft Initiator to use iscsi offload: 1. Open Microsoft Initiator. Setup 21

22 2. Configure the initiator IQN name according to your setup. To change the name, click Change. 3. Enter the initiator IQN name. Setup 22

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

24 6. From the General tab, select the HPE FlexFabric adapter from Local adapter. Setup 24

25 7. Select the IP address for the adapter from Source IP. Setup 25

26 8. Click OK to close Advanced settings, and then click OK to add the target portal. Setup 26

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

28 11. On the General tab, select the HPE 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. Setup 28

29 Troubleshooting Boot fails when switching to QLogic iscsi offload Possible cause: When switching iscsi boot from the Microsoft standard path to QLogic iscsi offload, the boot fails to complete. Action: Install or upgrade the QLogic Virtual Bus Device driver to 5.0.x and the OIS driver prior to switching the iscsi boot path. QLogic 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. Action: Be sure that the link speed for iscsi boot is configured for 1 Gbps or 10 Gbps, which are supported by the iscsi Crash Dump utility. HBA offload miniport BXOIS does not load Possible cause: Toggling between iscsi HBA offload mode and iscsi software initiator boot causes the HBA offload miniport BXOIS not to load. Action: Manually edit [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bxois\StartOverride] from 3 to 0. Modify the registry key before toggling back from NDIS to HBA path in CCM. Inbox driver does not update Possible cause: The inbox driver does not update if a non-inbox hardware ID present. Action: Create a custom slipstream DVD image with supported drivers present on the install media. Installing Windows on an iscsi target fails Possible cause: Installing Windows onto an iscsi target through iscsi boot fails when connecting to a 1 Gbps switch port. Action: This is a limitation relating to adapters that use SFP+ as the physical connection. SFP+ defaults to 10 Gbps operation and does not support auto-negotiation. IP address conflict Symptom: For static IP configurations, an IP address conflict message appears when switching from Layer 2 iscsi boot to QLogic iscsi HBA. Action: Change the IP address of the network property in the OS. Troubleshooting 29

30 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. For more information, see the article KB on the Microsoft website ( iscsi configuration utility does not run Symptom: The iscsi configuration utility does not run. Action: Be sure that the iscsi Boot firmware is installed in the NVRAM. NDIS miniports with Code 31 yellow-bang after L2 iscsi boot installation Symptom: NDIS miniports with Code 31 yellow-bang after L2 iscsi boot installation. Action: Run the T7.8 or later installer. System blue screen appears after setting iscsi boot LUN to 255 Possible cause: After configuring the iscsi boot LUN to 255, a system blue screen appears when performing iscsi boot. Action: Configure a LUN value from 0 to 254. Although QLogic iscsi supports a LUN range from 0 to 255, the Microsoft iscsi software initiator does not support a LUN of 255. System blue screen occurs when installing through Windows Plug-and-Play Possible cause: A system blue screen occurs when installing the QLogic drivers through Windows Plug-and-Play. Action: Install the drivers through the Setup installer. 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. Troubleshooting 30

31 Frequently asked questions iscsi offload FAQs Q: How do I assign an IP address for iscsi offload? A: Use the Configurations tab in BACS or use CNU. 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... A non-offloaded connection displays an entry beginning with Root... Q: What configurations should be avoided? A: The IP address should not be the same as the LAN. Frequently asked questions 31

32 Event notifications Offload iscsi driver The following table lists the offload iscsi driver event log messages. Message Number 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. Dump data contains Expected Command Sequence number followed by Maximum Command Sequence number. 4 Error MaxBurstLength is not serially greater than FirstBurstLength. Dump data contains FirstBurstLength followed by MaxBurstLength. 5 Error Failed to set up initiator portal. Error status is given in the dump data. 6 Error Initiator could not allocate resources for an iscsi connection. 7 Error Initiator could not send an iscsi PDU. Error status is given in the dump data. 8 Error Target or discovery service did not respond in time for an iscsi request sent by the initiator. iscsi function code is given in the dump data. For details about iscsi function code, see the iscsi user guide. 9 Error Target did not respond in time for a SCSI request. The CDB is given in the dump data. 10 Error Login request failed. The login response packet is given in the dump data. 11 Error Target returned an invalid login response packet. The login response packet is given in the dump data. 12 Error Target provided invalid data for login redirect. Dump data contains the data returned by the target. 13 Error Target offered an unknown AuthMethod. Dump data contains the data returned by the target. 14 Error Target offered an unknown digest algorithm for CHAP. Dump data contains the data returned by the target. 15 Error The CHAP challenge given by the target contains invalid characters. Dump data contains the challenge given. 16 Error An invalid key was received during CHAP negotiation. The key=value pair is given in the dump data. 17 Error CHAP response given by the target did not match the expected one. Dump data contains the CHAP response. 18 Error Header digest is required by the initiator, but target did not offer it. 19 Error Data digest is required by the initiator, but target did not offer it. 20 Error Connection to the target was lost. The initiator attempts to retry the connection. 21 Error Data Segment Length given in the header exceeds MaxRecvDataSegmentLength declared by the target. 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. Event notifications 32

33 Message Number Severity Message 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. 26 Error Target trying to send more data than requested by the initiator. 27 Error Initiator could not find a match for the initiator task tag in the received PDU. Dump data contains the entire iscsi header. 28 Error Initiator received an invalid R2T packet. Dump data contains the entire iscsi header. 29 Error Target rejected an iscsi PDU sent by the initiator. Dump data contains the rejected PDU. 30 Error Initiator could not allocate a work item for processing a request. 31 Error Initiator could not allocate resource for processing a request. 32 Information Initiator received an asynchronous logout message. The target name is given in the dump data. 33 Error Challenge size given by the target exceeds the maximum specified in iscsi specification. 34 Information A connection to the target was lost, but the initiator successfully reconnected to the target. Dump data contains the target name. 35 Error Target CHAP secret is smaller than the minimum size (12 bytes) required by the specification. 36 Error Initiator CHAP secret is smaller than the minimum size (12 bytes) required by the specification. Dump data contains the given CHAP secret. 37 Error FIPS service could not be initialized. Persistent logins are not processed. 38 Error Initiator requires CHAP for login authentication, but target did not offer CHAP. 39 Error Initiator sent a task management command to reset the target. The target name is given in the dump data. 40 Error Target requires login authentication via CHAP, but the initiator is not configured to perform CHAP. 41 Error Target did not send AuthMethod key during security negotiation phase. 42 Error Target sent an invalid status sequence number for a connection. Dump data contains the Expected Status Sequence number followed by the given status sequence number. 43 Error Target failed to respond in time for a login request. 44 Error Target failed to respond in time for a logout request. 45 Error Target failed to respond in time for a login request. This login request was for adding a new connection to a session. 46 Error Target failed to respond in time for a SendTargets command. 47 Error Target failed to respond in time for a SCSI command sent through a WMI request. 48 Error Target failed to respond in time to a NOP request. 49 Error Target failed to respond in time to a Task Management request. 50 Error Target failed to respond in time to a Text Command sent to renegotiate iscsi parameters. 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. Event notifications 33

34 Message Number Severity Message 55 Error Initiator failed to allocate resources to send data to target. 56 Error Initiator could not map an user virtual address to kernel virtual address, resulting in I/O failure. 57 Error Initiator could not allocate required resources for processing a request, resulting in I/O failure. 58 Error Initiator could not allocate a tag for processing a request, resulting in I/O failure. 59 Error Target dropped the connection before the initiator could transition to Full Feature Phase. 60 Error Target sent data in the SCSI Response PDU instead of Data_IN PDU. Only Sense Data can be sent in SCSI Response. 61 Error Target set DataPduInOrder to NO when the initiator requested YES. Login fails. 62 Error Target set DataSequenceInOrder to NO when the initiator requested YES. Login fails. 63 Error The target or LUN cannot be reset. Session recovery is attempted. 64 Information An attempt to bootstrap Windows using iscsi NIC Boot ibf is in progress. 65 Error Booting from iscsi is in progress, but no NIC could be set in the Paging Path. 66 Error An attempt to disable the Nagle Algorithm for iscsi connection failed. 67 Information If digest support is selected for iscsi Session, processor support for digest computation is used. 68 Error After receiving an async logout from the target, an attempt to re-login the session failed. Error status is given in the dump data. 69 Error An attempt to recover an unexpected terminated session failed. Error status is given in the dump data. 70 Error An error occurred when processing iscsi login request. The request was not retried. Error status is given in the dump data. 71 Information Initiator did not start a session recovery upon receiving the request. Dump data contains the error status. 72 Error Unexpected target portal IP types were found. Dump data contains the expected IP type. Event notifications 34

35 Warranty and regulatory information Warranty information HPE ProLiant and x86 Servers and Options ( HPE Enterprise Servers ( HPE Storage Products ( HPE Networking Products ( Regulatory information Safety and regulatory compliance For important safety, environmental, and regulatory information, see Safety and Compliance Information for Server, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise website ( Belarus Kazakhstan Russia marking Manufacturer and Local Representative Information Manufacturer information: Hewlett Packard Enterprise Company, 3000 Hanover Street, Palo Alto, CA U.S. Local representative information Russian: Russia: Belarus: Kazakhstan: Local representative information Kazakh: Warranty and regulatory information 35

36 Russia: Belarus: Kazakhstan: Manufacturing date: The manufacturing date is defined by the serial number. CCSYWWZZZZ (serial number format for this product) Valid date formats include: YWW, where Y indicates the year counting from within each new decade, with 2000 as the starting point; for example, 238: 2 for 2002 and 38 for the week of September 9. In addition, 2010 is indicated by 0, 2011 by 1, 2012 by 2, 2013 by 3, and so forth. YYWW, where YY indicates the year, using a base year of 2000; for example, 0238: 02 for 2002 and 38 for the week of September 9. Turkey RoHS material content declaration Ukraine RoHS material content declaration Warranty and regulatory information 36

37 Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website ( To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website ( Information to collect Technical support registration number (if applicable) Product name, model or version, and serial number Operating system name and version Firmware version Error messages Product-specific reports and logs Add-on products or components Third-party products or components Accessing updates Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method. To download product updates, go to either of the following: o Hewlett Packard Enterprise Support Center Get connected with updates page ( o Software Depot website ( To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page ( IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Websites Hewlett Packard Enterprise Information Library ( Hewlett Packard Enterprise Support Center ( Contact Hewlett Packard Enterprise Worldwide ( Support and other resources 37

38 Subscription Service/Support Alerts ( Software Depot ( Customer Self Repair ( Insight Remote Support ( Serviceguard Solutions for HP-UX ( Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix ( Storage white papers and analyst reports ( Customer Self Repair Hewlett Packard Enterprise products are designed with many Customer Self Repair (CSR) parts to minimize repair time and allow for greater flexibility in performing defective parts replacement. If during the diagnosis period Hewlett Packard Enterprise (or Hewlett Packard Enterprise service providers or service partners) identifies that the repair can be accomplished by the use of a CSR part, Hewlett Packard Enterprise will ship that part directly to you for replacement. There are two categories of CSR parts: Mandatory Parts for which customer self repair is mandatory. If you request Hewlett Packard Enterprise to replace these parts, you will be charged for the travel and labor costs of this service. Optional Parts for which customer self repair is optional. These parts are also designed for customer self repair. If, however, you require that Hewlett Packard Enterprise replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product. NOTE: Some Hewlett Packard Enterprise parts are not designed for customer self repair. In order to satisfy the customer warranty, Hewlett Packard Enterprise requires that an authorized service provider replace the part. These parts are identified as "No" in the Illustrated Parts Catalog. Based on availability and where geography permits, CSR parts will be shipped for next business day delivery. Same day or four-hour delivery may be offered at an additional charge where geography permits. If assistance is required, you can call the Hewlett Packard Enterprise Support Center and a technician will help you over the telephone. Hewlett Packard Enterprise specifies in the materials shipped with a replacement CSR part whether a defective part must be returned to Hewlett Packard Enterprise. In cases where it is required to return the defective part to Hewlett Packard Enterprise, you must ship the defective part back to Hewlett Packard Enterprise within a defined period of time, normally five (5) business days. The defective part must be returned with the associated documentation in the provided shipping material. Failure to return the defective part may result in Hewlett Packard Enterprise billing you for the replacement. With a customer self repair, Hewlett Packard Enterprise will pay all shipping and part return costs and determine the courier/carrier to be used. For more information about the Hewlett Packard Enterprise CSR program, contact your local service provider. For the North American program, go to the Hewlett Packard Enterprise CSR website ( Réparation par le client (CSR) Les produits Hewlett Packard Enterprise comportent de nombreuses pièces CSR (Customer Self Repair = réparation par le client) afin de minimiser les délais de réparation et faciliter le remplacement des pièces défectueuses. Si pendant la période de diagnostic, Hewlett Packard Enterprise (ou ses partenaires ou mainteneurs agréés) détermine que la réparation peut être effectuée à l'aide d'une pièce CSR, Hewlett Packard Enterprise vous l'envoie directement. Il existe deux catégories de pièces CSR : Support and other resources 38

39 Obligatoire Pièces pour lesquelles la réparation par le client est obligatoire. Si vous demandez à Hewlett Packard Enterprise de remplacer ces pièces, les coûts de déplacement et main d'œuvre du service vous seront facturés. Facultatif Pièces pour lesquelles la réparation par le client est facultative. Ces pièces sont également conçues pour permettre au client d'effectuer lui-même la réparation. Toutefois, si vous demandez à Hewlett Packard Enterprise de remplacer ces pièces, l'intervention peut ou non vous être facturée, selon le type de garantie applicable à votre produit. REMARQUE: Certaines pièces Hewlett Packard Enterprise ne sont pas conçues pour permettre au client d'effectuer lui-même la réparation. Pour que la garantie puisse s'appliquer, Hewlett Packard Enterprise exige que le remplacement de la pièce soit effectué par un Mainteneur Agréé. Ces pièces sont identifiées par la mention "Non" dans le Catalogue illustré. Les pièces CSR sont livrées le jour ouvré suivant, dans la limite des stocks disponibles et selon votre situation géographique. Si votre situation géographique le permet et que vous demandez une livraison le jour même ou dans les 4 heures, celle-ci vous sera facturée. Pour toute assistance, appelez le Centre d assistance Hewlett Packard Enterprise pour qu un technicien vous aide au téléphone. Dans les documents envoyés avec la pièce de rechange CSR, Hewlett Packard Enterprise précise s'il est nécessaire de lui retourner la pièce défectueuse. Si c'est le cas, vous devez le faire dans le délai indiqué, généralement cinq (5) jours ouvrés. La pièce et sa documentation doivent être retournées dans l'emballage fourni. Si vous ne retournez pas la pièce défectueuse, Hewlett Packard Enterprise se réserve le droit de vous facturer les coûts de remplacement. Dans le cas d'une pièce CSR, Hewlett Packard Enterprise supporte l'ensemble des frais d'expédition et de retour, et détermine la société de courses ou le transporteur à utiliser. Pour plus d'informations sur le programme CSR de Hewlett Packard Enterprise, contactez votre Mainteneur Agrée local. Pour plus d'informations sur ce programme en Amérique du Nord, consultez le site Web Hewlett Packard Enterprise ( Riparazione da parte del cliente Per abbreviare i tempi di riparazione e garantire una maggiore flessibilità nella sostituzione di parti difettose, i prodotti Hewlett Packard Enterprise sono realizzati con numerosi componenti che possono essere riparati direttamente dal cliente (CSR, Customer Self Repair). Se in fase di diagnostica Hewlett Packard Enterprise (o un centro di servizi o di assistenza Hewlett Packard Enterprise) identifica il guasto come riparabile mediante un ricambio CSR, Hewlett Packard Enterprise lo spedirà direttamente al cliente per la sostituzione. Vi sono due categorie di parti CSR: Obbligatorie Parti che devono essere necessariamente riparate dal cliente. Se il cliente ne affida la riparazione ad Hewlett Packard Enterprise, deve sostenere le spese di spedizione e di manodopera per il servizio. Opzionali Parti la cui riparazione da parte del cliente è facoltativa. Si tratta comunque di componenti progettati per questo scopo. Se tuttavia il cliente ne richiede la sostituzione ad Hewlett Packard Enterprise, potrebbe dover sostenere spese addizionali a seconda del tipo di garanzia previsto per il prodotto. NOTA: alcuni componenti Hewlett Packard Enterprise non sono progettati per la riparazione da parte del cliente. Per rispettare la garanzia, Hewlett Packard Enterprise richiede che queste parti siano sostituite da un centro di assistenza autorizzato. Tali parti sono identificate da un "No" nel Catalogo illustrato dei componenti. In base alla disponibilità e alla località geografica, le parti CSR vengono spedite con consegna entro il giorno lavorativo seguente. La consegna nel giorno stesso o entro quattro ore è offerta con un supplemento di costo solo in alcune zone. In caso di necessità si può richiedere l'assistenza telefonica di un addetto del centro di supporto tecnico Hewlett Packard Enterprise. Nel materiale fornito con una parte di ricambio CSR, Hewlett Packard Enterprise specifica se il cliente deve restituire dei component. Qualora sia richiesta la resa ad Hewlett Packard Enterprise del componente difettoso, lo si deve spedire ad Hewlett Packard Enterprise entro un determinato periodo di tempo, generalmente cinque (5) giorni lavorativi. Il componente difettoso deve essere restituito con la documentazione associata nell'imballo di Support and other resources 39

40 spedizione fornito. La mancata restituzione del componente può comportare la fatturazione del ricambio da parte di Hewlett Packard Enterprise. Nel caso di riparazione da parte del cliente, Hewlett Packard Enterprise sostiene tutte le spese di spedizione e resa e sceglie il corriere/vettore da utilizzare. Per ulteriori informazioni sul programma CSR di Hewlett Packard Enterprise, contattare il centro di assistenza di zona. Per il programma in Nord America fare riferimento al sito Web ( Customer Self Repair Hewlett Packard Enterprise Produkte enthalten viele CSR-Teile (Customer Self Repair), um Reparaturzeiten zu minimieren und höhere Flexibilität beim Austausch defekter Bauteile zu ermöglichen. Wenn Hewlett Packard Enterprise (oder ein Hewlett Packard Enterprise Servicepartner) bei der Diagnose feststellt, dass das Produkt mithilfe eines CSR-Teils repariert werden kann, sendet Ihnen Hewlett Packard Enterprise dieses Bauteil zum Austausch direkt zu. CSR-Teile werden in zwei Kategorien unterteilt: Zwingend Teile, für die das Customer Self Repair-Verfahren zwingend vorgegeben ist. Wenn Sie den Austausch dieser Teile von Hewlett Packard Enterprise vornehmen lassen, werden Ihnen die Anfahrt- und Arbeitskosten für diesen Service berechnet. Optional Teile, für die das Customer Self Repair-Verfahren optional ist. Diese Teile sind auch für Customer Self Repair ausgelegt. Wenn Sie jedoch den Austausch dieser Teile von Hewlett Packard Enterprise vornehmen lassen möchten, können bei diesem Service je nach den für Ihr Produkt vorgesehenen Garantiebedingungen zusätzliche Kosten anfallen. HINWEIS: Einige Hewlett Packard Enterprise Teile sind nicht für Customer Self Repair ausgelegt. Um den Garantieanspruch des Kunden zu erfüllen, muss das Teil von einem Hewlett Packard Enterprise Servicepartner ersetzt werden. Im illustrierten Teilekatalog sind diese Teile mit No bzw. Nein gekennzeichnet. CSR-Teile werden abhängig von der Verfügbarkeit und vom Lieferziel am folgenden Geschäftstag geliefert. Für bestimmte Standorte ist eine Lieferung am selben Tag oder innerhalb von vier Stunden gegen einen Aufpreis verfügbar. Wenn Sie Hilfe benötigen, können Sie das Hewlett Packard Enterprise Support Center anrufen und sich von einem Mitarbeiter per Telefon helfen lassen. Den Materialien von Hewlett Packard Enterprise, die mit einem CSR-Ersatzteil geliefert werden, können Sie entnehmen, ob das defekte Teil an Hewlett Packard Enterprise zurückgeschickt werden muss. Wenn es erforderlich ist, das defekte Teil an Hewlett Packard Enterprise zurückzuschicken, müssen Sie dies innerhalb eines vorgegebenen Zeitraums tun, in der Regel innerhalb von fünf (5) Geschäftstagen. Das defekte Teil muss mit der zugehörigen Dokumentation in der Verpackung zurückgeschickt werden, die im Lieferumfang enthalten ist. Wenn Sie das defekte Teil nicht zurückschicken, kann Hewlett Packard Enterprise Ihnen das Ersatzteil in Rechnung stellen. Im Falle von Customer Self Repair kommt Hewlett Packard Enterprise für alle Kosten für die Lieferung und Rücksendung auf und bestimmt den Kurier-/Frachtdienst. Weitere Informationen über das Hewlett Packard Enterprise Customer Self Repair Programm erhalten Sie von Ihrem Servicepartner vor Ort. Informationen über das CSR-Programm in Nordamerika finden Sie auf der Hewlett Packard Enterprise Website unter ( Reparaciones del propio cliente Los productos de Hewlett Packard Enterprise incluyen muchos componentes que el propio usuario puede reemplazar (Customer Self Repair, CSR) para minimizar el tiempo de reparación y ofrecer una mayor flexibilidad a la hora de realizar sustituciones de componentes defectuosos. Si, durante la fase de diagnóstico, Hewlett Packard Enterprise (o los proveedores o socios de servicio de Hewlett Packard Enterprise) identifica que una reparación puede llevarse a cabo mediante el uso de un componente CSR, Hewlett Packard Enterprise le enviará dicho componente directamente para que realice su sustitución. Los componentes CSR se clasifican en dos categorías: Support and other resources 40

41 Obligatorio componentes cuya reparación por parte del usuario es obligatoria. Si solicita a Hewlett Packard Enterprise que realice la sustitución de estos componentes, tendrá que hacerse cargo de los gastos de desplazamiento y de mano de obra de dicho servicio. Opcional componentes cuya reparación por parte del usuario es opcional. Estos componentes también están diseñados para que puedan ser reparados por el usuario. Sin embargo, si precisa que Hewlett Packard Enterprise realice su sustitución, puede o no conllevar costes adicionales, dependiendo del tipo de servicio de garantía correspondiente al producto. NOTA: Algunos componentes de Hewlett Packard Enterprise no están diseñados para que puedan ser reparados por el usuario. Para que el usuario haga valer su garantía, Hewlett Packard Enterprise pone como condición que un proveedor de servicios autorizado realice la sustitución de estos componentes. Dichos componentes se identifican con la palabra "No" en el catálogo ilustrado de componentes. Según la disponibilidad y la situación geográfica, los componentes CSR se enviarán para que lleguen a su destino al siguiente día laborable. Si la situación geográfica lo permite, se puede solicitar la entrega en el mismo día o en cuatro horas con un coste adicional. Si precisa asistencia técnica, puede llamar al Centro de asistencia técnica de Hewlett Packard Enterprise y recibirá ayuda telefónica por parte de un técnico. Con el envío de materiales para la sustitución de componentes CSR, Hewlett Packard Enterprise especificará si los componentes defectuosos deberán devolverse a Hewlett Packard Enterprise. En aquellos casos en los que sea necesario devolver algún componente a Hewlett Packard Enterprise, deberá hacerlo en el periodo de tiempo especificado, normalmente cinco días laborables. Los componentes defectuosos deberán devolverse con toda la documentación relacionada y con el embalaje de envío. Si no enviara el componente defectuoso requerido, Hewlett Packard Enterprise podrá cobrarle por el de sustitución. En el caso de todas sustituciones que lleve a cabo el cliente, Hewlett Packard Enterprise se hará cargo de todos los gastos de envío y devolución de componentes y escogerá la empresa de transporte que se utilice para dicho servicio. Para obtener más información acerca del programa de Reparaciones del propio cliente de Hewlett Packard Enterprise, póngase en contacto con su proveedor de servicios local. Si está interesado en el programa para Norteamérica, visite la página web de Hewlett Packard Enterprise CSR ( Customer Self Repair Veel onderdelen in Hewlett Packard Enterprise producten zijn door de klant zelf te repareren, waardoor de reparatieduur tot een minimum beperkt kan blijven en de flexibiliteit in het vervangen van defecte onderdelen groter is. Deze onderdelen worden CSR-onderdelen (Customer Self Repair) genoemd. Als Hewlett Packard Enterprise (of een Hewlett Packard Enterprise Service Partner) bij de diagnose vaststelt dat de reparatie kan worden uitgevoerd met een CSR-onderdeel, verzendt Hewlett Packard Enterprise dat onderdeel rechtstreeks naar u, zodat u het defecte onderdeel daarmee kunt vervangen. Er zijn twee categorieën CSR-onderdelen: Verplicht Onderdelen waarvoor reparatie door de klant verplicht is. Als u Hewlett Packard Enterprise verzoekt deze onderdelen voor u te vervangen, worden u voor deze service reiskosten en arbeidsloon in rekening gebracht. Optioneel Onderdelen waarvoor reparatie door de klant optioneel is. Ook deze onderdelen zijn ontworpen voor reparatie door de klant. Als u echter Hewlett Packard Enterprise verzoekt deze onderdelen voor u te vervangen, kunnen daarvoor extra kosten in rekening worden gebracht, afhankelijk van het type garantieservice voor het product. OPMERKING: Sommige Hewlett Packard Enterprise onderdelen zijn niet ontwikkeld voor reparatie door de klant. In verband met de garantievoorwaarden moet het onderdeel door een geautoriseerde Service Partner worden vervangen. Deze onderdelen worden in de geïllustreerde onderdelencatalogus aangemerkt met "Nee". Afhankelijk van de leverbaarheid en de locatie worden CSR-onderdelen verzonden voor levering op de eerstvolgende werkdag. Levering op dezelfde dag of binnen vier uur kan tegen meerkosten worden aangeboden, indien dit mogelijk is gezien de locatie. Indien assistentie is gewenst, belt u het Hewlett Packard Enterprise Support Center om via de telefoon ondersteuning van een technicus te ontvangen. Support and other resources 41

42 Hewlett Packard Enterprise vermeldt in de documentatie bij het vervangende CSR-onderdeel of het defecte onderdeel aan Hewlett Packard Enterprise moet worden geretourneerd. Als het defecte onderdeel aan Hewlett Packard Enterprise moet worden teruggezonden, moet u het defecte onderdeel binnen een bepaalde periode, gewoonlijk vijf (5) werkdagen, retourneren aan Hewlett Packard Enterprise. Het defecte onderdeel moet met de bijbehorende documentatie worden geretourneerd in het meegeleverde verpakkingsmateriaal. Als u het defecte onderdeel niet terugzendt, kan Hewlett Packard Enterprise u voor het vervangende onderdeel kosten in rekening brengen. Bij reparatie door de klant betaalt Hewlett Packard Enterprise alle verzendkosten voor het vervangende en geretourneerde onderdeel en kiest Hewlett Packard Enterprise zelf welke koerier/transportonderneming hiervoor wordt gebruikt. Neem contact op met een Service Partner voor meer informatie over het Customer Self Repair programma van Hewlett Packard Enterprise. Informatie over Service Partners vindt u op de Hewlett Packard Enterprise website ( Reparo feito pelo cliente Os produtos da Hewlett Packard Enterprise são projetados com muitas peças para reparo feito pelo cliente (CSR) de modo a minimizar o tempo de reparo e permitir maior flexibilidade na substituição de peças com defeito. Se, durante o período de diagnóstico, a Hewlett Packard Enterprise (ou fornecedores/parceiros da Hewlett Packard Enterprise) concluir que o reparo pode ser efetuado pelo uso de uma peça CSR, a Hewlett Packard Enterprise enviará a peça diretamente ao cliente. Há duas categorias de peças CSR: Obrigatória Peças cujo reparo feito pelo cliente é obrigatório. Se desejar que a Hewlett Packard Enterprise substitua essas peças, serão cobradas as despesas de transporte e mão-de-obra do serviço. Opcional Peças cujo reparo feito pelo cliente é opcional. Essas peças também são projetadas para o reparo feito pelo cliente. No entanto, se desejar que a Hewlett Packard Enterprise as substitua, pode haver ou não a cobrança de taxa adicional, dependendo do tipo de serviço de garantia destinado ao produto. OBSERVAÇÃO: Algumas peças da Hewlett Packard Enterprise não são projetadas para o reparo feito pelo cliente. A fim de cumprir a garantia do cliente, a Hewlett Packard Enterprise exige que um técnico autorizado substitua a peça. Essas peças estão identificadas com a marca "No" (Não), no catálogo de peças ilustrado. Conforme a disponibilidade e o local geográfico, as peças CSR serão enviadas no primeiro dia útil após o pedido. Onde as condições geográficas permitirem, a entrega no mesmo dia ou em quatro horas pode ser feita mediante uma taxa adicional. Se precisar de auxílio, entre em contato com o Centro de suporte técnico da Hewlett Packard Enterprise para que um técnico o ajude por telefone. A Hewlett Packard Enterprise especifica nos materiais fornecidos com a peça CSR de reposição se a peça com defeito deve ser devolvida à Hewlett Packard Enterprise. Nos casos em que isso for necessário, é preciso enviar a peça com defeito à Hewlett Packard Enterprise, você deverá enviar a peça com defeito de volta para a Hewlett Packard Enterprise dentro do período de tempo definido, normalmente em 5 (cinco) dias úteis. A peça com defeito deve ser enviada com a documentação correspondente no material de transporte fornecido. Caso não o faça, a Hewlett Packard Enterprise poderá cobrar a reposição. Para as peças de reparo feito pelo cliente, a Hewlett Packard Enterprise paga todas as despesas de transporte e de devolução da peça e determina a transportadora/serviço postal a ser utilizado. Para obter mais informações sobre o programa de reparo feito pelo cliente da Hewlett Packard Enterprise, entre em contato com o fornecedor de serviços local. Para o programa norte-americano, visite o site da Hewlett Packard Enterprise ( Support and other resources 42

43 Support and other resources 43

44 Support and other resources 44