Clearing The Audit Message Log; Reading The System Messages; Reading A Ras System Message - Brocade Communications Systems StoreFabric SN6500B Reference

Clearing the Audit message log

To clear the Audit message log for a particular switch instance, perform the following steps.
1. Log in to the switch as admin.
2. Execute the auditDump -c command to clear all Audit messages from memory.

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
192.0.2.2.
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:192.0.2.2.
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
Fabric OS Message Reference
53-1002749-01
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.

Reading the system messages

Table 4.
1
23