Setting Up Solaris iSCSI Targets and Initiators (Task Map)

Configuring Solaris iSCSI Targets and Initiators

Configuring your Solaris iSCSI targets and initiators involves the following steps:

• Identifying the hardware and software requirements

• Configuring your IP network

• Connecting and setting up your iSCSI target device

• (Optional) Configuring iSCSI authentication between the iSCSI initiator and the iSCSI target, if necessary

• Configuring the iSCSI target discovery method

• Creating file systems on your iSCSI disks

• Monitoring your iSCSI configuration

The iSCSI configuration information is stored in the /etc/iscsi directory. This information requires no administration.

iSCSI Terminology

Review the following terminology before configuring iSCSI targets and initiators.

Configuring Dynamic or Static Target Discovery

Determine whether you want to configure one of the dynamic device discovery methods or use static iSCSI initiator targets to perform device discovery.

• Dynamic device discovery – If an iSCSI node exposes many targets, such as an iSCSI to Fibre-Channel bridge, you can supply the iSCSI node IP address/port combination and allow the iSCSI initiator to use the SendTargets features to perform device discovery.

  Two dynamic device discovery methods are available:

  • SendTargets - If an iSCSI node exposes a large number of targets, such as an iSCSI to Fibre-Channel bridge, you can supply the iSCSI node IP address/port combination and allow the iSCSI initiator to use the SendTargets features to perform the device discovery.

  • iSNS - iSNS (Internet Storage Name Service) allows the iSCSI initiator to discover the targets to which it has access using as little configuration information as possible. It also provides state change notification to notify the iSCSI initiator when changes in the operational state of storage nodes occur. To use the iSNS discovery method, you can supply the iSNS server address/port combination and allow the iSCSI initiator to query the iSNS servers that you specified to perform the device discovery. The default port for the iSNS server is 3205. For more information about iSNS, see RFC 4171:

    http://www.ietf.org/rfc/rfc4171.txt

    The iSNS discovery service provides an administrative model to discover all targets in a network.

    For more information about setting up Solaris iSNS support, see Chapter 15, Configuring and Managing the Solaris Internet Storage Name Service (iSNS).

• Static device discovery – If an iSCSI node has few targets or if you want to restrict the targets that the initiator attempts to access, you can statically configure the target-name by using the following static target address naming convention:

  target,target-address[:port-number]

  You can determine the static target address from the array's management tool.

Do not configure an iSCSI target to be discovered by both static and dynamic device discovery methods. The consequence of using redundant discovery methods might be slow performance when the initiator is communicating with the iSCSI target device.

How to Prepare for a Solaris iSCSI Configuration

This procedure assumes that you are logged in to the local system where you want to access a configured iSCSI target device.

1. Become superuser.

2. Verify that the iSCSI software packages are installed.

   initiator# pkginfo SUNWiscsiu SUNWiscsir system SUNWiscsiu Sun iSCSI Device Driver (root) system SUNWiscsir Sun iSCSI Management Utilities (usr)

3. Verify that you are running at least the Solaris Express 8/06 release.

4. Confirm that your TCP/IP network is setup.

5. Connect your iSCSI target devices and confirm that they are configured.

   For example, determine if the iSCSI target device is reachable by using the telnet command to connect to the iSCSI target device using port 3260. If the connection is refused, see Troubleshooting iSCSI Configuration Problems.

   For information about connecting your third-party iSCSI target devices, see your vendor documentation.

Setting Up Your Solaris iSCSI Target Devices

You can use the iscsitadm command to set up and manage your Solaris iSCSI target devices, which can be disk or tape devices. For the device that you select as your iSCSI target, you must provide an equivalently sized ZFS or UFS file system as the backing store for the iSCSI daemon.

For information about setting up a Solaris iSCSI target device with ZFS, see ZFS and Solaris iSCSI Improvements in Solaris ZFS Administration Guide.

After the target device is set up, use the iscsiadm command to identify your iSCSI targets, which will discover and use the iSCSI target device.

For more information, see iscsitadm(1M) and iscsiadm(1M).

The basic process is as follows:

• Identify the backing store directory – For each target and logical unit that is created, the iSCSI daemon needs to store some information. By default, the backing store for this device is also located in the base directory. So, if the host system has a large ZFS pool to use, it might be easiest to allow the daemon to store everything in that location. If the backing store needs to be spread out, it's possible to specify the backing store location during the creation of each logical unit.

• Create the iSCSI target – By default, the CLI assumes that the requested device type is an LBA of logical unit 0. If a pass through mode is desired for character devices, the -raw option must be used. After the creation of the first LUN, other LUNs might be created for the same iSCSI target by specifying -lun number.

  The daemon starts a background task that initializes the LUN to zeros. If, during that initialization, the underlying file system becomes 100 percent full, the daemon removes the target. During this initialization, the LUN is marked as being offline and cannot be used by an initiator. During this time, however, it is possible to have an initiator discover this LUN. The Solaris initiator waits until it receives an Inventory Change notification and then automatically brings the device online.

How to Create an iSCSI Target

This procedure assumes that you are logged in to the local system that contains the iSCSI targets.

1. Become superuser.

2. Identify the backing store directory.

   For example:

   target# iscsitadm modify admin -d /export/sandbox

3. Create an iSCSI target.

   For example:

   target# iscsitadm create target --size 2g sandbox

4. Display information about the iSCSI target.

   For example:

   target# iscsitadm list target -v sandbox

5. Set up your iSCSI initiator to discover and use this target.

   For more information, see How to Configure iSCSI Target Discovery.

How to Configure iSNS Discovery for the Solaris iSCSI Target

If your network includes a third-party iSNS server or a Sun iSNS server, you can set up iSNS target discovery on your Solaris iSCSI targets.

This procedure assumes that you are logged in to the local system where you want to access a configured iSCSI target device.

1. Become superuser.

2. Add the iSNS server information.

   For example:

   initiator# iscsitadm modify admin --isns-server ip-address or hostname[:port]

   Identify the ip-address of the iSNS server in your network.

   This step adds the iSNS server information to all of the Solaris iSCSI targets.

3. Enable iSNS server discovery.

   For example:

   initiator# iscsitadm modify admin --isns-access enable

   This step enables iSNS discovery for all of the Solaris iSCSI targets.

Configuring Authentication in Your iSCSI-Based Storage Network

Setting up authentication for your iSCSI devices is optional.

In a secure environment, authentication is not required because only trusted initiators can access the targets.

In a less secure environment, the target cannot determine if a connection request is truly from a given host. In that case, the target can authenticate an initiator by using the Challenge-Handshake Authentication Protocol (CHAP).

CHAP authentication uses the notion of a challenge and response, which means that the target challenges the initiator to prove its identity. For the challenge/response method to work, the target must know the initiator's secret key, and the initiator must be set up to respond to a challenge. Refer to the array vendor's documentation for instructions on setting up the secret key on the array.

iSCSI supports unidirectional and bidirectional authentication:

• Unidirectional authentication enables the target to authenticate the identity of the initiator.

• Bidirectional authentication adds a second level of security by enabling the initiator to authenticate the identity of the target.

How to Configure CHAP Authentication for Your iSCSI Initiator

This procedure assumes that you are logged in to the local system where you want to securely access the configured iSCSI target device.

1. Become superuser.

2. Determine whether you want to configure unidirectional or bidirectional CHAP.

   • Unidirectional authentication, the default method, enables the target to validate the initiator. Complete steps 3–5 only.

   • Bidirectional authentication adds a second level of security by enabling the initiator to authenticate the target. Complete steps 3–9.

3. Unidirectional CHAP – Set the secret key on the initiator.

   For example, the following command initiates a dialogue to define the CHAP secret key.

   initiator# iscsiadm modify initiator-node --CHAP-secret

   ---

   Note –

   The CHAP secret length must be a minimum of 12 characters and a maximum of 16 characters.

   ---

4. (Optional) Unidirectional CHAP – Set the CHAP name on the initiator.

   By default, the initiator's CHAP name is set to the initiator node name.

   You can use the following command to change the initiator's CHAP name.

   initiator# iscsiadm modify initiator-node --CHAP-name new-CHAP-name

   In the Solaris environment, the CHAP name is always set to the initiator node name by default. The CHAP name can be set to any length text that is less than 512 bytes. The 512-byte length limit is a Solaris limitation. However, if you do not set the CHAP name, it is set to the initiator node name upon initialization.

5. Unidirectional CHAP – Enable CHAP authentication on the initiator after the secret has been set.

   initiator# iscsiadm modify initiator-node --authentication CHAP

   CHAP requires that the initiator node have both a user name and a password. The user name is typically used by the target to look up the secret for the given username.

6. Select one of the following to enable or disable Bidirectional CHAP.

   • Bidirectional CHAP – Enable bidirectional authentication parameters on the target.

     For example:

     initiator# iscsiadm modify target-param -B enable eui.5000ABCD78945E2B

   • Disable bidirectional CHAP. For example:

     initiator# iscsiadm modify target-param -B disable eui.5000ABCD78945E2B

7. Bidirectional CHAP – Set the authentication method to CHAP on the target.

   For example:

   initiator# iscsiadm modify target-param --authentication CHAP eui.5000ABCD78945E2B

8. Bidirectional CHAP – Set the target device secret key on the target.

   For example, the following command initiates a dialogue to define the CHAP secret key:

   initiator# iscsiadm modify target-param --CHAP-secret eui.5000ABCD78945E2B

9. Bidirectional CHAP - Set the CHAP name on the target.

   By default, the target's CHAP name is set to the target name.

   You can use the following command to change the target's CHAP name:

   initiator# iscsiadm modify target-param --CHAP-name target-CHAP-name

How to Configure CHAP Authentication for Your iSCSI Target

This procedure assumes that you are logged in to the local system that contains the iSCSI targets.

1. Become superuser.

2. Set the CHAP secret name for the target.

   A convention is to use the host name for the secret name. For example:

   target# iscsitadm modify admin -H stormpike

3. Specify the CHAP secret.

   The CHAP secret must be between 12 and 16 characters. For example:

   target# iscsitadm modify admin -C Enter secret: xxxxxx Re-enter secret: xxxxxx

4. Create an initiator object that will be associated with one or more targets.

   This step is done so that you can associate a friendly name (normally the host name, in this case monster620) with the IQN value, instead of typing it in every time. For example:

   # iscsitadm create initiator -n iqn.1986-03.com.sun: 01:00e081553307.4399f40e monster620

5. Provide the same CHAP name that was used on the initiator.

   This name can be different from the friendly name that was used for the initiator object. For example:

   target# iscsitadm modify initiator -H monster620 monster620

6. Use the same CHAP secret that was used on the initiator.

   For example:

   target# iscsitadm modify initiator -C monster620 Enter secret: xxxxxx Re-enter secret: xxxxxx

7. Associate the initiator object with one or more targets.

   For example:

   target# iscsitadm modify target -l monster620 sandbox

Using a Third-Party RADIUS Server to Simplify CHAP Management in Your iSCSI Configuration

You can use a third-party RADIUS server to simplify CHAP secret management. A RADIUS server is a centralized authentication service. While you must still specify the initiator's CHAP secret, you are no longer required to specify each target's CHAP secret on each initiator when using bidirectional authentication with a RADIUS server.

For more information, see:

• CHAP – http://www.ietf.org/rfc/rfc1994.txt

• RADIUS – http://www.ietf.org/rfc/rfc2865.txt

How to Configure RADIUS for Your iSCSI Configuration

This procedure assumes that you are logged in to the local system where you want to securely access the configured iSCSI target device.

1. Become superuser.

2. Configure the initiator node with the IP address and port (the default port is 1812) of the RADIUS server.

   For example:

   initiator# iscsiadm modify initiator-node --radius-server 10.0.0.72:1812

3. Configure the initiator node with the shared secret of the RADIUS server.

   initiator# iscsiadm modify initiator-node --radius-shared-secret

   ---

   Note –

   The Solaris iSCSI implementation requires that the RADIUS server is configured with a shared secret before the Solaris iSCSI software can interact with the RADIUS server.

   ---

4. Enable the RADIUS server.

   initiator# iscsiadm modify initiator-node --radius-access enable

Solaris iSCSI and RADIUS Server Error Messages

This section describes the error messages that are related to a Solaris iSCSI and RADIUS server configuration, along with potential solutions for recovery.

empty RADIUS shared secret

Cause:

The RADIUS server is enabled on the initiator, but the RADIUS shared secret is not set.

Solution:

Configure the initiator with the RADIUS shared secret. For more information, see How to Configure RADIUS for Your iSCSI Configuration.

WARNING: RADIUS packet authentication failed

Cause:

The initiator failed to authenticate the RADIUS data packet. This error can occur if the shared secret configured on the initiator node is different from the shared secret on the RADIUS server.

Reconfigure the initiator with the correct RADIUS shared secret. For more information, see How to Configure RADIUS for Your iSCSI Configuration.

How to Configure iSCSI Target Discovery

This procedure assumes that you are logged in to the local system where you want to configure access to an iSCSI target device.

1. Become superuser.

2. Configure the target device to be discovered dynamically or statically using one of the following methods:

   • Configure the device to be dynamically discovered (SendTargets).

     For example:

     initiator# iscsiadm add discovery-address 10.0.0.1:3260

   • Configure the device to be dynamically discovered (iSNS).

     For example:

     initiator# iscsiadm add iSNS-server 10.0.0.1:3205

   • Configure the device to be statically discovered.

     For example:

     initiator# iscsiadm add static-config eui.5000ABCD78945E2B,10.0.0.1

   The iSCSI connection is not initiated until the discovery method is enabled. See the next step.

3. Enable the iSCSI target discovery method using one of the following:

   • If you have configured a dynamically discovered (SendTargets) device, enable the SendTargets discovery method.

     initiator# iscsiadm modify discovery --sendtargets enable

   • If you have configured a dynamically discovered (iSNS) device, enable the iSNS discovery method.

     initiator# iscsiadm modify discovery --iSNS enable

   • If you have configured static targets, enable the static target discovery method.

     initiator# iscsiadm modify discovery --static enable

4. Create the iSCSI device links for the local system.

   initiator# devfsadm -i iscsi

How to Remove Discovered iSCSI Targets

After removing a discovery address, iSNS server, or static configuration, or after disabling a discovery method, the associated targets are logged out. If these associated targets are still in use, for example, they have mounted file systems, the logout of these devices will fail, and they will remain on the active target list.

This optional procedure assumes that you are logged in to the local system where access to an iSCSI target device has already been configured.

1. Become superuser.

2. (Optional) Disable an iSCSI target discovery method using one of the following:

   • If you need to disable the SendTargets discovery method, use the following command:

     initiator# iscsiadm modify discovery --sendtargets disable

   • If you need to disable the iSNS discovery method, use the following command:

     initiator# iscsiadm modify discovery --iSNS disable

   • If you need to disable the static target discovery method, use the following command:

     initiator# iscsiadm modify discovery --static disable

3. Remove an iSCSI device discovery entry using one of the following:

   • Remove an iSCSI SendTargets discovery entry.

     For example:

     initiator# iscsiadm remove discovery-address 10.0.0.1:3260

   • Remove an iSCSI iSNS discovery entry.

     For example:

     # iscsiadm remove isns-server 10.0.0.1:3205

   • Remove a static iSCSI discovery entry.

     For example:

     initiator# iscsiadm remove static-config eui.5000ABCD78945E2B,10.0.0.1

   ---

   Note –

   If you attempt to disable or remove a discovery entry that has an associated logical unit in use, the disable or remove operation fails with the following message:

   logical unit in use

   If this errors occurs, stop all associated I/O on the logical unit, unmount the file systems, and so on. Then, repeat the disable or remove operation.

   ---

4. Remove the iSCSI target device.

   Remove a target by specifying the logical unit number (LUN). If you did not specify a LUN when the target was created, a value of 0 was used. LUN 0 must be the last LUN removed if multiple LUNs are associated with a target.

   For example:

   initiator# iscsitadm delete target --lun 0 sandbox

Accessing iSCSI Disks

If you want to make the iSCSI drive available on reboot, create the file system, and add an entry to the /etc/vfstab file as you would with a UFS file system on a SCSI device.

After the devices have been discovered by the Solaris iSCSI initiator, the login negotiation occurs automatically. The Solaris iSCSI driver determines the number of available LUNs and creates the device nodes. Then, the iSCSI devices can be treated as any other SCSI device.

You can view the iSCSI disks on the local system by using the format utility.

In the following format output, disks 2 and 3 are iSCSI LUNs that are not under MPxIO control. Disks 21 and 22 are iSCSI LUNs under MPxIO control.

initiator# format
AVAILABLE DISK SELECTIONS:
       0. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e010685cf1,0
       1. c0t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0106e3ba1,0
       2. c3t0d0 <ABCSTORAGE-100E-00-2.2 cyl 20813 alt 2 hd 16 sec 63>
          /iscsi/disk@0000iqn.2001-05.com.abcstorage%3A6-8a0900-477d70401-
           b0fff044352423a2-hostname-020000,0
       3. c3t1d0 <ABCSTORAGE-100E-00-2.2 cyl 20813 alt 2 hd 16 sec 63>
           /iscsi/disk@0000iqn.2001-05.com.abcstorage%3A6-8a0900-3fcd70401 
           -085ff04434f423a2-hostname-010000,0
.
.
.
      21. c4t60A98000686F694B2F59775733426B77d0 <ABCSTORAGE-LUN-0.2 cyl  
          4606 alt 2 hd 16 sec 256>
          /scsi_vhci/ssd@g60a98000686f694b2f59775733426b77
      22. c4t60A98000686F694B2F59775733434C41d0 <ABCSTORAGE-LUN-0.2 cyl  
          4606 alt 2 hd 16 sec 256>
          /scsi_vhci/ssd@g60a98000686f694b2f59775733434c41

Monitoring Your iSCSI Configuration

You can display information about the iSCSI initiator and target devices by using the iscsiadm list command.

1. Become superuser.

2. Display information about the iSCSI initiator.

   For example:

   # iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003ba4d233b.425c293c Initiator node alias: zzr1200 Login Parameters (Default/Configured): Header Digest: NONE/- Data Digest: NONE/- Authentication Type: NONE RADIUS Server: NONE RADIUS access: unknown Configured Sessions: 1

3. Display information about which discovery methods are in use.

   For example:

   # iscsiadm list discovery Discovery: Static: enabled Send Targets: enabled iSNS: enabled

Example 14–1 Displaying iSCSI Target Information

The following example shows how to display the parameter settings for a specific iSCSI target.

# iscsiadm list target-param iqn.1992-08.com.abcstorage:sn.33592219
        Target: iqn.1992-08.com.abcstorage:sn.33592219

The iscsiadm list target-param -v command displays the following information:

• The authentication settings for the target

• The default settings for the target login parameters

• The configured value for each login parameter

The iscsiadm list target-param -v command displays the default parameter value before the / designator and the configured parameter value after the / designator. If you have not configured any parameters, the configured parameter value displays as a hyphen (-). For more information, see the following examples.

# iscsiadm list target-param -v eui.50060e8004275511 Target: eui.50060e8004275511
        Alias: -
        Bi-directional Authentication: disabled
        Authentication Type: NONE
        Login Parameters (Default/Configured):
                Data Sequence In Order: yes/-
                Data PDU In Order: yes/-
                Default Time To Retain: 20/-
                Default Time To Wait: 2/-
                Error Recovery Level: 0/-
                First Burst Length: 65536/-
                Immediate Data: yes/-
                Initial Ready To Transfer (R2T): yes/-
                Max Burst Length: 262144/-
                Max Outstanding R2T: 1/-
                Max Receive Data Segment Length: 65536/-
                Max Connections: 1/-
                Header Digest: NONE/-
                Data Digest: NONE/-
        Configured Sessions: 1

The following example output displays the parameters that were negotiated between the target and the initiator.

# iscsiadm list target -v eui.50060e8004275511
Target: eui.50060e8004275511
        TPGT: 1
        ISID: 4000002a0000
        Connections: 1
                CID: 0
                  IP address (Local): 172.90.101.71:32813
                  IP address (Peer): 172.90.101.40:3260
                  Discovery Method: Static
                  Login Parameters (Negotiated):
                        Data Sequence In Order: yes
                        Data PDU In Order: yes
                        Default Time To Retain: 0
                        Default Time To Wait: 3
                        Error Recovery Level: 0
                        First Burst Length: 65536
                        Immediate Data: yes
                        Initial Ready To Transfer (R2T): yes
                        Max Burst Length: 262144
                        Max Outstanding R2T: 1
                        Max Receive Data Segment Length: 65536
                        Max Connections: 1
                        Header Digest: NONE
                        Data Digest: NONE

Modifying iSCSI Initiator and Target Parameters

You can modify parameters on both the iSCSI initiator and the iSCSI target device. However, the only parameters that can be modified on the iSCSI initiator are the following:

• iSCSI initiator node name – You can change the initiator node name to a different name. If you change the initiator node name, the targets that were discovered by iSNS might be removed from the initiator's target list, depending on the discovery domain configuration on the iSNS server at the time when the name was changed. For more information, see How to Modify iSCSI Initiator and Target Parameters.

• Header digest – NONE, the default value or CRC32.

• Data digest – NONE, the default value or CRC32.

• Authentication and CHAP secret – For more information about setting up authentication, see How to Configure CHAP Authentication for Your iSCSI Initiator.

• Configured sessions – For more information about configuring multiple sessions, see How to Enable Multiple iSCSI Sessions for a Target.

The iSCSI driver provides default values for the iSCSI initiator and iSCSI target device parameters. If you modify the parameters of the iSCSI initiator, the modified parameters are inherited by the iSCSI target device, unless the iSCSI target device already has different values.

Ensure that the target software supports the parameter to be modified. Otherwise, you might be unable to log in to the iSCSI target device. See your array documentation for a list of supported parameters.

Modifying iSCSI parameters should be done when I/O between the initiator and the target is complete. The iSCSI driver reconnects the session after the changes are made by using the iscsiadm modify command.

How to Modify iSCSI Initiator and Target Parameters

The first part of this procedure illustrates how modified parameters of the iSCSI initiator are inherited by the iSCSI target device. The second part of this procedure shows how to actually modify parameters on the iSCSI target device.

This optional procedure assumes that you are logged in to the local system where access to an iSCSI target device has already been configured.

1. Become superuser.

2. List the current parameters of the iSCSI initiator and target device.

   1. List the current parameters of the iSCSI initiator. For example:

      initiator# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003ba4d233b.425c293c Initiator node alias: zzr1200 Login Parameters (Default/Configured): Header Digest: NONE/- Data Digest: NONE/- Authentication Type: NONE RADIUS Server: NONE RADIUS access: unknown Configured Sessions: 1

   2. List the current parameters of the iSCSI target device. For example:

      initiator# iscsiadm list target-param -v iqn.1992-08.com.abcstorage:sn.84186266 Target: iqn.1992-08.com.abcstorage:sn.84186266 Alias: - Bi-directional Authentication: disabled Authentication Type: NONE Login Parameters (Default/Configured): Data Sequence In Order: yes/- Data PDU In Order: yes/- Default Time To Retain: 20/- Default Time To Wait: 2/- Error Recovery Level: 0/- First Burst Length: 65536/- Immediate Data: yes/- Initial Ready To Transfer (R2T): yes/- Max Burst Length: 262144/- Max Outstanding R2T: 1/- Max Receive Data Segment Length: 65536/- Max Connections: 1/- Header Digest: NONE/- Data Digest: NONE/- Configured Sessions: 1

      Note that both header digest and data digest parameters are currently set to NONE for both the iSCSI initiator and the iSCSI target device.

      To review the default parameters of the iSCSI target device, see the iscsiadm list target-param output in Example 14–1.

3. Modify the parameter of the iSCSI initiator.

   For example, set the header digest to CRC32.

   initiator# iscsiadm modify initiator-node -h CRC32

   If you change the initiator node name, the targets that were discovered by iSNS might be logged out and removed from the initiator's target list, if the new name does not belong to the same discovery domain as that of the targets. However, if the targets are in use, they are not removed. For example, if a file is open or a file system is mounted on these targets, the targets will not removed.

   You might also see new targets after the name change if these targets and the new initiator node name belong to the same discovery domain.

4. Verify that the parameter was modified.

   1. Display the updated parameter information for the iSCSI initiator. For example:

      initiator# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003ba4d233b.425c293c Initiator node alias: zzr1200 Login Parameters (Default/Configured): Header Digest: NONE/CRC32 Data Digest: NONE/- Authentication Type: NONE RADIUS Server: NONE RADIUS access: unknown Configured Sessions: 1

      Note that the header digest is now set to CRC32.

   2. Display the updated parameter information for the iSCSI target device. For example:

      initiator# iscsiadm list target-param -v iqn.1992-08.com.abcstorage:sn.84186266 Target: iqn.1992-08.com.abcstorage:sn.84186266 Alias: - Bi-directional Authentication: disabled Authentication Type: NONE Login Parameters (Default/Configured): Data Sequence In Order: yes/- Data PDU In Order: yes/- Default Time To Retain: 20/- Default Time To Wait: 2/- Error Recovery Level: 0/- First Burst Length: 65536/- Immediate Data: yes/- Initial Ready To Transfer (R2T): yes/- Max Burst Length: 262144/- Max Outstanding R2T: 1/- Max Receive Data Segment Length: 65536/- Max Connections: 1/- Header Digest: CRC32/- Data Digest: NONE/- Configured Sessions: 1

      Note that the header digest is now set to CRC32.

5. Verify that the iSCSI initiator has reconnected to the iSCSI target. For example:

   initiator# iscsiadm list target -v iqn.1992-08.com.abcstorage:sn.84186266 Target: iqn.1992-08.com.abcstorage:sn.84186266 TPGT: 2 ISID: 4000002a0000 Connections: 1 CID: 0 IP address (Local): nnn.nn.nn.nnn:64369 IP address (Peer): nnn.nn.nn.nnn:3260 Discovery Method: SendTargets Login Parameters (Negotiated): . . . Header Digest: CRC32 Data Digest: NONE

6. (Optional) Unset an iSCSI initiator parameter or an iSCSI target device parameter.

   You can unset a parameter by setting it back to its default setting by using the iscsiadm modify command. Or, you can use the iscsiadm remove command to reset all target properties to the default settings.

   The iscsiadm modify target-param command changes only the parameters that are specified on the command line.

   The following example shows how to reset the header digest to NONE:

   initiator# iscsiadm modify target-param -h none iqn.1992-08.com.abcstorage:sn...

   For information about the iscsiadm remove target-param command, see iscsiadm(1M).

Setting Up Solaris iSCSI Multipathed Devices

Consider the following guidelines for using Solaris iSCSI multipathed (MPxIO) devices:

• Solaris iSCSI and MPxIO – MPxIO supports target port aggregation and availability in Solaris iSCSI configurations that configure multiple sessions per target (MS/T) on the iSCSI initiator.

  • Use IPMP for aggregation and failover of two or more NICs.

  • A basic configuration for an iSCSI host is a server with two NICs that are dedicated to iSCSI traffic. The NICs are configured by using IPMP. Additional NICs are provided for non-iSCSI traffic to optimize performance.

  • Active multipathing can only be achieved by using the Solaris iSCSI MS/T feature, and the failover and redundancy of an IPMP configuration.

    • If one NIC fails in an IPMP configuration, IPMP handles the failover. The MPxIO driver does not notice the failure. In a non-IPMP configuration, the MPxIO driver fails and offlines the path.

    • If one target port fails in an IPMP configuration, the MPxIO driver notices the failure and provides the failover. In a non-IPMP configuration, the MPxIO driver notices the failure and provides the failover.

    For more information about using the Solaris iSCSI MS/T feature with IPMP and multipathing, see SunSolve Infodoc 207607, Understanding an iSCSI MS/T multi-path configuration.

  • For information about configuring multiple sessions per target, see How to Enable Multiple iSCSI Sessions for a Target. For information about configuring IPMP, see Chapter 8, Administering IPMP, in System Administration Guide: Network Interfaces and Network Virtualization.

• Solaris iSCSI, Fibre-Channel (FC), and MPxIO – The MPxIO driver provides the following behavior in more complex iSCSI/FC configurations:

  • If you have dual iSCSI to FC bridges in an FC SAN, iSCSI presents target paths to MPxIO. MPxIO matches the unique SCSI per LUN identifier, and if they are identical, presents one path to the iSCSI driver.

  • If you have a configuration that connects a target by using both iSCSI and FC, the MPxIO driver can provide different transports to the same device. In this configuration, MPxIO utilizes both paths.

  • If you are using iSCSI and FC in combination with MPxIO, make sure that the MPxIO settings in the /kernel/drv/fp.conf file and the /kernel/drv/iscsi.conf files match the MPxIO configuration that you want supported. For example, in fp.conf, you can determine whether MPxIO is enabled globally on the HBA or on a per-port basis.

• Third-party hardware considerations– Find out if your third-party HBA is qualified to work with Solaris iSCSI and MPxIO.

  If you are using a third-party HBA, you might need to ask your third-party HBA vendor for the symmetric-option information for the /kernel/drv/scsi_vhci.conf file.

How to Enable Multiple iSCSI Sessions for a Target

This procedure can be used to create multiple iSCSI sessions that connect to a single target. This scenario is useful with iSCSI target devices that support login redirection or have multiple target portals in the same target portal group. Use iSCSI multiple sessions per target with Solaris SCSI Multipathing (MPxIO). You can also achieve higher bandwidth if you utilize multiple NICs on the host side to connect to multiple portals on the same target.

The MS/T feature creates two or more sessions on the target by varying the initiator's session ID (ISID). Enabling this feature creates two SCSI layer paths on the network so that multiple targets are exposed through the iSCSI layer to the Solaris I/O layer. The MPxIO driver handles the reservations across these paths.

For more information about how iSCSI interacts with MPxIO paths, see Setting Up Solaris iSCSI Multipathed Devices.

Review the following items before configuring multiple sessions for an iSCSI target:

• A typical MS/T configuration has two or more configured-sessions.

  However, if your storage supports multiple TPGTs and if you are using SendTarget discovery on your host system, then the number of configured sessions can be set to 1. SendTarget discovery automatically detects the existence of multiple paths and multiple target sessions are created.

• Confirm that the mxpio configuration parameter is enabled in the /kernel/drv/iscsi.conf file.

  # cd /kernel/drv # grep mpxio iscsi.conf iscsi.conf:mpxio-disable="no";

• Confirm that the multiple network connections are configured by using IPMP.

• Confirm that the multiple network connections are available.

  # ifconfig -a

1. Become superuser.

2. List the current parameters for the iSCSI initiator and target.

   1. List the current parameters for the iSCSI initiator. For example:

      initiator# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003ba4d233b.425c293c Initiator node alias: zzr1200 . . . Configured Sessions: 1

   2. List the current parameters of the iSCSI target device. For example:

      initiator# iscsiadm list target-param -v iqn.1992-08.com.abcstorage:sn.84186266 Target: iqn.1992-08.com.abcstorage:sn.84186266 Alias: - . . . Configured Sessions: 1

      The configured sessions value is the number of configured iSCSI sessions that will be created for each target name in a target portal group.

3. Select one of the following to modify the number of configured sessions either at the initiator node to apply to all targets or at a target level to apply to a specific target.

   The number of sessions for a target must be between 1 and 4.

   • Apply the parameter to the iSCSI initiator node.

     For example:

     initiator# iscsiadm modify initiator-node -c 2

   • Apply the parameter to the iSCSI target.

     For example:

     initiator# iscsiadm modify target-param -c 2 iqn.1992-08.com.abcstorage:sn.84186266

   • Bind configured sessions to one or more local IP addresses.

     Configured sessions can also be bound to a specific local IP address. Using this method, one or more local IP addresses are supplied in a comma-separated list. Each IP address represents an iSCSI session. This method can also be done at the initiator-node or target-param level. For example:

     initiator# iscsiadm modify initiator-node -c 10.0.0.1,10.0.0.2

     ---

     Note –

     If the specified IP address is not routable, the address is ignored and the default Solaris route and IP address is used for this session.

     ---

4. Verify that the parameter was modified.

   1. Display the updated information for the initiator node. For example:

      initiator# iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:0003ba4d233b.425c293c Initiator node alias: zzr1200 . . . Configured Sessions: 2

   2. Display the updated information for the target node. For example:

      initiator# iscsiadm list target-param -v iqn.1992-08.com.abcstorage:sn.84186266 Target: iqn.1992-08.com.abcstorage:sn.84186266 Alias: - . . . Configured Sessions: 2

5. List the multiple paths by using the mpathadm list lu command to confirm that the OS device name matches the iscsiadm list output, and that the path count is 2 or more.