Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Installation
- Chapter 3: Configuration
- 3.1 ESXi Command Line Tool Transition
- 3.2 FC Driver Configuration
- 3.2.1 Configuration Methods for FC Driver Parameters
- 3.2.2 Emulex ExpressLane Support
- 3.2.3 FC-SP-2 Authentication (DH-CHAP) Support
- 3.2.4 Trunking Support
- 3.2.5 Dynamically Adding LUNs
- 3.2.6 Dynamically Adding Targets
- 3.2.7 FC Driver Module Parameters
- 3.2.8 Creating an FC Remote Boot Disk
- 3.2.9 Managing Devices through the CIM Interface
- 3.2.10 Installing the Emulex CIM Provider
- 3.2.11 Creating, Deleting, and Displaying vPorts
- 3.2.12 Configuring VVols
- 3.2.13 Adjusting the LUN Queue Depth
- 3.3 Configuring NVMe over FC on a NetApp Target
- 3.4 Configuring NVMe over FC on an Initiator System
- Chapter 4: Troubleshooting the FC Driver
- Chapter 5: Troubleshooting the NVMe Driver
- Appendix A: esxcli Management Tool
- Appendix B: lpfc Driver BlockGuard Functionality
- Appendix C: Using the VMID Feature on a Brocade Switch
- Appendix D: Using the VMID Feature on a Cisco Switch
- Appendix E: NPIV Configuration
- Appendix F: License Notices
Broadcom DRVVM-UG128-100
45
Emulex Drivers for VMware ESXi User Guide
4.1 FC Driver Log Messages
Log messages have traditionally been organized into logical groups based on code functionality in the FC driver. With the
introduction of the latest Emulex adapters, that grouping is modified to account for additional behaviors. The traditional
grouping is maintained, but recently added messages are no longer grouped together.
The messages provided in this section are unmaskable error conditions. They are automatically added to the system console
log.
You can examine the /var/log/vmkernel.log file to view any of these messages. If you have concerns, the best policy
is to run a vm-support dump and contact VMware or Broadcom Technical Support.
Log messages are organized into logical groups based on code functionality within the driver. Each group consists of a block
of 100 log message numbers. Most groups require a single block of 100 message numbers; however, some groups (INIT,
FCP) require two blocks.
Table 8 lists the groups and defines the associated number ranges.
b. Data from KV command 2:
[root@chara:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhba11/Emulex -k node -g
Key 'node':
lpfc Node page:
WWNN WWPN ScsiID DID Type Status
10:00:00:05:33:a6:a8:bb 20:06:00:05:33:a6:a8:bb xfffffe Fabric Node ok
10:00:00:05:33:a6:a8:bb 21:fc:00:05:33:a6:a8:bb xfffffc Fabric Node ok
00:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 xfffffd Fabric Node logged out
20:00:00:00:c9:f3:f9:b6 10:00:00:00:c9:f3:f9:b6 x021600 Initiator Node ok
20:00:00:00:c9:f4:48:af 10:00:00:00:c9:f4:48:af x020700 Initiator Node ok
20:00:00:90:fa:02:19:16 10:00:00:90:fa:02:19:16 x021500 Initiator Node ok
20:00:00:90:fa:02:19:17 10:00:00:90:fa:02:19:17 x020e00 Initiator Node ok
20:00:00:90:fa:5d:2f:29 10:00:00:90:fa:5d:2f:29 x020902 Initiator Node ok
20:00:00:90:fa:5d:2f:31 10:00:00:90:fa:5d:2f:31 x020903 Initiator Node ok
20:00:00:90:fa:5d:92:2f 10:00:00:90:fa:5d:92:2f x02094a Initiator Node ok
20:00:00:11:0d:e0:54:00 20:00:00:11:0d:e0:54:00 0 x02090e Target Node ok
20:06:00:11:0d:19:9a:00 20:06:00:11:0d:19:9a:00 1 x021000 Target Node ok
20:07:00:11:0d:19:9b:00 20:07:00:11:0d:19:9b:00 2 x021100 Target Node ok
Table 8: Message Log Table
LOG Message Verbose Mask Definition Verbose Bit Verbose Description
LOG_ELS 0x00000001 Extended Link Service events
LOG_DISCOVERY 0x00000002 Link discovery events
LOG_MBOX 0x00000004 Mailbox events
LOG_INIT 0x00000008 Initialization events
LOG_LINK_EVENT 0x00000010 Link events
LOG_MGMT_ERROR 0x00000020 IODM management error logging
LOG_FCP 0x00000040 FCP traffic history
LOG_NODE 0x00000080 Node table events
LOG_BG 0x00000200 BlockGuard events
LOG_MEM_HEAP 0x00000400 Memory tracker heap logging
LOG_SLI 0x00000800 SLI events