Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Enabling or disabling verbose logging on QLogic and Emulex Host Bus Adapters (1005576)

Last Updated: 2/14/2020Categories: How toTotal Views: 32469Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

This article provides the commands to enable, disable, or decrease verbose or extended logging on the driver used to communicate with a QLogic or Emulex Host Bus Adapter (HBA).

Resolution

Determining the driver that your ESX host uses
Note: All commands are available through the vSphere Command-line Interface or VMware vSphere Management Assistant Guide, or from the ESX console / ESXi Direct Console User Interface (DCUI). For details on using the DCUI, see Tech Support Mode for Emergency Support (1003677).

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
In ESXi/ESX 3.5:

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

In ESXi/ESX 4.x/5.x:

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
To determine the options and modules that are in use, run the command:

# esxcfg-module -q | grep -E "^ql|^lpfc"

The output appears similar to:

lpfc820.o lpfc0_lun_queue_depth=2 lpfc1_lun_queue_depth=2
qla2xxx.o ql2xextended_error_logging=1

Enabling or disabling verbose logging

For the QLogic HBA

Note: Use the correct QLogic module name based on the result from the Determining the options and the modules in use section.

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:

Run the command:

esxcfg-module -s "ql2xextended_error_logging=1" qlnativefc

Or

esxcli system module parameters set -p "ql2xextended_error_logging=1" -m qlnativefc

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).

For Example : esxcfg-module -s debug=0xfffffff bnx2x

Storage Drivers:

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

esxcfg-module -i driver

For example: esxcfg-module -i bnx2x

To set parameter option run below command:

esxcfg-module -s

For Emulex

Emulex driver tuning is slightly more complicated as there are many different parameters that can be enabled to fine tune logging. VMware recommends that you refer to Emulex documentation for more information on these parameters.

This table contains a partial list of events which can be enabled for logging:

LOG_ELS

0x1

ELS events

LOG_DISCOVERY

0x2

Link discovery events

LOG_MBOX

0x4

Mailbox events

LOG_INIT

0x8

Initialization events

LOG_LINK_EVENT

0x10

Link events

LOG_FCP

0x40

FCP traffic history

LOG_NODE

0x80

Node table events

LOG_MISC

0x400

Miscellaneous events

LOG_SLI

0x800

SLI events

LOG_CHK_COND

0x1000

FCP Check condition flag

LOG_LIBDFC

0x2000

IOCTL events

LOG_ALL_MSG

0x7ffff

LOG all messages

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

Notes:

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

Related Information

Notes:

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.

Warning: VMware recommends that you reverse the configuration changes (to debug level 0) when troubleshooting has been completed. Verbose logging consumes logging partition space at an accelerated rate and may exhaust the partition of its free space. This prevents further logging for root-cause analysis of other issues, and may induce other ESX host operating system management problems.
QLotic および Emulex ホスト バス アダプタでの詳細なログを有効化または無効化する
在 QLogic 和 Emulex 主机总线适配器上启用或禁用详细日志记录

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant