Users Guide

Broadcom DRVLin-LPe-UG124-100
40
Emulex Drivers for Linux User Guide
5.3 Log Messages
5.3.1 FC Driver Log Messages
The following section describes retrieving and interpreting FC driver log messages.
5.3.1.1 Retrieving FC Driver Log Messages
LPFC error log messages are logged in the /var/log/messages file.
An example of an LPFC message follows:
Jul 2 04:23:34 daffy kernel: lpfc 0000:03:06.0: 0:1305 Link Down Event x2f2 received Data: x2f2 x20
x110
In this example:
 lpfc 0000:03:06.0 – Identifies the PCI location of the particular LPFC hardware port.
 0: – Indicates Emulex adapter 0.
 1305 – Indicates a log message number of 1305.
NOTE:
 If Data: is present in a log message, any information following Data: is intended only for Broadcom
®
Technical Support or Engineering use.
 If an error message instructs you to perform a firmware update, ensure that the driver is installed first. For more
information on installing the driver, see Chapter 2, Installing and Uninstalling.
5.3.1.2 LPFC Error Log Messages and Their Descriptions
The following table lists the LPFC error log messages and their descriptions.
Table 7: LPFC Error Log Messages and Their Descriptions
0111: Dropping received ELS cmd
The driver decided to drop an ELS Response ring entry.
Data: (1) ulpStatus (2) ulpWord[4] (3) ulpTimeout
Severity: Error
Log: Always
Action: This error could indicate a software driver or firmware issue. If this issue persists, report these errors to Broadcom Technical
Support.
0113: An FLOGI ELS command <elsCmd> was received from DID <did> in Loop Mode
While in Loop Mode, an unknown or unsupported ELS command was received.
Data: None
Severity: Error
Log: Always
Action: Check device DID.
0115: Unknown ELS command <elsCmd> received from NPORT <did>
Received an unsupported ELS command from a remote N_Port.
Data: None
Severity: Error
Log: Always
Action: Check the remote N_Port for a potential issue.