Technical data

Network OS Message Reference 3
53-1002489-01
Overview of system messages
1
The three event classes described in Table 1 can be audited.
You can enable event auditing by configuring the syslog daemon to send the events to a configured
remote host using the logging syslog-server command. You can set up filters to screen out
particular classes of events using the logging auditlog class command (the classes include
security, configuration, and firmware). All the Audit classes are enabled by default. The defined set
of Audit messages are sent to the configured remote host in the Audit message format, so that they
are easily distinguishable from other syslog events that may occur in the network. For details on
how to configure event auditing, refer to “Configuring event auditing” on page 10.
FFDC messages
First Failure Data Capture (FFDC) is used to capture failure-specific data when a problem or failure
is first noted before the switch reboots, or trace and log buffer get wrapped. This critical debug
information is saved in nonvolatile storage and can be retrieved by executing the copy support
command. The data are used for debugging or analyzing the problem.
FFDC is enabled by default. Execute the support command to enable or disable FFDC. If FFDC is
disabled, the FFDC daemon does not capture any data, even when a message with FFDC attributes
is logged.
The following is an example of the FFDC message.
2011/08/26-12:39:02, [HAM-1007], 2, FFDC, CRITICAL, VDX6720-24, Need to reboot the
system for recovery, reason: raslog-test-string0123456-raslog.
Message severity levels
There are four levels of severity for messages, ranging from CRITICAL to INFO. In general, the
definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all
cases, you must look at each specific error message description thoroughly before taking action.
System messages have the severity levels as listed in Table 2.
TABLE 1 Event classes of the Audit messages
Event class Operand Description
SECURITY SECURITY You can audit any user-initiated security event for all management
interfaces. For events that have an impact on the entire network, an
audit is generated only for the switch from which the event was
initiated.
DCMCFG CONFIGURATION You can audit all the configuration changes in the Network OS.
FIRMWARE FIRMWARE You can audit the events occurring during the firmware download
process.
TABLE 2 Severity levels of the system messages
Severity level Description
CRITICAL Critical-level messages indicate that the software has detected serious problems that cause a
partial or complete failure of a subsystem if not corrected immediately; for example, a power
supply failure or rise in temperature must receive immediate attention.
ERROR Error-level messages represent an error condition that does not affect overall system
functionality significantly. For example, error-level messages may indicate time outs on
certain operations, failures of certain operations after retries, invalid parameters, or failure to
perform a requested operation.