HP Hitachi Dynamic Link Manager Software User Manual

Page 121

3. Creating an HDLM Environment

• Configuring a boot disk environment
• Setting up HDLM functions

• Setting up an integrated trace

• Creating a file system
• Executing an HDLM command
• Using an HDLM device
• Changing the configuration of the HDLM operating environment
• Applying an HDLM service pack

In single-user mode, HDLM command activity is not logged to integrated

trace files.

When you install HDLM while the 32-bit kernel mode is being used, only the

32-bit version of HDLM will be installed. When you install HDLM while the

64-bit kernel mode is being used, both the 32-bit and 64-bit versions of HDLM

will be installed. Before installing HDLM, decide which kernel mode you will use

to operate Solaris and, if needed, change to the desired kernel mode. If you switch

the kernel mode from 32 bits to 64 bits when only the 32-bit version of HDLM is

installed, you must reinstall HDLM after the switch is completed. For details on

how to switch the kernel mode, see (5) Switch the Kernel Mode in

3.5.1 Preparations for a New Installation of HDLM.

When installing HDLM on a host where a Device Manager Agent 5.0 or later is

installed, do not execute any of the following commands of Device Manager

Agent during installation:

hbsasrv, HiScan, hdvmagt_account, hdvmagt_schedule, hldutil,
TIC

3.4.3 Notes on Related Software

When using VxVM on the same host as HDLM, do not register any disk groups

containing HDLM devices in

bootdg

When configuring a boot disk environment on a host that is using VxVM 4.1, and

then executing a VxVM command such as the

vxdisk

list

, or

vxdmpadm

listenclosure

all

command, the enclosure type

FAKE_ARRAY

is displayed

for the boot disk but there is no problem. For details on this phenomenon, see the

Symantec documentation VERITAS Storage Foundation(TM) 4.1 Release Notes

Solaris Maintenance Pack 1.

If you use the

vxinstall

program or the

vxdiskadm

utility to perform an