Reading The System Messages; Reading A Ras System Message - Brocade Communications Systems SN3000B Reference

1

Reading the system messages

You must configure the syslog daemon to send the Audit events to a configured remote host using
the syslogdIpAdd command. For more information on configuring the syslog server, refer to
"Configuring a syslog server"

Reading the system messages

This section provides information about reading the RASLog and Audit messages.

Reading a RAS system message

This section provides information about reading system messages.
The following example shows the format of a RAS system error message.
<timestamp>, [<Event ID>], <Sequence Number>, <Flags>, <Severity>, <Switch name>,
<Event-specific information>
The following example shows a sample message from the error log.
2011/02/10-14:18:04, [SS-1000], 88, SLOT 6 | FFDC | CHASSIS, INFO, ESNSVT_DCX,
supportSave has uploaded support information to the host with IP address
168.159.16.128
2011/02/10-14:13:34, [SS-1001], 87, SLOT 6/1 | FFDC | CHASSIS, WARNING,
ESNSVT_DCX, supportSave's upload operation to host IP address aborted
2011/02/10-15:44:51, [SEC-1203], 89, SLOT 6 | FFDC | FID 128, INFO, ESNSVT_DCX,
Login information: Login successful via TELNET/SSH/RSH. IP Addr:168.159.16.128
NOTE
Any reference to slot 0 in a system message is a reference to the blade within the switch platform,
for example, Brocade DCX contains FC8-48 blade, FC8-32 blade, FC8-16 blade, and so on.
The fields in the error message are described in
TABLE 4
Variable name
Time Stamp
Event ID
Sequence Number
18
on page 5.
System message field description
Description
The system time (UTC) when the message was generated on the switch. The
RASLog subsystem supports an internationalized time stamp format based on
the "LOCAL" setting.
The message module and number. These values uniquely identify each
message in the Fabric OS and reference the cause and actions recommended
in this manual. Note that not all message numbers are used; there can be
gaps in the numeric message sequence.
The error message position in the log. When a new message is added to the
log, this number is incremented by 1.
The message sequence number starts at 1 after a firmwareDownload and will
increase up to a value of 2,147,483,647 (0x7ffffff).
The sequence number continues to increase after the message log wraps
around, i.e. the oldest message in the log is deleted when a new message is
added. The sequence number can be reset to 1 using the errClear command.
The sequence number is persistent across power cycles and switch reboots.
Table 4.
Fabric OS Message Reference
53-1002448-01