Chapter 2 HDLM Functions
2.11 Error Management
HDLM collects information for troubleshooting into log files. HDLM can also filter error information according to the error level when collecting the information.
Figure 2.14 shows the data flow when collecting error information.
Figure 2.14 Data Flow When Collecting Error Information
Logs might be collected in layers lower than HDLM, such as for the SCSI driver. For details on such logs, see the Linux documentation.
2.11.1 Types of Logs Collected
HDLM collects information on the detected error and trace information in the integrated trace file, trace file, error logs, log for the dlmcfgmgr utility for managing the HDLM configuration and syslog. You can use the error information to examine the status of an error and analyze the cause of the error.
Table 2.7 describes the types of error information.
Table 2.7 Types of Error Information
Log name Description Output destination Integrated trace file Operation logs of
the HDLM command are collected.
The default file path is
/var/opt/hitachi/HNTRLib2/spool/hntr2[1-16].log.
To specify the output destination directory and the file prefix for integrated trace files, use a utility of Hitachi Network Objectplaza Trace Library (HNTRLib2).
Trace file Trace information on the HDLM need to change the settings to collect trace information.
The following is the trace file name:
/var/opt/DynamicLinkManager/log/hdlmtr[1-64].log
Error log Error information for the user-defined HDLM remote access interface logs:
/var/opt/DynamicLinkManager/log/dlmwebagent[1-N].log The value N depends on the setting in the file dlmwebagent.properties.
HDLM-configuration
The following is the log file name.
/var/opt/DynamicLinkManager/log/dlmcfgmgr[1-2].log
/var/opt/DynamicLinkManager/log/dlminquiry.log
Syslog The HDLM
messages on or above the level set by the user with syslogd settings file are collected. # We recommend that you configure the system so that information at the
The default file path is /var/log/messages.
The syslog file path is specified in the syslogd settings file. For details, see the Linux documentation.
#
When you want to configure the system so that HDLM messages are output to syslog, specify user for the facility in the syslog settings file. The following shows an example where the system function name is user, and messages at the info level or higher are output to the /tmp/syslog.user.log file:
user.info /tmp/syslog.user.log
For details on error levels, see section 2.11.2.
2.11.2 Filtering of Error Information
Errors that HDLM detects are classified into error levels. Table 2.8 lists the error levels, in order of adverse effect on the system.
Table 2.8 Error Levels
Error level Meaning
Critical Fatal errors that may stop the system.
Error Errors that crucially affect the system. This type of error can be avoided by using failover or other countermeasures.
Warning Errors that enable the system to continue but, if left, might cause the system to operate improperly.
Information Information that indicates the operating history when the system operates normally.
Error information is filtered according to the error level, and then collected.
The error level is equivalent to the level of the messages output by HDLM. For details on the level of the message, see section 8.1.1.
In syslog, the HDLM messages on or above the level set by the user configured in syslogd settings file are collected. It is recommended that you set the information to be output at the Information level or higher.
Note: all the facilities when HDLM outputs messages in syslog are user.
The error information in error logs and trace files are collected based on a user-defined collection level. The collection levels are as follows:
Collection levels for error logs – Collects no error information.
– Collects error information at the Error level and higher.
– Collects error information at the Warning level and higher.
– Collects error information at the Information level and higher.
– Collects error information at the Information level and higher (including maintenance information)
Collection levels for log information in trace files:
– Outputs no trace information – Outputs error information only
– Outputs trace information on program operation summaries – Outputs trace information on program operation details – Outputs all trace information
For details on how to set the collection level, see section 3.13.2.
2.11.3 Collecting Error Information Using the Utility for Collecting HDLM Error Information (DLMgetras)
HDLM has a utility for collecting HDLM error information (DLMgetras).
By executing this utility, you can simultaneously collect all the information required for analyzing errors: information such as error logs, integrated trace files, trace files, definition files, core files, and libraries. You can use the collected information when you contact your HDLM vendor or maintenance company (if there is a maintenance contract for HDLM).
For details on the DLMgetras utility, see section 7.2.
2.11.4 Utility for Collecting HDLM Installation Error Information (installgetras)
HDLM has a utility for collecting HDLM installation error information (installgetras).
By executing this utility, you can collect the logs required for analyzing errors that occurred during installation. You can use the collected information when you contact your HDLM vendor or maintenance company.
For details on the installgetras utility, see section 7.6.