Fabric OS Message Reference v6.4.0 (53-1001767-01, June 2010)
Table Of Contents
- Contents
- About This Document
- Introduction To System Messages
- RASLog Messages
- AG System Messages
- AN System Messages
- AUTH System Messages
- ANV System Messages
- BKSW System Messages
- BL System Messages
- BLL System Messages
- BLS System Messages
- BM System Messages
- C2 System Messages
- CDR System Messages
- CEE CONFIG System Messages
- CER System Messages
- CHASSIS System Messages
- CNM System Messages
- CONF System Messages
- CTAP System Messages
- CVLC System Messages
- CVLM System Messages
- DAUTH System Messages
- EM System Messages
- ESS System Messages
- ESWCH System Messages
- EVMD System Messages
- FABR System Messages
- FABS System Messages
- FBC System Messages
- FCMC System Messages
- FCIP System Messages
- FCOE System Messages
- FCPD System Messages
- FCPH System Messages
- FCR System Messages
- FICON System Messages
- FICU System Messages
- FKLB System Messages
- FLOD System Messages
- FSPF System Messages
- FSS System Messages
- FSSM System Messages
- FW System Messages
- HAM System Messages
- HAMK System Messages
- HIL System Messages
- HLO System Messages
- HMON System Messages
- HSL System Messages
- HTTP System Messages
- IBD System Messages
- IBPD System Messages
- ICPD System Messages
- IPAD System Messages
- IPS System Messages
- ISCS System Messages
- ISNS System Messages
- KAC System Messages
- KSWD System Messages
- KTRC System Messages
- L2SYS System Messages
- LACP System Messages
- LANCE System Messages
- LFM System Messages
- LOG System Messages
- LSDB System Messages
- MFIC System Messages
- MPTH System Messages
- MQ System Messages
- MS System Messages
- MSTP System Messages
- NBFS System Messages
- NS System Messages
- NSM System Messages
- ONM System Messages
- PDM System Messages
- PDTR System Messages
- PLAT System Messages
- PMGR System Messages
- PORT System Messages
- PS System Messages
- PSWP System Messages
- RAS System Messages
- RCS System Messages
- RKD System Messages
- RMOND System Messages
- RPCD System Messages
- RTWR System Messages
- SAS System Messages
- SCN System Messages
- SEC System Messages
- SFLOW System Messages
- SNMP System Messages
- SPC System Messages
- SPM System Messages
- SS System Messages
- SSM System Messages
- SULB System Messages
- SWCH System Messages
- SYSC System Messages
- SYSM System Messages
- TAPE System Messages
- TRCE System Messages
- TRCK System Messages
- TS System Messages
- UCST System Messages
- UPTH System Messages
- WEBD System Messages
- XTUN System Messages
- ZEUS System Messages
- ZOLB System Messages
- ZONE System Messages
- Audit Log Messages
- AUDIT AG System Messages
- AUDIT AN System Messages
- AUDIT AUTH System Messages
- AUDIT BLS System Messages
- AUDIT CNM System Messages
- AUDIT CONF System Messages
- AUDIT CVLM System Messages
- AUDIT FCIP System Messages
- AUDIT FICU System Messages
- AUDIT FW System Messages
- AUDIT HTTP System Messages
- AUDIT IPAD System Messages
- AUDIT PORT System Messages
- AUDIT SEC System Messages
- AUDIT SNMP System Messages
- AUDIT SPM System Messages
- AUDIT SULB System Messages
- AUDIT SWCH System Messages
- AUDIT UCST System Messages
- AUDIT ZONE System Messages
Fabric OS Message Reference 3
53-1001767-01
Overview of System Messages
1
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 might occur in the network. For
details on how to configure event auditing, see “Viewing and Configuring System Message Logs” on
page 4.
System Logging Daemon (syslogd)
The system logging daemon (syslogd) is a process on UNIX, Linux, and some Windows systems that
reads and logs messages as specified by the system administrator.
Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error
messages to log files on a remote host system. The host system can be running UNIX, Linux, or any
other operating system that supports the standard syslogd functionality. Configuring for syslogd
involves configuring the host, enabling syslogd on the Brocade model, and, optionally, setting the
facility level.
For the Brocade DCX, 24000 and 48000, each CP has a unique error log, depending on which CP
was active when that message was reported. To fully understand message logging on the Brocade
24000 and 48000 you should enable the system logging daemon, because the logs on the host
computer are maintained in a single merged file for both CPs and are in sequential order.
Otherwise, you must examine the error logs in both CPs, particularly for events such as
firmwareDownload or haFailover, for which the active CP changes.
For the Brocade DCX, 24000 and 48000, any security violations that occur through Telnet, HTTP, or
serial connections are not propagated between CPs. Security violations on the active CP are not
propagated to the standby CP counters in the event of a failover, nor do security violations on the
standby CP get propagated to the active CP counters.
For information on configuring syslogd functionality, refer to the Fabric OS Administrator’s Guide.
System Console
The system console displays messages only through the serial port. If you log in to a switch through
the Ethernet port or modem port, you will not receive system console messages.
The system console displays system messages, Audit messages (if enabled) and panic dump
messages. These messages are mirrored to the system console; they are always saved in one of
the system logs.
You can filter messages that appear on the system console by severity using the errFilterSet
command. All messages are still sent to the system message log and syslog (if enabled).
Port Logs
The Fabric OS maintains an internal log of all port activity. Each switch or logical switch maintains a
log file for each port. Port logs are circular buffers that can save up to 8000 entries per logical
switch. When the log is full, the newest log entries overwrite the oldest log entries. Port logs capture
switch-to-device, device-to-switch, switch-to-switch, some device A-to-device B, and control
information. Port logs are not persistent and are lost over power cycles and reboots.
Run the portLogShow command to display the port logs for a particular port.
Run the portLogEventShow command to display the specific events reported for each port.