HP StorageWorks 2/16V Brocade Fabric OS Message Reference Guide (53-1000242-01 - Page 57

Overview of System Messages 1 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 SilkWorm model, and, optionally, setting the facility level. For the SilkWorm 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 SilkWorm 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 SilkWorm 24000 and 48000, security violations such as telnet, HTTP, and serial connection violations 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 both system messages 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-todevice, 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. Refer to the Fabric OS Administrator's Guide for information on interpreting results of the portLogDump command. Port log functionality is completely separate from the system message log. Port logs are typically used to troubleshoot device connections. Fabric OS Message Reference 1-3 Publication Number: 53-1000242-01