Setting up the host server as an iSCSI initiator

Follow this procedure to set up a host server for use as an iSCSI initiator with the system. The specific steps vary depending on the particular host type and operating system that is involved.

To configure a host, first select a software-based iSCSI initiator or a hardware-based iSCSI initiator. For example, the software-based iSCSI initiator can be a Microsoft Windows iSCSI software initiator, and the hardware-based iSCSI initiator can be an iSCSI host bus adapter inside the host server.

You can use either the management GUI or the command-line interface to set up a host server. To set up your host server for use as an iSCSI software-based initiator with the system, complete the following steps:

Using the Management GUI

  1. To set up your system for iSCSI, complete these steps:
    1. In the management GUI, select Settings > Network > Ethernet Ports.
    2. Expand the I/O group, right-click the node that you want to change, and select Modify IP Settings.
    3. On the Modify IP Settings page, enter the IP address for the node. You can select either IPv4 or IPv6 addresses. Click Modify.
    4. Verify that you configured the node and the system Ethernet ports correctly. The Ethernet Ports page displays all the changed nodes as configured and Host Attach is set to Yes.
    5. To create hosts, select Hosts > Hosts and select Add Host. Select iSCSI or iSER Hosts and enter an iSCSI initiator name in the iSCSI port field. Check the host server to determine the iSCSI initiator name. Enter additional details about the host and click Add Host.
    6. To create volumes, select Volumes > Volumes and select Create Volumes. Select the type of volume you want to create and select the pool, size, and other details for the volume. Click Create and Map to Host.
    7. After the volume is created, click Continue to map the host to the volume. Select the host that you create and click Map Volumes.
  2. To set up your host server, complete these steps:
    1. Ensure that you configured your IP interfaces on the server.
    2. Install the software for the iSCSI software-based initiator on the server.
    3. On the host server, run the configuration methods for iSCSI so that the host server iSCSI initiator logs in to the system and discovers the volumes. The host then creates host devices for the volumes
  3. After the host devices are created, you can use them with your host applications.

Using the CLI

  1. To set up your system for iSCSI, complete these steps:
    1. Select a set of IPv4 or IPv6 addresses for the Ethernet ports on the nodes that are in the I/O groups that use the iSCSI volumes.
    2. Configure the node Ethernet ports on each node in the system with the cfgportip command.
    3. Verify that you configured the node and the system Ethernet ports correctly by reviewing the output of the lsportip command and lssystemip command.
    4. Use the mkvdisk command to create volumes on the system.
    5. Use the mkhost command to create a host object on the system that describes the iSCSI server initiator to which the volumes are to be mapped.
    6. Use the mkvdiskhostmap command to map the volume to the host object in the system.
  2. To set up your host server, complete these steps:
    1. Ensure that you configured your IP interfaces on the server.
    2. Install the software for the iSCSI software-based initiator on the server.
    3. On the host server, run the configuration methods for iSCSI so that the host server iSCSI initiator logs in to the system and discovers the volumes. The host then creates host devices for the volumes
  3. After the host devices are created, you can use them with your host applications.

What to do next

Be aware of the following considerations:
  • AIX does not support iSCSI with IPv6.
  • Each connection between a host initiator and a system Ethernet port can use IPv4 or IPv6 (where supported). Concurrent use of both IPv4 and IPv6 for the same initiator to the system Ethernet port is not supported.
  • Ethernet ports 1 and 2 can each be configured for both a cluster IP address and an iSCSI target IP address. A different cluster IP address can be assigned to each system Ethernet port, providing configuration with redundant Ethernet networks.
  • All service and configuration IP addresses associated with a clustered-system Ethernet port must be on the same subnet across all nodes. Each port can reside in its own subnet. However, for failover to work correctly, the same port index (for example port3) on all nodes must be in the same subnet (for example 192.168.1.x where x varies for each node).
  • When the host object on the system side is created or re-created for an iSCSI host, you must log out of any existing sessions from that host and then log back in.
  • A maximum of four Ethernet ports can be enabled for iSCSI logins by using the cfgportip command. Therefore, do not specify the "host=yes" setting for more than four of the Ethernet ports you configured with IP addresses. Specify the "host=no" setting for all other configured ports. If you enable more than four configured ports, login attempts to those ports are rejected by the system.
  • Host performance is reduced if you configure RTC with the iSCSI host attachment on the system because some CPU cores are dedicated to RTC processing, thus reducing the number of CPU cores available for iSCSI processing.
Parent topic: iSCSI Ethernet host attachment