Brocade Adapters Troubleshooting Guide 6953-1002145-01Logs 3NOTEComplete content for adapter driver event messages is included in Appendix A, “Adapter BIOS andEvent Message Reference”.LogsEvent and error messages that occur during adapter, driver, and HCM operation are important toolsfor isolating and resolving problems. These messages provide descriptions of an event or problem,severity, time and date of the event, and in some cases, cause and recommended actions.Messages are captured in logs available through HCM, BCU commands, and through host systemcommands. Monitoring events and errors in these logs allows early fault detection and isolation ona specific adapter.Host system logsBrocade adapter event messages are captured in host system log files. All messages related to theBrocade adapter are identified in these logs by BFA (Brocade fabric adapter), BNA (Brocadenetwork adapter), and BFAL (Brocade fabric adapter library]. Table 8 describes the logs for eachsupported operating system where adapter event messages display and how to view these logs.Syslog supportYou can configure the HCM Agent to forward events to a maximum of three system log destinationsusing the Syslog option on the HCM Configure menu. These events will display in the operatingsystem logs for systems such as Solaris and Linux. For procedures to configure syslog destinations,refer to the Brocade Adapters Administrator’s Guide.TABLE 8 System event LogsOperating System Log Name Location Viewing Message LogSolaris 11. Brocade 804 and 1007 adapters are not supported on Solaris systems.Syslog /var/adm/messages dmesg commandWindows Event Log Not applicable • System category in EventViewer (eventvwr.exe)• bcu winlog command22. Supported on Windows systems only.Linux Messages Log /var/log/message dmesg commandVMware33. For ESX Server platforms. For Guest system, refer to information in Windows or Linux.Messages Log /var/log/message* ,/var/log/vmkernel*,/var/log/vmkwarning*,/proc/vmware/logdmesg command
