内に含まその他のドキュメントサポート リソース |  PDF 文書ファイルをダウンロードする (8966 KB)
iscsitadm(1M)Name | Synopsis | Description | Options | Examples | Exit Status | Attributes | See Also | Notes Name
Synopsisiscsitadm create [-? | --help] object [-? | --help] [options] operand iscsitadm modify [-? | --help] object [-? | --help] [options] operand iscsitadm delete [-? | --help] object [-? | --help] [options] operand iscsitadm list [-? | --help] object [-? | --help] [options] operand iscsitadm show [-? | --help] admin iscsitadm show [-? | --help] object [-? | --help] [options] [operand] iscsitadm -? --help Description
The iscsitadm command enables you to manage Internet SCSI (iSCSI) target nodes. It is a companion to iscsiadm(1M), which enables you to manage iSCSI initiator nodes. The iscsitadm command has the following subcommands: The preceding subcommands work on the following objects: These objects are discussed in greater detail under the options descriptions for each subcommand. As indicated in the SYNOPSIS, iscsitadm has two levels of help. If you invoke -? or --help following a subcommand, the command displays available operands, options, and objects. If you invoke an help option following an object, iscsitadm displays options and operands. Options
The iscsitadm options and objects are discussed below in the context of each subcommand. Note that the help options (-? or --help) are invoked as shown in the SYNOPSIS. See EXAMPLES. create OptionsThe following are the options and objects for the create subcommand: modify OptionsThe following are the options and objects for the modify subcommand: delete OptionsThe following are the options and objects for the delete subcommand: list OptionsThe following are the options and objects for the list subcommand: show OptionsThe following are the options and objects for the show subcommand: ExamplesExample 1 Invoking HelpAll of the commands shown below are valid ways of invoking help.
Example 2 Establishing Backing StoreThe following command establishes the default location for the backing store. In addition to the backing store, certain configuration files will be stored in the same location.
The short form of the --base-directory option is -d. Example 3 Simplest-Case Target CreationThe following command creates a target that will emulate an LBA device that has 10 GB of storage available. With the base directory set up and as well as a single target, it is possible to use the system as an iSCSI target. Note that because the LUN is not specified on the command line, it reverts to the default, 0.
The short form of the --size option is -z. Example 4 Creating with Both Size and Backing StoreThe following iscsitadm create command specifies LUN size and a backing store location. The result of this command is that the daemon will create a LUN file at the named location, of the specified size (20 GB).
A target such as the one created by the preceding command might be useful, for example, when most of the LUN can be created in a default area, using whatever redundancy is provided by the underlying file system. Alternatively, you might want to create a special LUN on a higher speed storage medium or one with better failover characteristics. The long form of the -z option is --size. The long form of the -b option is --backing-store Example 5 Specifying a Local Name for a SCSI InitiatorConsider that you want to restrict access to the payroll target, created in the previous example, to a limited set of initiators. Because the initiator names can be quite long (and therefore prone to be entered incorrectly), you create a local name for each initiator, as in the command below.
The short form of the --iqn option is -q. Example 6 Granting an Initiator Access to a TargetUpon completion of the command below, only the initiator multistrada is allowed to log into the daemon and access the payroll target. This presents a potential gap in security, which is addressed in the following example.
The short form of the --acl option is -l. Example 7 Adding CHAP Secret and Name for an InitiatorThe initiator is allowed to identify itself. Because of this, it is prudent to add a CHAP secret an name for an initiator. This is accomplished with the following command.
The preceding command prompts you for a secret to use. This must be the same secret that was setup on the initiator with the local name of multistrada. If it is not, the target daemon will issue a challenge to multistrada when it attempts to login. A non-matching response will cause the target to drop the connection. If you have many targets that require authentication, it is probably best to setup a RADIUS server to administer the secrets. The long form of the -C option is --chap-secret. Example 8 Displaying Target InformationThe following commands displays information about iSCSI targets.
The following command differs from the preceding in that it uses the verbose (-v) option and it specifies a single target.
Example 9 Displaying Administrative InformationThe following command uses the show subcommand to display administrative information.
Example 10 Displaying StatisticsThe following command uses the show subcommand to display statistics.
Exit StatusAttributesSee attributes(5) for descriptions of the following attributes:
See AlsoNotesThis command set is considered to be experimental. Future releases, both minor and micro, might introduce incompatible changes to the command set. A future release will stabilize the command set. Any future changes in stability level will be reflected in the ATTRIBUTES section of this man page. The iSCSI Target daemon, iscsitgtd, is managed by the service management facility (smf(5)), under the fault management resource identifier (FMRI):
Use iscsitadm to perform administrative actions, such as are performed by the create, modify, and delete subcommands, on iSCSI Target properties. Such actions require that you become superuser or assume the Primary Administrator role. See rbac(5). Name | Synopsis | Description | Options | Examples | Exit Status | Attributes | See Also | Notes |
|||||||||||||||||||
|