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

Page: 96 / 178

does not have to be running UNIX to forward messages to syslogd, but it must
follow the basic syslog message format standard.
An example entry in a syslogd log file is:
Jul 18 12:48:00 sendmail [9558]: NOQUEUE: SYSERR (uucp):
/etc/mail/sendmail.cf: line 0: cannot open: No such file or directory
The first two items are the event date and time (as known by the machine where
syslogd is running) and the machine name that issued the error. This is the local
machine, if the message is generated by a task running on the same machine as
syslogd, or a remote machine, if the message is received on UDP port 514. The
first two items are always present. All other entries are message specific.
Note: The log file can be located on a different machine and can be locally
mounted. A local error can be an error that occurs where syslogd is running,
not on the machine where the error log physically resides.
syslogd applications for NT and Win95 are available at no charge on several FTP
servers on the Internet.
syslogd support
Switch firmware maintains an internal log of all error messages. The log is
implemented as a circular buffer, with a storage capability of 64 errors. After 64
errors are logged, the next error message overwrites the messages at the
beginning of the buffer.
If configured, the switch sends internal error messages to syslogd by sending the
UDP packet to port 514 on the syslogd machine. This allows the storage of switch
errors on a syslogd capable machine and avoids the limitations of the circular
buffer.
syslogd provides system error support using a single log file and can notify a
system administrator in real time of error events.
Error message format
Each error message logged sends the following information:
v
Error number (1 for the first error after startup, increments by one with each new
error).
v
The error message, exactly as it is stored in the error log and printed using the
errShow command.
The error message includes the switch that reported the error with the event
information:
v
ID of the task that generated the error.
v
Name of the task that generated the error.
v
Date and time when the error occurred, as seen by the switch. This can be
different from the first item in the log file, which is the time as seen by the
syslogd machine. These two time values are different if the clocks in the switch
and in the syslogd machine are not in sync.
v
The error identifier consisting of a module name, a dash and an error name.
v
The error severity.
v
Optional informational part.
v
Optional stack trace.
80
IBM SAN Fibre Channel Switch: 2109 Model S16 Installation and Service Guide
|
|
|
|
|
|
|
|
|
|
|
|