Currently, MPIO supports multiple paths to disk devices only. To use MPIO, at least one Host Bus Adapter (HBA) or Storage Area Network (SAN) controller attached to the system must be capable of supporting multiple logical or physical paths to a single disk drive. MPIO across multiple HBA controllers is not supported.
Multipath I/O is implemented as a device driver in the operating system kernel and as such is able to detect and discover all known paths for devices on system boot. By default the multipath I/O (MPIO) driver will attempt to use all paths and load balance I/O.
The sdipath command is the administrative interface to managing multipath I/O. There are operations provided for listing paths that include status and performance information, and operations for controlling which paths are active so you can tune your system for better performance or higher availability, as well as repair paths that have failed.
As the system boots, physical disks are discovered and brought online. Each disk has a stamp associated with it that is used to determine if this is the first occurrence of this disk. If it is the first occurrence, a device node is created in /dev/rdsk and /dev/dsk, then an entry is made into the resource manager database. All subsequent occurrences of this disk will only get an entry in the resmgr(ADM) database under an ``sdol'' entry.
The pathname associated with each path to the disk is created by appending the resource manager key value to the word path. Thus if a resource manager entry is made for a path having a resmgr key of 29, the name of this path would be ``path29''.
mkdev mpioFollow the insturctions to enable MPIO.
shutdown -i6 -g0 -yThe kernel is rebuilt and the system is rebooted with the new kernel.
sdipath -o listTo list the MPIO devices and defined paths.
MPIO_IOCTL_GET_PATHS() status -1, errno 22, output 0 UX:sdipath: ERROR: Getting paths for device disk1, errno 22.
The path state can be either Active, Inactive, or Failed.
If active, the path is currently available for I/O. In this state, the MPIO driver can send I/O through this path to the device.
If inactive, the path is not available for I/O. For example, a path may be inactive if it is connected to the inactive port of a standalone RAID device, such as a CLARiION disk array.
If failed, either the driver marked the path as failed after being unable to perform I/O on the path, or the system administrator marked the path as failed manually. Paths that are in the failed state will remain failed until the administrator issues a repair operation after the problem has been corrected.
To list information about all paths on the system:
sdipath -o list
To list information about all paths associated with
sdipath -o list -d disk3
To fail path51 of device c0b0t0d0p0:
sdipath -o fail -d c0b0t0d0p0 path51
To repair path52 of a device whose alias is
sdipath -o repair -d disk1 path52