This chapter describes how to configure Common Multiprotocol SCSI TARget, or COMSTAR, a software framework that enables you to convert any Oracle Solaris 11 host into a SCSI target device that can be accessed over a storage network by initiator hosts.

This means you can make storage devices on a system available to Linux, Mac OS, or Windows client systems as if they were local storage devices. Supported storage protocols are iSCSI, FC, iSER, and SRP.

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

For troubleshooting iSCSI configuration problems in Oracle Solaris, see Troubleshooting iSCSI Configuration Problems.

COMSTAR and iSCSI Technology (Overview)

iSCSI is an acronym for Internet SCSI (Small Computer System Interface), an Internet Protocol (IP)-based storage networking standard for linking data storage subsystems.

By carrying SCSI commands over IP networks, the iSCSI protocol enables you to access block devices from across the network as if they were connected to the local system. COMSTAR provides an easier way to manage these iSCSI target devices.

COMSTAR utilizes a SCSI Target Mode Framework (STMF) to manage target storage devices with the following components:

• Port providers (or plug-ins) – Implement protocols, such as Fibre Channel (FC) and iSCSI.

• Logical unit providers – Emulate various SCSI devices, such as disk and tape devices.

• The libstmf management library – Provides the COMSTAR management interface. The modules that implement the iSCSI functionality do not interact directly with the underlying transport. In a similar way, the modules that implement the transport protocol are unaware of the SCSI-level functionality that is inherent in the packets they are transporting. Some transport examples are Fibre Channel and iSCSI. The framework separates the execution and cleanup of SCSI commands and the associated resources. This separation simplifies the task of writing SCSI or transport modules.

  Use the following to administer these features:

  • The itadm command manages Internet SCSI (iSCSI) nodes within the SCSI target mode framework.

  • The stmfadm command configures logical units within the SCSI target mode framework.

  • The srptadm command manages SCSI RDMA Protocol (SRP) target ports within the SCSI target mode framework.

The following solutions are available to use storage devices in your existing TCP/IP network:

• iSCSI block devices or tape – Translates SCSI commands and data from the block level into IP packets. Using iSCSI in your network is advantageous when you need to have block-level access between one system and the target device, such as a tape device or a database. Access to a block-level device is not locked so that you can have multiple users or systems accessing a block-level device such as an iSCSI target device.

• NFS – Transfers file data over IP. The advantage of using NFS in your network is that you can share file data across many systems. Access to file data is locked appropriately when many users are accessing data that is available in an NFS environment.

Here are the benefits of usingiSCSI targets and initiators in Oracle Solaris:

• The iSCSI protocol runs across existing Ethernet networks.

  • You can use any supported network interface card (NIC), Ethernet hub, or Ethernet switch.

  • One IP port can handle multiple iSCSI target devices.

  • You can use existing infrastructure and management tools for IP networks.

• You might have existing Fibre-Channel devices that can be connected to clients without the cost of Fibre-Channel HBAs. In addition, systems with dedicated arrays can now export replicated storage with Oracle Solaris ZFS or UFS file systems.

• The protocol can be used to connect to Fibre Channel or iSCSI Storage Area Network (SAN) environments with the appropriate hardware.

Here are the current limitations or restrictions of using the iSCSI initiator software in Oracle Solaris:

• Support for iSCSI devices that use SLP is not currently available.

• iSCSI targets cannot be configured as dump devices.

• Transferring large amounts of data over your existing network can have an impact on performance.

COMSTAR Software and Hardware Requirements

• Oracle Solaris storage software and devices

• The group/feature/storage-server software package for the system that provides the storage devices

• Any supported NIC

Configuring COMSTAR (Task Map)

Configuring COMSTAR

Configuring your iSCSI targets and initiators with COMSTAR involves the following tasks:

• Identifying hardware and software requirements

• Configuring your IP network

• Connecting and setting up the iSCSI target device

• Configuring the initiators

• Configuring the iSCSI target discovery method

• Creating file systems on your iSCSI disks

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

• Monitoring your iSCSI configuration

The iSCSI configuration information is stored in the /etc/iscsi directory, but it requires no manual administration.

COMSTAR 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.http://www.ietf.org/rfc/rfc4171.txt

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

For more information about setting up iSNS support in Oracle Solaris, see Chapter 15, Configuring and Managing the Oracle 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.