Discovering and assigning volumes with OpenVMS

To recognize volumes, OpenVMS issues a UDID value, which can be set during a creation or a change of volumes by using the -udidXXX option, where XXX is any unique numeric number.

Each OpenVMS fibre-attached volume requires a user-defined identifier or unit device identifier (UDID). A UDID is a nonnegative integer that is used when an OpenVMS device name is created. All fibre-attached volumes have an allocation class of $1$ , followed by the letters DGA, followed by the UDID value. All storage unit LUNs that you assign to an OpenVMS system require a UDID so that the operating system can detect and name the device. LUN 0 must be created and present so that the OpenVMS system can detect the rest of the assigned volumes.

An OpenVMS UDID value must be a decimal number 0 - 32767. However, because the CLI utility does not enforce UDID value rules, you must ensure that your input is valid. For example, the CLI accepts values such as AaBbCcDd that are not valid for OpenVMS. It is also possible to assign the same UDID value to multiple storage unit volumes. However, each volume that you assign to an OpenVMS system must have a value that is unique within the OpenVMS cluster. For more information about UDID rules, see the HP OpenVMS documentation at http://h71000.www7.hp.com.

Note: Volumes with UDID values greater than 9999 cannot be MSCP-served in an OpenVMS cluster to other systems.

UDID values must be entered during volume creation after MDisk and related group and host information is set up. UDID values can be changed or added by using the chvdisk command. See Figure 1.

Figure 1. Example output for assigning volumes

mkvdisk -mdiskgrp 0 -size 2 -unit gb -iogrp io_grp0 -mdisk mdisk0 -udid 10 -name ovms_10

mkvdiskhostmap -host gs160a ovms_10

When you use the procedure that is outlined in Figure 1, you can then use the same procedure for the remaining new disks. See Figure 2.

Figure 2. Example output

 lsvdisk -delim :
id:name:IO_group_id:IO_group_name:status:mdisk_grp_id:mdisk_grp_name:capacity:type:
FC_id:FC_name:RC_id:RC_name:vdisk_UID
0:ovms_0:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000000
1:ovms_1:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000001
2:ovms_2:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000002
3:ovms_3:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000003
4:ovms_4:0:io_grp_0:online:0:ds6000:3.0GB:striped:::::60050768019381005000000000000004
5:ovms_5:0:io_grp_0:online:0:ds6000:3.0GB:striped:::::60050768019381005000000000000005
6:ovms_6:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000006
7:ovms_7:0:io_grp_0:online:0:ds6000:2.0GB:striped:::::60050768019381005000000000000007

If the system is already running, locate the WWPN by using the Show Device command or the Analyze/System utility. To run the Show Device command, enter the following command:

show device fg/full

To run the Analyze/System utility, you must have OpenVMS CMKRNL privilege. To use this utility, complete the following steps:

Enter the following command:
```
ANALYZE/SYSTEM
```
At the SDA> prompt, enter the following command:
```
fc show dev fgadapter0
```

Where adapter is the letter that identifies the adapter. For example, enter this command:

fc show dev fga0

Use the SYSMAN utility to discover new disks on the OpenVMS host. See Figure 3.

Figure 3. Example output

SYSMAN> IO SCSI_PATH_VERIFY
SYSMAN> IO AUTOCONFIGURE
SYSMAN> exit
$ sho dev d

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
GS160A$DKA0:            Online               0
$1$DGA10:     (GS160A)  Online               0
$1$DGA11:     (GS160A)  Online               1
$1$DGA12:     (GS160A)  Online               1
$1$DGA13:     (GS160A)  Online               1
$1$DGA14:     (GS160A)  Online               0
$1$DGA15:     (GS160A)  Online               0
$1$DGA16:     (GS160A)  Online               0
$1$DGA17:     (GS160A)  Online               0
$1$DGA10001:  (GS160A)  Online               0
$1$DKD100:    (GS160A)  Online               0
$1$DKD300:    (GS160A)  Mounted              0  GS160A_SYS    25643715   341   1
$1$DKD500:    (GS160A)  Online               0
$1$DQA0:      (GS160A)  Online               0
$1$DQA1:      (GS160A)  Offline              1
$ init $1$dga16: dga16
$ init $1$dga17: dga17
$ mou $1$dga16 dga16
%MOUNT-I-MOUNTED, DGA16 mounted on _$1$DGA16: (GS160A)
$ mou $1$dga17 dga17
%MOUNT-I-MOUNTED, DGA17 mounted on _$1$DGA17: (GS160A)
$ init $1$dga10: dga10
$ init $1$dga11: dga11
$ mou $1$dga11 dga11
%MOUNT-I-MOUNTED, DGA11 mounted on _$1$DGA11: (GS160A)
$ sho dev d

Device                  Device           Error    Volume         Free  Trans Mnt
 Name                   Status           Count     Label        Blocks Count Cnt
GS160A$DKA0:            Online               0
$1$DGA10:     (GS160A)  Online               0
$1$DGA11:     (GS160A)  Mounted alloc       12  DGA11          4193950     1   1
$1$DGA12:     (GS160A)  Online              57
$1$DGA13:     (GS160A)  Online              57
$1$DGA14:     (GS160A)  Online              56
$1$DGA15:     (GS160A)  Online              57
$1$DGA16:     (GS160A)  Mounted alloc       12  DGA16          4193950     1   1
$1$DGA17:     (GS160A)  Mounted alloc       20  DGA17          4193950     1   1
$1$DGA10001:  (GS160A)  Online               0
$1$DKD100:    (GS160A)  Online               0
$1$DKD300:    (GS160A)  Mounted              0  GS160A_SYS    25642572   341   1
$1$DKD500:    (GS160A)  Online               0
$1$DQA0:      (GS160A)  Online               0
$1$DQA1:      (GS160A)  Offline              1

Note: Lenovo Storage V series notification messages might appear on a host as ASC/ASCQ errors. Examples might include x2500 (Logical Unit Not Supported), x2900 (Power On, Reset, or Bus Device Reset Occurred), and x3F0E (Direct Access Device ASC/ASCQ unrecognized). These errors do not result in any data or access loss.