System error message logging – Dell POWEREDGE M1000E User Manual

Page 26

Advertising
background image

4

Fabric OS Message Reference

53-1002749-01

Overview of system messages

1

System error message logging

The RASLog service generates and stores messages related to abnormal or erroneous system
behavior. It includes the following features:

All RASLog error messages are saved to nonvolatile storage by default.

The system error message log can save a maximum of 1024 messages in random access
memory (RAM).

The system message log is implemented as a circular buffer. When more than the maximum
entries are added to the log file, old entries are overwritten by new entries.

Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence
number will continue to increase beyond the storage limit of 1024 messages. The sequence
number can be reset to 1 using the errClear command. The sequence number is persistent
across power cycles and switch reboots.

Trace dump, FFDC, and core dump files can be uploaded to the FTP server using the
supportSave command.

Brocade recommends that you configure the syslogd facility as a management tool for error
logs. This is particularly important for dual-domain switches because the syslogd facility saves
messages from two logical switches as a single file and in sequential order. For more
information, refer to

“System logging daemon”

on page 5.

RASLog messages are streamed to the console, and are forwarded to the configured syslog
servers and to the SNMP management station through the SNMP traps (in SNMPv1 and
SNMPv3) or informs (in SNMPv3). Use the snmpConfig command to configure the SNMPv1
and SNMPv3 hosts and their configurations.

Audit messages are streamed to the switch console, and are forwarded to the configured
syslog servers. The Audit log messages are not forwarded to an SNMP management station.

TABLE 2

Severity levels of a message

Severity level

Description

1 = CRITICAL

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.

2 = ERROR

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.

3 = WARNING

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.

4 = INFO

Info-level messages report the current non-error status of the system components: for
example, detecting online and offline status of a fabric port.

Advertising