Dell Emulex Family of Adapters - Manual (Page 1039)

Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev. A
4. Troubleshooting
Troubleshooting the FC/FCoE Driver
1039
ESXi 5.5 Message Log Example
The following is an example of a LOG message on ESXi 5.5 systems:
2013-09-10T16:50:13.137Z cpu7:33329)WARNING: lpfc:
lpfc_mbx_cmpl_read_topology:3154: 1:1305 Link Down Event x12
received Data: x12 x20 x110 x0
In the above LOG message:

lpfc - driver binary

lpfc_mbx_cmpl_read_topology - function generating the log

1: identifies Emulex HBA1.

1305 identifies the LOG message number.
Note: If the word 'Data:' is present in a LOG message, any information to the right of
'Data:' is intended for Emulex technical support/engineering use only.
Note: Unless otherwise noted in the ACTION: attribute, report these errors to Emulex
technical support. Emulex requests that when reporting occurrences of these
error messages, you provide a tarball of all vmkernel files in /var/log.
ESXi 5.0 and 5.1 Message Log Example
The following is an example of a LOG message on ESXi 5.0 and 5.1 systems:
Jul 2 04:23:34 daffy kernel: lpfc 0000:03:06.0: 0:1305 Link Down
Event x2f2 received Data: x2f2 x20 x110
In the above LOG message:

lpfc 0000:03:06.0: identifies the PCI location of the particular LPFC HW port.

0: identifies Emulex HBA0.

1305 identifies the LOG message number.
Note: If the word 'Data:' is present in a LOG message, any information to the right of
'Data:' is intended for Emulex technical support/engineering use only.
Note: Unless otherwise noted in the ACTION: attribute, report these errors to Emulex
technical support. Emulex requests that when reporting occurrences of these
error messages, you provide a tarball of all vmkernel files in /var/log.