Users Guide

Table Of Contents
Broadcom DRVVM-LPe-UG124-100
28
Emulex Drivers for VMware ESXi User Guide
Chapter 4: Troubleshooting
Your system may operate in an unexpected manner in certain circumstances. This section explains many of these
circumstances and offers one or more workarounds for each situation.
4.1 Troubleshooting the FC Driver
This section provides troubleshooting information for the FC driver.
Tab le 7 identifies some of the common situations and their potential resolutions.
Table 7: Troubleshooting the FC Driver
Situation Resolution
The port link fails to come up. If an FC link fails to come up, verify that the adapter is connected to a supported device.
The supported 8GFC adapters are:
2GFC
4GFC
8GFC
The supported 16GFC adapters are:
4GFC
8GFC
16GFC
The supported 32GFC adapters are:
8GFC
16GFC
32GFC
The Emulex driver is not loaded and all
paths are down.
Use the lspci utility to determine whether the Emulex ports are being properly identified. If
not, determine if the driver ISO was correctly installed. You must have the correct driver for
the installed adapter because the device
PCI IDs are installed with the driver package.
Examine the /var/log/vmkernel.log file for lpfc log messages indicating an error. If you
specified driver logging (see Section 3.2, FC Driver Configuration), make sure you spelled
the driver parameters correctly. The ESXi module subsystem does not load the driver on
reboot if the parameters are not spelled correctly. In this case, contact Broadcom Technical
Support.
All paths are down.
Use the driver's KV pages to get critical information.
First check the link state. The KV command shown in the footnote shows the driver's current
link, and whether it has found a fabric and the link speed.
a
If the data shows Link Up Ready and Mode Online, check the discovered nodes. Fabric,
initiator, and target types show the SAN as it was presented and discovered by the driver.
Additionally, if you are experiencing periodic path outage, the command shown in the second
footnote in a script loop shows if the node status is changing or if the node is going offline.
b
If your target or initiator is not in the driver's discovered list, check your zone membership and
the state of all zone members.
Contact Broadcom Technical Support if you are unable to resolve missing zone members.
The FC driver fails to recognize an adapter
and logs unknown IOCB messages in the
system log during driver load. The adapter
is running outdated firmware.
Download and install the adapter firmware that complies with the minimum supported version
(or later) listed on the Broadcom website at www.broadcom.com.