Hitachi XP P9500 User Manual page 264
Hitachi dynamic link manager software user guide for solaris (6.6) (hit5205-96011, november 2011)
Hide thumbs
Also See for XP P9500:
- User manual (746 pages) ,
- User manual (640 pages) ,
- User manual (450 pages)
Table of Contents
Advertisement
¢
¢
¢
¢
¢
If the HDLM logical device file has been re-created by specifying the different
file name, perform the following procedures:
•
Change the disk settings being used by the application programs.
•
When using VxVM, execute the following command to confirm that the
DEVICE column of the LUs being managed by HDLM is displayed in the
cWtXdYsZ format (for example, c6t0d10s2):
# vxdisk list
If the value is displayed in the cWtXdYsZ format, perform the following
procedures:
a
.
b
.
•
If the logical device file before re-creation might remain in the /dev/dsk
and /dev/rdsk directories, you must delete the logical device file before
re-creation. Delete the logical device file before its re-creation, and then
follow the instructions in
Uses HDLM on page
The logical device file names of HDLM devices on each LU are determined by
using the path (physical device file name corresponding to the sd or ssd
device) that can be obtained by using the following procedure:
To obtain the path to an LU:
1
Obtain the instance number of the HDLM driver corresponding to the LU.
.
Execute the following command to display the minor number of the HDLM
device of the desired LU (HDLM device on slice 0). The value obtained by
dividing the displayed minor number by 8 is the instance number of
HDLM.
# /usr/bin/ls -lL HDLM-logical-device-file-name-on-slice-0
The following shows an example of executing the command.
This example obtains the instance number of the HDLM driver of the LU
whose logical device file name is /dev/dsk/c4t21d0s0. In this case, since
the minor number is 8, the instance number is 1.
4-18
A LUN was changed.
The HBA model was changed.
The HBA mounting slot was changed.
The contents of the /etc/path_to_inst file were altered to change
the instance number of the HBA driver.
The FCode was installed on an HBA where the FCode had not been
previously installed. Alternatively, the FCode was uninstalled from an
HBA.
Delete the /etc/vx/disk.info file.
Restart the host, or restart the VxVM configuration daemon by
executing the following command:
# vxconfigd -k
4-17.
HDLM Operation
Hitachi Dynamic Link Manager User Guide (for Solaris(R))
Changing the Configuration of a System that
Advertisement
Table of Contents
