Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ././../../../../../../usr/man/man8/suriadm.8
Real path: /usr/share/man/man8/suriadm.8
Zurück

'\" te .\" Copyright (c) 2012, 2023, Oracle and/or its affiliates. .TH suriadm 8 "19 Jul 2023" "Oracle Solaris 11.4" "System Administration Commands" .SH NAME suriadm \- administer storage objects based on storage URIs .SH SYNOPSIS .LP .nf \fB/usr/sbin/suriadm\fR \fIcommand\fR [\fIoptions\fR] [\fIoperands\fR] .fi .SH DESCRIPTION .sp .LP The \fBsuriadm\fR command line administration tool allows system users to manage storage objects via storage URIs. The command allows to parse, map, unmap, query the state of mappings and look up storage URIs. .SS "Supported Storage URIs" .sp .LP Supported storage URIs are defined in \fBsuri\fR(7) manual page. .SH SUB-COMMANDS .sp .LP The following subcommands are supported: .sp .ne 2 .mk .na \fB\fBparse\fR [\fB-H\fR] [\fB-o\fR \fIp\fR,\fIp\fR,...] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Parses a given URI and displays a default list of properties. With \fB-H\fR, a header is omitted from the output. With \fB-o\fR, only properties from the list provided are displayed. The \fB-o\fR option implies output on one line, with property values separated by tabs, meant to be further processed by another command. .sp Allowed property names for the \fB-o\fR option are: \fBcreate-size\fR, \fBcreate-supported\fR, \fBfile-permissions\fR, \fBgroup\fR, \fBhostname\fR, \fBinitiator\fR, \fBis-slice\fR, \fBlun\fR, \fBluname\fR, \fBmapped-dev\fR, \fBmapped-devs\fR, \fBmount-options\fR, \fBmountpoint-prefix\fR, \fBmountpoint\fR, \fBpath\fR, \fBport\fR, \fBremovable\fR, \fBtarget\fR, \fBteardown-supported\fR, \fBuri\fR, \fBuri-type\fR, and \fBuser\fR. .RE .sp .ne 2 .mk .na \fB\fBnormalize\fR \fIURI\fR\fR .ad .br .sp .6 .RS 4n Parses and normalizes a storage URI string based on normalization specifications for the URI type. Displays the normalized URI and does not accept any options. .sp For iSCSI and logical unit URIs, all alphabetical characters in the URI are converted to lowercase characters. .sp Additionally for iSCSI URIs, the default iSCSI port number 3260 is removed. .sp For device URIs, all leading forward slashes that follow the URI type name and the occurrence of \fB/dev\fR at the head of the path component is removed. .sp For NFS URIs, a hostname is converted to lowercase and leading zeros are removed from numeric user/group IDs. .sp For file URIs, a hostname is removed and leading zeros are removed from numeric user/group IDs. .RE .sp .ne 2 .mk .na \fB\fBmap\fR [\fB-H\fR] [\fB-o\fR p,p,...] [\fB-p\fR \fIprop\fR=\fIvalue\fR] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Parses a storage URI, configures the storage subsystem if necessary to instantiate all devices corresponding to the URI provided, and displays device paths. If devices are already instantiated, the map operation only looks up device paths. .sp A storage object being mapped must exist beforehand, else the operation fails. See the \fBcreate\fR subcommand on how to create a storage object. For more information on what storage URI types support the create operation, see the \fBsuri\fR(7) man page. .sp For an iSCSI URI, this subcommand will add a send-targets discovery address(es) a hostname resolves to if a URI authority section is present. .sp For \fBdev\fR and \fBlu\fR URI types, this subcommand has no effect on system configuration. Options \fB-H\fR and \fB-o\fR have the same meaning as the \fBparse\fR subcommand. The property \fBmapped-devs\fR shows all the device paths corresponding to the URI provided, and the property \fBmapped-dev\fR shows only the first device path of \fBmapped-devs\fR. .sp Allowed input property names for the \fB-p\fR option are \fBmount-options\fR, \fBmountpoint-prefix\fR, and \fBremovable\fR. .RE .sp .ne 2 .mk .na \fB\fBlookup-mapping\fR [\fB-H\fR] [\fB-o\fR \fIp\fR,\fIp\fR,...] [\fB-p\fR \fIprop\fR=\fIvalue\fR] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Parses a URI and looks up for existing mappings between a storage URI and the objects represented by local system device paths. Default list of properties does not display any properties or accept any options. Options \fB-H\fR and \fB-o\fR have the same meaning as for the \fBparse\fR subcommand. Option \fB-p\fR has the same meaning as for the \fBmap\fR subcommand. .RE .sp .ne 2 .mk .na \fB\fBcreate\fR [\fB-H\fR] [\fB-o\fR \fIp\fR,\fIp\fR,...] [\fB-p\fR \fIprop\fR=\fIvalue\fR] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Creates the backing store for the storage URI then maps it. Option \fB-p\fR has the same meaning as for the \fBmap\fR subcommand. .sp Allowed input property names for the \fB-p\fR option are \fBcreate-size\fR and \fBfile-permissions\fR. .RE .sp .ne 2 .mk .na \fB\fBdestroy\fR [\fB-p\fR \fIprop\fR=\fIvalue\fR] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Unmaps the storage URI then destroys the backing store. Option \fB-p\fR has the same meaning as for the \fBmap\fR subcommand. The object represented by the \fIURI\fR must be mapped. .RE .sp .ne 2 .mk .na \fB\fBunmap\fR [\fB-p\fR \fIprop\fR=\fIvalue\fR] \fIURI\fR\fR .ad .br .sp .6 .RS 4n Parses and unmaps an object presumably mapped before. Option \fB-p\fR has the same meaning as for the \fBmap\fR subcommand. .sp For an iSCSI URI, this subcommand removes discovery addresses to which a hostname from a URI authority section resolves, if present. .sp For logical unit and \fBdev\fR URI types, this subcommand has no effect on system configuration. .RE .sp .ne 2 .mk .na \fB\fBlookup-uri\fR [\fB-t\fR \fIuri-type\fR] \fIdevice-path\fR\fR .ad .br .na \fB\fBlookup-uri\fR [\fB-t\fR \fIuri-type\fR] \fB-p\fR \fBmapped-dev\fR=\fIdevice-path\fR\fR .ad .br .sp .6 .RS 4n Looks up and displays URIs based on a local system device path. Allowed URI types for \fB-t\fR are \fBdev\fR, \fBlu\fR, and \fBiscsi\fR. If the \fB-t\fR option is not specified, the output consists of all URIs that match the device path for any URI type. Using the property option \fB-p\fR is optional. .RE .sp .ne 2 .mk .na \fB\fBlookup-uri\fR [\fB-t\fR \fIuri-type\fR] \fB-p\fR \fBluname\fR=\fIluname\fR\fR .ad .br .sp .6 .RS 4n Looks up and displays LU and iSCSI URIs based on a logical unit name. Allowed URI types for \fB-t\fR are \fBlu\fR and \fBiscsi\fR. If the \fB-t\fR option is not specified the output consists of all URIs that identify the logical unit matched by a given logical unit name. .sp If the logical unit name does not have an implicit ID type (as in IQN based name) the ID type must be explicitly stated. See EXAMPLES. .RE .sp .ne 2 .mk .na \fB\fBlookup-uri\fR [\fB-t\fR \fIuri-type\fR] \fB-p\fR \fBtarget\fR=\fItarget\fR \fB-p\fR \fBlun\fR=\fILUN\fR\fR .ad .br .sp .6 .RS 4n Looks up and displays URIs based on a target port and LUN. Allowed URI types for \fB-t\fR are \fBlu\fR and \fBiscsi\fR. If the \fB-t\fR option is not specified, the output consists of all URIs that identify the logical unit matched by the specified \fItarget\fR and \fILUN\fR. In general only one URI type will be present in the output even without the \fB-t\fR option. .sp The target must consists of an identifier type and the identifier, separated by a period. Supported ID types are \fBnaa\fR, \fBiqn\fR, and \fBeui\fR. Fibre-channel target ports are always NAA based names. iSCSI target ports are always IQN or EUI-64 based names. See EXAMPLES. .sp \fILUN\fR is a decimal number. .RE .SH EXAMPLES .LP \fBExample 1\fR Parsing a URI and Displaying Properties .sp .LP The following command parses and iSCSI URI and displays a default list of properties. .sp .in +2 .nf $ \fBsuriadm parse iscsi://10.0.0.1:3260/luname.naa.0123456789abcdef\fR PROPERTY VALUE uri-type iscsi hostname 10.0.0.1 port 3260 luname naa.0123456789abcdef target - lun - .fi .in -2 .sp .sp .in +2 .nf $ \fBsuriadm parse \e\fR \fB\ \ iscsi://10.0.0.1:3260/target.iqn.1990-12.com.sun:cng-002,lun.3\fR PROPERTY VALUE uri-type iscsi hostname 10.0.0.1 port 3260 luname - target iqn.1990-12.com.sun:cng-002 lun 3 .fi .in -2 .sp .LP \fBExample 2\fR Mapping an iSCSI URI and Displaying a Device Name .sp .LP The following command maps an iSCSI URI and displays the mapped local system device names. The effect of this command is to automatically add a \fBsend-targets\fR discovery address if one is not already present. .sp .in +2 .nf $ \fBsuriadm map \e\fR \fB\ \ iscsi://127.0.0.1/luname.naa.600144F0F4977D4000004F7EC8F00001\fR PROPERTY VALUE mapped-devs /dev/dsk/c0t600144F0F4977D4000004F7EC8F00001d0 .fi .in -2 .sp .LP \fBExample 3\fR Mapping an iSCSI URI and Displaying Device Names when the device is accessible by means of multiple paths. .sp .LP The following command displays all the device names, when there is multiple device paths corresponding to a URI. .sp .in +2 .nf $ \fBsuriadm map \e\fR \fB\ \ iscsi://localhost/luname.naa.600144F0F42B0A00000053BC37270001\fR PROPERTY VALUE mapped-devs /dev/dsk/c6t46d0 /dev/dsk/c6t45d0 /dev/dsk/c6t48d0 /dev/dsk/c6t47d0 /dev/dsk/c6t49d0 .fi .in -2 .sp .LP \fBExample 4\fR Looking Up Mapping .sp .LP The following command looks up an existing iSCSI mapping. .sp .in +2 .nf $ \fBsuriadm lookup-mapping \e\fR \fB\ \ iscsi://127.0.0.1/luname.naa.600144F0F4977D4000004F7EC8F00001\fR PROPERTY VALUE mapped-devs /dev/dsk/c0t600144F0F4977D4000004F7EC8F00001d0 .fi .in -2 .sp .LP \fBExample 5\fR Parsing a Logical Unit URI .sp .LP The following command parses an initiator,target,luname logical unit URI. .sp .in +2 .nf $ \fBsuriadm parse lu:initiator.naa.2101001b32ae7ab5,\e\fR \fB\ \ target.naa.2100001d38089fb0,luname.naa.500000e012942880\fR PROPERTY VALUE uri-type lu luname naa.500000e012942880 initiator naa.2101001b32ae7ab5 target naa.2100001d38089fb0 .fi .in -2 .sp .LP \fBExample 6\fR Mapping a Logical Unit URI, Looking Up URIs .sp .LP The following command sequence maps a logical unit URI, then looks up the matched logical unit URIs based on a found device name. .sp .in +2 .nf $ \fBsuriadm map lu:luname.naa.5000c5000288fa25\fR PROPERTY VALUE mapped-devs /dev/dsk/c7t26d0 $ \fBsuriadm lookup-uri -t lu /dev/dsk/c7t26d0\fR lu:luname.naa.5000c5000288fa25 lu:initiator.naa.500605b000ae7010,target.naa.5001636000019c11,\e \ \ naa.5000c5000288fa25 .fi .in -2 .sp .LP \fBExample 7\fR Looking Up Matching URIs .sp .LP The following command looks up all URIs that match a specific device name without specifying a URI type. .sp .in +2 .nf $ \fBsuriadm lookup-uri /dev/dsk/c7t26d0\fR lu:luname.naa.5000c5000288fa25 lu:initiator.naa.500605b000ae7010,target.naa.5001636000019c11,\e \ \ luname.naa.5000c5000288fa25 dev:dsk/c7t26d0 .fi .in -2 .sp .LP \fBExample 8\fR Parsing a URI, Displaying Selected Properties .sp .LP The following command parses a URI and displays only selected properties, all on the same line, separated by tabs, and with no header. .sp .in +2 .nf $ \fBsuriadm map -Ho uri-type,luname,mapped-dev \e\fR \fB\ \ lu:luname.naa.5000c5000288fa25\fR lu naa.5000c5000288fa25 /dev/dsk/c7t26d0 .fi .in -2 .sp .LP \fBExample 9\fR Looking Up Logical Unit URIs .sp .LP The following command looks up logical unit URIs for a device accessible by means of multiple paths. .sp .in +2 .nf $ \fBsuriadm lookup-uri -t lu /dev/dsk/c11t2000001D38089FB0d0\fR lu:luname.naa.2000001d38089fb0 lu:initiator.naa.2101001b32ae7ab5,target.naa.2100001d38089fb0,luname.\e \ \ naa.2000001d38089fb0 lu:initiator.naa.2100001b328e7ab5,target.naa.2200001d38089fb0,luname.\e \ \ naa.2000001d38089fb0 .fi .in -2 .sp .LP \fBExample 10\fR Trying to Parse Incorrect URI .sp .LP The following command attempts to parse a syntactically incorrect URI. .sp .in +2 .nf $ \fBsuriadm parse lu:luname.naa.0123456789\fR Failed to parse URI "lu:luname.naa.0123456789": GUID part in "luname.naa.GUID" not 16 or 32 character hexadecimal number: "0123456789" .fi .in -2 .sp .LP \fBExample 11\fR Trying to Map LU URI with Inaccessible LU .sp .LP The following command attempts to map an LU URI with a logical unit name not accessible from the system. .sp .in +2 .nf $ \fBsuriadm map lu:luname.naa.0123456789abcdef\fR Failed to map URI "lu:luname.naa.0123456789abcdef": No such logical unit "naa.0123456789abcdef" found .fi .in -2 .sp .LP \fBExample 12\fR Looking Up URI for Non-Existent Device Path .sp .LP The following command attempts to lookup a URI for a non-existent device path. .sp .in +2 .nf $ \fBsuriadm lookup-uri /dev/dsk/non-existent\fR Failed to map "/dev/dsk/non-existent" to URI: No such device: "/dev/dsk/non-existent" .fi .in -2 .sp .LP \fBExample 13\fR Looking Up \fBdev\fR URI .sp .LP The following command sequence illustrates the fact that the \fBdev\fR URI is the only URI type that accepts a disk pathname that specifies a slice. .sp .in +2 .nf $ \fBsuriadm lookup-uri -t dev /dev/dsk/c0t500000E012942880d0s0\fR dev:dsk/c0t500000E012942880d0s0 $ \fBsuriadm lookup-uri -t iscsi \e\fR \fB\ \ /dev/dsk/c0t600144F03E0A0C0000004FAB3B660001d0s0\fR Failed to look up "iscsi" URI for device: "/dev/dsk/c0t600144F03E0A0C0000004FAB3B660001d0s0": Device path with slice does not represent entire disk .fi .in -2 .sp .LP \fBExample 14\fR Normalizing a URI .sp .LP The following command normalizes an iSCSI URI. .sp .in +2 .nf $ \fBsuriadm normalize iscsi://10.0.0.1:3260/luname.naa.0123456789ABCDEF\fR iscsi://10.0.0.1/luname.naa.0123456789abcdef .fi .in -2 .sp .sp .LP The following invocations normalize \fBdev\fR URIs. .sp .in +2 .nf $ \fBsuriadm normalize dev:/dev/dsk/c0t0d0\fR dev:dsk/c0t0d0 .fi .in -2 .sp .sp .in +2 .nf $ \fBsuriadm normalize dev:///dev/dsk/c0t0d0\fR dev:dsk/c0t0d0 .fi .in -2 .sp .LP \fBExample 15\fR Getting URIs Based on Target and LUN .sp .LP The following command shows how to get URIs based on target and LUN. .sp .in +2 .nf $ \fBsuriadm lookup-uri -p target=naa.2100001d38089fb0 -p lun=0\fR lu:luname.naa.500000e012942880 lu:initiator.naa.2101001b32ae7ab5,target.naa.2100001d38089fb0,\e \ \ luname.naa.500000e012942880 .fi .in -2 .sp .sp .in +2 .nf $ \fBsuriadm lookup-uri -p lun=0 -p \e\fR \fB\ \ target=iqn.1986-03.com.sun:02:9548ddf8-e7ac335a760f\fR iscsi://10.0.0.1/luname.naa.600144f0a5320b470000527d66740009 iscsi://10.0.0.1/target.iqn.1986-03.com.sun:02:9548ddf8-e7ac335a760f,lun.0 .fi .in -2 .sp .sp .in +2 .nf $ \fBsuriadm lookup-uri -p target=eui.bbbbbbbbbbff0011 -p lun=1\fR iscsi://10.0.0.1/luname.naa.600144f0a76c607200005bcf451b0002 iscsi://10.0.0.1/target.eui.bbbbbbbbbbff0011,lun.1 .fi .in -2 .sp .LP \fBExample 16\fR Getting LU URIs Based on a Logical Unit Name .sp .LP The following command shows how to get LU URIs based on a logical unit name: .sp .in +2 .nf $ \fBsuriadm lookup-uri -t lu -p luname=naa.5000cca012b66e90\fR lu:luname.naa.5000cca012b66e90 lu:initiator.naa.5080020000fafcf8,target.naa.5000cca012b66e91,\e \ \ luname.naa.5000cca012b66e90 .fi .in -2 .sp .LP \fBExample 17\fR Setting an Input Property on \fBmap\fR .sp .LP The following command shows how to set an input property on \fBmap\fR. .sp .in +2 .nf $ \fBsuriadm create -p create-size=2G file://user1:group2@/export/file1\fR .fi .in -2 .sp .LP \fBExample 18\fR Device based look-up of all iSCSI URIs over all available targets .sp .in +2 .nf $ \fBsuriadm lookup-uri -t iscsi /dev/dsk/c0t600144F0A76C607200005BCF451B0002d0\fR iscsi://10.10.10.10/luname.naa.600144f0a76c607200005bcf451b0002 iscsi://10.10.10.10/target.eui.bbbbbbbbbbff0011,lun.1 iscsi://10.10.10.10/target.iqn.1986-03.com.sun:02:60ae9e51-dbc79738b319,lun.1 .fi .in -2 .sp .SH EXIT STATUS .sp .ne 2 .mk .na \fB\fB0\fR\fR .ad .br .sp .6 .RS 4n Command succeeded. .RE .sp .ne 2 .mk .na \fB\fB>0\fR\fR .ad .br .sp .6 .RS 4n Command failed. .RE .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for descriptions of the following attributes: .sp .TS tab( ) box; lw(2.75i) |lw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Availability system/library/storage/suri _ Interface Stability Committed .TE .sp .SH SEE ALSO .sp .LP \fBlibsuri\fR(3LIB), \fBscsi_vhci\fR(4D), \fBattributes\fR(7), \fBsuri\fR(7), \fBstmsboot\fR(8), \fBsvcadm\fR(8) .sp .LP \fISmall Computer System Interface-3\fR (SCSI-3) .SH NOTES .sp .LP When an iSCSI URI is used, the \fBsvc:/network/iscsi/initiator\fR service must be enabled, unless a parse operation is being performed. If this service is disabled and an iSCSI URI is being processed, the iSCSI initiator service will be automatically enabled temporarily. The service is never disabled through the \fBsuriadm\fR command. .sp .LP When a \fB/dev/chassis\fR form of a dev URI is used, the \fBsvc:/system/devchassis:daemon\fR service must be enabled, unless a parse operation is being performed. If the service is disabled and a \fB/dev/chassis\fR form of a dev URI is being processed, the service will be automatically enabled temporarily. The service is never disabled through the \fBsuriadm\fR command.