HP Hitachi Dynamic Link Manager Software User Manual
Page 138

3. Creating an HDLM Environment
116
Path Health Checking : on(30)
Auto Failback : on(1)
Intermittent Error Monitor : off
HDLM Manager Ver WakeupTime
Alive
x.x.x-xx
yyyy
/
mm
/
dd
hh
:
mm
:
ss
HDLM Alert Driver Ver WakeupTime ElogMem Size
Alive
x.x.x-xx
yyyy
/
mm
/
dd
hh
:
mm
:
ss
4096
HDLM Driver Ver WakeupTime
Alive
x.x.x-xx
yyyy
/
mm
/
dd
hh
:
mm
:
ss
License Type Expiration
Permanent -
KAPL01001-I The HDLM command completed normally. Operation
name = view, completion time =
yyyy
/
mm
/
dd
hh
:
mm
:
ss
#
Nothing is displayed for
Support Cluster
even if you are using cluster
software. However, the cluster-support functions are, in fact, operating without
problem.
15. By checking the execution results of the
view
operation, verify the version of the
installed HDLM.
If
HDLM Version
is
6.5.1-00
, the installed version of HDLM is correct.
16. By checking the execution results of the
view
operation, verify that the programs
are running normally.
If
HDLM Manager
,
HDLM Alert Driver
, and
HDLM Driver
are all
Alive
, the
programs are running normally.
17. In the environment settings files (such as
.profile
) for root permissions, add
/
opt/DynamicLinkManager/bin
to the
PATH
environment variable.
When the Bourne shell or Korn shell is used, add the path as shown below:
PATH=$PATH:/opt/DynamicLinkManager/bin ; export PATH
When the C shell is used, add the path as shown below:
set path=($path /opt/DynamicLinkManager/bin)
18. Execute the following command to view the HDevName and iLU columns:
# /opt/DynamicLinkManager/bin/dlnkmgr view -path
Check the execution results of this command to determine the correspondence
between each HDevName (the logical device file name of the HDLM device) and
iLU (the internal LU number). Then, compare the correspondence of the logical
device file names and internal LUs that took place before HDLM was installed,
and then re-register the correct HDLM devices in those programs that will use