Note: The information contained in this article is structured as help information for the System Management Interface Tool (SMIT) and is not intended for use as a procedural or conceptual article.
The device's iSCSI target name. The target name is unique for targets in different enclosures. Target names will be the same for all LUNs in the same target. The name can contain up to 255 characters.
This is either the device's host name or the IP version 4 or IP version 6 address. The information in this field will be the same for all LUNS in the same target.
The device's port number. The port number will be the same for all LUNs in the same target.
The name of a valid iSCSI initiator. You can specify the name using the following format:
iqn.0.<reverse-domain>.hostid.<hostid>
The maximum number of commands that can be active at one time. You can specify a number from 200 through 4096. The default value is 200.
The maximum number of targets allowed for the iSCSI protocol driver. You can specify a number from 1 through 16. The default value is 16.
The iSCSI protocol driver name.
Information about the iSCSI software initiator that describes its purpose or any other information that might be important to the administrator or another user. Information in this field is optional.
The current status of the iSCSI software initiator device.
Select "yes" to save any changed attributes in the ODM but not configure or reconfigure the iSCSI device with the new values. Other attributes will take effect immediately.
Select "no" to save the value in the ODM and use it the next time the machine is rebooted.
Indicates what mechanism will be used to discover iSCSI targets. "File" refers to the static configuration file used to configure iSCSI Targets. The configuration file used is specified by the disc_filename (Discovery filename) attribute. "ODM" refers to the static configuration in ODM used to configure iSCSI Targets. As with the "file" choice a user must explicitly specify all relevant iSCSI target discovery properties. The "ODM" setting is required for boot devices in which automatic iSCSI discovery (such as SLP, iSNS, DHCP) is not available. "SLP" refers to the Service Location Protocol, which provides a mechanism to automatically discover iSCSI targets. "SLP" requires that the iSCSI targets to be used support "SLP". The "SLP" choice should also be selected if DHCP iSCSI target discovery is being used.
This specifies the absolute filename used for the discovery policy of the static configuration file used to configure iSCSI targets.
This specifies the absolute filename used for authentication secrets when using an automatic Discovery Policy other than the static configuration file used to configure iSCSI targets. For example, Service Location Protocol (SLP).
The following SMIT menus apply to the iSCSI Adapter Device Driver.
The following SMIT menus apply to the iSCSI Protocol Device Driver that interfaces with the iSCSI Adapter Device Driver.
This value indicates the maximum number of commands that can be outstanding at the iSCSI adapter. If the devices attached to the adapter can accept more commands, you might need to change this value. The default value is usually sufficient.
This is the internet address that this iSCSI adapter should use. If you are not using a Dynamic Host Configuration Protocol (DHCP) server, you must type the address. If you use a DHCP server in your network to provide this adapter's network settings, leave this field blank. When this field is blank, the adapter expects the DHCP server to provide its internet address.
The internet address indicates the address to which network packets are sent to reach this adapter. Similarly, it indicates the network address from which all network packets originate for this adapter. Internet addresses are specified in dotted decimal form For example, 101.64.2.102.
This entry is the subnet mask that this adapter should use. If you are not using a Dynamic Host Configuration Protocol (DHCP) server, you must type the address. If you use a DHCP server in your network to provide this adapter's network settings, leave this entry blank. When it is blank, the adapter expects the DHCP server to provide its subnet mask.
The subnet mask, which identifies the subnet partitioning scheme to the system, is a bit mask consisting of the network address portion and subnet address portion of the internet address.
The subnet mask is a set of 4 bytes, like the network address. The subnet mask consists of high bits (1s) corresponding to the bit positions of the network and subnetwork address, and low bits (0s) corresponding to the bit positions of the host address. Subnet masks are specified in dotted decimal form. For example, 255.255.255.0.
Subnet addressing allows an autonomous system made up of multiple networks to share the same internet address. The subnetwork capability of TCP/IP also makes it possible to divide a single network into multiple logical networks (subnets). For example, an organization can have a single internet network address that is known to users outside the organization, yet configure its network internally into departmental subnets. In either case, fewer Internet network addresses are required, and local routing capabilities are enhanced.
This entry is the gateway address that this adapter should use. If you are not using a Dynamic Host Configuration Protocol (DHCP) server, you must type the gateway address. If you are using a DHCP server in your network to provide this adapter's network settings, leave this entry blank. When it is blank, the adapter expects the DHCP server to provide its gateway address.
The gateway address indicates the gateway to which packets are addressed. This address indicates the next gateway in the path. Further gateways might be involved in delivering the packet. Gateway addresses are specified in dotted decimal form. For example, 101.64.2.1.
This attribute indicates the mechanism used for discovery iSCSI targets. The static configuration file used to configure iSCSI targets is specified by the disc_filename (Discovery filename) attribute. Service Location Protocol (SLP) provides a mechanism to automatically discover iSCSI targets. The iSCSI targets must support SLP.
If an iSCSI target does not support automatic detection (such as via SLP, iSNS, or DHCP) or you prefer not to use automatic discovery, then you must explicitly specify all of the target's discovery parameters. If an iSCSI target supports automatic detection, but requires passwords for authentication, then you must specify the target's password and target name. The following panels are for managing these iSCSI target parameters.
Shows all iSCSI targets in ODM. This list will correspond to targets that do not use automatic discovery or that require password authentication for devices discovered automatically. For security purposes, the passwords are not displayed on the screen in this list.
Adds information about an iSCSI target in ODM. Used for a target that can not be detected automatically. It is also used for targets discovered automatically and that require password authentication.
Removes information about an iSCSI target in ODM for a target.
Specifies the iSCSI name of the target. An example of an iSCSI target name is 'iqn.2000-04.com.abcdef-K167-42.fc1a'. This is a required field.
Type the internet address that this iSCSI target is using. The internet address is the address to which network packets will be sent to reach this target. The internet address is also the network address from which all network packets originate for this target. Internet addresses are specified in dotted decimal form, such as '101.64.2.102'.
Specifies the TCP port number this iSCSI target is using to receive iSCSI requests. The default TCP port used by iSCSI is '3260'.
Specifies the password required for authentication by this iSCSI target. This is the CHAP password used for some iSCSI targets. If the iSCSI target is not using any authentication then do not set this. If you are using this SMIT panel to provide passwords for iSCSI targets detected automatically, then you must specify both the iSCSI target name and the password. Passwords are optional for iSCSI targets that are not automatically detected. This SMIT panel is not required if you are using iSCSI targets detected automatically that have no password.
Specifies the group to use for this iSCSI object. There are only two valid groups: static and auto. A static group indicates that this target must be discovered via user-specified information only (i.e. target name, IP address, port number). An auto group indicates that this target is automatically detected. For targets that are automatically discovered AIX only needs a target entry added if a password is required for the device.
Provides AIX with information about iSCSI targets when the disc_policy of ODM is used.
Provides AIX with information authentication information about iSCSI target devices that are automatically discovered.
Transfers the contents of a flat file into ODM, allowing you to migrage from using the disc_policy of file to the disc_policy of ODM.
Manages information in ODM about iSCSI targets that can not be detected automatically. It is also used for automatically detected targets that require password authentication.
Changes information about an iSCSI target in ODM for a target.
Changes authentication information about an iSCSI target device.
The following SMIT menus apply to the iSCSI Target Mode Device Driver. The iSCSI target mode device driver allows to configure local targets and LUNs, mapped to local physical disks or logical volumes, and make them available to the iSCSI outside world, using local Ethernet interfaces. iSCSI targets objects are defined as a collection of LUNs. They are supporting the iSCSI addressing scheme. iSCSI target LUNs are local virtual disk space, mapped over physical disks or logical volumes, that can be used by remote iSCSI initiators as iSCSI disks.
The following SMIT menus apply to the iSCSI Target Mode Protocol device driver.
The following SMIT menus apply to the iSCSI Target Mode Targets management.
The following SMIT menus apply to the iSCSI Target Mode Logical Units management.
The following SMIT menus apply to the iSCSI Target Mode Logical Units management.
This attribute can be used to set/unset the support for ImmediateData to be sent along with a SCSI command PDU for writes. The default value for ImmediateData=no, meaining ImmediateData will not be sent along with the SCSI Command PDU.
This attribute can be used to set/unset the support for an unsolicited Data-Out PDU to be sent after a SCSI command PDU for writes without having to wait for an Initial R2T from the target. The default value for InitialR2T=yes, meaining the initiator waits for an R2T to be received from the target before sending out the unsolicited data.
Use the following panels to configure the iSNS client to discover iSCSI targets.
The iSCSI protocol driver name.
Enter the hostname or IP ddress of the iSNS servers. Multiple names or IP addresses may be specified, separated by commas. The word "auto" may be entered to use SLP to discover the address of the iSNS server.
Enter the TCP port numbers to connect to on each of the iSNS servers. There should be the same number of port numbers, separated by commas, as there are iSNS servers in the previous field. If the iSNS server field contains "auto" then this field should be left blank.
The following SMIT menus apply to the iSCSI Target Mode Device Driver. The iSCSI target mode device driver allows you to configure local targets and LUNs that are mapped to local physical disks or logical volumes, and make them available to the iSCSI outside world, using local Ethernet interfaces. iSCSI targets objects are defined as a collection of LUNs. They are supporting the iSCSI addressing scheme. iSCSI target LUNs are local virtual disk space, mapped over physical disks or logical volumes, that can be used by remote iSCSI initiators as iSCSI disks.
The following SMIT menus apply to the iSCSI Target Mode Protocol device driver.
The following SMIT menus apply to the iSCSI Target Mode Targets management.
The following SMIT menus apply to the iSCSI Target Mode Logical Units management.
When a device is defined, the device instance is recorded in the Customized Configuration Database. All of the device's attributes, including connection and location information, are known and recorded, but the device cannot be used by the operating system. After you configure a device, the device is said to be available. When listing defined devices, the information is presented in three columns: device name, status (indicating whether a device is available or just defined), and device description.
When adding a device, the device is defined and configured in the Customized database. You can also set attributes when adding a device.
Change one or more attributes for a specific device.
When deleting a device, you can make the device unavailable, but still defined, or remove the device definition from the Customized database.
Indicates whether or not the configuration changes being made should be applied only too the database or to both the database and the current device operation. For devices that are in use and cannot be changed, this allows the database to be changed for the device so that the changes take effect the next time the system is rebooted.
Allows you to unconfigure a device to the Defined state, or to unconfigure, then delete it from the Device Configuration database. Select 'Yes' to unconfigure the path and leave it in the Defined state. Select 'No' to unconfigure and delete the path.
The iSCSI target protocol driver name.
Displays information about the iSCSI target mode device driver and describes its purpose or any other information that might be important to the administrator or another user. The information in this field is optional.
Displays the current status of the iSCSI software target device.
Enter the maximum number of sessions that can be opened at one time. You can specify a number from 200 to 4096. The default value is 200.
Enter the maximum transfer size allowed in one SCSI request. You can specify a value from 8192 to 16777216. The default value is 262144.
If set to 'on', the 'access_lists' configuration file '/etc/tmiscsi/access_lists' will be taken into account. The default value is 'off'.
Use this option to indicate whether or not the Persistent Reservation information is saved when the system reboots. The default value is 'no'.
Displays the Target logical name. If not specified, a name starting with the 'target' prefix will be automatically generated.
Information about the iSCSI Target that describes its purpose or any other information that might be important to the administrator or another user. Information in this field is optional.
Displays the current status of this iSCSI target.
Displays the Protocol Device owning this target.
Displays the iSCSI target name. You can specify the name using one of the following two formats: iqn. <what-you-want>, eui. <16 ASCII-encoded hexadecimal digits>. The iSCSI name must be unique within the entire network.
Enter the maximum number of Logical Units that can be attached to this target. Specify a number from 1 to 512. The default value is 512.
Displays a list of interfaces on which initiators will be able to request a connection with the target.
This list is made of tuples, each one having the following syntax: ethernet-interface-logical-name:port-number, portal-group-tag
The separator between tuples is the semi-colon (';') character. The number of tuples is limited by the maximum number of characters allowed in an ODM string (256). With an interface-name of 3 characters, a port-number of 4 characters and a portal-group-tag of 1 character for each tuple, you can specify up to 23 Interfaces. The driver will try to launch one listening kernel process by tuple found in this attribute. Example: en0:3260,1;en1:3260,2;en0:3267,1.
Indicates whether the target should force a disconnection before removing it. If set to 'soft', the target will send an asynchronous event to all initiators requesting that they issue a logout. If set to 'hard', the target will send an asynchronous event with 'drop all connections' to all initiators and then close all the connections. If set to 'no', the remove of the target will fail if an iSCSI initiator is connected on it.
When the 'force_logout' is set to 'hard', this attribute indicates how long an initiator should wait before attempting a new connection after it receives a 'drop all connections' asynchronous event.
Indicates the logical unit addressing method used to generate the Logical Unit Numbers for this target. 0: Peripheral device addressing method, 1: Flat space addressing method, 2: Logical unit addressing method. The default value is 0.
Indicates whether or not the configured children of the device should be recursively unconfigured.
Displays the Logical Unit logical name. If not specified, a name starting with the 'lu' prefix will be automatically generated.
Displays information about the iSCSI Logical Unit and describes its purpose or any other information that might be important to the administrator or another user. Information in this field is optional.
Displays the current status of this iSCSI LUN.
Displays the target object owning this Logical Unit.
Displays the type of device the Logical Unit Numbers (LUN) will be backed on. Currently, LUNs can be backed on Logical Volumes (lv), Disks (disk) or Files (file). If you select 'lv' or 'disk', then the 'Backing Device Name' entry must be filled to specify the backing device. If you select 'file', then the 'Backing File Full Path Name' entry must be filled to specify the backing file.
Displays the logical name of the device the LUN will be backed on.
Enter the maximum number of commands that can be active at one time on the LUN. You can specify a number from 1 to 32. The default value is 3.