Determining the driver that your ESX host uses

• To list all modules currently loaded, run the command:
  
  # esxcfg-module --list
  
  The output appears similar to:
  
  Device Driver Modules
Module Enabled Loaded
vmklinux true true
[...]
vmfs2 true true
iscsi_mod true true
qla2300_707_vmw true false
  
  Note: QLogic driver names begin with ql and Emulex begins with lpfc.
  
  
• To list all available QLogic modules, run the command:
  
  # ls /usr/lib/vmware/vmkmod | grep ql
  
  
• To list all available Emulex modules, run the command:
  
  # ls /usr/lib/vmware/vmkmod | grep lpfc

Module names

• The QLogic modules are:
  
  
  • For FC: qla2300_707_vmw.o
  • For iSCSI: qla4010.o
  • For iSCSI: qla4022.o
  
  
• The Emulex module is:
  
  
  • lpfc_740.o

• The QLogic modules are:
  
  
  • For FC: qla2xxx.o or qlnativefc (5.5)
  • For iSCSI: qla4xxx.o
  
  
• The Emulex module is:
  
  
  • lpfc820.o

Determining the options and the modules in use

Enabling or disabling verbose logging

• qlge
  
  To enable verbose logging:
  
  esxcfg-module -s debug=Debug_Level driver
  
  Note: Debug level values can range from 0 (none) to 16 (all).
  
  
• qla2xxx or qla2300_707_vmw
  
  To enable verbose logging:
  
  esxcfg-module -s ql2xextended_error_logging=1 driver
  
  To disable verbose logging:
  
  esxcfg-module -s ql2xextended_error_logging=0 driver
  
  
• qla4xxx, qla4010, or qla4022
  
  To enable verbose logging:
  
  esxcfg-module -s extended_error_logging=1 driver
  
  To disable verbose logging:
  
  esxcfg-module -s extended_error_logging=0 driver
  
  Note: Forqla4xxx, the ql4xextended_error_logging parameter may be used instead ofextended_error_logging.
  
  To check which parameter should be used, run this command:
  
  vmkload_mod -s qla4xxx | grep extended
  
  Notes:
  
  
  • To make this parameter change active, you must reboot the host.
  • Choosing an incorrect module may result in unexpected behavior or failure.
  • To enable options immediately and/or to make them persistent, see Configuring advanced driver module parameters in ESX/ESXi (1017588).
  
  
• qlnativefc
  
  To enable extended logging:
  
  /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhbaX/qlogic -s scsi-qlaenable-log -k ADAPTER
  
  To disable extended logging:
  
  /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhbaX/qlogic -s scsi-qladisable-log -k ADAPTER
  
  To enable at boot time:
  
  
  1. Run the command:
     
     esxcfg-module -s "ql2xextended_error_logging=1" qlnativefc
     
     Or
     
     esxcli system module parameters set -p "ql2xextended_error_logging=1" -m qlnativefc
     
     
  2. Reboot the host.
     
     Extended logging is now enabled at boot, and begins immediately after boot.

• bnx2x
  
  To enable verbose logging:
  
  esxcfg-module -s debug=Debug_Level driver
  
  Note: Debug level values can range from 0 (none) to 16 (all).

• bnx2fc (fcoe)
  
  To enable verbose logging:
  
  esxcfg-module -s debug=Debug_Level driver
  
  Note: Debug level values can range from 0 (none) to 16 (all).
  
  For example: esxcfg-module -s bnx2fc_debug_level=0xfffffff bnx2fc
  
  
  
• bnx2i (iscsi)
  
  To enable verbose logging:
  
  esxcfg-module -s debug=Debug_Level driver
  
  Note: Debug level values can range from 0 (none) to 16 (all).
  
  For example: esxcfg-module -s bnx2i_debug_level=0xfffffff bnx2i
  
  

To see what parameter is needed for debug: run below command

For more information on the complete list of parameters, see Emulex Drivers for VMware ESX/ESXi User Manual.

Note: The preceding link was correct as of October 24, 2014. If you find the link is broken, provide feedback and a VMware employee will update the link.

• To enable all logging, run the command:
  
  esxcfg-module -s lpfc_log_verbose=0x7ffff driver_name
  
  Caution: Setting the maximum verbosity level above generates significant logging output.
  
  
• To enable a slightly limited verbose logging level, run the command:
  
  esxcfg-module -s lpfc_log_verbose=0xc3 driver_name
  
  
• To disable verbose logging, run the command:
  
  esxcfg-module -s lpfc_log_verbose=0 driver_name
  
  
• To enable logging in ESXi 5.x, run the esxcli system module parameters set command. For example, for the Emulex light pulse fibre channel card, run the command:
  
  esxcli system module parameters set -p lpfc0_log_verbose=1 -m driver name
  

• You must reboot the ESX host for the changes to take effect.
• Choosing an incorrect module may result in unexpected behavior or failure.
• To enable options immediately and/or to make them persistent, see Configuring advanced driver module parameters in ESX/ESXi (1017588).
• You can make the non-boot persistent change without rebooting ESXi 5.x host on the Emulex driver.
• For information on real-time configuration/parameter changes that can be made to a running QLogic FC HBA driver, see Real-time configuration/parameter changes that can be made to the running QLogic or Emulex FC HBA driver (1031199).
• To enable and modify logging on an Emulex driver, run this command:
  
  /bin/echo 'lpfc_log_verbose 0x4048c3' > /proc/scsi/lpfc820/X
  
  
• To stop logging on an Emulex driver, run this command:
  
  /bin/echo 'lpfc_log_verbose 0x0' > /proc/scsi/lpfc820/X

• These changes take effect after rebooting the server. Evacuate the server of virtual machines using vMotion (or power them down), or select the VMware ESX host in your VMware vSphere or VMware Infrastructure Client inventory and reboot it. Alternatively, reboot it through the terminal by running the reboot command.
• The system logs show the additional logging after the server is rebooted.