iscsi Boot for PRIMERGY Servers with Intel Network Controllers Installation and Configuration with Linux

Transcription

1 iscsi Boot for PRIMERGY Servers with Intel Network Controllers Installation and Configuration with Linux June 2015

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2008 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright 2015 Fujitsu Technology Solutions GmbH. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers.

3 Contents 1 Introduction iscsi Boot with SuSE Linux Enterprise Server 11 SP 3/ 11 SP4 / Installation Overview iscsi Boot with Linux Installing SLES on an iscsi Target iscsi Boot with Red Hat Enterprise Linux 6.5 and Installation Overview iscsi Boot with Linux Installing Red Hat Enterprise Linux 6.5 and 6.6 on an iscsi Target iscsi Boot with Red Hat Enterprise Linux Installation Overview iscsi Boot with Linux Installing Red Hat Enterprise Linux 7.1 on an iscsi Target Intel iscsi Boot Configuration Utility iscsi Boot Configurations in Legacy Mode Configuring Controller for iscsi Boot Activating the Option ROM Scan Configuring Network Controller for iscsi Boot Intel iscsi Boot Configuration Utility iscsi Port Selection Menu iscsi Port Configuration Menu iscsi Boot Configuration Menu iscsi Boot with Intel Controllers (Linux)

4 Contents iscsi CHAP Configuration Menu Checking the Connection iscsi Boot Configurations in UEFI Mode Configuring Controller for iscsi Boot Configuring Network Controller for iscsi Boot iscsi Boot Configuration Menu iscsi CHAP Configuration Checking the Connection and Preparing for Installation Checking the Connection Preparing the Operating System Installation Configuring a DHCP Server Troubleshooting Glossary iscsi Boot with Intel Controllers (Linux)

5 1 Introduction iscsi (Internet SCSI) is a protocol for linking servers and data storage facilities, similar to the Fibre Channel Protocol (FCP). iscsi means SCSI over Internet Protocol. iscsi boot allows a server to be booted remotely from a drive in an iscsi-based Storage Area Network (SAN). Bild 1: iscsi connection This manual describes how to configure a PRIMERGY server equipped with Intel network controllers for iscsi boot, focusing on the following issues: Configuring the system BIOS and network controllers Associating an iscsi initiator with the iscsi target Recording the iscsi target name, TCP port number, iscsi LUN, and authentication details iscsi Boot with Intel Controllers (Linux) 5

6 Introduction Configuring the iscsi Target Configuration of the iscsi target varies according to the iscsi target vendor. In this document the various vendors cannot be covered in detail. The general steps include: Creating an iscsi target Associating an iscsi initiator with the iscsi target Recording the iscsi target name, TCP port number, iscsi LUN, and authentication details Refer to the iscsi target vendor s documentation for the specific steps associated with the selected iscsi target device. After the target has been configured the following information should be collected from the target: The iscsi target IQN The iscsi target IP address The iscsi target TCP port number The iscsi target CHAP ID & secret The exact configuration process of a PRIMERGY server for iscsi depends on the operating system. References RFC 3720, Internet Small Computer Systems Interface (iscsi), RFC 4173, Bootstrapping Clients using the Internet Small Computer System Interface (iscsi) Protocol, Please begin by finding out about the requirements of your PRIMERGY system as well as those of the Intel controllers you use. I iscsi via IPv4 is used in this document. It is also possible to use IPv6. 6 iscsi Boot with Intel Controllers (Linux)

7 Introduction Supported network adapters for iscsi Model FTS Code No. Part No. Fujitsu Dual Port 10G S26361-F3629-E2/E202 A3C Adapter D2755 Intel X540-T Dual Port 10GBase-T Network Adapter S26361-F3752-E2/E202 A3C Installation via ServerView is also supported for these adapters. However, an installation of this type is not possible for onboard LAN cards. iscsi Boot with Intel Controllers (Linux) 7

8 Introduction 8 iscsi Boot with Intel Controllers (Linux)

9 2 iscsi Boot with SuSE Linux Enterprise Server 11 SP 3/ 11 SP4 / 12 This chapter describes how to configure your server with SuSE Linux Enterprise Server (SLES) 11 SP3 / 11 SP4/ 12 to support iscsi boot with Intel LAN controllers. 2.1 Installation Overview The following steps are necessary to configure a system to support iscsi boot processes under SuSE Linux: Configuring the iscsi Target (for general information, see the similarly named section on page 6. For further information, please see the documentation provided by the iscsi target manufacturer.) "iscsi Boot with Linux" on page 9 "Installing SLES on an iscsi Target" on page 10 All these steps are described in detail in this document with appropriate examples. 2.2 iscsi Boot with Linux iscsi boot is possible both in legacy mode and in UEFI mode. If you want to perform the iscsi boot in legacy mode, follow the information for configuring the LAN controllers in section "iscsi Boot Configurations in Legacy Mode" on page 23. If you want to perform the iscsi boot in UEFI mode, refer to the information for configuring the LAN controllers in section "iscsi Boot Configurations in UEFI Mode" on page 32. iscsi Boot with Intel Controllers (Linux) 9

10 Installing SLES on an iscsi Target 2.3 Installing SLES on an iscsi Target I For an operating system setup via network (NFS/FTP), the iscsi target and the server to be installed must be allowed to be accessed via the same LAN port. Starting the Installation This section explains the iscsi boot with SLES 11 SP3 / SP4 and with SLES 12. The installation process differs only slightly, which is why only screenshots of SLES 12 are used in the following. Start the operating system setup for SLES 11 SP3 / SP4 or SLES 12 from the installation medium. I You only need to specify additional boot parameters for a UEFI boot. Therefore only follow the next two screens if booting in this mode. In the case of a legacy boot, you can skip the next section and continue to page 12. Additional Boot Parameters for a UEFI Boot Start the installation and call the editor on the next screen by pressing [e]: Bild 2: First installation screen (for installation via UEFI only) 10 iscsi Boot with Intel Controllers (Linux)

11 Installing SLES on an iscsi Target Bild 3: Editor with parameter already inserted Go to the end of the third line (see figure above). Add the parameter withiscsi=1. Then confirm this by pressing [F10] to start the installation. You can now continue with the operating system installation on page 12. iscsi Boot with Intel Controllers (Linux) 11

12 Installing SLES on an iscsi Target Follow the wizard as far as the Disk Activation step: Bild 4: Installation screen Disk Activation. Click Configure iscsi Disks. 12 iscsi Boot with Intel Controllers (Linux)

13 Installing SLES on an iscsi Target Check under Connected Targets to see whether the required LUN has been recognized. Bild 5: iscsi Initiator Overview, Connected Targets tab Confirm by clicking Ok, and follow the wizard until you reach the end of the installation. iscsi Boot with Intel Controllers (Linux) 13

14 Installing SLES on an iscsi Target 14 iscsi Boot with Intel Controllers (Linux)

15 3 iscsi Boot with Red Hat Enterprise Linux 6.5 and 6.6 This chapter describes how to configure your server with Red Hat Enterprise Linux (RHEL) 6.5 and 6.6 to support iscsi boot with Intel LAN controllers. 3.1 Installation Overview The following steps are necessary to configure a system to support iscsi boot processes under RHEL: Configuring the iscsi Target (for general information, see page 6. For further information, please see the documentation provided by the iscsi target manufacturer.) "iscsi Boot with Linux" on page 15 "Installing Red Hat Enterprise Linux 6.5 and 6.6 on an iscsi Target" on page 16 All these steps are described in detail in this document with appropriate examples. 3.2 iscsi Boot with Linux iscsi boot is possible both in legacy mode and in UEFI mode. If you want to perform the iscsi boot in legacy mode, follow the information for configuring the LAN controllers in section "iscsi Boot Configurations in Legacy Mode" on page 23. If you want to perform the iscsi boot in UEFI mode, refer to the information for configuring the LAN controllers in section "iscsi Boot Configurations in UEFI Mode" on page 32. iscsi Boot with Intel Controllers (Linux) 15

16 Installing RHEL on an iscsi Target 3.3 Installing Red Hat Enterprise Linux 6.5 and 6.6 on an iscsi Target I For an operating system setup via network (NFS/FTP), the iscsi target and the server to be installed must be allowed to be accessed via the same LAN port. Starting the Installation This section explains the iscsi boot with RHEL 6.5 and 6.6. The installation process differs only slightly, which is why only screenshots of RHEL 6.6 are used in the following. Start the operating system setup for RHEL 6.5 / 6.6 from the installation medium. It is not necessary to specify additional boot parameters. The welcome screen appears: Bild 6: Welcome Screen RHEL iscsi Boot with Intel Controllers (Linux)

17 Installing RHEL on an iscsi Target Follow the wizard as far as the What type of devices will your installation involve step. Bild 7: Selecting the installation device, Specialized Storage option Proceed by selecting the Specialized Storage Devices option here. iscsi Boot with Intel Controllers (Linux) 17

18 Installing RHEL on an iscsi Target In the Other SAN Devices tab, check that the required LUN is selected. Bild 8: Selecting the boot medium, confirming the recognized LUN If the LUN is correct, confirm this by clicking Next, and follow the wizard until you reach the end of the installation. 18 iscsi Boot with Intel Controllers (Linux)

19 4 iscsi Boot with Red Hat Enterprise Linux 7.1 This chapter describes how to configure your server with Red Hat Enterprise Linux (RHEL) 7.1 to support iscsi boot with Intel LAN controllers. 4.1 Installation Overview The following steps are necessary to configure a system to support iscsi boot processes under RHEL: Configuring the iscsi Target (for general information, see page 6. For further information, please see the documentation provided by the iscsi target manufacturer.) "iscsi Boot with Linux" on page 19 "Installing Red Hat Enterprise Linux 7.1 on an iscsi Target" on page 20 All these steps are described in detail in this document with appropriate examples. 4.2 iscsi Boot with Linux iscsi boot is possible both in legacy mode and in UEFI mode. If you want to perform the iscsi boot in legacy mode, follow the information for configuring the LAN controllers in section "iscsi Boot Configurations in Legacy Mode" on page 23. If you want to perform the iscsi boot in UEFI mode, refer to the information for configuring the LAN controllers in section "iscsi Boot Configurations in UEFI Mode" on page 32. iscsi Boot with Intel Controllers (Linux) 19

20 Installing RHEL on an iscsi Target 4.3 Installing Red Hat Enterprise Linux 7.1 on an iscsi Target I For an operating system setup via network (NFS/FTP), the iscsi target and the server to be installed must be allowed to be accessed via the same LAN port. Starting the Installation This section explains the iscsi boot with RHEL 7.1. Start the operating system setup for RHEL 7.1. Press the Tab key to go directly to the line for entering boot parameters. Enter rd.iscsi.ibft=1, and confirm by pressing "Enter". Bild 9: Welcome Screen RHEL iscsi Boot with Intel Controllers (Linux)

21 Installing RHEL on an iscsi Target In the next steps you can enter other important parameters for localizing the required software as well as for the system. Bild 10: Configuration area in the installation wizard for RHEL 7.1 You now need to confirm the automatically selected LUN in the "System" category under Installation Destination. iscsi Boot with Intel Controllers (Linux) 21

22 Installing RHEL on an iscsi Target Bild 11: Selecting / confirming the recognized LUN Confirm the LUN as the installation medium by clicking Done. Then after configuring all other parameters, click Begin Installation to start the installation. Work your way through the wizard until you are requested to reboot. The installation is then completed. 22 iscsi Boot with Intel Controllers (Linux)

23 5 Intel iscsi Boot Configuration Utility This chapter explains the configuration options for the iscsi boot. For information on the legacy mode configuration options, see the next section iscsi Boot Configurations in Legacy Mode. For information on the UEFI mode configuration options, see "iscsi Boot Configurations in UEFI Mode" on page iscsi Boot Configurations in Legacy Mode Configuring Controller for iscsi Boot Activating the Option ROM Scan In the system BIOS, you must activate the Option ROM Scan for the controller in question to be able to call the Intel iscsi Boot Configuration Utility for configuring the controller. V Caution Activate the Option ROM Scan only for the controller you want to use for iscsi boot. The procedure for activating the Option ROM Scan depends on the BIOS setup of your system. An example for a PRIMERGY Server RX1330 M1 server is provided below. In the Advanced menu of the BIOS setup, select Onboard Devices Configuration, and open the submenu. Select the entry of the LAN controller that you want to configure for iscsi boot and set the parameter for this controller to iscsi. Save the changes and exit the BIOS Setup. iscsi Boot with Intel Controllers (Linux) 23

24 Configuring the LAN Controller Bild 12: BIOS Setup menu under Advanced -> Onboard Devices Configuration Configuring Network Controller for iscsi Boot To configure the network controller for iscsi boot, restart the system. When the message Press <Ctrl-D> to run setup... is displayed, press {Ctrl}[D]. The Intel iscsi Boot Configuration Utility starts. Continue as described in section "Intel iscsi Boot Configuration Utility" on page iscsi Boot with Intel Controllers (Linux)

25 Port Selection Menu Intel iscsi Boot Configuration Utility The menus of the Intel iscsi Boot Configuration Utility allow you to make the settings for the iscsi boot iscsi Port Selection Menu The first menu of the Intel iscsi Boot Configuration Utility displays a list of iscsi boot-capable adapters. For each adapter port the associated PCI device ID, PCI bus/device/function location, and a field indicating iscsi boot status is displayed. Up to 10 iscsi boot-capable ports can be displayed within the port selection menu. If there are more iscsi boot-capable adapters, these are not listed in the menu. Bild 13: iscsi Port Selection menu One network port in the system can be selected as the primary boot port by pressing the [P] key when highlighted. The primary boot port will be the first port used by the Intel iscsi Boot Configuration Utility to connect to the iscsi target. Only one port may be selected as a primary boot port. One network port in the system can be selected as the secondary boot port by pressing the [S] key when highlighted. The secondary boot port will only be used to connect to the iscsi target disk if the primary boot port fails to establish a connection. Only one port may be selected as a secondary boot port. Pressing the [D] key with a network port highlighted will disable iscsi boot on that port. iscsi Boot with Intel Controllers (Linux) 25

26 Port Configuration Menu Pressing the [B] key with a network port highlighted will blink an LED on that port. Use the arrow keys to select the required controller and press the "Enter" key to go to the iscsi Boot Configuration menu (see section "iscsi Port Configuration Menu"). Press the [Esc] key to leave the screen iscsi Port Configuration Menu Bild 14: iscsi Port Configuration menu iscsi Boot Configuration Selecting this option will take you to the iscsi Boot Configuration menu. This menu is described in detail in the section below and will allow you to configure the iscsi parameters for the selected network port. iscsi CHAP Configuration Selecting this option will take you to the iscsi CHAP Configuration menu. This menu is described in detail in the section below. Discard changes and Exit Selecting this option will discard all changes made in the iscsi Boot Configuration and iscsi CHAP Configuration menus, and return back to the iscsi Port Configuration menu. 26 iscsi Boot with Intel Controllers (Linux)

27 Boot Configuration Menu Save changes and Exit Selecting this option will save all changes made in the iscsi Boot Configuration and iscsi CHAP Configuration menus. After selecting this option, you will return to the iscsi Port Configuration menu iscsi Boot Configuration Menu This menu allows you to configure the iscsi boot and IP parameters for a specific port. The iscsi settings can be configured manually or retrieved dynamically from a DHCP server. Bild 15: iscsi Boot Configuration menu Use Dynamic IP Configuration (DHCP) Selecting this checkbox will cause iscsi boot to attempt to get the client IP address, subnet mask, and gateway IP address from a DHCP server. If this checkbox is enabled, these fields will not be visible (see also chapter "Configuring a DHCP Server" on page 41). iscsi Boot with Intel Controllers (Linux) 27

28 Boot Configuration Menu Initiator Name Enter the iscsi initiator name to be used by iscsi boot when connecting to an iscsi target. The value entered in this field is global and used by all iscsi boot enabled ports in the system. This field may be left blank if the Use DHCP for iscsi Target information checkbox is enabled. For information on how to retrieve the iscsi initiator name dynamically from a DHCP server see chapter "Configuring a DHCP Server" on page 41. Initiator IP Enter the client IP address to be used for this port as static IP configuration in this field. This IP address will be used by the port during the entire iscsi session. This option is visible if DHCP is not enabled. Subnet Mask Enter the IP subnet mask in this field. This should be the IP subnet mask used on the network which the selected port will be connecting to for iscsi. This option is visible if DHCP is not enabled. Gateway IP Enter the IP address of the network gateway in this field. This field is necessary if the iscsi target is located on a different sub-network than the selected iscsi boot port. This option is visible if DHCP is not enabled. Use DHCP for iscsi Target Information Selecting this checkbox will cause iscsi boot to attempt to gather the iscsi target's IP address, IP port number, iscsi target name, and SCSI LUN ID from a DHCP server on the network. For information on how to configure the iscsi target parameters using DHCP see chapter "Configuring a DHCP Server" on page 41. When this checkbox is enabled, these fields will not be visible. Target Name Enter the IQN name of the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. Target IP Enter the target IP address of the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. Target Port TCP Port Number (default: 3260 for iscsi). Boot LUN Enter the LUN ID of the boot disk on the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. 28 iscsi Boot with Intel Controllers (Linux)

29 CHAP Configuration Menu iscsi CHAP Configuration Menu iscsi boot supports Mutual CHAP MD5 authentication with an iscsi target. iscsi boot uses the MD5 Message Digest Algorithm developed by RSA Data Security, Inc. Bild 16: iscsi CHAP Configuration menu Use CHAP Selecting this checkbox will enable CHAP authentication for this port. CHAP allows the target to authenticate the initiator. After activating CHAP, you must enter a user name and password for the target. User Name Enter the CHAP user name in this field. This must be the same as the CHAP user name configured on the iscsi target. Target Secret Enter the CHAP password in this field. This must be the same as the CHAP password configured on the iscsi target and must be between 12 and 16 characters in length. This password must differ from the password in the Initiator Secret field. iscsi Boot with Intel Controllers (Linux) 29

30 CHAP Configuration Menu Use Mutual CHAP Selecting this checkbox will enable Mutual CHAP authentication for this port. Mutual CHAP allows the initiator to authenticate the target. After enabling Mutual CHAP authentication, an initiator password must be entered. Mutual CHAP can only be selected if Use CHAP is selected. Initiator Secret Enter the Mutual CHAP password in this field. This must be the same as the CHAP password configured on the iscsi target and must be between 12 and 16 characters in length. This password must differ from the password in the Target Secret field. The CHAP Authentication feature of this product requires the following acknowledgments: This product includes cryptographic software written by Eric Young This product includes software written by Tim Hudson This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit A complete licensing statement can be found here. VLAN ID The VLAN ID field was grayed out in the iscsi boot firmware screen because the Microsoft iscsi Boot Initiator does not support Vlans. 30 iscsi Boot with Intel Controllers (Linux)

31 CHAP Configuration Menu Checking the Connection During the boot process you can see whether a connection to the target was established: The following screen is displayed for a short time in legacy mode if it was possible to establish a connection to the iscsi target. Bild 17: Connecting to the iscsi target iscsi Boot with Intel Controllers (Linux) 31

32 Configuring the LAN Controller 5.2 iscsi Boot Configurations in UEFI Mode Configuring Controller for iscsi Boot Before starting with the configuration of the iscsi boot in UEFI mode, you need to configure various settings in the BIOS. Examples of the settings selected on the PRIMERGY Server RX1330 M1 are provided below. In the Boot menu of the BIOS Setup, first select CSM Configuration, and open the submenu. Set the parameter for Launch CSM to Disabled. Bild 18: Setup under Boot -> CSM Configuration Next, in the Advanced tab of the BIOS Setup, select Network Stack, and open the submenu. Set all parameters to Enabled. 32 iscsi Boot with Intel Controllers (Linux)

33 Configuring the LAN Controller Bild 19: Setup under Advanced -> Network Stack Save the changes and exit the BIOS Setup Configuring Network Controller for iscsi Boot iscsi Boot Configuration Menu To configure the network controller for iscsi boot, restart the system. Boot into the BIOS again. In the Advanced tab, you can first view the adapter properties and configurations. If several adapters are connected, you can then use this and other information to decide which adapter you want to configure, or whether you wish to configure two adapters to make the system less prone to failure. iscsi Boot with Intel Controllers (Linux) 33

34 Configuring the LAN Controller Bild 20: Menu under Advanced You then need to call the iscsi configurations in the BIOS. Bild 21: Setup under Advanced -> iscsi Configuration Enter the name of the initiator. Note that the iscsi initiator name as well as the other information below must comply with a specific syntax. Initiator Name Enter the iscsi initiator name to be used by iscsi boot when connecting to an iscsi target. The value entered in this field is global and used by all iscsi boot enabled ports in the system. Now add a new attempt with the required adapter in Add an Attempt. 34 iscsi Boot with Intel Controllers (Linux)

35 Configuring the LAN Controller Bild 22: Setup options under Advanced -> iscsi Configuration -> Add an Attempt Enter the parameters to be used in Add an Attempt, and confirm these by clicking Save Changes. You can configure the following information: Enable DHCP By selecting Enabled, iscsi boot will attempt to retrieve the client IP address, subnet mask, and gateway IP address from a DHCP server. If the parameter is set to Enabled, the input fields for the settings obtained automatically (initiator IP, subnet mask, gateway IP) are not visible (see also chapter "Configuring a DHCP Server" on page 41). Initiator IP Enter the client IP address to be used for this port as static IP configuration in this field. This IP address will be used by the port during the entire iscsi session. This option is visible if DHCP is not enabled. Subnet Mask Enter the IP subnet mask in this field. This should be the IP subnet mask used on the network which the selected port will be connecting to for iscsi. This option is visible if DHCP is not enabled. iscsi Boot with Intel Controllers (Linux) 35

36 Configuring the LAN Controller Gateway IP Enter the IP address of the network gateway in this field. This field is necessary if the iscsi target is located on a different sub-network than the selected iscsi boot port. This option is visible if DHCP is not enabled. Use DHCP for iscsi Target Information This option appears if the general DHCP is set to Enabled. If this option is also set to Enabled, iscsi boot will attempt to retrieve the iscsi target's IP address, IP port number, iscsi target name, and SCSI LUN ID from a DHCP server on the network. For information on how to retrieve the iscsi target parameters dynamically from a DHCP server, see "Configuring a DHCP Server" on page 37. You can now enter the following information (Target Name, Target IP, Target Port, Boot LUN) if this option is set to disabled. Target Name Enter the IQN name of the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. Target IP Enter the target IP address of the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. Target Port TCP Port Number (default: 3260 for iscsi). Boot LUN Enter the LUN ID of the boot disk on the iscsi target in this field. This option is visible if DHCP for iscsi target is not enabled. Authentication Type Here you can configure whether you want to use an authentication method. If you select None, all other parameters are hidden. If you select CHAP, these parameters are shown. For more information, see the next chapter (iscsi CHAP Configuration) 36 iscsi Boot with Intel Controllers (Linux)

37 Configuring the LAN Controller iscsi CHAP Configuration If the authentication type is set to CHAP for the iscsi configurations, additional options appear. Bild 23: Setup options for CHAP under Advanced -> iscsi Configuration -> Add an Attempt CHAP Type Here you can configure whether the authentication method is to be oneway CHAP (the target authenticates the initiator, but the initiator does not authenticate the target) or "Mutual CHAP" (both the target and initiator authenticate each other). If one-way CHAP authentication is enabled, only the following two options CHAP Name and CHAP Secret are displayed. If mutual CHAP authentication is enabled, the options Reverse CHAP Name and Reverse CHAP Secret are also displayed. CHAP Name Enter the CHAP user name in this field. This must be the same as the CHAP user name configured on the iscsi target. CHAP Secret Enter the CHAP password in this field. This password must iscsi Boot with Intel Controllers (Linux) 37

38 Configuring the LAN Controller be identical to the password configured on the iscsi target. It must contain 12 to 16 characters. This password must differ from the password in the Reverse CHAP Secret field. Reverse CHAP Name Enter the Mutual CHAP user name in this field. This must be the same as the CHAP user name configured on the iscsi target. Reverse CHAP Secret VLAN ID Enter the Mutual CHAP password in this field. This password must be identical to the password configured on the iscsi target. It must contain 12 to 16 characters. This password must differ from the password in the CHAP Secret field. I The CHAP Authentication feature of this product requires the following acknowledgments: This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit A complete licensing statement can be found here. The Microsoft iscsi Boot Initiator does not support VLANS in UEFI mode. 38 iscsi Boot with Intel Controllers (Linux)

39 Configuring the LAN Controller Checking the Connection and Preparing for Installation Checking the Connection For iscsi booting in UEFI mode, the connection to the iscsi target can be tested by booting to the EFI Shell. When doing so, the following entry is displayed: Bild 24: Checking the connection via the EFI Shell Preparing the Operating System Installation If you then want to install the operating system, it is important that you select the image next to the UEFI in the boot menu if there are several possible entries. Bild 25: Boot menu for the iscsi UEFI boot Confirm this to boot, and then follow the steps described in the chapter for the operating system you wish to install. iscsi Boot with Intel Controllers (Linux) 39

40 Configuring the LAN Controller 40 iscsi Boot with Intel Controllers (Linux)

41 6 Configuring a DHCP Server If you want to use Dynamic Host Configuration Protocol (DHCP) for the iscsi boot, the DHCP server needs to be configured to provide the iscsi boot configurations to the iscsi initiator. It is necessary to set up the DHCP server to specify Root Path option 17 and Host Name option 12 to respond iscsi target information back to the iscsi initiator. DHCP option 3, router list may be necessary, depending on the network configuration. DHCP Root Path Option 17 The iscsi root path option configuration string uses the following format: iscsi:<server name or IP address>:<protocol>:<port>:<lun>:<target name> server name or IP address DHCP server name or valid IPv4 address literal. Example: protocol Transportation protocol used by iscsi. Default is tcp (6). No other protocols are currently supported. port LUN Port number of the iscsi. A default value of 3260 will be used if this field is left blank. LUN ID configured on iscsi target system. Default is zero. target name iscsi target name to uniquely identify an iscsi target in IQN format. Example: iqn com.intel:target1 DHCP Host Name Option 12 Configure option 12 with the host name of the iscsi initiator. DHCP Option 3, Router List Configure option 3 with the gateway or router IP address, if the iscsi initiator and iscsi target are on different subnets. iscsi Boot with Intel Controllers (Linux) 41

42 Configuring a DHCP Server 42 iscsi Boot with Intel Controllers (Linux)

43 7 Troubleshooting This chapter lists problems that can occur when using Intel iscsi Boot. iscsi Boot does not load on system startup and the sign-on banner is not displayed. While the system logon screen may display for a longer time during system startup, iscsi Boot may not be displayed during POST. It may be necessary to disable a system BIOS feature in order to display messages from iscsi Boot. From the system BIOS menu, disable any quiet boot or quick boot options. Also disable any BIOS splash screens. These options may be suppressing output from iscsi Boot. Option ROM Scan is disabled in the system BIOS. Enable Option ROM Scan if you want to use the legacy mode. The system BIOS may be suppressing output from iscsi Boot. Sufficient system BIOS memory may not be available to load iscsi Boot. Attempt to disable unused disk controllers and devices in the system BIOS setup menu. SCSI controllers, RAID controller, PXE enabled network connections, and shadowing of system BIOS all reduce the memory area available to iscsi Boot. Disable these devices and reboot the system to see if iscsi Boot is able to initialize. If disabling the devices in the system BIOS menu does not resolve the problem then attempt to remove unused disk devices or disk controllers from the system. After installing iscsi Boot, the system will not boot to a local disk or network boot device. The system becomes unresponsive after iscsi Boot displays the signon banner or after connecting to the iscsi target. A critical system error has occurred during iscsi Boot initialization. Power on the system and press the [s] key or [ESC] key before iscsi Boot initializes. This will bypass the iscsi Boot initialization process and allow the system to boot to a local drive. Update the system BIOS. iscsi Boot with Intel Controllers (Linux) 43

44 Troubleshooting Intel(R) iscsi Remote Boot does not show up as a boot device in the system BIOS boot device menu. The system BIOS may not support iscsi Boot. Update the system BIOS with the most recent version available from the system vendor. A conflict may exist with another installed device. Attempt to disable unused disk and network controllers. Some SCSI and RAID controllers are known to cause compatibility problems with iscsi Boot. ERROR: Failed to detect link iscsi Boot was unable to detect link on the network port. Check the link detection light on the back of the network connection. The link light should illuminate green when link is established with the link partner. ERROR: DHCP Server not found! iscsi was configured to retrieve an IP address from DHCP but no DHCP server responded to the DHCP discovery request. This issue can have multiple causes: The DHCP server may have used up all available IP address reservations. The client iscsi system may require static IP address assignment on the connected network. There may not be a DHCP server present on the network. Spanning Tree Protocol (STP) on the network switch may be preventing the iscsi Boot port from contacting the DHCP server. Refer to your network switch documentation on how to disable Spanning Tree Protocol. ERROR: Invalid iscsi connection information The iscsi configuration information received from DHCP or statically configured in the setup menu is incomplete and an attempt to login to the iscsi target system could not be made. Verify that the iscsi initiator name, iscsi target name, target IP address, and target port number are configured properly in the iscsi setup menu (for static configuration) or on the DHCP server (for dynamic BOOTP configuration). 44 iscsi Boot with Intel Controllers (Linux)

45 Troubleshooting ERROR: Unsupported SCSI disk block size! The iscsi target system is configured to use a disk block size that is not supported by iscsi Boot. Configure the iscsi target system to use a disk block size of either 512, 1024, or 2048 in bytes. ERROR: Could not establish TCP/IP connection with iscsi target system. iscsi Boot was unable to establish a TCP/IP connection with the iscsi target system. Verify that the initiator and target IP address, subnet mask, port and gateway settings are configured properly. Verify the settings on the DHCP server if applicable. Check that the iscsi target system is connected to a network accessible to the iscsi Boot initiator. Verify that the connection is not being blocked by a firewall. ERROR: CHAP authentication with target failed. The CHAP user name or secret does not match the CHAP configuration on the iscsi target system. Verify the CHAP configuration on the iscsi Boot port matches the iscsi target system CHAP configuration. Disable CHAP in the iscsi Boot setup menu if it is not enabled on the target. ERROR: Login request rejected by iscsi target system. A login request was sent to the iscsi target system but the login request was rejected. Verify the iscsi initiator name, target name, LUN number, and CHAP authentication settings match the settings on the iscsi target system. Verify that the target is configured to allow the iscsi Boot initiator access to a LUN. When installing Linux to Net App Filer, after a successful target disk discovery, error messages may be seen similar to those listed below. Iscsi-sfnet:hostx: Connect failed with rc 113 : No route to host Iscsi-sfnet:hostx: establish_session failed. Could not connect to target iscsi Boot with Intel Controllers (Linux) 45

46 Troubleshooting If these error messages are seen, unused iscsi interfaces on Net App filer should be disabled. Continuous=no should be added to the iscsi.conf file. ERROR: iscsi target not found. Target IP address, however an iscsi target with the specified iscsi target name could not be found on the target system. Verify that the configured iscsi target name and initiator name match the settings on the iscsi target. ERROR: iscsi target can not accept any more connections. The iscsi target cannot accept any new connections. This error could be caused by a configured limit on the iscsi target or a limitation of resources (no disks available). ERROR: iscsi target has reported an error. An error has occurred on the iscsi target. Inspect the iscsi target to determine the source of the error and ensure it is configured properly. ERROR: There is an IP address conflict with another system on the network. A system on the network was found using the same IP address as the iscsi Option ROM client. If using a static IP address assignment, attempt to change the IP address to something which is not being used by another client on the network. If using an IP address assigned by a DHCP server, make sure there are no clients on the network which are using an IP address which conflicts with the IP address range used by the DHCP server. 46 iscsi Boot with Intel Controllers (Linux)

47 Glossary CHAP Challenge Handshake Authentication Protocol. An authentication protocol in which the authentication agent (typically a network server) sends the client program a random value that is used only once. DHCP Dynamic Host Configuration Protocol. A protocol for assigning dynamic IP addresses to devices on a network. FQDN Fully Qualified Domain Name. An Internet address which consists of a hostname and a domain name of the form IQN iscsi Qualified Name. A naming convention supported by iscsi to uniquely identify an iscsi initiator or target. iscsi Initiator A client device that connects to the iscsi service offered by an iscsi target. Similar in concept to a SCSI controller that plugs into a PC system. iscsi Target A server device that offers the iscsi service to an iscsi initiator. Similar in concept to a SCSI drive used in a PC system. PXE Pre-Boot execution Environment. An environment to bootstrap computers using a network interface card rather than using local media. UNDI Universal Network Device Interface. An application programming interface (or API) for network interface cards. Most commonly associated with PXE. iscsi Boot with Intel Controllers (Linux) 47

48 Glossary 48 iscsi Boot with Intel Controllers (Linux)