Message Severity Levels - Brocade Communications Systems SN3000B Reference

Event auditing is a configurable feature, set to off by default. You must enable event auditing using
the auditCfg
configured for logging audit messages. You can set up filters to screen out particular classes of
events using the auditCfg command. The defined set of Audit messages is 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
"Displaying, clearing, and configuring Audit messages"
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. All subsequent
iterations of the same error are ignored. This critical debug information is saved in nonvolatile
storage and can be retrieved using the supportSave command. The FFDC data is used for
debugging or analyzing the problem. FFDC is intended for use by Brocade technical support.
FFDC is enabled by default. Execute the supportFfdc command to enable or disable FFDC. If FFDC
is disabled, the FFDC daemon does not capture any data, even when a message with an FFDC
attribute is logged.
The following is an example of the FFDC message.
2000/12/17-08:30:13, [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.

Message severity levels

Table 2
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 can have the following severity levels.
TABLE 2
Severity level
1 = CRITICAL
2 = ERROR
3 = WARNING
4 = INFO
Fabric OS Message Reference
53-1002448-01
enable command to send the events to a configured remote host. Syslogd must be
--
shows the four levels of severity for messages, ranging from CRITICAL (1) to INFO (4). In
Severity levels of a message
Description
Critical-level messages indicate that the software has detected serious problems that
will 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-level messages represent an error condition that does not impact overall system
functionality significantly. For example, error-level messages might indicate time-outs
on certain operations, failures of certain operations after retries, invalid parameters, or
failure to perform a requested operation.
Warning-level messages highlight a current operating condition that should be
checked or it may lead to a failure in the future. For example, a power supply failure in
a redundant system relays a warning that the system is no longer operating in
redundant mode unless the failed power supply is replaced or fixed.
Info-level messages report the current non-error status of the system components: for
example, detecting online and offline status of a fabric port.
Overview of system messages
on page 16.
1
3