suri

- storage URIs

Description

Storage URIs uniquely identify storage objects across different nodes.

The following Storage URIs are supported:

Dev URI

dev:<local-path-under-/dev>
dev:///<path-with-dev>
dev:<absolute-path-with-dev>

Examples:

dev:dsk/c0t0d0s0
dev:///dev/dsk/c0t0d0s0
dev:/dev/dsk/c0t0d0s0

The dev URI specifies an object in the form of an existing device. All forms of the dev URI are functionally equivalent. The “dev:dsk” format with no authority section and an implied “/dev/” prefix is usually preferred. The path must be a device in the /dev name space.

Components of the device path may only include characters from POSIX.1-2008 Portable Filename Character Set, 0-9a-zA-Z._-.

Logical Unit URI

lu:luname.naa.<ID>
lu:initiator.naa.<ID>,target.naa.<ID>,luname.naa.<ID>

Examples:

lu:luname.naa.5000c5000288fa25
lu:initiator.naa.2100001d38089fb0,target.naa.2100001d38089fb0,luname.naa.5000c5000288fa25

Logical unit URI specifies a logical unit attached via fibre channel or serial-attached SCSI. In the luname-only URI form, the ID describes a logical unit name. In the initiator,target,luname form, an initiator specifies an initiator port and a target specifies a target port, and together they specify a path to the logical unit whose name must match the URI's luname part as in the luname-only form.

IDs are represented by using the SCSI-3 VPD page (0x83) global unique identifier (GUID) formatted as hexadecimal numbers (64/128 bits). IDs are case insensitive. Only GUIDs based on NAA identifiers are supported. See NOTES for information on NAA identifier format.

In general it is recommended using multipathing in conjunction with luname-only URIs. If multipathing is disabled and a luname-only URI is used, a random path to the specified logical unit will be chosen. To avoid this random path assignment an initiator,target,luname URI form can be used to select a specific path to a logical unit. If multipathing is enabled and an initiator,target,luname URI form is used then the multipathing framework controls which paths are used to access the logical unit and the URI is only used to identify the unit, not the access path.

If an initiator or/and a target IDs are not matched but the logical unit is found based on a logical unit name, the unit will be accessed via an alternate path.

iSCSI URI

iscsi:///luname.naa.<ID>
iscsi://<host>[:<port>]/luname.naa.<ID>

Examples:

iscsi:///luname.naa.600144f03d70c80000004ea57da10001
iscsi://[::1]/luname.naa.600144f03d70c80000004ea57da10001
iscsi://127.0.0.1/luname.naa.600144f03d70c80000004ea57da10001
iscsi://127.0.0.1:3620/luname.naa.600144f03d70c80000004ea57da10001
iscsi://hostname:3620/luname.naa.600144f03d70c80000004ea57da10001

The iSCSI URI specifies an object based on a logical unit number accessible via iSCSI protocol. Optional hostname[:<port>] authority section provides information for a consumer to set up a send-targets discovery address. IPv6 addresses must be enclosed in square brackets.

Format of an ID is explained in the “Logical Unit URI” section. See NOTES for information on NAA identifier format.

Getting URIs

To avoid errors by generating URIs manually, the suriadm(1M) subcommand lookup-uri is recommended to be used to generate URIs based on existing system device paths. Such device paths must be identified via other means. For Fibre Channel devices, fcadm(1M) may be used. For Serial Attached SCSI devices, sasinfo(1M) may be used. For iSCSI devices, iscsiadm(1M) may be used.

Attributes

See attributes(5) for descriptions of the following attributes:

See Also

fcadm(1M), iscsiadm(1M), sasinfo(1M), suriadm(1M), attributes(5)

Small Computer System Interface-3 (SCSI-3)

Notes

NAA stands for “Name Address Authority” and it is a field within an identifier that specifies the format and length of that identifier. NAA identifier format is defined in SCSI Primary Commands - 3 specification, section “7.6.3.6 NAA identifier format”. WWN (World Wide Name) identifiers use an NAA identifier format.