lshostvol
The lshostvol command displays the mapping of host device names or volume names to machine type 2107 volume IDs. (This command is not supported on the i5/OS).
Parameters
This command has no parameters.
Notes:
- The lshostvol command displays only volumes that are accessed by using a
direct Fibre Channel path when you use the command on an OpenVMS host system that is a member of an
OpenVMS cluster. The command output does not display information about the following OpenVMS
cluster devices:
- Volumes to which the host system has only Mass Storage Control Protocol (MSCP) paths.Note: Mass Storage Control Protocol uses two queues. Into one queue, packets are placed which fully describe the commands to be run by the mass storage subsystem. To start an I/O request, the creates a small data structure in memory and appends it to a "send" queue. If this packet is the first packet in the send queue, it wakes the MSCP controller. After the command is processed, an appropriate status packet is placed into the second queue to be read by the CPU.
- Volumes to which the host system uses only MSCP paths now even though it has both MSCP and direct paths.
- Volumes to which the host system has only Mass Storage Control Protocol (MSCP) paths.
- If you did not install the IBM® Multipath Subsystem Device Driver (SDD), the virtual path (vPath) name is not displayed.
- On a Red Hat Enterprise Linux® system, attached devices
might be detected by the HBA driver, but they are not registered with the operating system.
Normally, the operating system is set up to automatically detect all LUNS. However, if this
detection does not occur automatically, you must issue the following command for every volume
(LUN):
echo scsi add-single-device host# channel# lun# >/proc/scsi/scsi
If SDD is installed on your system, you can run the scsiscan script to detect all the LUNs.
- If the user that is running the DS CLI on the host does not have permissions to view the host volumes, the lshostvol command returns no host volumes found.
Example: Displaying the mapping of host device names or volume names to machine type 2107 volume IDs
The information that is displayed on the report that is generated from the lshostvol command is different depending on whether you installed SDD. The following example tables indicate the differences.
Note: For DS CLI list commands, the results are shown in table format to provide clarity. The actual
reports do not display as tables.
The following tables represent the headers that are displayed on the output reports that are associated with the lshostvol command.
dscli> lshostvol
Output
With SDD installed
Disk Name | Volume ID | Vpath Name |
---|---|---|
my_vol_01,my_vol_04 | IBM.2107-75DA110/175D | vpath01 |
my_vol_02,my_vol_05 | IBM.2107-75EA120/175E | vpath02 |
my_vol_03,my_vol_06 | IBM.-75FA130/175F | vpath03 |
Without SDD installed
Device/Volume Name | Volume ID | Vpath Name |
---|---|---|
Hdisk01 | IBM.2107-75DA110/175D | - |
Hdisk02 | IBM.2107-75EA120/175E | - |
Hdisk03 | IBM.2107-75FA130/175F | - |
Report column definitions
- Device/Volume name
- The nickname that you assigned to the device or volume. When SDD is installed, this column reports the volume name instead of the device name.
- Volume ID
- The ID of the storage system.
- Vpath name
- The virtual path name. When SDD is not installed, this value is reported as " - ".