Compaq AA-RHBYA-TE 135267-001, User Manual

Page: 77 / 256

Managing the Switch 3-41
Example:
syslogd running on Switch
sw9
is sending log events to the UNIX machine
called
example
. The following is an example of a
No memory
error
generated by the shell. This is a severity 1 (
LOG_CRITICAL
) error. syslogd is
configured to store the errors in:
/var/adm/silkworm
file.
example% egrep sw9 /var/adm/silkworm
Jul 11 16:48:25 sw9 1 0x103d8620 (tShell): Jul 11 16:48:19
Jul 11 16:48:25 sw9Error SYS-NOMEM, 1, No memory
Jul 11 16:48:25 sw9 Traceback:
Jul 11 16:48:25 sw9 _tl+0x40 (0x103a2030)
Jul 11 16:48:25 sw9 _0x95c (0x1017128c)
Jul 11 16:48:25 sw9 _0x694 (0x10172dc4)
Jul 11 16:48:25 sw9 _0xdc (0x1014c06c)
Jul 11 16:48:25 sw9 _sh0x964 (0x1003aea4)
Jul 11 16:48:25 sw9 _sh0x198 (0x1003a6d8)
Jul 11 16:48:25 sw9 _vxTa0x10 (0x10114d14)
Jul 11 16:48:25 sw9
Message Classification
syslogd messages are classified according to facility and priority (severity
code). Thus allowing a system administrator to take different actions
depending on the error. The action taken, based on the message’s facility and
priority, is defined in the syslog configuration file. Example configurations are
provided in a following section.
The Switch uses the facility
local7
for all error messages sent to the
syslogd.
UNIX provides eight priorities, whereas the Switch provides four severity
codes (code
LOG_PANIC (0)
causes a reboot and is not sent to the syslogd).
The mapping between the Switch’s severity codes and UNIX syslogd priorities
is provided in Table 3-9.
Table 3-9
syslog Message Classification
Switch UNIX
LOG_CRITICAL (1) alert
LOG_ERROR (2) err
LOG_WARNING (3) warning
LOG_DEBUG (4) debug