beautypg.com

HP Hitachi Dynamic Link Manager Software User Manual

Page 171

background image

3. Creating an HDLM Environment

147

Table 3-15: LU Deletion Function Values

Setting up LU deletion by using the

set

operation

The following is an example of setting up LU deletion by using a command:


>dlnkmgr set -rmlu on -force

To enable the LU deletion function, specify

on

. To disable the LU deletion

function, specify

off

. If you specify

on

, you can set the conditions for the

-force

parameter.

(6) Setting the Error Log Collection Level

There are two error logs: the HDLM manager log file

dlmmgr

n

.log

(n indicates a file

number from

1

to

16

) and the HDLM GUI log file

dlmgui

n

.log

(n indicates a file

number of

1

or

2

).

Table 3-16: Values for the Error Log Collection Level Setting lists and describes the

values for the error log collection level setting.

Table 3-16: Values for the Error Log Collection Level Setting

Values in the

set

operation

Description

off

The LU is not removed from HDLM-management even if the error occurs on all the
paths to the LU, all the paths to the LU are disconnected, or the LU is deleted. The

status of the paths is either

Offline(E)

or

Online(E)

. This operation is equal to

the operation in HDLM 05-01 or earlier. The

off

option is recommended when you

do not want to use the LU deletion function and you want the system to operate as it

did in HDLM 05-01 and earlier.

on

The LU is removed from HDLM-management when all the paths to the LU are
disconnected. However, if an

Offline(C)

path is included in the disconnected

paths, the LU is not deleted from HDLM-management.
The deleted LU is restored when it is recovered from the physical failure and the disk

is re-scanned.

on -force

The LU is removed from HDLM-management when all the paths to the LU are
disconnected, even when an

Offline(C)

path is included.

The removed LU is restored after it is recovered from the physical failure and the disk
is re-scanned.

Value

Description

0

No error logs are collected.

1

All information for errors of the "Error" level or higher is

collected.