Hitachi Dynamic Link Manager Software GUI Help

[Contents][Index][Back][Next]

2.1.2 Setting up HDLM the Functionality

The recommended and default values for the HDLM functions are shown below in Table 2-1 The recommended and default values for each function.

Table 2-1 The recommended and default values for each function

Function Default value Recommended value
Load-balancing ON
Algorithm is round robin		 ON
The recommended algorithm depends on the operating environment.
Path health checking ON
30-minute check interval		 ON
The recommended checking interval depends on the operating environment.
Automatic failback ON
1-minute check interval		 The recommended checking interval depends on the operating environment.
Intermittent Error Monitor OFF OFF
Reservation level (Not specifiable) (Not specifiable)
LU dynamic removal OFF The recommended value depends on the operating environment.
Logging level 3: Information or higher level 3: Information or higher level
Trace level 0: Do not output a trace 0: Do not output a trace
File size (for Error log) 9900 (KB) 9900 (KB)
Number of files (for Error log) 2 2
File size (for Trace) 1000 (KB) 1000 (KB)
Number of files (for Trace) 4 4
Organization of this subsection
(1) Setting Load Balancing
(2) Setting Path Health Checking
(3) Setting Automatic Failback
(4) Settings for Intermittent Error Monitoring
(5) Setting the Reservation Level
(6) Setting the LU Dynamic Removal Functionality
(7) Setting the Error Log Collection Level
(8) Setting the Trace Level
(9) Setting the Error Log File Size
(10) Setting the Number of Error Log Files
(11) Setting the Trace File Size
(12) Setting the Number of Trace Files

(1) Setting Load Balancing

You can select whether to enable load balancing.

(2) Setting Path Health Checking

You can select whether to enable path health checking.

(3) Setting Automatic Failback

You can select whether to enable automatic failback.

When intermittent error monitoring is enabled and the number of error occurrences is 2 or more, the following condition must be satisfied:

 
error-monitoring-interval >= checking-interval-for-automatic-failback x number-of-times-error-is-to-occur-during-intermittent-error-monitoring

If this condition is not satisfied, an error occurs and a message is output.

In such a case, change any of the following settings: the checking interval for automatic failback, intermittent error monitoring interval, or the number of times that the error is to occur. When you set the number of times that the error is to occur to 1, the condition above does not need to be satisfied.

(4) Settings for Intermittent Error Monitoring

Intermittent error monitoring is specifiable only when automatic failback is enabled. To prevent an intermittent error from reducing I/O performance, we recommend that you monitor intermittent errors when automatic failback is enabled.

When intermittent error monitoring is enabled, you can specify intermittent error conditions (the conditions used by the system to determine whether an intermittent error is occurring). The default value for the intermittent error monitoring interval is 30. The default value for the number of error occurrences is 3.

The system assumes that an intermittent error is occurring if the specified number of times that the error is to occur is reached during the monitoring interval (from the time that the monitoring interval starts, until the specified interval ends). A path that is assumed to have an intermittent error is excluded from automatic failback. Intermittent error monitoring starts when the path is recovered from the error by using automatic failback. Monitoring is performed on individual paths.

When a value of 2 or more is specified in number of times, make sure that the condition shown in (3) Setting Automatic Failback is satisfied.

You can check whether a path is assumed to have an intermittent error by using the Path List view of the HDLM GUI.

(5) Setting the Reservation Level

You cannot set the reservation level (reservation control method for the LU).

(6) Setting the LU Dynamic Removal Functionality

You can select whether to enable the LU dynamic removal functionality.

For details on the LU dynamic removal functionality, see 3.3.2 Deleting an LU dynamically.

Table 2-2 LU Dynamic Removal Settings Values shows the values for the LU deletion functionality.

Table 2-2 LU Dynamic Removal Settings Values

Values in the Options window Description
OFF The LU is not removed from HDLM-management even if the error occurs in 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 Offline(E) and Online(E). This operation is as equal as the operation in HDLM 05-01 or earlier. The off option is recommended when you want to use the same functionality as you use in HDLM 05-01 or earlier, without using the LU deletion functionality.
ON The Remove the LU even if there are Offline(C) paths option is set to OFF. 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.
The Remove the LU even if there are Offline(C) paths option is set to ON. 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 when it is recovered from the physical failure and the disk is re-scanned.

(7) Setting the Error Log Collection Level

The error log collection level can be set.

There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2).

Table 2-3 Values for the error log collection level setting lists and describes values for the error log collection level setting.

Table 2-3 Values for the error log collection level setting

Value Description
0: Do not collect an error log No error logs are collected.
1: Error or higher level All information for errors with the level "Error" or higher is collected.
2: Warning or higher level All information for errors with the level "Warning" or higher is collected.
3: Information or higher level All information for errors with the level "Information" or higher is collected.
4: Information or higher level (including maintenance information) All information for errors with the level "Information" or higher (including maintenance information) is collected.

If an error occurs, you might have to change the collection level to 1 or higher to collect log information. The higher this value is set, the more log information will be output. When the output log is large, it takes less time to overwrite the old error log information with the new information.

(8) Setting the Trace Level

The trace output level can be set.

A trace file in which a trace level can be set is hdlmtrn.log (n indicates a file number from 1 to 64).

Table 2-4 Values for the trace level setting lists and describes values for the trace level setting.

Table 2-4 Values for the trace level setting

Value Description
0: Do not output any trace No trace is output.
1: Error information only Only error information is output.
2: Summary of program operation Program operation summaries are output.
3: Details of program operation Program operation details are output.
4: All information All information is output.

If an error occurs, you might have to set the trace level to 1 or higher to collect the log information. The higher this value is set, the more log information will be output. When the output log is large, it takes less time to overwrite the old error log information with the new information.

(9) Setting the Error Log File Size

The error log file size can be set.

There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2).

You can specify a value (in kilobytes) from 100 to 2000000 for the error log file size. For HDLM GUI logs, the valid range of a file size is from 100 to 9900. If you specify a value of 9901 or more, 9900 is applied. The specified value is applied for HDLM manager logs.

When an error log file reaches the specified size, the information in the old error log file is replaced with new information, beginning with the oldest file. By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30GB) of error logs in total.

(10) Setting the Number of Error Log Files

The number of the error log files can be set.

There are two error logs: the HDLM manager log file dlmmgrn.log (n indicates a file number from 1 to 16) and the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2). The error logs you can set in the Options window are limited to the HDLM manager log files dlmmgrn.log (n indicates a file number from 1 to 16). The number of files for the HDLM GUI log file dlmguin.log (n indicates a file number of 1 or 2) is fixed to 2. You can specify a value from 2 to 16 for the number of error log files (log files for the HDLM manager). By specifying both the log file size and the number of log files, you can collect up to 32000000KB (approximately 30GB) of error logs in total.

(11) Setting the Trace File Size

The trace file size can be set.

Trace files for which a trace file size can be set are hdlmtrn.log (n indicates a file number from 1 to 64). The length of a trace file is fixed. Thus, even if the amount of written trace information is less than the set file size, the file size of each output trace file is always fixed.

For the trace file size, you can specify a value (in kilobytes) from 100 to 16000. If you specify a value smaller than the setting value, a message is displayed to confirm execution, and the trace file is temporarily deleted.

Once trace data has been written to all the trace files, the oldest file is overwritten with new trace data.

By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data in total.

(12) Setting the Number of Trace Files

You can set the number of trace files.

Trace files for which the number of files can be set are hdlmtrn.log (n indicates a file number from 1 to 64).

For the number of trace files, you can specify a value from 2 to 64. If you specify a value smaller than the setting value, a message is displayed to confirm execution, and the trace file is temporarily deleted.

By specifying both the trace file size and the number of trace files, you can collect up to 1024000KB of trace data in total.

[Contents][Back][Next]

[Trademarks]