# iSCSI Target Configuration

For specific information on configuring your iSCSI target system and disk volume, refer to instructions provided by the 3rd party vendor. Listed below are the basic steps necessary to setup Intel® Ethernet iSCSI Boot to work with most iSCSI target systems. The specific steps will vary from one vendor to another.

| NOTE: In order to be able to support iSCSI Boot, the target needs to be able to support multiple sessions from the same initiator. Both the iSCSI Boot firmware initiator and the OS High Initiator need to establish an iSCSI session at the same time. Both these initiators use the same Initiator Name and IP Address to connect and access the OS disk but these two initiators will establish a different iSCSI session. In order for the target to support iSCSI Boot, the target must be capable of supporting multiple sessions and client logins.

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

2. Note the iSCSI Qualified Name (IQN) of the iSCSI target, which will likely look like:

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

   This value will be used as the iSCSI target name when configuring in Intel® Ethernet iSCSI Boot firmware setup.

3. Configure the iSCSI target system to accept the iSCSI connection from the iSCSI initiator. This usually requires listing the initiator's IQN name or MAC address for permitting the initiator to access to the disk volume. See the section "Firmware Setup" for information on how to set the iSCSI initiator name.

4. One-way authentication protocol can be enabled optionally for secure communications. Challenge-Handshake Authentication Protocol (CHAP) is enabled by configuring username/password on iSCSI target system. For setting up CHAP on the iSCSI initiator, refer to the section "Firmware Setup" for information.

## Booting from Targets Larger than 2TB

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

- The block size on the target must be 512 bytes
- The following operating systems are supported:
  - VMware* ESX 5.0, or later
  - Red Hat* Enterprise Linux* 6.3, or later
  - SUSE* Enterprise Linux 11SP2, or later
  - Microsoft* Windows Server* 2012, or later
- You may be able to access data only within the first 2 TB.

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

`Last modified on 5/26/11 3:52p Revision`