Technical data

12 Network OS Message Reference
53-1002489-01
Reading the system messages
1
Audit event messages
Compared to RASLog error messages, messages flagged as AUDIT provide additional user and
system-related information of interest for post-event auditing and problem determination.
The following example shows the format of the Audit event message.
<Sequence Number> AUDIT, <Timestamp>, [<Event ID>], <Severity>, <Event Class>,
<User ID>/<Role>/<IP address>/<Interface>/<app name>, <Reserved field for future
expansion>, <Switch name>, <Event-specific information>
The following is a sample Audit event message.
0 AUDIT,2011/08/26-07:51:32 (GMT), [DCM-2001], INFO, DCMCFG,
root/none/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli start, Status: success,
Info: Successful login attempt through console from 127.0.0.1.
The fields in the Audit event message are described in Table 5.
Flags For most messages, this field contains a space character (null value) indicating that the
message is neither an FFDC or VCS message. Messages may contain the following values:
• FFDC–Indicates that additional first failure data capture information has also been
generated for this event.
• VCS–Indicates a VCS message generated by a node in the management cluster.
Severity The severity level of the notification:
• CRITICAL
• ERROR
• WARNING
• INFO
Switch name The defined switch name or the chassis name of the switch. This value is truncated if it
exceeds 16 characters in length.
Event-specific
information
A text string explaining the error encountered and provides the parameters supplied by the
software at runtime.
TABLE 5 Audit message field description
Variable name Description
Sequence Number The error message position in the log.
AUDIT Identifies the message as an Audit message.
Timestamp The system time (UTC) when the message was generated on the switch. The RASLog
subsystem supports an internationalized time stamp format base on the “LOCAL”
setting.
Event ID The Event ID is the message module and number. These values uniquely identify each
message in the Network 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.
Severity The severity level of the error:
• CRITICAL
• ERROR
• WARNING
• INFO
TABLE 4 System message field description (Continued)
Variable name Description