HP StorageWorks XP Command View Advanced Edition Software 6.4 Server Administrator Guide for Device Manager and Provisioning Manager (web) (T1780-96341, July 2010)

Setting up logs and alerts
102
Table 6-6 Log.facility values and the corresponding values in syslog.conf
Facility Corresponding value in syslog.conf
20
local4
21
local5
22
local6
23
local7
* Although you can specify this value, HP does not recommend that you specify it.
The table below shows the correspondence between the severity levels of audit events, the values
indicating severity that are specified in the syslog.conf file, and the types of event log data.
Table 6-7 Correspondence between the severity levels of audit events, the severity levels in
syslog.conf, and the types of event log data
Severity of audit events Severity in syslog.conf Type of event log data
0
emerg
Error
1
alert
2
crit
3
err
4
warning
Warning
5
notice
Information
6
info
7
debug
The following shows an example of the auditlog.conf file:
# Specify an integer for Facility. (specifiable range: 1-23)
Log.Facility 1
# Specify the event category.
# You can specify any of the following:
# StartStop, Failure, LinkStatus, ExternalService,
# Authentication, AccessControl, ContentAccess,
# ConfigurationAccess, Maintenance, or AnomalyEvent.
Log.Event.Category Authentication,ConfigurationAccess
# Specify an integer for Severity. (specifiable range: 0-7)
Log.Level 6
In the example above, the audit events related to Authentication or ConfigurationAccess
are output. In Windows, Log.Level 6 outputs audit log data corresponding to the Error, Warning,
and Information levels. In Linux, Log.Facility 1 outputs the audit log data to the syslog file
that is defined as the user facility in the syslog.conf file.
6-3 Settings required for centrally managing
storage subsystem alerts
In Device Manager, you can use web client to centrally manage alerts that were output on storage
subsystems. By viewing alerts, you can check the name of the storage subsystem where an error