Emulex Driver for VMware ESX 4.x. Version vmw User Manual. One Network. One Company.

Transcription

1 Emulex Driver for VMware ESX 4.x Version vmw User Manual P A Rev. A One Network. One Company. Connect with Emulex.

2 Copyright Emulex. All rights reserved worldwide. No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex. Information furnished by Emulex is believed to be accurate and reliable. However, no responsibility is assumed by Emulex for its use; or for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent, copyright or related rights of Emulex. Emulex, the Emulex logo, AutoPilot Installer, AutoPilot Manager, BlockGuard, Connectivity Continuum, Convergenomics, Emulex Connect, Emulex Secure, EZPilot, FibreSpy, HBAnyware, InSpeed, LightPulse, MultiPulse, OneCommand, OneConnect, One Network. One Company., SBOD, SLI, and VEngine are trademarks of Emulex. All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations. Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex may make improvements and changes to the product described in this manual at any time and without any notice. Emulex assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties that may result. Periodic changes are made to information contained herein; although these changes will be incorporated into new editions of this manual, Emulex disclaims any undertaking to give notice of such changes. Emulex, 3333 Susan Street Costa Mesa, CA Driver for VMware ESX 4.x - User Manual Page ii

3 Installation...1 Driver Information... 1 Supported Features... 1 New Features in this Release... 1 Prerequisites... 2 Compatibility... 2 Things to Know Before You Download... 2 Known Issues... 2 Installing the Driver... 3 Uninstalling the Driver... 3 Installing the Utilities... 3 Uninstalling the Utilities... 3 Configuration...4 Introduction... 4 Configuration Methods Using Native ESX Tools... 4 Permanent Configuration Methods... 4 Dynamically Add LUNs and Targets... 6 Driver Configuration Parameters... 6 Creating a Fibre Channel Remote Boot Disk... 8 Working with Virtual Ports (Vports)... 8 Creating, Deleting and Displaying vports... 8 Troubleshooting...9 Introduction... 9 Unusual Situations and their Resolutions... 9 General Situations... 9 lpfc Log Messages Introduction Message Log Example ELS Events ( ) Link Discovery Events ( ) Mailbox Events ( ) Temperature Events (0340 and 0347) IOCB Events ( ) Initialization Events ( ) FARP Events ( ) FCP Traffic History ( ) Node Table Events ( ) Security Events ( ) Miscellaneous and FCoE Events ( ) Link Events ( ) IOCTL Events ( ) VPort Events ( ) IOCTL Events ( ) Driver for VMware ESX 4.x - User Manual Page iii

4 Installation Driver Information Supported Features SNIA-CTP compliant SMI-S 1.1 Provider Topology support: Fibre Channel Arbitrated Loop (FC-AL), point-to-point, fabric with autotopology negotiation Supports 1, 2, 4, 8 and 10 Gb/s capable adapters with auto-rate negotiation. (1 Gb/s is not supported on 8 Gb/s adapters.) Protocols: SCSI-FCP, FCP-2, FC initiator mode and Fibre Channel over Ethernet (FCoE) Tested up to sixteen adapter ports Dynamic parameter setting using Emulex s HBAnyware GUI-based configuration utility version 4.0 as part of a master kit: enabling GUI-based driver configuration including out-of-band (TCP/ IP) remote SAN management capability, diagnostics (loopback and diagnostics dump), logical unit number (LUN) masking and virtual port support. See the HBAnyware 4.0 Utility User Manual for a complete list of supported features. Support for Common HBA API Batch firmware download capability PCI hot plug support (Vendor specific) Vital Product Data (VPD) support VMware Tools link on the VMware portion of the Emulex Web site (visit the link to see the available tools) Supports N_Port ID Virtualization (NPIV) virtual ports New Features in this Release This is Emulex's initial release of vmw for ESX 4x. Driver for VMware ESX 4.x - Installation Section Page 1

5 Prerequisites The following table lists the support relationship between VMware ESX releases and Emulex drivers. Refer to VMware s online Compatibility Guide for more detailed information. Table 1: Emulex Driver Support in ESX Releases VMware ESX Release Emulex Driver Version ESX lpfc_7.3.2_vmw3 (4 Gb/s) provided with ESX Patch 4 ESX ESX ESX ESX ESX ESX 3.5 Update 1 ESX 3.5 Update 2 Asynchronous CNA Release for ESX 3.5 Update 2 ESX 3.5 Update 4 ESX 4.0 ESX 4.0 Update 1 lpfc_7.3.2_vmw4 (2 and 4 Gb/s) lpfc_7.1.14_vmw1 (2 Gb/s) lpfc_7.3.2_vmw1 (4 Gb/s) lpfc_7.3.2_vmw2 (2 and 4 Gb/s) lpfc_7.3.2_vmw4 (2 and 4 Gb/s) lpfc_ (2 and 4 Gb/s) lpfc_ (2 and 4 Gb/s) lpfc_ (2, 4, and 8 Gb/s) lpfc_ ( FCoE) lpfc_ (2, 4, 8 Gb/s and FCoE) lpfc_ _vmw (2, 4, 8 Gb/s and FCoE) lpfc_ _vmw (2, 4, 8 Gb/s and FCoE) Compatibility For a list of adapters that are compatible with this driver, see the driver's Downloads page on the Emulex Web site. For compatible firmware versions, see the Downloads page for the specific adapter. Things to Know Before You Download There are no issues at this time. Known Issues Refer to the README file located in /usr/sbin/hbanyware/readme.txt for issues related to the HBAnyware and hbacmd configuration utilities. At times, the switch name server maintains the device name after the vport sends a LOGO. This could be misleading for administrators looking at the name server database. Some switches require an explicit DA_ID ELS command to clean up the name server database; other switches do not. Emulex provides a driver attribute called enable_da_id to address this issue if necessary. Boot from SAN support on the LPe12000 series adapters requires the Emulex 2.02a2 BIOS. For operations such as firmware download, Emulex recommends the server be brought into ESX maintenance mode prior to flashing the firmware. Driver for VMware ESX 4.x - Installation Section Page 2

6 Installing the Driver The Emulex vmw driver is available through VMware's Support site. Refer to VMware's Support Web site for further details. Uninstalling the Driver See VMware's patch download page for instructions. Installing the Utilities Follow these instructions to install the Emulex HBAnyware configuration utility. To install the HBAnyware Agent: 1. Log in as root. 2. Copy the elxvmwarecorekit-<kit version>.rpm file to a directory on the install machine. 3. CD to the directory to which you copied the rpm file. 4. Install the rpm. Type: rpm -U elxvmwarecorekit-esx40-<kit version>.x86_64.rpm For example: rpm -U elxvmwarecorekit-esx40-4.0a44-1.x86_64.rpm The rpm contents and README are installed in /usr/sbin/hbanyware. The hbacmd utility is also located in this directory. Uninstalling the Utilities Follow these instructions to uninstall the Emulex configuration utilities. To uninstall the HBAnyware Agent: 1. Log in as root. 2. Type "rpm -q elxvmwarecorekit" to verify that this kit is installed. This command should list "elxvmwarecorekit-<kit version>" for the current release. 3. Type: rpm -e elxvmwarecorekit-esx40-<kit version> Driver for VMware ESX 4.x - Installation Section Page 3

7 Configuration Introduction You can configure the driver parameters using native ESX tools or Emulex s HBAnyware and lputil configuration utilities. This document describes how to configure parameters using native ESX tools. For a more comprehensive description of ESX tools, refer to the vi3_server_config.pdf documentation. If you have further questions, contact a VMware technical support representative. Refer to the Emulex HBAnyware version 4.0 User Manual and the lputil User Manual for more information about those utilities. Configuration Methods Using Native ESX Tools There are four ways to configure the driver parameters: Permanently (global) Permanently (per adapter) Temporary (global) Temporary (per adapter) Note: The HBAnyware utility version 4.0 also supports all four ways to configure driver parameters. This is the preferred method of setting configuration parameters. Refer to the HBAnyware 4.0 User Manual for more information. Permanent Configuration Methods Permanent configuration requires that the new values be saved in the ESX environment. These changes are considered permanent because they stay in effect across system reboots. To make changes that impact all adapters in the system (global changes), follow these steps. See Driver Configuration Parameters on page 6 for parameter names and values. Parameter values are hexadecimal and decimal. 1. From the Console Operating System (COS) terminal window type: esxcfg-module -s param=value param2=value... <driver_name> The <driver_name> is obtained from the vmkload_mod -l call. Look for the lpfc prefix. 2. Rebuild the initial ram disk before rebooting: esxcfg-boot -b 3. Reboot the server. Type: reboot Note: VMware does not officially support unloading the driver via vmkload_mod -u. If you must unload the driver, contact VMware technical support. Note: NPIV port creation and deletion are performed by VMware's Infrastructure Client (VIC). Refer to the VIC documentation for more information. Driver for VMware ESX 4.x - Configuration Section Page 4

8 Example of Permanent Global Configuration The following example sets lun_queue_depth to 20 (default is 30) for all Emulex adapters in your system. 1. Locate the parameter in Table Set the permanent value. Type: esxcfg-module -s lpfc_lun_queue_depth=20 <driver_name> 3. Rebuild the ESX bootstrap settings. Type: esxcfg-boot -b 4. Reboot the server. Type: reboot The new setting is used when the driver reloads. To verify the setting type: esxcfg-module -g lpfc820 Example of Permanent Per Adapter Configuration The following example sets lun_queue_depth to 20 (default is 30) for adapter #1. 1. Set the adapter-specific value. Type: esxcfg-module -s lpfc1_lun_queue_depth=20 <driver_name> 2. Rebuild the ESX bootstrap settings. Type: esxcfg-boot -b 3. Reboot the server. Type: reboot The new setting is used when the driver reloads. To verify the setting type: esxcfg-module -g lpfc820 The following example sets lun_queue_depth to 20 (default is 30) for adapter #1 and lun_queue_depth to 10 (default is 30) for adapter #2. 1. Set the adapter-specific value. Type: esxcfg-module -s lpfc1_lun_queue_depth=20 lpfc2_lun_queue_depth=10 <driver_name> Note: Type command all on one line without a carriage return. 2. Rebuild the ESX bootstrap settings. Type: esxcfg-boot -b 3. Reboot the server. Type: reboot The new settings are used when the driver reloads. To verify the settings type: esxcfg-module -g lpfc820 Driver for VMware ESX 4.x - Configuration Section Page 5

9 Dynamically Add LUNs and Targets For instructions on dynamically adding LUNs and targets, refer to VMware s SAN Config documentation, Using Rescan section. Driver Configuration Parameters All adapter-specific parameters have an lpfcx_ prefix (where X is the driver instance number); For example, setting lpfc0_lun_queue_depth=20 makes 20 the default number of maximum commands which can be sent to a single logical unit (disk) for lpfc instance 0. Dynamic parameters do not require a system reboot for changes to take effect. Table 2: Driver Configuration Parameters Variable Default Min Max Dynamic Comments lpfc_hba_queue_depth 0xffff 1 0xffff Yes Maximum number of FCP commands that can queue to an Emulex adapter. The value cannot exceed what the adapter supports. lpfc_initiator_login 0 0=Off 1=On Yes Enables logins to other virtual initiators. lpfc_ack0 0 0=Off 1=On No Use ACK0 for class 2. lpfc_automap 1 0=Off 1=On No Automatically assign SCSI IDs to FCP targets detected. lpfc_check_cond_err 0 0=Off 1=On Yes Treat certain FCP check conditions as FCP RSP errors. lpfc_cr_count No Determines the values for I/O coalescing for cr_delay (msec) or cr_count outstanding commands. lpfc_cr_delay No Determines the values for I/O coalescing for cr_delay (msec) or cr_count outstanding commands. lpfc_delay_rsp_err 0 0=Off 1=On Yes Treat FCP RSP errors like nodevice-delay. lpfc_discovery_threads No Specifies the maximum number of ELS commands that can be outstanding for a discovery. lpfc_enable_da_id No Deregister Emulex objects registered with the NameServer. lpfc_fcp_class Yes FC class for FCP data transmission. lpfc_fdmi_on No False (0) if disabled. (1) or (2) if enabled depending on type of support needed. Driver for VMware ESX 4.x - Configuration Section Page 6

10 Table 2: Driver Configuration Parameters (Continued) Variable Default Min Max Dynamic Comments lpfc_link_speed 0 0=auto select 1=1 Gb/s 2=2 Gb/s 4=4 Gb/s 8=8 Gb/s No Sets link speed. Note: Not supported for FCoE. lpfc_log_verbose 0x0 0x0 0xffffffff Yes (bit mask) Extra activity logging. lpfc_lun_queue_depth Yes Default max commands sent to a single logical unit (disk). lpfc_max_luns Yes Specifies the maximum number of LUNs per target. A value of 20 means LUNs from 0 to 19 are valid. lpfc_max_vpi 0xffff 0 0xffff No NPIV: Maximum number of VPIs available per physical port. lpfc_max_scsicmpl_time No Limits SCSI command completion time to control I/O queue depth. The default 0 means SCSI layer control maintains control. Value is in milliseconds. lpfc_pci_max_read 0 0 = driver default 512 = 512 bytes 1024 = 1024 bytes 2048 = 2048 bytes 4096 = 4096 bytes No The maximum number of bytes transferred per pci DMA read. The default value 0 means the driver will automatically determine the correct value. lpfc_peer_port_login Yes NPIV: Allows peer vports to log into each other. lpfc_scan_down 1 0=Off 1=On Yes Select method for scanning ALPA to assign a SCSI ID. lpfc_topology 0 0x0=loop then P2P 0x2=P2P only 0x4=loop only 0x6=P2P then loop No FC link topology (defaults to loop, if it fails attempts point-to-point mode). Note: Not supported for FCoE. lpfc_use_adisc 0 0=Off 1=On Yes Send ADISC instead of PLOGI for device discovery or RSCN. Driver for VMware ESX 4.x - Configuration Section Page 7

11 Creating a Fibre Channel Remote Boot Disk For instructions on creating a Fibre Channel remote boot disk, refer to VMware s SAN Configuration Documentation, Chapter 6, Using Boot from SAN with ESX Server Systems. Working with Virtual Ports (Vports) Creating, Deleting and Displaying vports The Emulex driver for VMware supports NPIV by default. The only management API for creating and deleting a vport comes from ESX and the creation of an NPIV-enable virtual machine. Virtual ports in the driver discover the fabric just like the physical port and are subject to the same SAN delays. As the number of vports increase, the amount of time it takes to complete remote port discovery increases as each vport executes synchronous discovery and the vports are created sequentially. If your NPIVenabled virtual machines are configured to power-on automatically, you could experience longer delays than normal when completing the power on sequence. This is normal for NPIV virtual machines. Note: Ensure you are using the latest recommended firmware for vport functionality. Check the Emulex Web site for the latest firmware. Note: Loop devices and NPIV are not supported on the same port simultaneously. If you are running a loop topology and you create a vport, the vport's link state will be offline. VMware ESX only supports fabric mode. Note: You can only create virtual ports on 4 Gb/s and 8 Gb/s adapters. You cannot create virtual ports on 1 Gb/s and 2 Gb/s adapters. Note: The HBAnyware utility sees all vports created by the driver, but the utility has readonly access to the vports. Driver for VMware ESX 4.x - Configuration Section Page 8

12 Troubleshooting Introduction There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation. Unusual Situations and their Resolutions General Situations Table 3: General Driver Situations Situation FC link fails to come up. Resolution If an FC link fails to come up, verify that an 8 Gb/s adapter is not attempting to connect to a 1 Gb/s device. Only 2, 4 and 8 Gb/s devices are supported on 8 Gb/sec adapters. For LP21000 adapters, ensure the adapter is not in maintenance mode and that it is not running the manufacturing firmware. If a SAN configuration has 256 targets mapped by the lpfc driver, any additional added targets do not get a target ID mapping by the driver and cause target discovery to fail. Removing targets or reinitializing the link does not solve the problem. An lspci will show recent Emulex adapters as "unknown". This is because of the delay of getting new product ID's into the VMware ESX development cycle. lpfc driver fails to recognize an adapter and logs "unknown IOCB" messages in the system log during driver load. The adapter is running outdated firmware. System panics when booted with a failed adapter installed. Unload and reload the driver to reset available target IDs. Ensure that the SAN configuration is correct prior to rebooting the driver. This will clear the driver s consistent binding table and free target IDs for new target nodes. None at this time. Upgrade adapter firmware to minimum supported revision listed in installation guide (or newer). Remove the failed adapter and reboot. Driver for VMware ESX 4.x - Troubleshooting Section Page 9

13 lpfc Log Messages Introduction Log messages are organized into logical groups based on code functionality within the Fibre Channel 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. The groups and the associated number ranges are defined in the Message Log table below. Table 4: Message Log Table LOG Message Verbose Mask Definition From To Verbose Bit Verbose Description LOG_ELS x1 ELS events LOG_DISCOVERY x2 Link discovery events LOG_SLI x800 SLI events LOG_MBOX x4 Mailbox events LOG_TEMP x100 Temperature sensor events LOG_INIT x8 Initialization events Reserved LOG_IP x20 IPFC events LOG_FCP x40 FCP traffic history Reserved LOG_NODE x80 Node table events Reserved Reserved LOG_MISC LOG_FCoE x400 Miscellaneous and FCoE events LOG_LINK_EVENT x10 Link events Reserved Reserved LOG_LIBDFC x2000 IOCTL events Driver for VMware ESX 4.x - Troubleshooting Section Page 10

14 Table 4: Message Log Table (Continued) LOG Message Verbose Mask Definition From To Verbose Bit Verbose Description LOG_VPORT x4000 NPIV events LOG_EVENT X10000 CT, TEMP. DUMP events LOG_ALL_MSG xffffffff Log all messages Message Log Example The following is an example of a LOG message: 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 identifies the pci location of the particular lpfc hw port. 0: identifies Emulex HBA 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. ELS Events ( ) elx_mes0100: FLOGI failure DESCRIPTION: An ELS FLOGI command that was sent to the fabric failed. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout LOG: LOG_ELS verbose elx_mes0101: FLOGI completes successfully DESCRIPTION: An ELS FLOGI command that was sent to the fabric succeeded. DATA: (1) ulpword[4] (2) e_d_tov (3) r_a_tov (4) edtovresolution LOG: LOG_ELS verbose elx_mes0102: PLOGI completes to NPort <nlp_did> DESCRIPTION: The HBA performed a PLOGI into a remote NPort. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout (4)disc (5) num_disc_nodes LOG: LOG_ELS verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 11

15 elx_mes0103: PRLI completes to NPort <nlp_did> DESCRIPTION: The HBA performed a PRLI into a remote NPort. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout (4) num_disc_nodes LOG: LOG_ELS verbose elx_mes0104: ADISC completes to NPort <nlp_did> DESCRIPTION: The HBA performed a ADISC into a remote NPort. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout (4) disc (5) num_disc_nodes LOG: LOG_ELS verbose elx_mes0105: LOGO completes to NPort <nlp_did> DESCRIPTION: The HBA performed a LOGO to a remote NPort. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout (4) num_disc_nodes LOG: LOG_ELS verbose elx_mes0106: ELS cmd tag <ulpiotag> completes DESCRIPTION: The specific ELS command was completed by the firmware. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout LOG: LOG_ELS verbose elx_mes0107: Retry ELS command <elscmd> to remote NPORT <did> DESCRIPTION: The driver is retrying the specific ELS command. DATA: (1) retry (2) delay LOG: LOG_ELS verbose elx_mes0108: No retry ELS command <elscmd> to remote NPORT <did> DESCRIPTION: The driver decided not to retry the specific ELS command that failed. DATA: (1) retry LOG: LOG_ELS verbose elx_mes0109: ACC to LOGO completes to NPort <nlp_did> DESCRIPTION: The driver received a LOGO from a remote NPort and successfully issued an ACC response. DATA: (1) nlp_flag (2) nlp_state (3) nlp_rpi LOG: LOG_ELS verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 12

16 elx_mes0110: ELS response tag <ulpiotag> completes DESCRIPTION: The specific ELS response was completed by the firmware. DATA: (1) ulpstatus (2) ulpword[4] (3) nlp_did (4) nlp_flag (5) nlp_state (6) nlp_rpi LOG: LOG_ELS verbose elx_mes0111: Dropping received ELS cmd DESCRIPTION: The driver decided to drop an ELS Response ring entry. DATA: (1) ulpstatus (2) ulpword[4] (3) ulptimeout ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0112: ELS command <elscmd> received from NPORT <did> DESCRIPTION: Received the specific ELS command from a remote NPort. DATA: (1) hba_state LOG: LOG_ELS verbose elx_mes0113: An FLOGI ELS command <elscmd> was received from DID <did> in Loop Mode DESCRIPTION: While in Loop Mode an unknown or unsupported ELS command was received. ACTION: Check device DID. elx_mes0115: Unknown ELS command <elscmd> received from NPORT <did> DESCRIPTION: Received an unsupported ELS command from a remote NPORT. ACTION: Check remote NPORT for potential problem. elx_mes0116: Xmit ELS command <elscmd> to remote NPORT <did> DESCRIPTION: Xmit ELS command to remote NPORT. DATA: (1) icmd->ulpiotag (2) hba_state LOG: LOG_ELS verbose elx_mes0117: Xmit ELS response <elscmd> to remote NPORT <did> DESCRIPTION: Xmit ELS response to remote NPORT. DATA: (1) icmd->ulpiotag (2) size LOG: LOG_ELS verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 13

17 elx_mes0118: Xmit ELS RPS ACC response tag <ulpiotag> DESCRIPTION: An RPS ACC response for the specified IO tag has been sent. DATA:(1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose elx_mes0120: Xmit ELS RPL ACC response tag <ulpiotag> DESCRIPTION: An RPL ACC response for the specified IO tag has been sent. DATA:(1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose elx_mes0125: FDISC Failed (x%x). Fabric out of resources DESCRIPTION: The fabric rejected an FDISC because the switch can not support any more Virtual ports. DATA: lsrjterror ACTION: Reconfigure the switch to support more NPIV logins. If problem persists, contact Technical Support. elx_mes0126: FDISC failed <error> reason <error> DESCRIPTION: The vport's fdisc failed. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0127: ELS timeout DESCRIPTION: An ELS IOCB command was posted to a ring and did not complete within ULP timeout seconds. DATA: (1) elscmd (2) remote_id (3) ulpcommand (4) ulpiotag ACTION: If no ELS command is going through the adapter, reboot the system; If problem persists, contact Technical Support. elx_mes Xmit ELS ACC response tag <ulpiotag> DESCRIPTION: An ELS accept response for the specified IO tag has been sent. DATA: (1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 14

18 elx_mes Xmit ELS RJT <rejecterror> response tag <ulpiotag> DESCRIPTION: An ELS reject response with the specified error for the specified IO tag has been sent. DATA: (1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose elx_mes Xmit ADISC ACC response tag <ulpiotag> DESCRIPTION: An ADISC ACC response for the specified IO tag has been sent. DATA: (1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose elx_mes Xmit PRLI ACC response tag <ulpiotag> DESCRIPTION: A PRLI ACC response for the specified IO tag has been sent. DATA: (1) ulpcontext (2) nlp_did (3) nlp_flag (4) nlp_state (5) nlp_rpi LOG: LOG_ELS verbose elx_mes Xmit RNID ACC response tag <ulpiotag> DESCRIPTION: A RNID ACC response for the specified IO tag has been sent. DATA: (1) ulpcontext LOG: LOG_ELS verbose elx_mes0134: PLOGI: cannot issue reg_login DESCRIPTION: The REG_LOGIN following a PLOGI failed. DATA: (1) node DID (2) node state (3) node flags (4) node rpi ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0135: PLOGI: cannot format reg_login DESCRIPTION: The REG_LOGIN format process failed. DATA: (1) node DID (2) node state (3) node flags (4) node rpi ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. Driver for VMware ESX 4.x - Troubleshooting Section Page 15

19 elx_mes0136: PLOGI completes to NPORT <DID> with no NDLP DESCRIPTION: A PLOGI completed without a driver NDLP node. DATA: (1) remote DID (2) IO status (3) IO word4 (4) IoTag ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0137: No Retry ELS command <elscmd> to remote NPORT <did>: Out of Resources: Error <error> DESCRIPTION: The driver is not retrying an ELS command due to an error. DATA: (1) cmd (2) did (3) IO status (4) IO word4 ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0138: ELS rsp: Cannot issue reg_login for <did> DESCRIPTION: The driver cannot issue the reg_login for a remote node DATA: (1) remote DID (2) node flags (3) node state (4) node rpi ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0139: Ignoring ELS cmd tag <IoTag> completion DESCRIPTION: The driver is ignoring an ELS completion during driver/vport shutdown. DATA: (1) nlp_flag (2) nlp_state (3) nlp_rpi LOG: LOG_ELS verbose Link Discovery Events ( ) elx_mes0200: CONFIG_LINK bad hba state <hba_state> DESCRIPTION: A CONFIG_LINK mbox command completed and the driver was not in the right state. ACTION: Software driver error. If this problem persists, report these errors to Technical Support. elx_mes0201: Abort outstanding I/O on Nport <DID> DESCRIPTION: The driver is aborting all outstanding IO on the ELS ring. : LOG: LOG_DISCOVERY verbose ACTION: No action needed, informational Driver for VMware ESX 4.x - Troubleshooting Section Page 16

20 elx_mes0202: Start Discovery hba state <hba_state> DESCRIPTION: Device discovery / rediscovery after FLOGI, FAN or RSCN has started. DATA: (1) fc_flag (2) fc_plogi_cnt (3) fc_adisc_cnt LOG: LOG_DISCOVERY verbose elx_mes0203: Devloss timeout on WWPN <address> NPort <nlp_did> DESCRIPTION: A remote NPort that was discovered by the driver disappeared for more than lpfc_devloss_tmo seconds. DATA: (1) nlp_flag (2) nlp_state (3) nlp_rpi ACTION: If the device generating this message is not a target to which the HBA is connected, this error will not affect the data integrity of the I/O between the HBA and the attached storage and can be ignored. elx_mes0204:devloss timeout on WWPN <address> NPort <nlp_did> DESCRIPTION: A remote NPort that was discovered by the driver disappeared for more than lpfc_devloss_tmo seconds. DATA: (1) nlp_flag (2) nlp_state (3) nlp_rpi al LOG: LOG_DISCOVERY verbose ACTION: If the device generating this message is not a target to which the HBA is connected, this error will not affect the data integrity of the I/O between the HBA and the attached storage and can be ignored. elx_mes0205: Abort outstanding I/O on NPort <Fabric_DID> DESCRIPTION: All outstanding I/Os are cleaned up on the specified remote NPort. DATA: (1) nlp_flag (2) nlp_state (3) nlp_rpi LOG: LOG_DISCOVERY verbose elx_mes0206: Device discovery completion error DESCRIPTION: This indicates that an incorrectable error was encountered during device (re)discovery after a link up. Fibre Channel devices will not be accessible if this message is displayed. ACTION: Reboot the system. if problems persist, report these errors to Technical Support. Run with verbose mode on for more details. elx_mes0207: Device <DID> (<WWN>) sent invalid service parameters. Ignoring device. DESCRIPTION: Invalid service parameters were received from DID. Ignoring this remote port. DATA: DID, WWN ACTION: Verify the remote port's configuration. if problems persist, report these errors to Technical Support. Run with verbose mode on for more details. Driver for VMware ESX 4.x - Troubleshooting Section Page 17

21 elx_mes0208: Skip <Did> NameServer Rsp DESCRIPTION: The driver received a NameServer response. DATA: (1) size (2) fc_flag (3) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0209: CT request completes <ulpstatus> <ulpstatus> <CmdRsp> <CmdRsp> DESCRIPTION: A RFT request that was sent to the fabric completed. DATA: (1) latt (2) ulpstatus (3) cmdrsp (4) context (5) tag LOG: LOG_DISCOVERY verbose elx_mes0210: Continue discovery with <num_disc_nodes> ADISCs to go DESCRIPTION: A device discovery is in progress. DATA: (1) fc_adisc_cnt (2) fc_flag (3) phba->hba_state LOG: LOG_DISCOVERY verbose elx_mes0211: DSM in event <evt> on NPort <nlp_did> in state <cur_state> DESCRIPTION: The driver Discovery State Machine is processing an event. DATA: (1) nlp_flag LOG: LOG_DISCOVERY verbose elx_mes0212: DSM out state <rc> on NPort <nlp_did> DESCRIPTION: The driver Discovery State Machine completed processing an event. DATA: (1) nlp_flag LOG: LOG_DISCOVERY verbose elx_mes213: DSM out state <state> on Nport free DESCRIPTION: The discovery state machine is exiting from an unknown node. LOG: LOG_DISCOVERY verbose elx_mes0214: RSCN received DESCRIPTION: An RSCN ELS command was received from a fabric. DATA: (1) fc_flag (2) payload_len (3) *lp (4) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 18

22 elx_mes0215: RSCN processed DESCRIPTION: An RSCN ELS command was received from a fabric and processed. DATA: (1) fc_flag (2) cnt (3) fc_rscn_id_cnt (4) hba_state LOG: LOG_DISCOVERY verbose elx_mes0218: FDMI Request DESCRIPTION: The driver is sending an FDMI request to the fabric. DATA: (1) fc_flag (2) hba_state (3) cmdcode LOG: LOG_DISCOVERY verbose elx_mes0219: Ignore RSCN DESCRIPTION: The driver received an RSCN payload ID that matched the HBA. DATA: (1) vport flags (2) payload len (3) first did (4) RSCN ID cnt LOG: LOG_DISCOVERY verbose elx_mes0220: FDMI rsp failed DESCRIPTION: An error response was received to FDMI request. DATA:(1) SWAP_DATA16(fdmi_cmd) LOG: LOG_DISCOVERY verbose ACTION: The fabric does not support FDMI, check fabric configuration. elx_mes0221: FAN timeout DESCRIPTION: A link up event was received without the login bit set, so the driver waits E_D_TOV for the Fabric to send a FAN. If no FAN if received, a FLOGI will be sent after the timeout. LOG: LOG_DISCOVERY verbose ACTION: None required. The driver recovers from this condition by issuing a FLOGI to the fabric. elx_mes0222: Initial FLOG/FDISKI timeout DESCRIPTION: The driver sent the initial FLOGI or FDISK to the fabric and never got a response back. ACTION: Check fabric configuration. The driver recovers from this and continues with device discovery. elx_mes0223: Timeout while waiting for NameServer login DESCRIPTION: Our login request to the NameServer was not acknowledged within R_A_TOV. ACTION: Check the fabric configuration. The driver recovers and continues with device discovery. Driver for VMware ESX 4.x - Troubleshooting Section Page 19

23 elx_mes0224: NameServer Query timeout DESCRIPTION: Node authentication timeout, node Discovery timeout. A NameServer Query to the Fabric or discovery of reported remote NPorts is not acknowledged within R_A_TOV. DATA: (1) fc_ns_retry (2) fc_max_ns_retry ACTION: Check Fabric configuration. The driver recovers and continues with device discovery. elx_mes0225: Device Discovery completes DESCRIPTION: This indicates successful completion of device (re)discovery after a link up. LOG: LOG_DISCOVERY verbose elx_mes0226: Device discovery completion error DESCRIPTION: This indicates that an incorrectable error was encountered during device (re)discovery after a link up. Fibre Channel devices will not be accessible if this message is displayed. ACTION: Reboot the system. if problems persist, report these errors to Technical Support. Run with verbose mode on for more details. elx_mes0227: Node Authentication timeout DESCRIPTION: The driver has lost track of what NPORTs are being authenticated. ACTION: None required. The driver should recover from this event. elx_mes0228: CLEAR LA timeout DESCRIPTION: The driver issued a CLEAR_LA that never completed. ACTION: None required. The driver should recover from this event. elx_mes0229: FDMI cmd <cmd> failed, latt <state> ulpstatsu <status> rid <rid> DESCRIPTION: An FDMI request completed, but there was an error. DATA: (1) fdmi cmd (2) latt (3) IO status (4) IO word4 LOG: LOG_DISCOVERY verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 20

24 elx_mes0230: Unexpected timeout, hba link state <state> DESCRIPTION: The hba link down timer expired ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0231: RSCN timeout DESCRIPTION: The driver has lost track of what NPORTs have RSCNs pending. DATA: (1) fc_ns_retry (2) lpfc_max_ns_retry ACTION: None required. The driver should recover from this event. elx_mes0232: Continue discovery with <num_disc_nodes> PLOGIs to go DESCRIPTION: Device discovery is in progress. DATA: (1) fc_plogi_cnt (2) fc_flag (3) phba->hba_state LOG: LOG_DISCOVERY verbose elx_mes0233: Nodelist not empty DESCRIPTION: The driver is waiting for the nodelist to empty during cleanup ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0234: ReDiscovery RSCN DESCRIPTION: The number / type of RSCNs has forced the driver to go to the nameserver and rediscover all NPORTs. DATA: (1) fc_rscn_id_cnt (2) fc_flag (3) hba_state LOG: LOG_DISCOVERY verbose elx_mes0235: Deferred RSCN DESCRIPTION: The driver has received multiple RSCNs and has deferred the processing of the most recent RSCN. DATA: (1) fc_rscn_id_cnt (2) fc_flag (3) hba_state LOG: LOG_DISCOVERY verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 21

25 elx_mes0236: NameServer req DESCRIPTION: The driver is issuing a NameServer request to the fabric. DATA: (1) cmdcode (2) fc_flag (3) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0237: Pending Link Event during Discovery: State <hba_state> DESCRIPTION: Received link event during discovery. Causes discovery restart. LOG: LOG_DISCOVERY verbose ACTION: None required unless problem persists. If persistent check cabling. elx_mes0238: Process <Did> NameServer Rsp DESCRIPTION: The driver received a NameServer response. DATA: (1) nlp_flag (2) fc_flag (3) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0239: Skip <did> Nameserver Rsp Data DESCRIPTION: The driver is ignoring an RSCN entry DATA: (1) vc_flag (2) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0240: NameServer Rsp Error DESCRIPTION: The driver received a NameServer response containing a status error. DATA: (1) CommandResponse.bits.CmdRsp (2) ReasonCode (3) Explanation (4) fc_flag LOG: LOG_DISCOVERY verbose ACTION: Check the fabric configuration. The driver recovers and continues with device discovery. elx_mes0241: NameServer rsp error DESCRIPTION: The driver received a NameServer response containing a status error. DATA: (1) CommandResponse.bits.CmdRsp (2) ReasonCode (3) Explanation (4) fc_flag LOG: LOG_DISCOVERY verbose ACTION: Check the fabric configuration. The driver recovers and continues with device discovery. elx_mes0242: Process <did> GFF NameServer Rsp Data DESCRIPTION: The driver is processing a DID GFF response. DATA: (1) nlp_flag (2) fc_flag (3) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 22

26 elx_mes0243: Skip <did> GFF_ID NameServer Rsp Data DESCRIPTION: The driver is skipping a DID GFF ID Nameserver response entry. DATA: (1) vc_flag (2) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0244: Issue FDMI request failed DESCRIPTION: Cannot issue an FDMI request to the HBA. DATA: (1) cmdcode LOG: LOG_Discovery verbose elx_mes0245: Skip <did> GFT_ID NameServer Rsp Data DESCRIPTION: The driver is skipping a DID GFF ID Nameserver response entry. DATA: (1) vc_flag (2) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0246: RegLogin failed DESCRIPTION: The firmware returned a failure for the specified RegLogin. DATA: (1) Did (2) mbxstatus (3) hbastate ACTION: This message indicates that the firmware could not perform a RegLogin for the specified Did. There may be a limitation on how many nodes the HBA can see. elx_mes0247: Start Discovery Timer state <hba_state> DESCRIPTION: Start the device discovery / RSCN rescue timer. DATA: (1) tmo (2) fc_disctmo (3) fc_plogi_cnt (4) fc_adisc_cnt LOG: LOG_DISCOVERY verbose elx_mes0248: Cancel Discovery Timer state <hba_state> DESCRIPTION: Cancel the device discovery / RSCN rescue timer. DATA: (1) fc_flag (2) fc_plogi_cnt (3) fc_adisc_cnt LOG: LOG_DISCOVERY verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 23

27 elx_mes0249: Cannot issue Register Fabric login, Err <error> DESCRIPTION: The driver cannot register the new fabric login with the firmware. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support elx_mes0250: Retrying NS cmd <cmd> DESCRIPTION: The driver is retrying an ELS command to the NameServer. LOG: LOG_DISCOVERY verbose elx_mes0252: Cannot issue NameServer login DESCRIPTION: The driver cannot issue a PLOGI to the Nameserver. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes Illegal State Transition: node <nlp_did> event <evt>, state <nlp_state> DESCRIPTION: An unexpected response was received from the specified node. DATA: (1) nlp_rpi (2) nlp_flag ACTION: Check connection to fabric and/or remove device. If problem persists, report the issue to Technical Support. elx_mes0254: Register VPI: no memory DESCRIPTION: The driver failed to allocate memory for a REG_VPI mailbox command. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0255: Issue FDISC, no IOCB. DESCRIPTION: The driver tried to issue an FDISC, but no IOCBs were available. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. Driver for VMware ESX 4.x - Troubleshooting Section Page 24

28 elx_mes0256: Issue FDISC, cannot send IOCB DESCRIPTION: The driver tried to send an FDISC, but the issue_iocb failed. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0257: GID_FT Query error: <status> <retries> DESCRIPTION: The GID_FT request failed with status <status> retry count <retries> ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0258: Register Fabric login error <status> DESCRIPTION: The mailbox command to register the fabric login failed. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0259: No NPIV Fabric support DESCRIPTION: The FLOGI response indicates no NPIV support in the fabric. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0260: Register NameServer error: <status> DESCRIPTION: The driver failed to register the Nameserver login with the firmware <status>. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support elx_mes0261: Cannot Register NameServer login DESCRIPTION: The driver cannot register a Nameserver login with the firmware. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support Driver for VMware ESX 4.x - Troubleshooting Section Page 25

29 elx_mes0262: No NPIV Fabric support DESCRIPTION: A vport detected no NPIV support and did not send an FDISC. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0263: Discovery Mailbox error: state <state> sparam <buffer> cfglink <buffer> DESCRIPTION: The driver processed a link up and failed to set the state. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0264: No NPIV fabric support DESCRIPTION: The driver could not reenable a vport - no NPIV fabric support. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0265: FAN Received. DESCRIPTION: The driver received a FAN request and is processing it. LOG: LOG_DISCOVERY verbose elx_mes0266: Issue NameServer Req <cmd> err <rc> DESCRIPTION: The driver tried to issue a NameServer command and failed. DATA: (1) fc_flag (2) fc_rscn_id_cnt ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0267: NameServer GFF Rsp <rsp> Error <status ulpword4> DESCRIPTION: The driver detect a GFF_ID Rsp failure. DATA: (1) fc_flag (2) fc_rscn_id_cnt ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. Driver for VMware ESX 4.x - Troubleshooting Section Page 26

30 elx_mes0268: NS cmd <cmd> Error <status ulpword4> DESCRIPTION: The driver detect a Nameserver request failure. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0269: No NameServer Entries DESCRIPTION: The GID_FT response had no entries in it. DATA: (1) CmdRsp (2) ReasonCode (3) Explanation (4) fc_flag LOG: LOG_DISCOVERY verbose elx_mes0270: Skip <did> GFF NameServer Rsp DESCRIPTION: The driver is skipping a DID in the GFF_ID because it's an initiator. DATA: (1) fbits (2) fc_rscn_id_cnt LOG: LOG_DISCOVERY verbose elx_mes0271: Illegal State Transition: Node <did> event <evt> state <state> DESCRIPTION: The driver received an event on a node that was illegal for its current state. DATA: (1) node rpi (2) node flag ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0272: Illegal PLOGI State Transition: Node <did> event <evt> state <state> DESCRIPTION: The driver received an event on a node in state PLOGI that was illegal. DATA: (1) node rpi (2) node flag ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0273: Unexpected discovery timeout DESCRIPTION: The driver detected an unrecognized discovery timeout event, vport state <state>. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. Driver for VMware ESX 4.x - Troubleshooting Section Page 27

31 elx_mes0274: lpfc_nlp_put: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected a put on a node that is transitioning to unused. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0275: lpfc_nlp_put: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected a put on a node that is currently inactive. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0276: lpfc_nlp_get: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected a get on a node that is currently inactive. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0277: lpfc_enable_node: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected an enable request on a node in the free state. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0278: lpfc_enable_node: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected an enable request on an active node. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0279: lpfc_nlp_release: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver is releasing an ndlp and all resources. LOG: LOG_NODE verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 28

32 elx_mes0280: lpfc_cleanup_node: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver detected a cleanup request on a free node. LOG: LOG_NODE verbose ACTION: This error could indicate a software driver. If problems persist, report these errors to Technical Support. elx_mes0281: lpfc_cleanup_node: ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver is disabling a node. LOG: LOG_NODE verbose elx_mes0282: did <did> ndlp <ndlp> usgmap <nlp_usg_map> refcnt <refcount> DESCRIPTION: The driver found this node pending while cleaning up a vport. ACTION: This error could indicate a software driver or firmware problem. If problems persist, report these errors to Technical Support. elx_mes0283: Devloss timeout Skipped on WWPN <WWPN> Nport <did> Time <elapsed time> DESCRIPTION: The driver is ignoring a second devloss timeout callback from the transport. LOG: LOG_DISCOVERY verbose elx_mes0284: Devloss timeout Skipped on WWPN <WWPN> Nport <did> Time <elapsed time> DESCRIPTION: The driver is ignoring a devloss timeout callback on a mapped node. LOG: LOG_DISCOVERY verbose Mailbox Events ( ) elx_mes0300: ATT: Cannot issue READ_LA DESCRIPTION: The driver detected a get on a node that is currently inactive.the driver failed to issue a READ_LA mailbox command on a LATT event. DATA: (1) rc ACTION: This error could indicate a software driver problem. If problems persist, report these errors to Technical Support. Driver for VMware ESX 4.x - Troubleshooting Section Page 29

33 elx_mes0301: READ_SPARAM: no buffers DESCRIPTION: The driver attempted to issue a READ_SPARAM mailbox command to the HBA, but there were no buffers available. LOG: LOG_MBOX verbose ACTION: This message indicates: (1) The kernel virtual memory is depleted. Check that the system meets minimum RAM requirements for the Emulex Fibre Channel adapter. Try closing other applications to free some memory. (2) A possible driver buffer management problem. if problems persist, report these errors to Technical Support. elx_mes0302: REG_LOGIN: no buffers DESCRIPTION: The driver attempted to issue a REG_LOGIN mailbox command to the HBA, but there were no buffers available. DATA: (1) Did (2) flag LOG: LOG_MBOX verbose ACTION: This message indicates: (1) The kernel virtual memory is depleted. Check that the system meets minimum RAM requirements for the Emulex Fibre Channel adapter. Try closing other applications to free some memory. (2) A possible driver buffer management problem. if problems persist, report these errors to Technical Support. elx_mes0303: Ring <ringno> handler: portrspput <portrspput> is bigger then rsp ring <portrspmax> DESCRIPTION: The port rsp ring put index is larger than the size of the rsp ring. ACTION: This error could indicate a software driver, firmware or hardware problem. Report these errors to Technical Support. elx_mes0304: Stray mailbox interrupt, mbxcommand <mbxcommand> mbxstatus <mbxstatus> DESCRIPTION: Received a mailbox completion interrupt and there are no outstanding mailbox commands. ACTION: This error could indicate a hardware or firmware problem. if problems persist, report these errors to Technical Support. elx_mes0305: Mbox cmd cmpl error - RETRYing DESCRIPTION: A mailbox command completed with an error status that causes the driver to reissue the mailbox command. DATA: (1) mbxcommand (2) mbxstatus (3) un.varwords[0] (4) hba_state LOG: LOG_MBOX verbose, LOG_SLI verbose Driver for VMware ESX 4.x - Troubleshooting Section Page 30