HP XP Racks - Manual (Page 153)

This example shows how to specify the audit log facility:
# /usr/DynamicLinkManager/bin/dlnkmgr set -audfac local0
Checking the Updated Settings
This chapter describes steps involved in how to check the updated settings by
using the dlnkmgr command's set operation after settings have been
changed.
When you change some settings, you can display information about all of
HDLM function settings. The following is an example of executing the
command:
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc
HDLM Version : x.x.x-xx
Service Pack Version :
Load Balance : on(extended lio)
Support Cluster :
Elog Level : 2
Elog File Size(KB) : 1000
Number Of Elog Files : 5
Trace Level : 1
Trace File Size(KB) : 2000
Number Of Trace Files : 10
Path Health Checking : on(10)
Auto Failback : on(10)
Intermittent Error Monitor : on(2/20)
Dynamic I/O Path Control : off(10)
KAPL01001-I The HDLM command completed normally. Operation name =
view, completion time = yyyy/mm/dd hh:mm:ss
#
After you have set up the collection of audit log data, use the following
command to make sure that the setting has been specified correctly:
# /usr/DynamicLinkManager/bin/dlnkmgr view -sys -audlog
Audit Log : on(6)
Audit Log Category : all
Audit Log Facility : local0
KAPL01001-I The HDLM command completed normally. Operation name =
view, completion time = yyyy/mm/dd hh:mm:ss
#
Setting up Integrated Traces
When HDLM is used, the dlnkmgr command logs are output to the integrated
trace information files of Hitachi Network Objectplaza Trace Library
(HNTRLib2) (/var/opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates a
file number)).
If a lot of integrated trace information is output, the older information might
end up getting deleted in a very short amount of time. Also, if a large amount
of integrated trace information is suddenly all output at the same time, any
integrated trace information that is overflowing the buffer might not be saved
Creating an HDLM Environment
3-87
Hitachi Dynamic Link Manager (for AIX) User Guide