IBM 2109 - SAN Fibre Channel Switch Model S16, Service Manual

Page: 97 / 178

syslogd running on switch sw9 is sending log events to the UNIX machine called
example
. Figure 29 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 the
/var/adm/silkworm
file.
Message classification
syslogd messages are classified according to facility and priority (severity code).
This allows a system administrator to take different actions depending on the error.
The action taken, based on the message facility and priority, is defined in the syslog
configuration file. See “Switch configuration” for examples of configurations.
The switch uses the facility local7 for all error messages sent to the syslogd.
UNIX provides eight priorities, and the switch provides five severity codes (code
LOG_PANIC (0)
causes a restart and is not sent to syslogd). The mapping between
the switch severity codes and the UNIX syslogd priorities is shown in Table 22, in
order of decreasing priorities.
Table 22. syslogd message classifications
Switch UNIX
LOG_CRITICAL (1) alert
LOG_ERROR (2) err
LOG_WARNING (3) warning
LOG_INFO (4) info
LOG_DEBUG (5) debug
Switch configuration
Type the following command to start syslogd.
syslogdIp <IP address of the syslogd machine>
Entering the command with no parameter prints the IP address of the current target
syslogd machine. Entering an IP address of
0.0.0.0
disables the forwarding of error
messages to syslogd. Error messages are still logged internally to the switch, but
they are not forwarded to syslogd. Figure 30 on page 82 shows examples of
syslogd support.
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
Figure 29. Example of a no memory error generated by the shell
Chapter 7. Management tools
81
|
|
|
|
|
|
|
|
|
|
|
|
|