Home

Emulex Drivers for VMware User Manual

1. Firmware halted This firmware does not support this Driver for VMware ESX 4 1 Troubleshooting Section Page 67 iSCSI Troubleshooting SE EMULEX The following table provides iSCSI troubleshooting information Table 7 General Driver Situations iSCSI Problem Solutions 1 When logging into more than 139 targets only 139 targets appear in vmkernel ESX by default can only show 139 targets even if up to 256 are supported To log into more than 139 targets and allow these targets to appear in vmkernel you must configure the tunable parameter vmklinuxHeapMaxSizeMB There are two methods to set this tunable parameter On the command line Or e With VI Client To set the parameter by the command line option set the value esxcfg advcfg k lt MBS gt vmklinuxHeapMaxSizeMB For example esxcfg advcfg k 48 vmklinuxHeapMaxSizeMB To set the parameter using VI Client Under Configuration gt Advanced Settings gt vmkernel set VMKernel Boot vmklinuxHeapMaxSizeMB to 48 Note You must reboot the ESX machine for the change to take effect Retrieving iSCSI Error Log Codes For ESX systems the iSCSI driver generates error codes to the var log vmkernel log file The vmkernel log file is an ASCII test file and can be viewed and searched with a text editor such as vim The vmkernel log file is automatically rotated as it gets larger and the rotated log files are named vmkernel x where x is a
2. DESCRIPTION A device reset has completed on tgt lun Status values are displayed DATA 1 tgt 2 lun 3 task mgmt status 4 flush status ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 40 SE EMULEX elx_mes0714 SCSI layer issued bus reset DESCRIPTION The SCSI layer is requesting the driver to abort all I Os to all targets on this adapter DATA 1 ret ACTION Check the state of the targets in question elx_mes0718 Unable to dma_map single request_buffer x x DESCRIPTION The driver could not map a single virtual address to a dma address DATA 1 dma mapping error ACTION None The driver fails the IO back to ESX elx_mes0721 Device Reset rport failure rdata lt rdata gt DESCRIPTION The reset of the Rport failed DATA None ACTION None required elx_mes0724 I O flush failure for context lt cntx gt on lt tgt lun gt cnt x x DESCRIPTION The I O flush to the LUN TARGET or HOST has failed DATA 1 cnt of unrecovered IO ACTION None required The reset is retried elx_mes0727 TMF lt cmd gt to TGT lt TGT gt LUN lt LUN gt failed lt ulpStatus gt lt ulpWord 4 gt DESCRIPTION The task management command failed DATA None ACTION None required The TMF command gets retried elx_mes0748 Abort handler timed out waiting for abort to complete ret lt status gt ID lt target id gt LUN lt lun id gt snum lt serial number gt DESCRIPTION The abort hand
3. Vital Product Data support e NPIV N Port ID Virtualization support New Features in this Release e Supports the Emulex OCe10100 family of UCNAs e Supports FC FCoE e Supports NIC Supports the OneCommand Manager application Driver for VMware ESX 4 1 Installation Section Page 1 SE EMULEX Prereduisites e There are no prerequisites at this time Compatibility e Fora list of adapters that are compatible with this driver see the driver 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 e The driver is matched to a particular version of the Emulex Core Kit the OCe10100 firmware and the NIC driver Refer to the Downloads page on the Emulex Web site for details Known Issues e See the product release notes for the latest information Installing the FC FCoE Driver Introduction This part of the guide provides installation and troubleshooting information for the Emulex OneCommand Manager application using the FC FCoE interface Before using this product you need a working knowledge of FC FCoE TOE TCP Offload Engine technology and the fundamentals of network storage devices Installing the FC FCoE Driver and Management Software The Emulex 8 2 x driver is available through the VMware support site Refer to the VMware support Web site for further details See the OneCommand Manager Command Line User Inte
4. elx_mes0261 Cannot Register NameServer login DESCRIPTION Either a memory allocation issue or an invalid parameter was sent to the REG_LOGIN DATA None ACTION At least one message 0142 0121 0133 0134 0135 should precede this message elx_mes0262 No NPIV Fabric support DESCRIPTION The switch to which the port is connected does not support NPIV DATA None ACTION Check the switch configuration elx_mes0263 Discovery Mailbox error state lt port_state gt lt sparam_mbox gt lt cfglink_mbox gt DESCRIPTION Either the driver could not allocate resources or it could not send sparam_mbox or cfglink mbox DATA 1 address of sparam mbox command 2 address of cfglink mbox command ACTION Attempt to unload and reload the driver when it is convenient elx_mes0264 No NPIV Fabric support DESCRIPTION The switch to which the port is connected does not support NPIV DATA None ACTION Check the switch configuration elx mes0266 Issue NameServer Req lt cmdcode gt err lt rc gt Data lt fc_flag gt lt fc_rscn_id_cnt gt DESCRIPTION The driver was not able to send the nameserver CT command DATA 1 VPorts fc_flag 2 VPorts fc_rscn_id_cnt ACTION Check the switch and port configurations elx_mes0267 NameServer GFF Rsp lt did gt Error lt ulpStatus gt lt un ulpWord 4 gt Data lt fc_flag gt lt fc_rscn_id_cnt gt DESCRIPTION The nameServer GFF CT request failed DATA 1 VPorts fc flag 2 VPorts fc
5. report the error to Technical Support elx_mes2756 LOGO failure DID lt DID gt Status lt Status gt lt Extended Status gt DESCRIPTION A LOGO to lt DID gt was failed either by the driver firmware or target The lt status gt and lt extended status gt indicates why the LOGO failed DATA None ACTION If the problem persists report the error to Technical Support elx_mes2757 Protocol failure detected during processing of FCP I O op tgt lt tgt ID gt lun lt LUN gt cmnd lt CMD gt rsplnfo3 lt rsplinfo3 gt DESCRIPTION The FCP response from a target indicated that the response length is valid but rspInfo3 indicates that there is no Failure This is a FCP spec violation by the target DATA None ACTION If the problem persists report the error to Technical Support elx_mes2758 Failed to allocate mempool for read FCF record mbox command DESCRIPTION The driver failed to allocate memory from the mempool for issuing FCF read mailbox command during the round robin FCF bmask update DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 63 5G EMULEX elx_mes2759 Failed to allocate memory for round robin FCF failover bmask DESCRIPTION The driver failed to allocate memory for the round robin FCF failover bmask DATA None ACTION Make sure system has enough kernel memory might need to reload the driver after memory problem resolved elx_mes2762 HBA reported FCF index
6. ulploTag ACTION If no ELS command is going through the adapter reboot the system If problem persists contact Technical Support elx mes0133 PLOGI no memory for reg login DESCRIPTION Memory allocation error DATA 1 nlp_DID 2 nip state 3 nlp_flag 4 nlp_rpi ACTION Memory allocation error Check system resources Unload unused modules elx_mes0134 PLOGI cannot issue reg_login DESCRIPTION The ELS PLOGI mailbox command has failed DATA 1 nlp_DID 2 nlp_state 3 nlp_flag 4 nlp_rpi ACTION Check the port and switch configuration elx_mes0135 cannot format reg_login DESCRIPTION Could not allocate an RPI or DMA buffer for the mailbox command DATA 1 nlp_DID 2 nlp_state 3 nlp_flag 4 nlp_rpi ACTION None required elx mes0136 PLOGI completes to N Port lt DID gt completion DESCRIPTION A PLOGI has completed for which there is no NDLP DATA 1 ulpStatus 2 ulpWord 4 ACTION None required elx_mes0137 No retry ELS command lt ELS_CMD gt to remote DESCRIPTION DATA 1 ulpStatus 2 ulpWord 4 ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 17 SG EMULEX elx_mes0138 ELS rsp Cannot issue reg_login for lt DID gt DESCRIPTION REG_LOGIN mailbox command failed DATA 1 nlp_DID 2 nlp_state 3 nlp_flag 4 nlp_rpi ACTION None required elx_mes0139 Ignoring ELS cmd tag lt ioTag gt completion Data DESCRIPTION This ELS command was
7. 1 Troubleshooting Section Page 55 5G EMULEX elx_mes2532 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION The mailbox bootstrap code detected that the SLI layer is active DATA 1 sli4_mbox_opcode 2 sli_flag 3 MBX_POLL ACTION None required elx_mes2533 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION DATA 1 sli4_mbox_opcode 2 sli_flag 3 MBX_NOWAIT ACTION None required elx_mes2535 Unsupported RQ count lt entry_count gt DESCRIPTION The receive queue ring can only be 512 1024 2048 or 4096 DATA None ACTION None required elx_mes2536 Unsupported RQ count lt entry_count gt DESCRIPTION The receive queue ring can only be 512 1024 2048 or 4096 DATA None ACTION None required elx_mes2537 Receive Frame Truncated DESCRIPTION The receive unsolicited handler detected a truncated frame DATA None ACTION None required elx_mes2541 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION DATA 1 sli4_mbx_opcode 2 sli_flag 3 flag ACTION None required elx_mes2543 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION The mailbox command does not have all of the fields set correctly DATA 1 sli4_mbx_opcode 2 sli_flag 3 flag ACTION None required elx_mes2544 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION The adapter cannot be accessed on
8. Driver for VMware ESX 4 1 Troubleshooting Section Page 24 5G EMULEX elx_mes0304 Stray mailbox interrupt mbxCommand lt mbxcommand gt mbxStatus lt mbxstatus gt DESCRIPTION Received a mailbox completion interrupt and there are no outstanding mailbox commands DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0306 CONFIG_LINK mbxStatus error lt mbxStatus gt HBA state lt hba_state gt DESCRIPTION The driver issued a CONFIG_LINK mbox command to the adapter that failed DATA None ACTION This error could indicate a firmware or hardware problem Report these errors to Technical Support elx_mes0310 Mailbox command lt mbxcommand gt timeout DESCRIPTION A mailbox command was posted to the adapter and did not complete within 30 seconds DATA 1 hba_state 2 sli_flag 3 mbox_active ACTION This error could indicate a software driver or firmware problem If no I O is going through the adapter reboot the system If the problem persists report the error to Technical Support elx_mes0312 Ring lt ringno gt handler portRspPut lt rspPutlnx gt is bigger then rsp ring lt numRiocb gt DESCRIPTION The IOCB command rings put pointer is ahead of the get pointer DATA None ACTION None required elx_mes0315 Ring lt ringno gt issue portCmdGet lt local_getidx gt is bigger then cmd ring lt max_cmd_idx gt DESCRIPTI
9. Driver resource initialization failed DATA None ACTION None required elx_mes1405 Failed to initialize iocb list DESCRIPTION IOCB initialization failed DATA None ACTION None required elx_mes1406 Failed to set up driver resource DESCRIPTION Initialization failed to set up driver resource DATA None ACTION None required elx_mes1407 Failed to create scsi host DESCRIPTION Initialization failed to create SCSI host DATA None ACTION None required elx_mes1408 Failure HBA POST Status sta_reg lt status reg gt perr lt port error gt sfi lt sfi reg nip lt nip reg ipc lt ipc reg xrom lt xrom gt dl lt dl reg pstatus lt port status gt DESCRIPTION The adapter s power on self test has failed DATA None ACTION Make sure the adapter firmware is up to date Contact the technical support if the issue persists after system reboot elx_mes1409 Failed to enable pci device DESCRIPTION Failed to enable PCI device during initialization DATA None ACTION None required elx_mes1410 Failed to set up pci memory space DESCRIPTION Initialization failed to set up PCI memory space DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 43 gt lt EMULEX elx_mes1411 Failed to set up driver resource DESCRIPTION Initialization failed to set up driver resource DATA None ACTION None required elx_mes1412 Failed to set up driver resou
10. Ee DE OE 6 Introduction to FC FCoE Configuration esse ees ees ee ee 6 Temporary FC FCoE Configuration Methods Using Native ESX Tools 6 Permanent FC FCoE Configuration Methods Using Native ESX Tools 6 Dynamically Adding LUNs and Target esse sesse seke ee ee ee ee ee ee ee ee ee ee 7 Emulex FC FCOE Driver Configuration ParameterS ee ee ee ee 7 Creating a Fibre Channel Remote Boot DiskK ee ee 9 Working with Virtual Ports VPorts 0 ee 10 Creating Deleting and Displaying VPortS ees ee ee RR ee ee ee 10 NIC Network Driver Performance TUNING ee ee 10 Using vmxnet Emulation Enabling Jumbo Frames and TSO 05 10 Configuring a Virtual Switch to Use Jumbo Frames iss ees ese ese 11 Pinning VMs and Interrupts to CPUS eed eed ee ee ee ee ee ee ee ee dee ee 11 iSCSI Error Handling ees eed ede ede ee ee EEE 12 Configuring LDTO and ETO iese sesse ese ee ee ee ae 12 Error Handling Under MultiPath MPIO and Cluster Configurations 13 TiOLUBIES HOOG EE KEER GEREG Ge N ENE GE N ed Ee N EE ER ER EE Ne ED ie 14 Introduction EE cece eee eeeeeeeeeeeeeaaaeeeeeeeeeeeecaaaaeeeeeeeeeeeeaaaaeeeeeeseesaaaaceeeeeeeeeesaaa 14 FC FCOE Troubleshooting ss se EE ER EA ER EA ER N AA ER RA Ee RA RA ER RA ER AA AAK KA Ad 14 General Situation S anainn a SR SR DE ee GR SR SR Se De es De Se 14 pic LOG Messages is Es ee ee ee Ge ee ee ee ee ee ea NANA ENER 15 D
11. Emulex Technical Support elx mes0523 Failed setup of fast path EQ lt fcp_eqidx gt rc lt rc gt DESCRIPTION The fast path EQ setup failed DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0526 Fast path FCP CQ lt fcp_cqidx gt not allocated DESCRIPTION The fast path FCP is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support gt lt EMULEX elx_mes0527 Failed setup of fast path FCP CQ lt fcp_cqidx gt rc lt rc gt DESCRIPTION The fast path FCP CQ setup failed DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0528 Mailbox CQ not allocated DESCRIPTION The mailbox CQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0530 ELS CQ not allocated DESCRIPTION The ELS CQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 38 gt lt EMULEX elx_mes0531 0531 Failed setup of slow path ELS CQ rc 0x x DESCRIPTION The ELS CQ is allocated but failed initial setup DATA 1 status ACTION The driver fails to load Contact Emulex Technical Support elx_mes0534 Fast path FCP WQ lt fcp_eqidx gt not allocated DESCRIPTION The fast path FCP WO is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Su
12. None ACTION Software driver error If this problem persists report these errors to Technical Support elx mes0203 Devloss timeout on WWPN lt address gt N Port lt nlp_DID gt DESCRIPTION A remote N Port that was discovered by the driver disappeared for more than Ipfc devloss tmo seconds DATA 1 nlp_flag 2 nlp state 3 nlp_rpi ACTION If the device generating this message is not a target of the adapter to which it is connected this error does not affect the data integrity of the I O between the adapter and the attached storage and can be ignored elx_mes0206 Device discovery completion error DESCRIPTION This indicates that an uncorrectable error was encountered during device re discovery after a link up Fibre Channel devices are not accessible if this message is displayed DATA None ACTION Reboot the system If the problem persists report the error to Technical Support Run with verbose mode on for more details elx_mes0207 Device lt DID gt lt WWN gt 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 the problem persists report the error to Technical Support Run with verbose mode on for more details elx_mes0222 Initial FLOG FDISKI timeout DESCRIPTION The driver sent the initial FLOGI or FDISK to the fabric and did not get a response DATA None
13. also require that I O errors be reported as soon as they are detected so the software can failover to an alternate path or an alternative node as quickly as possible When the be2iscsi driver is run under these configurations the error handling implemented in the be2iscsi driver needs to be turned off by setting the default values of LDTO and ETO to 0 The changes will take effect during the next driver load Also if ETO values have been modified using the OneCommand Manager CLI then the utility must be used to explicitly set the ETO value to 0 Again the ETO modifications done using the utility is immediate and will persist for the target across reboots upgrades and will override any value for ETO that you provide during driver load Driver for VMware ESX 4 1 Configuration Section Page 13 Troubleshooting Introduction SE EMULEX 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 FC FCoE Troubleshooting General Situations Table 3 General Driver Situations FC and FCoE Situation Resolution Port link fails to come up 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 s adapters For LP21000 adapters ensure the adapter is not in maintenance
14. example sets lun_queue_depth to 20 default is 30 for adapter 1 1 Set the adapter specific value Type esxcfg module s lpfcl lun queue depth 20 1pfc820 2 Reboot the server Type 7 7 7 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 lpfcl lun _queue_depth 20 lpfc2 lun queue depth 10 1pfc820 Note Type the command all on one line without a carriage return 2 Reboot the server Type reboot The new settings are used when the driver reloads To verify the settings type esxcfg module g lpfc820 Dynamically Adding LUNs and Targets For instructions on dynamically adding LUNs and targets refer to the Using Rescan section of the VMware SAN Config documentation Emulex FC FCoE Driver Configuration Parameters All adapter specific parameters have an IpfcX prefix where X is the driver instance number For example setting lpfcO_lun_queue_depth 20 makes 20 the default maximum number of commands that can be sent to a single logical unit disk for Ipfc instance 0 Driver for VMware ESX 4 1 Configuration Section Page 7 SE EMULEX Dynamic parameters do not require a system reboot for changes to take effect Table 1 FC FCoE Driver C
15. gt lt EMULEX Emulex Drivers for VMware ESX 4 1 FC and FCoE Version 8 2 1 78 22 NIC Version 2 102 404 0 iSCSI Version 2 102 404 0 User Manual One Network One Company P005240 01A Rev A Connect with Emulex SE EMULEX Copyright 2003 2010 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 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 produ
16. memory for fcf record DESCRIPTION DATA None ACTION None required elx_mes2555 UNREG_VFI mbxStatus error lt u mb mbxStatus gt HBA state lt port_state gt DESCRIPTION The unregister VFI mailbox command has failed DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 57 SE EMULEX elx mes2556 UNREG_VFI mbox allocation failed HBA state sport state DESCRIPTION Could not allocate memory for UNREG VFI mailbox command DATA None ACTION None reguired elx mes2557 UNREG_VFI issue mbox failed rc lt rc gt HBA state sport state DESCRIPTION Could not issue the UNREG_VFI mailbox command DATA None ACTION None required elx_mes2558 ADD_FCF_RECORD mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt DESCRIPTION The ADD FCF RECORD mailbox command has failed DATA None ACTION None reguired elx mes2560 Failed to allocate mbox cmd memory DESCRIPTION Failed to allocate mailbox command memory DATA None ACTION None reguired elx mes2561 Allocated DMA memory size lt alloclen gt is less than the requested DMA memory size lt reqlen gt DESCRIPTION Could not get the memory required for the number of XRIs that are attempting to be posted DATA None ACTION None required elx_mes2562 No room left for SCSI XRI allocation max_xri lt sli4_hba max_cfg_param max_xri gt els_xri lt els_xri_cnt gt DESCRIPTION The number of alloc
17. mode and that it is not running the manufacturing firmware For the OCe10100 family of adapters ensure that the fabric port is enabled The Emulex driver is not loaded and all paths are down Use Ispci to determine if the Emulex ports are being properly identified If not find out 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 file for Ipfc820 log messages indicating an error In this case contact Emulex support Ipfc driver fails to recognize an adapter and logs unknown IOCB messages in the system log during driver load The adapter is running outdated firmware Upgrade the adapter firmware to the minimum supported revision or newer listed in the installation guide System panics when booted with a failed adapter installed Remove the failed adapter and reboot Driver for VMware ESX 4 1 Troubleshooting Section Page 14 SE EMULEX Ipfc Log Messages Introduction Log messages have traditionally been organized into logical groups based on code functionality in the FC driver With the introduction of OneConnect UCNAs by Emulex that grouping is modified to account for new behaviors The traditional grouping is maintained but new messages no longer group together nicely The messages provided in this section are unmaskable error conditions They a
18. net be2net 400 2 102 200 10 1 0 4 164009 retired 2010 03 18T13 59 02 520994 07 00 Driver for VMware ESX 4 1 Installation Section Page 5 SE EMULEX Configuration Introduction to FC FCoE Configuration You can configure the driver parameters using native ESX tools or the Emulex OneCommand Manager application This document describes how to configure parameters using native ESX tools For a more comprehensive description of ESX tools refer to the current documents for VMware ESX 4 1 on the VMware public Web site If you have further questions contact a VMware technical support representative Refer to the Emulex OneCommand Manager User Manual for more information about the utility Temporary FC FCoE Configuration Methods Using Native ESX Tools There are four ways to configure the driver parameters e Permanent global Permanent per adapter e Temporary global e Temporary per adapter Note The OneCommand Manager application version 5 0 also supports all four ways to configure driver parameters This is the preferred method of setting configuration parameters Refer to the OneCommand Manager 5 0 User Manual for more information Permanent FC FCoE Configuration Methods Using Native ESX Tools 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 cha
19. parameter applies to Emulex PCI X adapters only Ipfc_scan_down 0 Off 1 On No Select a method for scanning ALPA to assign a SCSI ID Driver for VMware ESX 4 1 Configuration Section Page 8 Table 1 FC FCoE Driver Configuration Parameters Continued SE EMULEX Variable Default Min Max Dynamic Comments Ipfc_tgt_queue_depth 8192 10 8192 No Default maximum number of commands sent to a single target Ipfc_topology 0 0x0 loop No FC link topology Defaults then P2P to loop If that fails the 0x1 internal driver attempts to link in loopback point to point mode 0x2 P2P only Note Not supported for 0x4 loop only FCoE Ox6 P2P then loop Ipfc_use_adisc 0 0 Off 1 On Yes Send ADISC instead of Port Login PLOGI for device discovery or Registered State Change Notification RSCN Ipfc devloss tmo 10 1 255 Yes Number of seconds a remote port can drop from the SAN before that port is removed from the driver Ipfc use msi 0 0 use INTX min No Selects which interrupt 1 use MSI mode to use By default the 2 use MSI X max driver uses INTX VMware guidance is to use MSI X but MSI is available Ipfc_fcp_wq_count 4 1 31 No Configures the number of fast path work queues used by the host and port Ipfc_fcp_eq_count 4 1 7 No Configures the number of fast path event queues used by the host and port Ipfc_sg_seg_count 64 64 256 No Config
20. rscn id cnt ACTION Check the switch and port configurations elx_mes0268 NS cmd lt cmdcode gt Error lt ulpStatus gt lt un ulpWord 4 gt DESCRIPTION The nameServer CT request failed DATA None ACTION Check the switch and port configurations elx_mes0271 Illegal State Transition node lt nlp_DID gt event lt evt gt state lt nlp_state gt Data lt nlp_rpi gt snlp flag DESCRIPTION The current node state does not have a handler for this event DATA 1 nlp_rpi 2 nlp flag ACTION Verify that all targets are still visible to the SCSI mid layer Driver for VMware ESX 4 1 Troubleshooting Section Page 22 SE EMULEX elx_mes0272 Illegal State Transition node lt nlp_DID gt event lt evt gt state snlp state Data snlp rpi lt nlp_flag gt DESCRIPTION The driver is completing a PLOGI but do not have the rcv_plogi flag set DATA 1 nlp_rpi 2 nlp flag ACTION Verify that all targets are still visible to the SCSI mid layer elx_mes0273 Unexpected discovery timeout vport State lt port_state gt DESCRIPTION The discovery process has timed out DATA None ACTION Ensure all targets are visible elx_mes0282 did x x ndlp x pusgmap x x refcnt d ndlp gt nlp_DID void ndlp Ipfc_init c ndlp gt nlp_usg_ map DESCRIPTION Driver clean up has found a node that is still on the node list during driver unload or PCI hotplug removal DATA None ACTION None required elx_mes0283 Failed to a
21. sreg len DESCRIPTION The asychronous DCBX events are not handled in the driver DATA None ACTION Check the switch configuration elx mes0293 PM resume failed to start workerthread error lt error gt DESCRIPTION The PCI resume hotplug could not start the worker thread for the driver DATA None ACTION Unload and reload the driver elx_mes0294 PM resume Failed to enable interrupt DESCRIPTION The PCI resume hotplug could not get an interrupt vector DATA None ACTION Unload and reload the driver envalid device group lt pci_dev_grp gt DESCRIPTION While unloading the driver the driver detect a PCI device that it should not have claimed DATA None ACTION None required elx_mes0299 Invalid SLI revision lt sli_rev gt DESCRIPTION While processing a host attention or unrecoverable error the driver detected an invalid SLI revision DATA None ACTION None required Mailbox Events 0300 0339 elx_mes0300 LATT Cannot issue READ LA Data lt rc gt DESCRIPTION The link attention handler could not issue a READ_LA mailbox command DATA None ACTION None required elx_mes0303 Ring lt ringno gt handler portRspPut lt portRspPut gt is bigger then rsp ring lt portRspMax gt DESCRIPTION The port rsp ring put index is larger than the size of the rsp ring DATA None ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support
22. standard operating mode the driver creates two interfaces one for each physical port The first and second interfaces are respectively named vmnicO and vmnic1 assuming there are no other network interfaces in your configuration The same applies to virtual NIC vNIC capable UCNAs when vNIC mode is disabled in the adapter BIOS for those boards that support vNIC Driver for VMware ESX 4 1 Installation Section Page 4 SE EMULEX When vNIC mode is enabled in the adapter BIOS the driver creates eight interfaces four for each physical port The interfaces are labeled vmnic0 through vmnic7 assuming there are no other network interfaces in your configuration All eight vNICs are fully functional and support the same feature set as a standard NIC The vNICs can also be linked to a virtual switch in the same way E esxcfg nics 1l list recognized nics esxcfg vswitch 1 list available vswitches esxcfg vswitch a vSwitch0 create vSwitch0 esxcfg vswitch A VMNet0 vSwitch0 create virtual machine network VMNetO and add it to vSwitch0 esxcfg vswitch L vmnic0 vSwitch0 link vmnic0 to vSwitch0 The only difference being that in vNIC mode each of the four vNICs tied to a physical port share the port s 10GbE bandwidth Configuring VLANs The OneCommand Manager application supports VLAN filtering in the hardware To configure VLANs on a OneConnect interface create the vSwitch with the required VLAN
23. will return in the following form BE2ISCSI FUNCTION_NAME LINE MESSAGE For example be2iscsi 1088 kmalloc failed You will be requested to find the function FUNCTION_NAME at line LINE in the source Driver for VMware ESX 4 1 Troubleshooting Section Page 71 SE EMULEX APPENDIX DHCP Recommendations If you use a DHCP Dynamic Host Configuration Protocol server to obtain an IP address for the OneConnect UCNA Emulex recommends that you set up a reservation A reservation assigns a specific IP address based on the MAC address of the OneConnect UCNA If you do not reserve an IP Address through DHCP then you must set the lease length for the OneConnect UCNA IP address to unlimited to prevent the IP address lease from expiring Driver for VMware ESX 4 1 Appendix Page 72 SE EMULEX EMULEX END USER LICENSE AGREEMENT Any software and documentation respectively Software and Documentation provided under this End User License Agreement License Agreement are the copyrighted works of Emulex Corporation Emulex or its licensors Software may include firmware drivers and boot code The Software and Documentation are licensed not sold Emulex or its licensors retain all right title and interest including without limitation all intellectual property rights in and to all copies regardless of form or media of the Software and Documentation The Software or Documentation includes any revisions or updates Emulex g
24. 2 Unknown PCI error state x x DESCRIPTION The PCI bus has detected an error DATA 1 state value ACTION Driver resets the adapter and attempts recovery If problem persists contact Emulex technical support elx_mes0474 Unable to allocate memory for issuing MBOX_CONFIG_MSI command DESCRIPTION Mailbox memory pool allocation error DATA None ACTION None required elx_mes0475 Not configured for supporting MSI X cfg_use_msi lt cfg_use_msi gt DESCRIPTION The Ipfc use msi module parameter should have been set to 2 DATA None ACTION Set module parameter Ipfc_use_msi 2 elx_mes0476 HBA not supporting SLI 3 or later SLI Revision lt sli_rev gt DESCRIPTION The adapter does not support SLI 3 or SLI 4 DATA None ACTION This adapter does not support msi Set lpfc_use_msi 0 elx_mes0479 Deferred Adapter Hardware Error DESCRIPTION An adapter hardware error was sent to the driver DATA 1 work hs 2 work status 0 3 work_status 1 ACTION Perform a dump using hbacmd elx_mes0483 Invalid link attention link speed x x bf get lpfc acde link speed acde link DESCRIPTION The link speed reported in the link attention interrupt is invalid DATA None ACTION Check the switch configuration elx mes0493 SLI CONFIG SPECIAL mailbox failed with status lt rc gt DESCRIPTION Mailbox command failed DATA None ACTION Ensure the adapter s firmware is current Unload and reload the driver elx_mes049
25. 23333 tcp in onecommand esxcfg firewall openPort 23333 tcp out onecommand To verify that the correct port is open run the following command esxcfg firewall q The TCP port number can be changed The default is 23333 Refer to the VMware Server Configuration Guide for more details on how to configure the ESX firewall Uninstalling the FC FCoE Utilities Follow these instructions to uninstall the Emulex configuration utilities To uninstall the OneCommand Manager agent 1 2 Log in as root Type rpm qa grep elx to verify that this kit is installed This command should list elxocmcore esx41 lt kit version gt for the current release Type rpm e elxocmcore esx41 lt kit version gt Installing the NIC and iSCSI Drivers Introduction This part of the guide provides installation and troubleshooting information for the Emulex OneConnect UCNA Before using this product you need a working knowledge of the NIC network interface card TOE TCP offload engine technology iSCSI and the fundamentals of network storage devices Driver for VMware ESX 4 1 Installation Section Page 3 gt G EMULEX Installing the NIC and iSCSI Drivers and Management Software The Emulex NIC and iSCSI drivers for VMware ESX 4 1 are available through the VMware support site The VMware support Web site also includes a documentation link to the correct installation procedures for this driver Follow the installation instructio
26. 4 Unable to allocate memory for issuing SLI_FUNCTION_RESET mailbox command DESCRIPTION Mailbox memory pool allocation error DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0495 SLI_FUNCTION_RESET mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION Mailbox command failed DATA None ACTION The driver fails to load Contact Emulex Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 36 elx_mes0496 Failed allocate slow path EQ DESCRIPTION The event queue for the slow path was not allocated DATA None ACTION Unload and reload the driver elx_mes0497 Failed allocate fast path EQ DESCRIPTION The event queue for the fast path was not allocated DATA None ACTION Unload and reload the driver elx_mes0499 Failed allocate fast path FCP CQ lt fcp_cqidx gt gt lt EMULEX DESCRIPTION The completion queue event for the fast path could not be allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0500 Failed allocate slow path mailbox CQ DESCRIPTION Failed to allocate slow path mailbox CQ DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0501 Failed allocate slow path ELS CQ DESCRIPTION Failed to allocate slow path ELS CQ DATA None ACTION The driver fails to load Contact Emulex Technical Suppor
27. 43 Ipfc create static vport failed to allocate vport info DESCRIPTION Failed to allocate VPort info DATA None ACTION Static VPorts does not load Contact Emulex Technical Support elx_mes0545 Ipfc create static vport bad information header 0x x 0x x le32 to cpu vport info signature le32_to_cpu vport_info gt rev amp VPORT INFO REV MASK DESCRIPTION Invalid information header the signature or revision is invalid DATA None ACTION Static VPorts does not load Contact Emulex Technical Support elx_mes0582 Error lt rc gt during sgl post operation DESCRIPTION The SGL post operation failed DATA None ACTION None required elx_mes0602 Failed to allocate CQ_EVENT entry DESCRIPTION Failed to allocate a CQ_EVENT entry DATA None ACTION None required elx_mes0603 Invalid work queue CQE subtype lt subtype gt DESCRIPTION Invalid work queue CQE DATA None ACTION None required FCP Traffic History 0700 0799 elx_mes0700 Bus Reset on target lt i gt failed DESCRIPTION The bus reset for the specified target failed DATA None ACTION None required elx_mes0706 0706 IOCB Abort failed outstanding d failed d DESCRIPTION The driver did not recover all IO following a reset task management command DATA 1 outstanding IO count 2 number of unrecovered IO ACTION Reset call fails to ESX tries to recover elx_mes0713 SCSI layer issued Device Reset d d reset status x x flush status x X
28. 5 copper cables attached the operating system indicates link up or down status When inserting or removing copper cables attached to a switch to the module link up or down events are not reported to the operating system Flow control setting is not stored per port With flow control there is no persistence across reboot It after rebooting the system always starts with both RX and TX on For persistence run a config command from an RC file at reboot NIC Event Error Logging Retrieving NIC Error Log Codes For ESX Server systems the NIC OneConnect be2net driver generates error codes to the var log vmkernel log file The vmkernel log file is an ASCII text file and can be viewed and searched with a text editor such as vi The vmkernel log file is automatically rotated as it gets larger and the rotated log files are named vmkernel x where x is an integer To search the log file for error messages at the command prompt type cd var log less vmkernel For example you might see the following message Sep 9 19 48 04 esx server vmkernel WARNING Found a BE2 card in Gen 1 x8 PCI e slot Should be in Gen 2 x8 slot for best performance NIC Event Log Entries The following is a list of ESX Server network event log error messages It includes the severity of the error the message displayed and the message description When reporting a problem with the OneConnect UCNA to Emulex check the me
29. 62 gt lt EMULEX elx_mes2751 Adapter failed to restart status reg lt status gt FW Data A8 lt 0xA8 gt AC lt 0xAC gt DESCRIPTION The adapter has failed to restart DATA None ACTION If the problem persists report the error to Technical Support elx_mes2752 KILL BOARD command failed retval lt retval gt DESCRIPTION The KILL BOARD mailbox command failed to complete DATA None ACTION If the problem persists report the error to Technical Support elx_mes2753 PLOGI failure DID lt DID gt Status lt Status gt lt Extended Status gt DESCRIPTION A PLOGI to lt DID gt was failed either by the driver firmware or target The lt status gt and lt extended status gt indicates why the PLOGI failed DATA None ACTION If the problem persists report the error to Technical Support elx_mes2754 PRLI failure DID lt DID gt Status lt Status gt lt Extended Status gt DESCRIPTION A PRLI to lt DID gt was failed either by the driver firmware or target The lt status gt and lt extended status gt indicates why the PRLI failed DATA None ACTION If the problem persists report the error to Technical Support elx_mes2755 ADISC failure DID lt DID gt Status lt Status gt lt Extended Status gt DESCRIPTION A ADISC to lt DID gt was failed either by the driver firmware or target The lt status gt and lt extended status gt indicates why the ADISC failed DATA None ACTION If the problem persists
30. 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 RATOV DATA None ACTION Check the fabric configuration The driver recovers from this and continues with device discovery elx_mes0224 NameServer Query timeout DESCRIPTION Node authentication timeout node discovery timeout A NameServer query to the fabric or discovery of reported remote N Ports is not acknowledged within R_A_TOV DATA 1 fc ns retry 2 fe_max_ns_retry ACTION Check fabric configuration The driver recovers from this and continues with device discovery Driver for VMware ESX 4 1 Troubleshooting Section Page 19 5G EMULEX elx_mes0226 Device discovery completion error DESCRIPTION This indicates that an uncorrectable error was encountered during device re discovery after a link up Fibre Channel devices are not accessible if this message is displayed DATA None ACTION Reboot the system If the problem persists report the error to Technical Support Run with verbose mode on for more details elx_mes0227 Node Authentication timeout DESCRIPTION The driver has lost track of what N_Ports are being authenticated DATA None ACTION None required The driver should recover from this event elx_mes0228 CLEAR LA timeout DESCRIPTION The driver issued a CLEAR_LA that ne
31. D DATA None ACTION Check the port connection and switch configuration elx_mes0253 Register VPI Can t send mbox DESCRIPTION Could not issue the REG_LOGIN command for this VPort DATA None ACTION None required elx_mes0254 Register VPI no memory goto mbox_err_exit DESCRIPTION Could not allocate memory for the REG_LOGIN mailbox command DATA None ACTION None required elx_mes0255 Issue FDISC no IOCB DESCRIPTION All of the pre allocated OCBs are in use DATA None ACTION None required elx mes0256 Issue FDISC Cannot send lOCB DESCRIPTION Unable to send the fabric IOCB DATA None ACTION Check the switch configuration elx_mes0257 GID_FT Query error lt ulpStatus gt lt fc_ns_retry gt DESCRIPTION The GID_FT CT request for the nameserver has failed DATA None ACTION Check the switch configuration elx_mes0258 Register Fabric login error lt mbxStatus gt DESCRIPTION The REG_LOGIN for the fabric has failed DATA None ACTION Check the port and switch configuration elx_mes0259 No NPIVFabric support DESCRIPTION The switch to which the port is connected does not support NPIV DATA None ACTION Check the switch configuration elx_mes0260 Register NameServer error lt mbxStatus gt DESCRIPTION The REG_LOGIN mailbox command has failed for the nameserver DATA None ACTION Check the switch configuration Driver for VMware ESX 4 1 Troubleshooting Section Page 21 5G EMULEX
32. Description Warning alloc skb failed Try increas Could not allocate skb structure to send a ing netPktHeapMaxSize frame received from the network to the OS Transient failure can be ignored Persistent message points to insufficient memory allocated for network heap For example to increase the heap size to 128MB run esxcfg advcfg k 128 netPk tHeapMaxSize Warning Invalid MTU requested Must be Invalid MTU size in MTU configuration ioctl between 64 and 8174 bytes The MTU is not changed Warning Invalid vlan priority labeled Request to set VLAN priority tag was made Must be 0 7 with invalid value Warning Failed to allocate memory for Memory allocation for pass through pass through command command failed The driver should continue to function The configuration utility that issued the pass through ioctl fails Warning Pass through command failed opcode The pass through firmware command with lt DDD gt status 0x lt XXX gt indicated opcode failed The driver should continue to function The configuration utility that issued the pass through ioctl fails Warning Command to modify EQ delay failed Firmware command to change the EQ delay failed The driver continues to function The adaptive interrupt coalescing does not function correctly NIC Adapter Firmware Error The following POST message appears if you have loaded firmware on the OneConnect adapter that the controller does not support POST Error controller
33. EMULEX Table 4 Message Log Table Continued LOG Message From To Verbose Verbose Description Verbose Mask sk Bit Definition FCOE EVENTS 1833 2800 The verbose bit remains with the previous rows LOG_ALL_MSG 0100 2600 Oxffffffff Log all messages Message Log Example The following is an example of a LOG message Jul 9 09 38 02 raman vmkernel 0 00 01 42 995 cpu0 4225 lt 3 gt lpfc820 0000 0a 00 2 0 1303 Link Up Event xl received Data xl x0 x40 x0 x0 x0 0 In the above LOG message e pfc820 0000 0a 00 2 identifies the identifies the PCI location of the particular Ipfc hw port e 0 identifies Emulex HBA 0 e 1303 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 Note Unless otherwise noted in the ACTION attribute report these errors to Technical Support Emulex requests that when reporting occurrences of these error messages you provide a tarball of all vmkernel files in var log ELS Events 0100 0199 elx_mes0100 FLOGI failure Status lt status gt lt extended_status gt TMO lt timeout gt DESCRIPTION An ELS FLOGI command that was sent to the fabric failed DATA 1 ulpStatus 2 ulpWord 4 3 ulpTimeout ACTION This error could indicate a fabric configuration error or internal driver issue If problems persist report
34. FCFI issue mbox failed DESCRIPTION Could not issue the UNREG FCFI mailbox command DATA None ACTION None required elx_mes2619 Config region 23 has bad signature DESCRIPTION Configuration region 23 has an invalid signature DATA None ACTION None required elx_mes2620 Config region 23 has bad version DESCRIPTION Configuration region 23 has an invalid version DATA None ACTION None required elx_mes2621 Failed to allocate mbox for query firmware config cmd DESCRIPTION Failed to allocate mailbox memory DATA None ACTION None required elx_mes2622 Query Firmware Config failed mbx status lt rc gt status lt shdr_status gt add_status lt shdr_add_status gt DESCRIPTION Could not read the firmware configuration DATA None ACTION None required elx_mes2623 FCoE Function not supported by firmware Function mode lt function_mode gt DESCRIPTION FCoE is not supported by this firmware DATA None ACTION Use the OneCommand Manager application to update to the latest firmware Driver for VMware ESX 4 1 Troubleshooting Section Page 61 5G EMULEX elx mes2707 Ring lt Ring gt handler Failed to allocate iocb Rctl lt fh_rctl gt Type lt fh_type gt received DESCRIPTION Could not allocate an IOCB with which to associate this received frame DATA None ACTION None required elx_mes2718 Clear Virtual Link Received for VPI lt index gt tag lt event_tag gt DESCRIPTION A Clear virtual link w
35. ID and use this interface as an adapter to this vSwitch A native VLAN can also be configured in the guest operating system in VGT Virtual Guest Tagging mode For example using vconfig in the Linux guest operating system Configuring Network Heap Size in ESX Server By default the ESX Server network stack allocates 64MB of buffers to handle network data Even if the network load requires more than 64MB of memory the OneConnect driver cannot allocate it When this happens the driver logs messages in the file proc vmware log indicating that the alloc_skb call failed This impacts network performance considerably To read the current size of the network heap run esxcfg advcfg j netPktHeapMaxSize netPktHeapMaxSize 0 e Ifthe default value of 64MB is in effect this command shows the size as 0 If any other value is in effect the command prints that value For example to set the heap size to 128MB run the command esxcfg advcfg k 128 netPktHeapMaxSize esxcfg advcfg j netPktHeapMaxSize netPktHeapMaxSize 128 The new value takes effect after a reboot Interrogating the NIC Driver To get information on the installed NIC driver enter esxupdate query vib view grep be2net This is a sample output root blade1l0 esxupdate query vib view grep be2net cross vmwar sx drivers net be2net 00 2 102 225 12 1 0 4 164009 installed 2010 04 05T11 28 38 540372 07 00 cross vmwar sx drivers
36. Menlo Maint Mode Link up Event x x rcvd Data x x x x x x DESCRIPTION Link up notification in Menlo maintenance mode DATA 1 fc eventTag 2 port state 3 VPort fc_flag ACTION None reguired elx mes1309 Link Down Event x x received Data x x x x x x DESCRIPTION The port generated a link down event to the host DATA 1 fc eventTag 2 port state 3 VPort fc flag ACTION None reguired elx mes1310 Link Up Event npiv not supported in loop topology DESCRIPTION Loop topologies are not supported when NPIV is enabled DATA None ACTION Put link into fabric mode Reserved 1400 1499 elx_mes1400 Failed to initialize sgl list DESCRIPTION Failed to initialize SGL list during initialization DATA None ACTION Reboot the server If the issue persist contact technical support elx_mes1401 Failed to enable pci device DESCRIPTION Failed to enable PCI device during initialization DATA None ACTION Reboot the server If the issue persist contact technical support Driver for VMware ESX 4 1 Troubleshooting Section Page 42 gt lt EMULEX elx_mes1402 Failed to set up pci memory space DESCRIPTION PCI initialization failed DATA None ACTION Reboot the server If the issue persist contact technical support elx_mes1403 Failed to set up driver resource DESCRIPTION Driver resource initialization failed DATA None ACTION None required elx_mes1404 Failed to set up driver resource DESCRIPTION
37. ON A signal other than the LPFC_DATA_READY was received on the worker thread DATA None ACTION Unload and reload the driver elx_mes0434 PM resume failed to start worker thread error lt error gt DESCRIPTION The driver s power management resume function could not start the worker thread DATA None ACTION Unload and reload the driver elx_mes0435 Adapter failed to get Option ROM version status lt rc gt DESCRIPTION The driver could not read the adapter s option ROM DATA None ACTION Reset the adapter Ensure the adapter s firmware is current elx_mes0436 Adapter failed to init timeout status reg lt status gt DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 33 SE EMULEX elx_mes0437 Adapter failed to init chipset status reg lt status gt DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0438 Adapter failed to init chipset status reg lt status gt DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None ACTION This error could indicate a hardware or firmware pro
38. ON The port cmd ring get index is greater than the size of cmd ring DATA None ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support elx_mes0317 iotag lt ulp_loTag gt is out of range max iotag lt max_iotag gt wd0 lt wd0 gt DESCRIPTION The loTag in the completed IOCB is out of range DATA None ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support elx_mes0318 Failed to allocate IOTAG last IOTAG is lt last_allocated_iotag gt DESCRIPTION The driver cannot allocate an loTag Display the last value used DATA None ACTION This message indicates the adapter I O queue is full Typically this happens when heavy I O is running on a low end 3 digit adapter We suggest you upgrade to a higher end adapter Driver for VMware ESX 4 1 Troubleshooting Section Page 25 gt lt EMULEX elx_mes0319 READ_SPARAM mbxStatus error lt mbxStatus gt hba state lt hba_state gt DESCRIPTION The driver issued a READ SPARAM mbox command to the adapter that failed DATA None ACTION This error could indicate a firmware or hardware problem Report these errors to Technical Support elx_mes0320 CLEAR_LA mbxStatus error lt mbxStatus gt hba state lt hba_state gt DESCRIPTION The driver issued a CLEAR_LA mbox command to the adapter that failed DATA None ACTION This error could indicate a
39. PTION Failed to allocate memory for MSI X interrupt vector entries DATA None ACTION None required elx_mes2574 Not enough EQs lt sli4_hba max_cfg_param max_eq gt from the pci func tion for supporting FCP EQs lt cfg_fcp_eq_count gt DESCRIPTION Failed to create the minimum fast path event queues DATA None ACTION elx_mes2576 Failed allocate memory for fast path EQ record array DESCRIPTION Failed to allocate memory for the fast path EQ record array DATA None ACTION None required elx_mes2577 Failed allocate memory for fast path CQ record array DESCRIPTION Failed to allocate memory for the fast path CQ record array DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 59 gt lt EMULEX elx_mes2578 Failed allocate memory for fast path WQ record array DESCRIPTION Failed to allocate memory for the fast path WQ record array DATA None ACTION None required elx_mes2581 Not enough WGs ssli4 hba max cfg param max wa from the pci func tion for supporting FCP WQs lt cfg_fcp_wq_count gt DESCRIPTION The driver was not configured with the minimum number of fast path work queues DATA None ACTION None required elx_mes2597 Mailbox command lt vpi gt lt mbxCommand gt cannot issue DESCRIPTION Synchronous mailbox command failed after blocking asynchronous mailbox commands DATA 1 sli4_mbx_opcode 2 sli_flag 3 flag ACTION None required elx_
40. TA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 29 SG EMULEX elx_mes0376 READ_REV Error SLI Level lt sli_rev gt FCoE enabled lt hba_flag amp HBA_FCOE_SUPPORT gt DESCRIPTION This SLI 4 only adapter setup function was called for a non SLI 4 device DATA None ACTION None required elx_mes0377 Error lt rc gt parsing vpd Using defaults DESCRIPTION Could not parse the VPD data so the driver is using the default values DATA None ACTION None required elx_mes0381 Error lt rc gt during queue setup DESCRIPTION Could not set up all the queues that driver requires to exchange lOs with the adapter DATA None ACTION Reload the driver elx_mes0382 READ_SPARAM command failed status lt issue status gt mbxStatus lt mailbox status gt DESCRIPTION The READ_SPARAM mailbox command has failed during initialization The adapter has been set to error state DATA None ACTION Take a dump with hbacmd and then try reloading the driver elx_mes0384 There is pending active mailbox cmd DESCRIPTION The mailbox commands have overlapped This command should have been added to the mailbox queue DATA None ACTION None required elx_mes0385 rc should have been MBX_BUSY DESCRIPTION The completion handler for REG_LOGIN detected the IMMED_UNREG flag and tried to issue the unreg_login command from an interrupt level The mailbox status should still be busy DATA None AC
41. TION None required elx_mes0387 Failed to allocate an iocbq DESCRIPTION Failed to get an IOCBQ from the list of available IOCBQs DATA None ACTION None required elx_mes0388 Not a valid WCQE code lt hex cqe_code gt DESCRIPTION The event code is invalid This event is dropped DATA None ACTION Ensure the adapter s firmware is current Driver for VMware ESX 4 1 Troubleshooting Section Page 30 5G EMULEX elx_mes0391 Error during rpi post operation DESCRIPTION The driver was trying to post pages to the firmware to be used to keep target login information and encountered a failure DATA None ACTION Unload and reload the driver elx_mes0393 Error lt rc gt during rpi post operation DESCRIPTION The driver was trying to post pages to the firmware to keep target login information and encountered a failure DATA None ACTION Unload and reload the driver elx_mes0394 Failed to allocate CQ_EVENT entry DESCRIPTION The asynchronous event handler was not able to allocate an event queue entry to which to transfer the asynchronous event DATA None ACTION This could be a V LINK clear from the switch or a fatal error from the firmware Perform a dump from the OneCommand Manager application elx_mes0395 The mboxq allocation failed DESCRIPTION The asynchronous link event handler could not allocate a mailbox command to issue the READ LA read link attention mailbox command DATA None ACTION None requir
42. _reg lt Online1 gt DESCRIPTION The adapter has notified the driver that it has encountered an unrecoverable error DATA None ACTION A dump from the OneCommand Manager application should be taken Then the driver should be unloaded and reloaded elx_mes1423 HBA Unrecoverable error uerr_lo_reg lt ue lo gt uerr_hi_reg lt ue hi gt online0_reg lt Online0 gt online1_reg lt Online1 gt DESCRIPTION The adapter has notified the driver that it has encountered an unrecoverable error DATA None ACTION A dump from the OneCommand Manager application should be taken Then unload and reload the driver elx_mes1424 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx mes1425 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None reguired elx_mes1426 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx_mes1427 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx_mes1428 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx_mes1429 Invalid PCI device group lt pci_dev_grp gt DESCRIPTION In
43. aborted DATA 1 ulpStatus 2 ulpWord 4 3 ulpTimeout ACTION None required elx_mes0140 PLOGI Reject invalid nname DESCRIPTION Invalid node WWN provided DATA None ACTION None required elx_mes0141 PLOGI Reject invalid pname DESCRIPTION Invalid port WWN provided DATA None ACTION None required elx_mes0142 PLOGI RSP Invalid WWN DESCRIPTION The PLOGI sent to the port by a remote port had an invalid WWN DATA None ACTION None required elx_mes0144 Not a valid WCQE code lt Completion Code gt DESCRIPTION The completion queue handler detected an invalid type DATA None ACTION None required elx_mes0147 Failed to allocate memory for RSCN event DESCRIPTION Memory could not be allocated to send the RSCN event to the management application DATA None ACTION None required elx_mes0148 Failed to allocate memory for LOGO event DESCRIPTION Memory could not be allocated to send the LOGO event to the FC transport DATA None ACTION None required elx_mes0154 Authentication not complete DESCRIPTION Authentication was restarted because the previous authentication did not complete DATA None ACTION Check the switch configuration Driver for VMware ESX 4 1 Troubleshooting Section Page 18 2E EMULEX Link Discovery Events 0200 0299 elx mes0200 CONFIG LINK bad hba state shba state DESCRIPTION A CONFIG LINK mbox command completed and the driver was not in the right state DATA
44. an find the IRQ NO corresponding to a vmnic by running cat proc vmware interrupts To see all IRQ Vectors and the CPU to which they are pinned run cat proc vmware intr tracker iSCSI Error Handling The goal of iSCSI error handling is to be tolerant of link level and or target level failures up to configured timeout values so that I O errors are not seen by the application or operating system The error handling is triggered under the following conditions e Loss of immediate link to the initiator for example cable disconnect port failure The UCNA firmware detects and notifies the driver of a loss of the link When this happens the driver will queue I O requests internally up to a configured timeout period so that the operating system does not see I O errors This timeout is known as Link Down Timeout LDTO e Loss of connection to the target due to target and or network disconnection at the target If the driver has I O requests pending with the target and the target becomes unavailable due to target going down failing over or network issues at the target the driver queues up the I O request internally up to a configured timeout period This timeout is known as Extended Timeout ETO When the configured threshold for LDTO and ETO is reached and the initiator is still unable to connect to the target the driver fails all VO requests At this point VO errors will be seen by the application and operating system Con
45. as received from the fabric for this VPI DATA None ACTION None required elx_mes2719 Invalid response length tgt lt TGT_ID gt lun lt LUN gt cmnd lt CMD gt rsplen lt RSPLEN gt DESCRIPTION The response length for this FCP command is not supported DATA None ACTION None required elx_mes2726 READ_FCF_RECORD Indicates empty FCF table DESCRIPTION The driver requested the firmware provide a list of FCF entries to connect to and the firmware responded that the FCF table is empty DATA None ACTION None required elx_mes2731 Cannot find fabric controller node DESCRIPTION Driver not able to find fabric controller node in its data base DATA None ACTION None required elx_mes2732 Failed to issue INIT_VPI mailbox command DESCRIPTION The driver wanted to send a INIT_VPI mailbox command to initialize a VPort but failed to send the mailbox command due to state of the adapter DATA None ACTION None required elx_mes2746 Failed FCF rediscover mailbox command failure DESCRIPTION The adapter returned failure on FCF rediscover mailbox command DATA None ACTION None required elx_mes2747 Failed to issue read FCF record mailbox command DESCRIPTION The driver wanted to send a read FCF record mailbox command to start fast FCF failover FCF scan but failed to send the mailbox command due to state of the adapter DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page
46. ate a software driver or firmware problem If these problems persist report these errors to Technical Support elx_mes0340 Adapter temperature is OK now DESCRIPTION Adapter temperature has reverted to normal range DATA Temperature in Celsius ACTION No action needed informational Driver for VMware ESX 4 1 Troubleshooting Section Page 26 SE EMULEX elx mes0341 Ring lt ringno gt Cannot find buffer for an unsolicited iocb tag lt un ulpWord 3 gt DESCRIPTION There are no more pre allocated buffers available to handle unsolicited buffers DATA None ACTION Ensure this port is not being managed by multiple ports elx_mes0342 Ring lt ringno gt Cannot find buffer for an unsolicited iocb tag lt unsli3 sli3Words gt DESCRIPTION This is a multiple IOCB unsolicited command and sufficient buffer space cannot be allocated for it DATA None ACTION None required elx_mes0343 Ring lt ringno gt Cannot find buffer for an unsolicited iocb tag lt un ulpWord 3 gt DESCRIPTION There are no more pre allocated buffers available to handle unsolicited buffers DATA None ACTION None required elx_mes0344 Ring lt ringno gt Cannot find buffer for an unsolicited iocb tag lt unsli3 sli3Words 7 gt DESCRIPTION There are no more pre allocated buffers available to handle unsolicited buffers DATA None ACTION None required elx_mes0345 Resetting board due to mailbox timeout DESCRIPTION A mailbox command failed to
47. ated XRIs has reached the max_xri value DATA None ACTION None required elx_mes2563 Failed to allocate memory for SCSI XRI management array of size lt sli4_hba scsi_xri_max gt DESCRIPTION Initialization could not allocate memory to hold the XRIs DATA None ACTION None required elx_mes2564 POST_SGL_BLOCK mailbox command failed status lt shdr_status gt add status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The list of XRI SGEs failed to be registered with the firmware DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 58 gt lt EMULEX elx_mes2566 Failed to allocate connection table entry DESCRIPTION Failed to allocate connection table entry DATA None ACTION None required elx_mes2567 Config region 23 has bad signature DESCRIPTION Configuration region 23 has an invalid signature DATA None ACTION None required elx_mes2568 Config region 23 has bad version DESCRIPTION Configuration region 23 has an invalid version DATA None ACTION None required elx_mes2570 Failed to read FCoE parameters DESCRIPTION Failed to read the FCoE parameters DATA None ACTION None required elx_mes2572 Failed allocate memory for fast path per EQ handle array DESCRIPTION Failed to allocate memory for the fast path per EQ handle array DATA None ACTION None required elx_mes2573 Failed allocate memory for msi x interrupt vector entries DESCRI
48. blem If the problem persists report the error to Technical Support elx_mes0439 Adapter failed to init mbxCmd lt mbxCommand gt READ_REV mbxStatus lt mbxStatus gt DESCRIPTION Adapter initialization failed when issuing a READ_REV mailbox command DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0440 Adapter failed to init READ_REV has missing revision information DESCRIPTION A firmware revision initialization error was detected DATA None ACTION This error could indicate a hardware or firmware problem Update the firmware If the problem persists report the error to Technical Support elx_mes0442 Adapter failed to init mbxCmd lt mbxCommand gt CONFIG_PORT mbxStatus lt mbxStatus gt DESCRIPTION Adapter initialization failed when issuing a CONFIG_PORT mailbox command DATA 1 hbainit ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0443 Adapter failed to set maximum DMA length mbxStatus lt u mb mbxStatus gt DESCRIPTION Cannot set the maximum DMA length to reflect cfg_pci_max_read DATA None ACTION Set module parameter Ipfc_pci_max_read to 512 1024 2048 or 4096 elx_mes0445 Firmware initialization failed DESCRIPTION The driver was unable to initialize the hardware DATA None ACTION This error could indicat
49. c mode Note You can create VPorts only on 4 Gb s 8 Gb s and OneConnect adapters You cannot create VPorts on 1 Gb s or 2 Gb s adapters Note The OneCommand Manager application sees all VPorts created by the driver but the application has read only access to them NIC Network Driver Performance Tuning Network driver performance tuning improves performance of the network and the TCP Offload driver The OneConnect Universal Converged Network Adapter UCNA is an x8 Generation 2 Gen 2 or Gen2 PCI Express PCle device and requires substantial system memory bandwidth to support 10 Gb s data streams Using vmxnet Emulation Enabling Jumbo Frames and TSO The OneConnect UCNA supports jumbo frames and TSO both of which are necessary to achieve optimal performance with the OneConnect UCNA Also the use of the vmxnet NIC emulator can provide a significant performance boost These features are not enabled by default in ESX Server To enable these features 1 Log into the console operating system 2 For each guest operating system there is a vmx file in the path vmfs volumes lt VM NAME gt VM NAME gt vmx where lt VM NAME gt is the name of the VM 3 For each VM edit this file and add the following line for the OneConnect driver interface thernet0O features 15 4 To enable vmxnet emulation add the following line for the OneConnect driver interface ethernetO virtualDev vmxnet 5 Res
50. complete The driver is resetting the port DATA None ACTION If the mailbox command fails again set the lpfc_log_verbose to LOG MBOX and retry elx_mes0346 Ring lt ring number gt handler unexpected ASYNC_STATUS evt_code lt evtcode gt W0 lt hex w0 gt W1 lt hex wi W2 lt hex W2 gt W3 lt hex W3 gt W4 lt hex W4 gt W5 lt hex Z5 gt W6 lt hex W6 gt W7 lt hex W7 gt W8 lt hex W8 gt W9 lt hex W9 gt W10 lt hex W10 gt W11 lt hex W11 gt DESCRIPTION The adapter received an asynchronous event that was not a temperature event DATA None ACTION None required elx_mes0347 Adapter is very hot please take corrective action DESCRIPTION Adapter temperature is above normal range DATA Temperature in Celsius ACTION Shutdown and remove the adapter Contact customer support elx_mes0348 NameServer login node freed DESCRIPTION The enable mode failed to free up the nameserver login DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 27 SE EMULEX elx mes0349 rc should be MBX SUCCESS DESCRIPTION The next mailbox command on the mailbox gueue has failed DATA None ACTION None required elx_mes0350 rc should have been MBX_BUSY DESCRIPTION Attempting to unregister a default RPI from an interrupt context and the mailbox state is not busy DATA None ACTION None required elx_mes0352 Config MSI mailbox command failed mbxCmd lt u mb mbxCommand gt mbxStatus lt
51. ct 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 US patent notice is given for one or more of the following 6226680 6247060 6334153 6389479 6393487 6427171 6427173 6434620 6591302 6658480 6697868 6751665 6757746 6941386 6965941 6687758 7042898 7133940 7124205 7089326 6938092 6996070 The license terms that govern the use of this document are set forth in the Emulex end user license agreement that appears at the end of this document Emulex 3333 Susan Street Costa Mesa CA 92626 Copyright 2003 2010 ServerEngines Corporation TRADEMARKS ServerEngines the ServerEngines logo and BladeEngine 2 are trademarks or registered trademarks of ServerEngines Corporation Microsoft Windows Windows XP Windows 2003 and Windows 2008 are U S registered trademarks of Microsoft Corporation Adaptec is a trademark of Adaptec Inc which may be registered in some jurisdictions Adobe and Acrobat are trademarks of Adobe Systems Incorporated Driver for VMware ESX 4 1 User Manual Page ii SE EMULEX Installati n EE AE EE NE AO OO EE EE 1 Driver Information EE eN aaaea aaaea Ge ee e
52. d DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 52 SE EMULEX elx mes2502 MO CREATE mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to create the mailbox queue has failed DATA None ACTION None required elx_mes2503 WQ_CREATE mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to create the work queue has failed DATA None ACTION None required elx_mes2504 RQ_CREATE mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to create the receive queue has failed DATA None ACTION None required elx mes2505 EQ_DESTROY mailbox failed with status lt shdr_status gt add status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the event queue has failed DATA None ACTION None required Preliminary Second Review elx_mes2506 CQ_DESTROY mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the completion queue has failed DATA None ACTION None required elx_mes2507 MQ_DESTROY mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx stat
53. dd_status gt mbx DESCRIPTION The READ_FCF_RECORD mailbox command has failed DATA None ACTION None required elx_mes2523 Allocated DMA memory size lt alloc_len gt is less than the requested DMA memory size lt req_len gt DESCRIPTION The ADD_FCF_RECORD mailbox command failed to retrieve the length required from the firmware DATA None ACTION None required elx_mes2524 Failed to get the non embedded SGE virtual address DESCRIPTION The READ_FCF_RECORD mailbox command could not retrieve the Scatter Gather Entry that was requested DATA None ACTION None required elx_mes2527 Failed to allocate non embedded SGE array DESCRIPTION Failed to allocate the non embedded SGE array DATA None ACTION None required elx_mes2528 Mailbox command lt vpi gt cannot issue DESCRIPTION The mailbox command could not be issued because the mailbox interrupt is disabled DATA 1 mbxCommand 2 sli_flag 3 flag ACTION None required elx_mes2529 Mailbox command lt vpi gt cannot issue DESCRIPTION DATA 1 mbxCommand 2 sli_flag 3 flag ACTION None required elx_mes2530 Mailbox command lt vpi gt cannot issue DESCRIPTION The SLI layer in the driver is inactive DATA 1 mb mbxCommand 2 sli flag 3 flag ACTION None required elx_mes2531 Mailbox command lt cpi gt cannot issue DESCRIPTION DATA 1 mb mbxComman4d 2 sli_flag 3 flag ACTION None required Driver for VMware ESX 4
54. e ACTION None required elx_mes2007 Only Limited Edition cmd Format supported lt iocb ulpCommand gt DESCRIPTION SLI 4 only supports the Limited Edition command format DATA None ACTION None required elx_mes2008 Error lt rc gt posting all rpi headers DESCRIPTION The RPI headers could not be posted to the firmware DATA None ACTION None required elx_mes2009 Failed to allocate mbox for ADD_FCF cmd DESCRIPTION Failed to allocate mailbox for ADD FCF command DATA None ACTION None required elx_mes2010 Resume RPI Mailbox failed status lt status gt mbxStatus lt mbx status gt DESCRIPTION DATA None ACTION None required elx_mes2011 Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command PTION Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command DATA None ACTION None required elx mes2012 Mailbox failed mbxCmd lt mbx_cmd gt READ CONFIG mbxStatus lt mbx status gt DESCRIPTION The READ_CONFIG mailbox command failed DATA None ACTION None required elx_mes2013 Could not manually add FCF record 0 status lt rc gt DESCRIPTION Could not add FCF record to the FCF list DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 51 SE EMULEX elx mes2014 Invalid command lt iocb ulpCommand gt DESCRIPTION The IOCB command is invalid DATA None ACTION None required elx_mes2015 Invalid CT x command
55. e a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0446 Adapter failed to init mbxCmd lt mbxCommand gt CFG_RING mbxStatus lt mbxStatus gt ring lt num gt DESCRIPTION Adapter initialization failed when issuing a CFG_RING mailbox command DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 34 SE EMULEX elx_mes0448 Adapter failed to init mbxCmd lt mbxCommand gt READ SPARM mbxStatus lt mbxStatus gt DESCRIPTION Adapter initialization failed when issuing a READ SPARM mailbox command DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0449 Phys attribute Instance Error Defaulting to Ipfc attr to d Allowed range is min max DESCRIPTION A physical device attribute has an out of range value The driver is correcting it DATA 1 value written 2 minimum value 3 maximum value ACTION Write the default value elx_mes0450 Ipfc_ attr attribute cannot be set to d allowed range is min max DESCRIPTION Sysfs attribute value written exceeds attribute range DATA 1 attribute name 2 value written 3 minimum value 3 maximum value ACTION Write a value within the supported range elx_mes0453 Adapter failed
56. e a target is in error or may point to transient network connectivity issues It may also indicate a BladeEngine firmware error The be2iscsi driver did not receive an iSCSI command window update for up to 25 seconds during I O operations Following this error log entry the next entry will indicate the session handle and the iSCSI parameters MaxCmdSN and ExpCmdsSN respectively Check for any errors reported at the target The iSCSI Initiator is only supported with certified Targets Check for software updates at the target vendor s website If the above fails contact your technical support Driver for VMware ESX 4 1 Troubleshooting Section Page 69 SE EMULEX Table 8 iSCSI Error Log Code Entries Continued Message Recommend Resolution A connection to the target was lost for a period exceeding the Extended Timeout ETO The error log entry immediately following this entry will indicate the session ID or the target that lost the connection There will be event log entries from the disk subsystem indicating that the drives were lost If any I Os were in progress the system may see I O errors or failures Check the connection to the target or the state of the target device If the target is made available any sessions that existed previously will be reestablished and the devices will be available for VO The be2iscsi driver received a Task Management Function that is not supported and re
57. e channels wide The driver prints this warning if it finds the device in a slower or narrower PCl e slot The device continues to work with lesser performance Warning Command to get pause frame set The firmware command to get PAUSE tings failed settings failed Warning Command to set pause frame set The firmware command to change PAUSE tings failed settings failed Warning Command to apply MAC address Driver could not set the MAC address filter on filter failed the hardware The device continues to work There may be an impact on the performance Warning Command to delete MAC address The firmware command to delete a MAC filter failed address filter failed The device should continue to work Warning Unable to get Firmware Version The command to get firmware revision number failed The version number is not shown The device must continue to work Warning Did not receive completions for While unloading the driver some outstanding all TX requests transmit requests are found This is an indication that the hardware is not functioning properly Warning Failed to register char device Could not create the char device used for certain management functions The driver must still work You may not be able to use HBACMD to interact with the device Driver for VMware ESX 4 1 Troubleshooting Section Page 66 Table 6 ESX Server NIC Event Log Entries Continued SE EMULEX Severity Message Displayed
58. e ee Ge a ee EG 1 Supported FeatureS ees ee ee ee AR EE Ee ee ee AA ee ee ee ee ee AAR ee ee ee ee ee eke ee ee ee 1 New Features in this Release ee ee ee 1 Preieduisites ee RA ED ED Ge Ee 2 eie ulle RE OE OE EE 2 Things to Know Before You Download iese esse ees ee teeta 2 KNOWN ISSUES EE iae aaaRa 2 Installing the FC FCOE Driver ees esse ee ee ee ee nn ee ee ee ee ee ee EEEE ee ee ee ee 2 Tal cele Te fe EE ia Aaa AEE aE AEA 2 Installing the FC FCoE Driver and Management Software iss sesse ees 2 Uninstalling the FC FCOE Driver sees esse esse ee ee ee ee ee ee ee ee 2 Installing the FC FCOE Utilities ee 3 Uninstalling the FC FCOE Utilities ee ee 3 Installing the NIC and iSCSI Drivers ee ee ee ee ee ee 3 IMUPOGU CUOM ER ER EO N 3 Installing the NIC and iSCSI Drivers and Management Software 4 Uninstalling the NIC and iSCSI Drivers ee ee 4 Virtualization FeatureS iese ees ee ee ee ee AAR ee ee ee ee ee AAR ee ee ee ee ee ee RR ee ee ee ee ee ee 4 Enabling the NetQueue Feature sesse ee Ee ee ee ee AAR ee ee ee ee ee ee RR ee ee ee 4 Creating and Naming Interfaces in ESX Server 4 Contiguniing VEANS Ee ED EE EDE a GE ARE ee Ee ee Ee Gee ee 5 Configuring Network Heap Size in ESX Server ede ee ee ee ee ee ee ee ee ee ee ee ee ee ee 5 Interrogating the NIC Driver iii eek ee ee ee AAR ee ee ee ee ee RR ee ee ee ee ee 5 Configuration DE N tess EE Ed N
59. e or Documentation described herein at any time without notice INNO EVENT SHALL EMULEX AND ITS LICENSORS BE LIABLE FOR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE DATA OR PROFITS WHETHER IN AN ACTION OF CONTRACT NEGLIGENCE OR OTHERWISE ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF SOFTWARE DOCUMENTATION OR PROVISION OF OR FAILURE TO PROVIDE SERVICES RESTRICTED RIGHTS LEGEND The Software may be provided to units or agencies of the U S government only as commercial computer software restricted computer software or with restricted rights as defined in Driver for VMware ESX 4 1 EULA Page 73 SE EMULEX applicable regulations and may not be provided as source code Manufacturer is Emulex Design amp Manufacturing Corporation 3333 Susan St Costa Mesa CA 92626 TRADEMARKS COPYRIGHT NOTICE Emulex or Emulex products referenced herein are either trademarks or registered trademarks of Emulex Copyright 2006 Emulex or its licensors All rights reserved CHOICE OF LAW SEVERABILITY The laws of the State of California without giving effect to its conflicts of laws principles govern all matters arising out of or relating to this License Agreement including without limitation its validity interpretation construction performance and enforcement If any term or condition of this Agreement is held invalid illegal or unenforceable by a court of competen
60. ed elx_mes0396 The Ipfc dmabuf allocation failed DESCRIPTION The asynchronous link event handler could not allocate a DMA buffer for the mailbox command to issue the READ_LA read link attention mailbox command DATA None ACTION None required elx_mes0397 The mbuf allocation failed DESCRIPTION The asynchronous link event handler could not allocate DMA able memory for the READ_LA mailbox command DATA None ACTION None required elx_mes0398 Invalid link fault code lt hex link_fault gt DESCRIPTION The attempt to read the link attention register has returned an unknown value DATA None ACTION None required elx_mes0399 Invalid link attention type lt hex link_type gt DESCRIPTION The READ_LA mailbox command has returned an invalid link type DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 31 SE EMULEX Initialization Events 0400 0599 elx mes0400 Phys Attribute Count Exceeded Max d Actual d DESCRIPTION Too many driver configuration parameters have been set The limit is given as Max DATA 1 Maximum number 2 Actual number ACTION Reduce the number of actual parameters elx_mes0402 Cannot find virtual addr for buffer tag on ring lt ringno gt DESCRIPTION A DMA buffer is not available for this unsolicited command DATA 1 tag 2 next 3 prev 4 postbufq_cnt ACTION None required elx_mes0403 Ipfc nodev tmo attribute cannot be set
61. ed to indicate that a port was created in the system It is displayed at this level to ensure it is always appears at all log levels DATA None ACTION No action informational elx_mes1826 Vport Disabled DESCRIPTION The port had to be disabled in the system DATA None ACTION No action informational elx_mes1827 Vport Enabled DESCRIPTION The port had to be enabled after possible recovery from some errors DATA None ACTION No action informational elx_mes1828 Vport Deleted DESCRIPTION A VPort was deleted DATA None ACTION No action informational elx_mes1829 CT command failed to delete objects on fabric DESCRIPTION A command issued to the fabric to delete an associated resource for an object such as for a port failed DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1830 Signal aborted mbxCmd lt command gt DESCRIPTION A pending mailbox command was aborted because the thread received a signal DATA None ACTION The command is retried Driver for VMware ESX 4 1 Troubleshooting Section Page 49 SE EMULEX elx mes1831 Create VPORT Interrupted DESCRIPTION The port creation process was unexpectedly interrupted at a critical time and the operation was unsuccessful DATA None ACTION The process was interrupted while creating a VPort Retry the command elx mes1832 No pending MBOX command to handle DESCRIPTION DATA No
62. elx_mes1803 Bad hbd tag Data lt tag gt lt count gt DESCRIPTION An error occurred when processing queue related tags for an adapter in a particular slot DATA 1 tag 2 buffer_count ACTION Software driver error If this problem persists report these errors to Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 46 5G EMULEX elx_mes1804 Invalid asynchrous event code lt evt code gt DESCRIPTION The asynchronous event code that the firmware passed to the driver is invalid DATA None ACTION None required elx_mes1805 Adapter failed to init Data lt command gt lt status gt lt queue num gt DESCRIPTION An error occurred when processing queue related tags for an adapter in a particular slot DATA 1 mbxCommand 2 mbxStatus 3 hbaqno ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1806 Mbox lt command gt failed No vport DESCRIPTION A mailbox command could not be communicated because there was no VPort associated with the mailbox command DATA 1 mbxCommand ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1807 IOCB lt value gt failed No vport DESCRIPTION An IOCB command could not be communicated because there was no VPort associated with the mailbox command DATA 1 ulpCommand ACTION Software driver error If this problem persists report these errors to Tec
63. esse ee ee ee ee ee ee ee ee ee ee ee 69 Additional iSCSI Driver MessageS ie ee ee ee ee ee ee 70 EMULEX END USER LICENSE AGREEMENT ee 73 Driver for VMware ESX 4 1 User Manual Page iv SE EMULEX Installation Driver Information Supported Features e Supports the Emulex OCe10100 family of UCNAs e Supports dynamic and permanent driver parameter setting using the OneCommand Manager application version 5 from Emulex This is a GUI and CLI based configuration utility used as part of a master kit enabling driver configuration including Out of band TCP IP remote SAN management capability Diagnostics loopback and diagnostic dump except for OCe1010x LUN logical unit number masking Virtual port VPort support See the OneCommand Manager User Manual for a complete list of supported features e Supports the following protocols e NIC e FCoE Fibre Channel over Ethernet e iSCSI e Fibre Channel initiator mode SCSI FCP e FCP 2 e SNIA CTP compliant SMI S 1 1 Provider e Supports the following topologies e FC AL Fibre Channel Arbitrated Loop For non UCNA adapters only e Point to point e Fabric with auto topology negotiation e Supports FC in band management e 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 e Support for Common HBA API e Batch firmware download capability e PCI hot plug support vendor specific e VPD
64. figuring LDTO and ETO The following table lists the default values of LDTO and ETO on ESX 4 1 and the limits within which they can be configured Table 2 Configuring LDTO and ETO Value Default Min Max LDTO 20 secs 0 secs 30 secs ETO 30 secs 20 secs 30 secs a the value of 0 secs is allowed but will internally translate to 20 secs The ETO value can be configured on a per target basis using the OneCommand Manager CLI User s Manual See the OneCommand Manager CLI User s Manual for details on configuring ETO ETO settings configured using the OneCommand Manager CLI are persistent across reboots driver upgrades and operating system upgrades If the ETO is set for a target using the OneCommand Manager CLI it must be modified or removed from within the OneCommand Manager CLI Driver for VMware ESX 4 1 Configuration Section Page 12 SE EMULEX The following command line shows how to configure the driver with LDTO value as 25 secs vmkload mod be2iscsi ldto 25 To configure ESX Server to load the iSCSI driver with this value after each reboot run the following commands and reboot the system esxcfg module s ldto 25 be2iscsi usr sbin esxcfg boot r reboot Error Handling Under MultiPath MPIO and Cluster Configurations In an MPIO or cluster configuration fault tolerant software is present on the system that makes the iSCSI driver error handling redundant These configurations
65. firmware or hardware problem Report these errors to Technical Support elx_mes0323 Unknown Mailbox command lt mbxCommand gt Cmpl DESCRIPTION A unknown mailbox command completed DATA None ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support elx_mes0324 Config port initialization error mbxCmd lt mbxCommand gt READ_NVPARM mbxStatus lt mbxStatus gt DESCRIPTION A read nvparams mailbox command failed during port configuration DATA None ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support elx_mes0330 IOCB wake NOT set DESCRIPTION The completion handler associated with the IOCB was never called DATA 1 timeout 2 timeleft jiffies ACTION This error could indicate a software driver firmware or hardware problem If the problem persists report the error to Technical Support elx_mes0334 Unknown IOCB command DESCRIPTION Received an unknown IOCB command completion DATA 1 type 2 uIpCommand 3 ulpStatus 4 ulploTag 5 ulpContext ACTION This error could indicate a software driver or firmware problem If these problems persist report these errors to Technical Support elx_mes0335 Unknown IOCB command DESCRIPTION Received an unknown IOCB command completion DATA 1 ulpCommand 2 ulpStatus 3 ulploTag 4 ulpContext ACTION This error could indic
66. go beyond driver bmask dimension DESCRIPTION Adapter reports an FCF record index goes beyond the driver s internal resource dimension for the bmask DATA None ACTION Inform Emulex about this elx_mes2763 Failed to allocate mempool for read FCF record mbox command DESCRIPTION The driver failed to allocate memory from the mempool for issuing an FCF read mailbox command during the round robin FCF failover DATA None ACTION None required elx_mes2772 Failed to issue FCF rediscovery mailbox command due to dead FCF DESCRIPTION The driver wanted to send an FCF rediscovery mailbox command to start fast FCF failover due to a dead FCF asynchronous event but failed to send the mailbox command due to state of the adapter DATA None ACTION None required elx_mes2774 Failed to issue FCF rediscovery mailbox command due to CVL DESCRIPTION The driver wanted to send an FCF rediscovery mailbox command to start fast FCF failover due to a Clear Virtual Link asynchronous event but failed to send the mailbox command due to state of the adapter DATA None ACTION None required NIC Troubleshooting This section includes NIC troubleshooting information Table 5 General Driver Situations NIC Problem Answer Solution 1 When there is a great deal of network This could be due to low configured value for traffic in some VMs a few VMs appear netPktHeapMaxSize Try increasing it to a higher value To read to have lost ne
67. gured to run in SLI 2 mode Nevertheless it is recommended to use the auto setting 0 elx_mes1821 Create VPORT failed Invalid WWN format DESCRIPTION The port could not be created due to an invalid WWNN or WWPN format DATA None ACTION Provide a valid WWN when creating VPorts elx_mes1822 Invalid lt name gt lt xx XX XX XX XX XX XX XX gt DESCRIPTION An invalid WWN was used when creating a VPort DATA 1 type name 2 wwn 1 3 wwn 3 3 wwn 5 4 wwn 7 ACTION When creating a VPort you must furnish a valid WWN Driver for VMware ESX 4 1 Troubleshooting Section Page 48 5G EMULEX elx_mes1823 Create VPORT failed Duplicate WWN on HBA DESCRIPTION The port could not be created because it would duplicate an existing WWNN adapter address The resources for the port had to be discarded DATA None ACTION Provide a WWN that is unique elx_mes1824 NPIV enabled Override Ipfc sli mode parameter lt mode gt to auto 0 DESCRIPTION The Ipfc_enable_npiv and Ipfc sli mode driver parameter settings conflict The adapter must be configured for SLI 3 mode to support NPIV DATA 1 Ipfc sli mode ACTION This is an informational message that indicates that the Ipfc enable npiv and Ipfc sli mod parameter settings are not compatible Resolve the parameter conflict by setting the SLI mode to 0 or 3 or if SLI 2 mode is required then disable NPIV elx_mes1825 Vport Created DESCRIPTION This message is display
68. hnical Support elx_mes1808 Create VPORT failed NPIV is not enabled SLImode lt mode gt DESCRIPTION The driver failed to create a port because the adapter was in wrong mode or was not capable of NPIV DATA 1 sli_rev ACTION Load the driver with npiv enabled on an adapter that supports SLI 3 elx_mes1809 Create VPORT failed Max VPORTs lt vpi gt exceeded DESCRIPTION The driver failed to create a port because the maximum number of port supported by the driver is exceeded DATA 1 max_vpi ACTION No Action The driver can not create any more VPorts elx_mes1810 Create VPORT failed Cannot get instance number DESCRIPTION The driver failed to allocate resources for an adapter and could not assign an instance number DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1811 Create VPORT failed vpi x lt vpi gt DESCRIPTION The driver failed to create a port and had to eliminate all its resources DATA 1 vpi ACTION Software driver error If this problem persists report these errors to Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 47 5G EMULEX elx_mes1812 vport_delete failed Cannot delete physical host DESCRIPTION An attempt to delete a port failed because it was to delete a physical port and not a virtual port Only VPorts on physical ports can be deleted on an NPIV system DATA None ACTION Software driver e
69. icating that the drives were lost If any I Os were in progress the system may see I O errors or failures Check the links to the OneConnect UCNA If the link is reestablished any sessions that existed previously will be reestablished and the devices will be available for I O Both Port 0 and Port 1 links are down Check the links to the OneConnect UCNA Additional iSCSI Driver Messages The following error messages are returned when you specify illegal options when loading the driver WARNING dic value d out of range Valid Range is 0 1 Using Default Value 1 WARNING eto value d out of range Valid Range is 0 30 Using Default Value 30 WARNING Idto value d out of range Valid Range is 0 30 Using Default Value 30 WARNING ios_per_ctrl value d out of range Valid Range is 1 512 Using Default Value 512 WARNING max io size value d out of range Valid Range is 4 256 Using Default Value 256 WARNING tmf reset value d out of range Valid Range is 1 3 Using Default Value 1 Driver for VMware ESX 4 1 Troubleshooting Section Page 70 SE EMULEX WARNING ddm value d out of range Valid Range is 0 1 Using Default Value 0 WARNING dic value d out of range Valid Range is 0 1 Using Default Value 1 d represents a signed integer outside the valid range The driver will return a number in the actual warning message Any other messages
70. jected this request the error log entry immediately following this entry will indicate the TMF function code that was rejected The be2iscsi driver encountered a mismatched version of the firmware running on the board This error may be followed by more error codes 0x31840001 of 0x31880001 indicating that the be2iscsi driver failed to load The operating system version is not supported This failure indicates that the driver version that is running on the system does not match the version of the firmware flashed on the board See Installing the NIC and iSCSI Drivers and Management Software on page 4 Downgrade the driver to a version that is compatible with the firmware version currently on the adapter Then reboot the server and follow the firmware upgrade procedure as appropriate Finally upgrade the driver to a version that is compatible with the new version of firmware The be2iscsi driver detected a failure in the hardware during initialization This error may be followed by more error codes 0x31840001 or 0x31880001 indicating that the be2iscsi driver failed to load This failure indicates that the hardware has not been initialized or is malfunctioning this may also indicate that the firmware is not running correctly Both Port 0 and Port 1 links were down for a period exceeding the Link Down Timeout LDTO If the initiator has connection to the target there will be event log entries from the disk subsystem ind
71. ler timed out waiting for abort to complete DATA None ACTION None required Node Table Events 0900 0999 elx_mes0915 Register VPI failed lt mbxStatus gt DESCRIPTION Could not register the VPI DATA None ACTION None required Miscellaneous and FCoE Events 1200 1299 elx_mes1262 Failed to allocate dfc_host DESCRIPTION Could not allocate memory the dfc_host_struct DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 41 gt EMULEX Link Events 1300 1399 elx_mes1303 Link Up Event lt eventTag gt received Data x x x x x x X Xx X X X Xx Vd DESCRIPTION A link up event was received It is also possible for multiple link events to be received together DATA 1 fc eventTag 2 granted AL PA 3 UlnkSpeed 4 alpa_map 0 ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network elx mes1305 Link Down Event lt eventTag gt received Data x x x x x x DESCRIPTION A link down event was received DATA 1 fc eventTag 2 hba state 3 fc flag ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network elx mes1306 Link Up Event in loop back mode lt eventTag gt received Data x x x x x x x X DESCRIPTION Link up notification configured for loopback DATA 1 fc eventTag 2 granted AL PA 3 UlnkSpeed 4 alpa_map 0 ACTION None required elx_mes1308
72. letion queue DATA None ACTION None required elx_mes0366 Not a valid fast path completion event majorcode lt major code hex gt minorcode lt minor code hex gt DESCRIPTION The major or minor code in the Event Queue field is not valid DATA None ACTION None required elx_mes0367 Fast path completion queue does not exist DESCRIPTION The fast path completion queue referenced by the CQID does not exist DATA None ACTION None required elx_mes0368 Miss matched fast path completion queue identifier eqcqid lt cqid gt fcpcqid lt queue_id gt DESCRIPTION The CQID in the event queue entry does not match the fcp_cqid that was passed into the routine DATA None ACTION None required elx mes0369 No entry from fast path completion queue fepcqid lt queue_id DESCRIPTION There were no completions in the completion queue referenced by fcpcqid DATA None ACTION None required elx_mes0370 Invalid completion queue type lt type gt DESCRIPTION The event queue entry is not for a mailbox or a work queue entry DATA None ACTION None required elx_mes0371 No entry from the CQ identifier lt queue_id gt type lt type gt DESCRIPTION There was no completion queue event for this event queue entry DATA None ACTION None required elx_mes0372 iotag lt iotag gt is out of range max iotag lt sli last_iotag gt DESCRIPTION The IOCB lookup cannot be performed because the iocb_tag is out of range DA
73. llocate mbox cmd memory DESCRIPTION Mailbox allocation error DATA None ACTION None required elx_mes0285 Allocated DMA memory size lt alloclen gt is less than the requested DMA memorysize lt reqlen gt DESCRIPTION Memory allocation was truncated DATA None ACTION None required elx_mes0286 Ipfc_nlp_state_cleanup failed toallocate statistical data buffer lt nlp_DID gt DESCRIPTION Memory allocation failed for node s statistical data DATA None ACTION None required elx_mes0287 Ipfc_alloc_bucket failed to allocate statistical data buffer lt nlp_DID gt DESCRIPTION Memory allocation failed for node s statistical data DATA None ACTION None required elx_mes0288 Unknown FCoE event type lt event_type gt event tag lt event_tag gt DESCRIPTION The firmware has detected an unknown FCoE event DATA None ACTION Check the FCoE switch configuration and the adapter DCBX mode elx_mes0289 Issue Register VFI failed Err lt rc gt DESCRIPTION The driver could not register the virtual fabric Index for the FCFI DATA None ACTION Check the switch and port configurations Driver for VMware ESX 4 1 Troubleshooting Section Page 23 SE EMULEX elx mes0290 The SLI4 DCBX asynchronous event is not handled yet DESCRIPTION The SLI 4 DCBX asynchronous event is not handled yet DATA None ACTION None reguired elx mes0291 Allocated DMA memory size salloc len is less than the requested DMA memorysize
74. lt iocb ulpCommand gt DESCRIPTION Invalid Command Type in the IOCB is not supported DATA None ACTION None required elx_mes2017 REG FCFI mbxStatus error lt mbx status gt HBA state sport state DESCRIPTION The REG FCFI mailbox command has failed DATA None ACTION None required elx_mes2018 REG_VFI mbxStatus error lt mbx status gt HBA state lt port_state gt DESCRIPTION The REG_VFI mailbox command has failed DATA None ACTION None required elx_mes2020 Failed to allocate mbox for ADD_FCF cmd DESCRIPTION Failed to allocate mailbox for ADD FCF command DATA None ACTION None required elx_mes2022 INIT VPI Mailbox failed status lt status gt mbxStatus lt mbxStatus gt DESCRIPTION The INIT VPI mailbox command has failed DATA None ACTION None required elx_mes2401 Failed to allocate memory for ELS XRI management array of size lt els_xri_cnt gt DESCRIPTION Initialization failed to allocate memory for the ELS XRI management array DATA None ACTION None required elx mes2500 EQ CREATE mailbox failed with status lt shdr_status gt add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to create the event gueue has failed DATA None ACTION None reguired elx mes2501 CA CREATE mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to create the completion queue has faile
75. mes2598 Adapter Link is disabled DESCRIPTION The adapter link is disabled DATA None ACTION None required elx_mes2599 Adapter failed to issue DOWN LINK mbox command rc lt re gt DESCRIPTION The adapter failed to issue a DOWN_LINK mailbox command DATA None ACTION None required elx_mes2600 Ipfc_sli_read_serdes_param failed to allocate mailbox memory DESCRIPTION Failed to allocate mailbox memory DATA None ACTION None required elx_mes2605 Ipfc_dump_static_vport memory allocation failed DESCRIPTION Memory allocation failed DATA None ACTION None required elx_mes2606 No NPIV Fabric support DESCRIPTION No NPIV fabric support DATA None ACTION None required elx_mes2607 Failed to allocate init_vpi mailbox DESCRIPTION Failed to allocate init_vpi mailbox DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 60 gt lt EMULEX elx_mes2608 Failed to issue init_vpi mailbox DESCRIPTION Failed to issue init_vpi mailbox DATA None ACTION None required elx_mes2609 Init VPI mailbox failed lt u mb mbxStatus gt DESCRIPTION Initialization of VPI mailbox has failed DATA None ACTION None required elx_mes2610 HBA FCF index goes beyond driver s resource dimension DESCRIPTION During updating the round robin FCF bmask the FCF index goes beyond the driver s internal resource dimension DATA None ACTION None required elx mes2611 UNREG_
76. n integer To search the log file for error messages at the command prompt type cd var log vim vmkernel For example you may see the following message Sep 9 19 48 04 esx server vmkernel BladeEngine 2 iSCSI Driver The be2iscsi driver received a Task Management Function that is not supported and rejected this request The error log entry immediately following this entry will indicate the TMF function code that was rejected Driver for VMware ESX 4 1 Troubleshooting Section Page 68 iSCSI Error Log Code Entries SE EMULEX The following is a brief description of the error log codes generated by the iSCSI driver It includes the message displayed the meaning of the message and the recommended resolution Table 8 iSCSI Error Log Code Entries Message Recommend Resolution The be2iscsi driver failed to load because initialization failed during a power management bootup This failure may be due to the firmware not being present or not being running currently This failure may also indicate a hardware problem The be2iscsi driver failed It was unable to map one or more PCI Base Address Registers and hence failed to load This failure may indicate a low memory condition or a hardware error The be2iscsi driver ignored a configuration entry as the entry was invalid Check the registry configuration for any new entries added for Driver Parameters The invalid ent
77. ne ACTION ELS Events 1833 2800 elx mes1835 Vport discovery quiesce failed state sport state fc flags lt fc_flag gt wait msecs lt jiffies_to_msecs jiffies start time DESCRIPTION Could not pause discovery on this VPort DATA None ACTION None reguired elx mes1836 Could not issue unreg login all rpis status lt rc gt DESCRIPTION The unreg login cannot be issued DATA None ACTION None reguired elx mes1837 vport delete failed Cannot delete static vport DESCRIPTION Static VPorts cannot be deleted DATA None ACTION None required elx_mes1838 Failed to INIT_VPI on vpi lt vpi gt status lt rc gt DESCRIPTION Failed to INIT_VPI DATA None ACTION None required elx_mes2000 Failed to allocate mbox for READ_FCF cmd DESCRIPTION Failed to allocate mbox for READ_FCF command DATA None ACTION None required elx_mes2001 Unable to allocate memory for issuing SLI_CONFIG_SPECIAL mailbox command DESCRIPTION Unable to allocate memory for issuing the SLI_CONFIG_SPECIAL mailbox command DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 50 5G EMULEX elx_mes2002 Error Could not grow rpi count DESCRIPTION An error occurred because the RPI count could not be increased DATA None ACTION None required elx_mes2005 Unable to deregister pages from HBA lt rc gt DESCRIPTION The SGL pages could not be unregistered from the firmware DATA Non
78. nges that impact all adapters in the system global changes follow these steps See FC FCoE Driver Configuration Parameters on page 8 for parameter names and values Parameter values are in both hexadecimal and decimal 1 From the Console Operating System COS terminal window type esxcfg module s param value param2 value driver name gt The lt driver_name gt is obtained from the vmkload mod 1 call Look for the Ipfc prefix 2 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 the VMware vSphere client or Virtual Center Server Refer to the VMware documentation for more information Driver for VMware ESX 4 1 Configuration Section Page 6 SE EMULEX Example of Permanent Global Configuration The following example sets lun dueue depth the maximum number of commands that can be sent to a single LUN to 20 default is 30 for all Emulex adapters in your system 1 Locate the parameter Ipfc_lun_queue_depth in Table 1 on page 8 2 Setthe permanent value Type esxcfg module s lpfc lun queue depth 20 lpfc820 3 Reboot the server Type reboot The new setting is used when the driver reloads To verify the setting type esxcfg module g 1pfc820 Example of Permanent Per Adapter Configuration The following
79. ns provided on the VMware support Web site See the OneCommand Manager Command Line User Manual for instructions on installing the Emulex core kit Note Before installing the Emulex elxocmcore kit you must install the Ipfc driver from the VMware Web site Note 1 Install the OneConnect network driver 2 Install the OneConnect iSCSI driver 3 Update the Ipfc driver 4 Install or update the Emulex core kit 5 Update the firmware 6 Reboot the system Uninstalling the NIC and iSCSI Drivers See the VMware support site for instructions Virtualization Features For the best performance you must install VMware Tools in each guest operating system For information on installing VMware Tools in a Linux or Windows guest operating system refer to the VMware ESX Server 4 1 documentation Enabling the NetQueue Feature To use the multiple interface feature in ESX Server you must enable the NetQueue feature It is disabled by default e To check if NetQueue is enabled run the following command from the ESX Server console esxcfg advcfg j netNetqueueEnabled If it prints netNetqueueEnabled FALSE the feature is disabled To enable NetQueue run the following command esxcfg advcfg k TRUE netNetqueueEnabled Reboot the ESX Server for the change to take effect Creating and Naming Interfaces in ESX Server The NIC driver supports a maximum of four UCNAs per system For dual channel UCNAs running in
80. onfiguration Parameters Variable Default Min Max Dynamic Comments Ipfc_hba_queue_depth 8192 32 8192 No Maximum number of FCP commands that can queue to an Emulex adapter The value cannot exceed what the adapter supports Ipfc_ackO 0 Off 1 On No Use ACKO for class 2 Ipfc_discovery_threads 32 64 No Specifies the maximum number of PLOGI commands that can be outstanding for a discovery Ipfc_fcp_class No FC class for FCP data transmission Ipfc fdmi on Yes 0 disabled 1 support FDMI without attribute of hostname 2 support FDMI with attribute of hostname Ipfc link speed O 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 Ipfc_log_verbose 0x0 0x0 Ox7fffffff Yes Extra activity logging bit mask Ipfc lun agueue depth 30 128 Yes Default max commands sent to a single logical unit disk Ipfc max scsicmpl time 60000 Yes Limits SCSI command completion time in mS to control I O queue depth The default 0 means the SCSI layer maintains control Ipfc_pci_max_read 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 automatically determines the correct value This
81. pport elx_mes0535 Failed setup of fast path FCP WO lt fcp_wqidx gt rc lt rc gt DESCRIPTION The fast path FCP WO setup failed DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0536 Slow path ELS WQ not allocated DESCRIPTION The slow path ELS WO is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0538 Slow path MQ not allocated DESCRIPTION The slow path MQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0539 Failed setup of slow path MQ rc 0x x DESCRIPTION The slow path MQ is allocated but failed initial setup DATA 1 status ACTION The driver fails to load Contact Emulex Technical Support elx_mes0540 Receive Queue not allocated DESCRIPTION The Receive Queue is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0541 Failed setup of Receive Queue rc 0x x DESCRIPTION The Receive Queue is allocated but failed setup DATA 1 status ACTION The driver fails to load Contact Emulex Technical Support elx mes0542 Ipfc_create_static_vport failed to allocate mailbox memory DESCRIPTION Failed to allocate mailbox memory for VPort creation DATA None ACTION Static VPorts does not load Contact Emulex Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 39 SE EMULEX elx mes05
82. rants the party receiving the Software or Documentation the Licensee a personal worldwide nontransferable nonexclusive royalty free right and license to use the Software or Documentation only with Emulex hardware products and without circumventing any security or rights management feature Any rights not expressly granted herein are reserved This License Agreement terminates when the Licensee no longer rightfully possesses the associated Emulex hardware product s ceases using the Software and Documentation or breaches any provision of this License Agreement The Licensee hereunder shall not 1 reverse engineer reverse compile or reverse assemble all or any part of the Software 2 disseminate performance information or analysis to any third party other than solely for product support purposes from any source relating to the Software or cause or permit others to do either of both of the foregoing The Licensee agrees to prevent any unauthorized copying of the Software In addition permission to use Documentation is granted provided that 1 the below copyright notice and this permission notice appears on all copies 2 use of such Documentation is for informational and non commercial or personal use only 3 the Documentation is not copied or posted on any network computer or broadcast in any media to make it available to third parties and 4 no modification of any Documentation is made Any use reproduction or redistribution of the Softwa
83. rce DESCRIPTION Initialization failed to set up driver resource DATA None ACTION None required elx_mes1413 Failed to initialize iocb list DESCRIPTION Initialization failed to initialize the IOCB list DATA None ACTION None required elx_mes1414 Failed to set up driver resource DESCRIPTION Initialization failed to set up driver resource DATA None ACTION None required elx_mes1415 Failed to create scsi host DESCRIPTION Initialization failed to create SCSI host DATA None ACTION None required elx_mes1416 Failed to allocate sysfs attr DESCRIPTION Initialization failed to sysfs attribute DATA None ACTION None required elx mes1418 Invalid HBA PCl device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx_mes1419 Invalid HBA PCl device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx mes1420 Invalid HBA PCl device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 44 5G EMULEX elx_mes1421 Failed to set up hba DESCRIPTION Initialization failed to set up the adapter DATA None ACTION None required elx_mes1422 HBA Unrecoverable error uerr_lo_reg lt ue lo gt uerr_hi_reg lt ue hi gt online0_reg lt Online0 gt online1
84. re automatically added to the system console log You can examine the var log vmkernel file to see any of these messages If you have concerns the best policy is to execute a vm support dump and push it to the VMware Emulex support staff 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 reduire a single block of 100 message numbers however some groups INIT FCP require two blocks Table 4 the Message Log table shows the groups and defines the associated number ranges Table 4 Message Log Table SN From To Verbose Verbose Description Definition Pit LOG ELS 0100 0199 0x1 ELS events LOG_DISCOVERY 0200 0299 0x2 Link discovery events LOG_SLI 0300 0399 0x800 SLI events LOG_MBOX 0300 0339 0x4 Mailbox events LOG_TEMP 0340 0347 0x100 Temperature sensor events LOG INIT 0400 0599 0x8 Initialization events LOG_FCP 0700 0799 0x40 FCP traffic history Reserved 0800 0899 LOG_NODE 0900 0999 0x80 Node table events Reserved 1000 1099 Reserved 1100 1199 LOG_MISC 1200 1299 0x400 Miscellaneous and FCoE events LOG_FCoE LOG_LINK_EVENT 1300 1399 0x10 Link events Reserved 1400 1499 Reserved 1500 1599 LOG_LIBDFC 1600 1699 0x2000 IOCTL events LOG_VPORT 1800 1832 0x4000 NPIV events Driver for VMware ESX 4 1 Troubleshooting Section Page 15 5G
85. re or Documentation not in accordance with the License Agreement is expressly prohibited by law and may result in severe civil and criminal penalties The Licensee accepts the terms of this License Agreement by downloading or initial use of a product containing the Software or Documentation Copying or reproduction of the Software or Documentation to any other server or location for further reproduction or redistribution to third parties is expressly prohibited unless specifically authorized in writing by Emulex THE SOFTWARE IS WARRANTED IF AT ALL ONLY ACCORDING TO THE TERMS OF THE LICENSE AGREEMENT EXCEPT AS SPECIFIED IN THE LICENSE AGREEMENT EMULEX HEREBY DISCLAIMS ALL EXPRESS IMPLIED AND STATUTORY WARRANTIES WITH REGARD TO THE SOFTWARE INCLUDING BUT NOT LIMITED TO ALL WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE TITLE AND NON INFRINGEMENT EMULEX AND ITS LICENSORS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY FOR ANY PURPOSE OF THE INFORMATION CONTAINED IN THE DOCUMENTATION ALL SUCH DOCUMENTATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EMULEX AND ITS LICENSORS HEREBY DISCLAIM ALL EXPRESS IMPLIED AND STATUTORY WARRANTIES WITH REGARD TO THIS INFORMATION INCLUDING ALL WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE TITLE AND NON INFRINGEMENT The Documentation could include technical inaccuracies or typographical errors Emulex and its licensors reserve the right to make changes to the Softwar
86. rface Manual for instructions on how to install on the ESXCOS Note Before installing the Emulex elxocmcore kit you must install the Ipfc driver from the VMware Web site Note Before installing OneConnect network driver and management software verify that the firmware version is current If it is proceed with the installation If it is not update the firmware using the OneCommand Manager application and reboot your system before proceeding with the installation Uninstalling the FC FCoE Driver See the VMware Patch Download page for instructions Driver for VMware ESX 4 1 Installation Section Page 2 5G EMULEX Installing the FC FCOE Utilities Follow these instructions to install the OneCommand Manager CLI To install the OneCommand Manager agent 1 2 Log in as root Copy the elxocmcore esx41 lt kit version gt x86_64 rpn file to a directory on the install machine CD to the directory to which you copied the RPM file Install the RPM file Type rpm U elxocmcore esx41 lt kit version gt x86 64 rpm For example rpm U elxocmcore esx41 5 0 643 6 1 x86 64 rpm The RPM file contents are installed in usr sbin nbanyware The CLI utility is also located in this directory Note For VMware ESX Server systems the firewall on the ESX Server must be opened to manage systems remotely using TCP IP To enable TCP port 23333 run the following commands esxcfg firewall openPort
87. river for VMware ESX 4 1 User Manual Page iii gt lt EMULEX IN ODUCUON BE EG edna aed 15 Message Log Example ccccccccccccceceeeeeeeeeeeeeeeeeensnsneeeneeeeanenaaaeeeeeeeee 16 ELS Events 0100 0199 EERS EE GE GE EES SON Mad E AE R 16 Link Discovery Events 0200 0299 ee ee 19 Mailbox Events 0300 0339 ee 24 Initialization Events 0400 0599 ee ee ee ee ee ee 32 FCP Traffic History 0700 0799 ee dee ee ee ee ee ee ee ee 40 Node Table Events 0900 0999 ee 41 Miscellaneous and FCoE Events 1200 1299 ee ee 41 Link Events 1300 1899 sesse see seg ee ees ee ee ee Ge Ge Ge Ge ee 42 Reserved 1400 1499 nananana 42 IOCTL Events 1600 1699 ooo i ii ee ee ee ee ee ee ee ee 46 VPort Events 16001632 ER EE Ee Ee ee ee Ge oe Ge er Gee er Ge EE Ee 46 ELS Events 1833 2800 ee ee ee ee ee ee ee ee ee ee ee ee 50 NIC Troubleshooting EE EE EE EI I EI EE EEE ee ee 64 NIC Event Error Logging cccccccccceceeceeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteeeeeteeeas 65 Retrieving NIC Error Log Codes 65 NIC Event Log Entries sesse SE NEER tete taba net RNEER Cede net ER ee lese siele ien 65 NIC Adapter Firmware EFFOF ees sesse ee ee ee ee eek ee ee ee ee ee ee RR ee ee ee ee eed ee Ee ee 67 iSCSI Troubleshooting edanean EE 68 Retrieving iSCSI Error Log Codes 2 0 0 0 sesse esse seed eke ee ee ee ee ee ee ee ee ee ee ee ee ee ee 68 iSCSI Error Log Code Entries esse
88. rror If this problem persists report these errors to Technical Support elx_mes1813 Create VPORT failed Cannot get sparam DESCRIPTION The port could not be created because it could not be initialized possibly due to unavailable resources DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1814 Mbox lt u mb mbxCommand gt failed no vport DESCRIPTION The VPort field of this mailbox command was not completed DATA None ACTION None required elx_mes1815 Could not issue unreg_did default rpis DESCRIPTION Attempt to unregister RPI failed DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1818 VPort failed init mbxCmd lt mailbox command gt READ_SPARM mbxStatus lt mailbox status gt rc lt status gt DESCRIPTION A pending mailbox command issued to initialize port failed DATA 1 mbxCommand 2 mbxStatus 3 rc ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1820 Unable to select SLI 3 Not supported by adapter DESCRIPTION The adapter is not capable of operating in a given mode DATA None ACTION This is an informational message SLI 3 mode is only available on some adapters Do not attempt to force an adapter to run in SLI mode 3 if that adapter does not support SLI 3 mode Adapters that do not support SLI 3 are confi
89. ry must be removed or corrected The be2iscsi driver failed to load due to a memory allocation failure This failure occurred due to a failed memory allocation in the driver Check low memory conditions The be2iscsi driver failed to load because initialization failed during normal bootup This failure ma be due to the firmware not being present or running currently This failure may also indicate a hardware problem An internal API failed in be2iscsi driver during initialization This failure may indicate a low memory condition There was an Unrecoverable Error detected by the be2iscsi driver Following this error log entry the next 3 entries will indicate the error codes This may be due to hardware errors or due to unhandled exceptions in the hardware or firmware The be2iscsi driver failed an IOCTL request since the number of scatter gather elements required for the IOCTL buffer exceeded the BladeEngine s firmware limit Following this error log entry the next entry will indicate the IOCTL opcode and the payload length requested This error may indicate an incorrect configuration option for the driver It may also indicate a low memory condition The be2iscsi driver detected an error during offloading the iSCSI connection The operation will be tried again Following this error log entry the next entry will indicate the session handle and the BladeEngine firmware error code This may indicat
90. ssage log proc vmware log and report any of these entries that may be present Note In the following table lt D gt lt DD gt or lt DDD gt in the Message Displayed column refers to decimal values that appear in the actual error messages Driver for VMware ESX 4 1 Troubleshooting Section Page 65 Table 6 ESX Server NIC Event Log Entries SE EMULEX Severity Message Displayed Description Error BladeEngine POST failed Power ON Self Test of the OneConnect UCNA failed This indicates either a hard ware or a firmware problem Try rebooting the system after a reset Error BladeEngine 2 initalization Either the initialization of the OneConnect failed UCNA or the allocation of some resource for initializing the driver failed In most cases this message is accompanied by another more specific error message Try rebooting the system after a power cycling If the problem persists this could indicate a hardware problem or corrupted firmware Warning Using INTx interrupts Net The driver could not allocate MSIx vector for Queues feature are disabled interrupt The driver may continue to work but the performance may be impacted Warning WARNING Found a BE2 card in OneConnect is a x8 Gen2 PCl e device For Gen lt D gt x lt D gt PCI e slot Should best performance OneConnect should be be in Gen 2 x8 slot for best installed in a Gen2 PCl e slot 8 or 16 performanc
91. t elx_mes0503 Failed allocate fast path FCP DESCRIPTION Failed to allocate fast path FCP DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0504 Failed allocate slow path ELS WQ DESCRIPTION Failed to allocate slow path ELS WO DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0505 Failed allocate slow path MQ DESCRIPTION Failed to allocate slow path MQ DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0506 Failed allocate receive HRQ DESCRIPTION Failed to allocate receive HRQ DATA None ACTION The driver fails to load Contact Emulex Technical Support Driver for VMware ESX 4 1 Troubleshooting Section Page 37 elx_mes0507 Failed allocate receive DRQ DESCRIPTION Failed to allocate receive DRQ DATA None ACTION The driver fails to load Contact Emulex Technical Support elx_mes0520 Slow path EQ not allocated DESCRIPTION The slow path EQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx mes0521 Failed setup of slow path EQ rc 0x x DESCRIPTION The slow path EQ setup failed with status rc DATA 1 status code ACTION The driver fails to load Contact Emulex Technical Support elx_mes0522 Fast path EQ lt fcp_eqidx gt not allocated DESCRIPTION The fast path EQ is not allocated DATA None ACTION The driver fails to load Contact
92. t jurisdiction all the other terms and conditions shall survive ENTIRE AGREEMENT Emulex may modify this License Agreement from time to time Any amendments or modifications may be provided to you through on line notice This is the complete agreement between the parties regarding the subject matter hereof and except as expressly permitted hereunder may be changed only by a written agreement executed by authorized representatives of the parties Last updated September 5 2006 Driver for VMware ESX 4 1 EULA Page 74
93. tart the VMs Driver for VMware ESX 4 1 Configuration Section Page 10 5G EMULEX Steps 1 through 5 assume that eth0 is the interface added to the VM from the OneConnect Network Note The use of vmx NIC emulation requires VMware Tools to be installed in the guest operating systems For information on installing VMware Tools in a Linux or Windows guest operating system refer to the VMware ESX Server 4 1 documentation Configuring a Virtual Switch to Use Jumbo Frames To use jumbo frames you must increase the MTU Maximum Transmission Unit size in the vSwitch and also in the guest operating system For the best combination of performance and resource usage set the MTU to the maximum MTU supported by the OneConnect driver which is 8179 bytes This requires the MTU to be changed in the virtual switch as well as the guest operating systems Setting the MTU Size in the vSwitch To change the MTU to 8179 in the console operating system run the following command for each switch in the console operating system esxcfg vswitch vSwitch lt N gt m 8179 where lt N gt is the number of the switch Setting the MTU Size for a Linux Guest Operating System To set the MTU of the OneConnect driver interface in each Linux Guest operating system to 8179 run the following command ifconfig eth lt N gt mtu 8179 where lt N gt is the number of the Ethernet interface on which you are working Setting the MTU Size for a Windows Guest Opera
94. the PCI bus DATA 1 sli4_mbx_opcode 2 sli_flag 3 flag ACTION None required elx_mes2546 New FCF found index lt index gt tag lt event_tag gt DESCRIPTION A new FCF has been found DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 56 SE EMULEX elx mes2547 Read FCF record failed DESCRIPTION Could not read the FCF record from the firmware DATA None ACTION None reguired elx_mes2548 FCF Table full count lt count gt tag sevent tag DESCRIPTION The FCF table is full DATA None ACTION None reguired elx mes2549 FCF disconnected from network index lt index gt tag event tag DESCRIPTION The FCF has disconnected from the network DATA None ACTION None reguired elx mes2550 UNREG FCFI mbxStatus error lt u mb mbxStatus gt HBA state sport state DESCRIPTION The unregistered FCFI has failed DATA None ACTION None required elx_mes2551 UNREG FCFI mbox allocation failed HBA state lt port_state gt DESCRIPTION The allocation for the UNREG_FCFI mailbox command has failed DATA None ACTION None required elx_mes2552 UNREG_FCFI issue mbox failed rc lt rc gt HBA state sport state DESCRIPTION The unregister FCFI mailbox command has failed DATA None ACTION None required elx_mes2553 Ipfc_unregister_unused_fcf failed to read FCF record HBA state DESCRIPTION DATA None ACTION None required elx_mes2554 Could not allocate
95. these errors to Technical Support 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_mes0113 An FLOGI ELS command lt elsCmd gt was received from DID lt did gt in Loop Mode DESCRIPTION While in Loop Mode an unknown or unsupported ELS command was received DATA None ACTION Check device DID Driver for VMware ESX 4 1 Troubleshooting Section Page 16 5G EMULEX elx_mes0115 Unknown ELS command lt elsCmd gt received from N_Port lt did gt DESCRIPTION Received an unsupported ELS command from a remote N_Port DATA None ACTION Check remote N Port for potential problem elx_mes0125 FDISC Failed x x Fabric out of resources DESCRIPTION The fabric rejected an FDISC because the switch can not support any more VPorts DATA None ACTION Reconfigure the switch to support more NPIV logins If problem persists contact Technical Support elx_mes0126 FDISC failed ulpStatus ulpWord 4 n DESCRIPTION The ELS FDISC command has failed DATA None ACTION Check the port and switch configuration 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
96. ting System To set the MTU in each Windows guest operating system 1 Go to the Start menu and select Control Panel gt System Select the Hardware tab and open Device Manager Expand the Network Adapters heading Right click on the NIC and select Properties Select the Advanced tab and set the MTU value Or IN Pinning VMs and Interrupts to CPUs The OneConnect driver supports MSI X interrupts The driver requests separate MSI X interrupt request IRQ vectors for each of the interfaces Pinning VMs and the IRQ vector to a CPU core helps provide the best performance from the OneConnect UCNA With a multi core CPU pinning a VM and the MSI X vector of the OneConnect driver interface configured in that VM to two cores sharing an L2 cache provides the best performance For example in a quad core Xeon CPUO and CPU1 share a 4MB L2 cache If you have configured vmnic16 in VM1 for the best performance pin VM1 to CPUO and the IRQ corresponding to vmnic16 to CPU1 To pin a VM to a CPU in the VI Client 1 Power off the VM 2 Click Edit Settings in the Resources tab for that VM 3 Select Advanced CPU 4 Inthe Scheduling Affinity frame select the CPU to pin it to Driver for VMware ESX 4 1 Configuration Section Page 11 5G EMULEX 5 Power on the VM To pin an IRQ vector to a CPU run the following command in the console operating system echo move lt IRQ NO gt lt CPU ID gt gt proc vmware intr tracker You c
97. to lt val gt allowed range is lt LPFC_MIN_DEVLOSS_TMO gt lt LPFC_MAX_DEVLOSS_TMO gt DESCRIPTION Attempt to set the nodev timeout value is outside the range of the devloss timeout range DATA None ACTION Set the nodev timeout between the minimum and maximum devloss timeout range elx_mes0404 Config Param s set to x x DESCRIPTION Driver is setting a persistent VPort parameter to a new value DATA 1 New value ACTION None This message is notification only elx_mes0405 Config Param s set to x x DESCRIPTION Driver is setting a persistent VPort parameter to a new value DATA 1 New value ACTION None This message is notification only elx_mes0406 Adapter maximum temperature exceeded lt temperature gt taking this port offline DESCRIPTION The driver has received an error for the adapter indicating that the maximum allowable temperature has been exceeded DATA 1 work hs 2 work status 0 3 work_status 1 ACTION Ensure the server fans are not blocked Shut down the server if the airflow is restricted elx mes0410 Cannot find virtual addr for mapped buf on ring lt ringno gt DESCRIPTION The driver cannot find the specified buffer in its mapping table Thus it cannot find the virtual address needed to access the data DATA 1 phys 2 next 3 prev 4 postbufq_cnt ACTION This error could indicate a software driver or firmware problem If the problem persists report these errors to Technical S
98. to init mbxCmd lt mbxCommand gt READ CONFIG mbxStatus lt mbxStatus gt DESCRIPTION Adapter initialization failed when issuing a READ_CONFIG mailbox command DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0454 Adapter failed to init mbxCmd lt mbxCommand gt INIT LINK mbxStatus lt mbxStatus gt DESCRIPTION Adapter initialization failed when issuing an INIT_LINK mailbox command DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0456 Adapter failed to issue ASYNCEVT_ENABLE mbox status lt rc gt DESCRIPTION The mailbox command to enable an asynchronous event notification failed DATA None ACTION Ensure the adapter firmware is current Reload the driver elx_mes0457 Adapter Hardware Error DESCRIPTION The driver received an interrupt indicating a possible hardware problem Data 1 status 2 status1 3 status2 ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support elx_mes0459 Adapter heartbeat failure taking this port offline DESCRIPTION The Heartbeat mailbox command failed DATA None ACTION Ensure the adapter firmware is current Reload the driver Driver for VMware ESX 4 1 Troubleshooting Section Page 35 SE EMULEX elx mes047
99. twork connectivity the current value run 2 A lot of alloc_skb failed messages esxcfg advcfg j netPktHeapMaxSize appear in thelog file procivmware log A value of 0 indicates default 64MB To increase the size to for example 128 MB run esxcfg advcfg k 128 netPktHeapMaxSize netPktHeapMaxSize can also be configured through VI Client using Configuration gt Advanced Settings gt VMKernel After configuring the size reboot the system Driver for VMware ESX 4 1 Troubleshooting Section Page 64 5G EMULEX Table 5 General Driver Situations NIC Continued Problem Answer Solution Unable to ping from one VM to another OneConnect driver creates two vmnic interfaces one for each VM port If these interfaces are configured as uplinks in two separate vSwitches the VMs in each of these switches are in separate networks with no network path between them Thus pinging between the VMs in the two groups fails If you want all these VMs in the same network configure them as teaming uplinks to one vSwitch option Each of the vmnics vmnic1 to vmnic16 must be configured in a separate vSwitch In this configuration there is no network path between the vSwitches and pinging between these VMs does not work When inserting or removing a 1Gb SFP There is no solution to this issue as the link status is not RJ45 module on a OneConnect adapter reported due to a PHY limitation on the card without RJ4
100. u mb mbxStatus gt DESCRIPTION The mailbox command sent to the firmware to configure the adapter to use MSI X has failed DATA None ACTION Ensure the hardware platform supports MSI X elx_mes0353 Active Mailbox cleared mailbox timeout exiting DESCRIPTION The mailbox timeout handler has determined that the driver is in the process of completing this mailbox command DATA None ACTION None required elx_mes0359 Not a valid slow path completion event majorcode x x minor code x x n bf get lpfc ede major code eqe bf get lpfc edge minor code ede DESCRIPTION SLI 4 The EQE is not valid DATA None ACTION None reguired elx_mes0360 Unsupported EQ count sentry count DESCRIPTION Cannot create an event gueue of this size DATA None ACTION None reguired elx mes0361 Unsupported CQ count entry count DESCRIPTION Cannot create a completion gueue of this size DATA None ACTION None reguired elx_mes0362 Unsupported MO count entry count DESCRIPTION Cannot create MO count of this size DATA None ACTION None reguired Driver for VMware ESX 4 1 Troubleshooting Section Page 28 5G EMULEX elx_mes0364 Invalid param DESCRIPTION SLI 4 The post SGL function was passed an invalid XRI DATA None ACTION None required elx_mes0365 Slow path CQ identifier lt cqid gt does not exist DESCRIPTION The Completion Queue ID passed in the Event Queue entry does not reference a valid comp
101. upport elx mes0423 Vport Attribute Instance Error Defaulting Ipfc attr to d error value od allowed range is min max DESCRIPTION A Vport attribute was set out of range The driver reset the parameter to its default DATA None ACTION Set the module parameter between the minimum and maximum values Driver for VMware ESX 4 1 Troubleshooting Section Page 32 SG EMULEX elx_mes0424 Vport Attribute Count Exceeded Max d Actual d DESCRIPTION The total number of Vport attributes set exceeded the max allowed DATA None ACTION Reduce the number set attributes below max elx_mes0425 Ipfc_ attr attribute cannot be set to d allowed range is min max DESCRIPTION Driver attribute Ipfc_ attr was defined with an out of range value DATA None ACTION Set the parameter between the minimum and maximum value elx mes0427 Cannot re enable interrupt after slot reset DESCRIPTION The driver was not able to enable the interrupt after an adapter reset DATA None ACTION Unload and reload the driver elx mes0430 PM resume Failed to enable interrupt DESCRIPTION The driver s power management resume function could not enable the interrupt DATA None ACTION Perform another PM suspend and resume or adapter reset elx_mes0431 Failed to enable interrupt DESCRIPTION The driver failed to start the interrupt DATA None ACTION Unload and reload the driver elx_mes0433 Wakeup on signal rc lt rce gt DESCRIPTI
102. ures the maximum number of scatter gather elements the driver accepts in a single SCSI command Creating a Fibre Channel Remote Boot Disk For instructions on creating a Fibre Channel remote boot disk refer to the VMware SAN configuration documentation Chapter 6 Using Boot from SAN with ESX Server Systems Driver for VMware ESX 4 1 Configuration Section Page 9 gt G EMULEX 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 and creating an NPIV enabled virtual machine comes from ESX VPorts in the driver discover the fabric just like physical ports do and are subject to the same SAN delays As the number of VPorts increases the amount of time it takes to complete remote port discovery increases This is because the VPorts are created sequentially and each VPort executes discovery synchronously If your NPIV enabled virtual machines power on automatically powering on could take longer than usual 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 at the same time If you are running a loop topology and you create a VPort the VPort s link state is offline VMware ESX supports only fabri
103. us lt rc gt DESCRIPTION The mailbox command sent to delete the mailbox queue has failed DATA None ACTION None required elx_mes2508 WQ_DESTROY mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the work queue has failed DATA None ACTION None required elx_mes2509 RQ_DESTROY mailbox failed with status lt shdr_status gt add_status lt shdr_add_status gt mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the receive queue has failed DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 53 SE EMULEX elx mes2510 RA DESTROY mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the receive queue has failed DATA None ACTION None reguired elx mes2511 POST SGL mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to post the SGL pages to the firmware has failed DATA None ACTION None reguired elx mes2512 REMOVE ALL SGL PAGES mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to delete the SGL pages from the firmware has failed DATA None ACTION None reguired elx mes2513 POST SGL BLOCK mailbo
104. valid adapter PCl device group detected DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 45 SE EMULEX elx mes1430 Failed to initialize sgl list DESCRIPTION Failed to initialize SGL list DATA None ACTION None reguired elx mes1431 Invalid HBA PCl device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx_mes1432 Failed to initialize rpi headers DESCRIPTION RPI headers required by the firmware failed to initialize DATA None ACTION None required elx_mes1476 Failed to allocate sysfs attr DESCRIPTION Failed to allocate sysfs attribute DATA None ACTION None required elx_mes1477 Failed to set up hba DESCRIPTION Failed to set up adapter DATA None ACTION None required IOCTL Events 1600 1699 None VPort Events 1800 1832 elx_mes1800 Could not issue unreg_vpi DESCRIPTION Driver attempt to unregister VPI failed DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1802 HBO lt index gt local_hbqGetldx lt index gt is gt than hbqp gt entry_count lt count gt DESCRIPTION An error occurred when processing queue related to an adapter in a particular slot DATA 1 hbqno 2 local_hbqGetldx 3 entry count ACTION Software driver error If this problem persists report these errors to Technical Support
105. ver completed DATA None ACTION None required The driver should recover from this event elx_mes0230 Unexpected timeout hba linkstate lt link_state gt DESCRIPTION Discovery has timed out and the adapter state is not ready DATA None ACTION None required elx_mes0231 RSCN timeout DESCRIPTION The driver has lost track of which N_Ports have RSCNs pending DATA 1 fc ns retry 2 Ipfc max ns retry ACTION None required The driver should recover from this event elx_mes0233 Nodelist not empty DESCRIPTION Driver unload or hotplug detected a node still in use DATA None ACTION None required 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 do RegLogin for the specified DID There may be a limitation on how many nodes an adapter can see elx_mes0249 Cannot issue Register Fabric login Err lt err gt DESCRIPTION Could not issue the fabric reg login the err value is unique for each possible failure DATA None ACTION None required elx_mes0251 NameServer login no memory DESCRIPTION Could not allocate memory for the NDLP structure DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 20 gt lt EMULEX elx_mes0252 Cannot issue NameServer login DESCRIPTION Could not issue an ELS PLOGI to the nameserver DI
106. x command failed status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to post the SGL pages to the firmware has failed DATA None ACTION None reguired elx mes2514 POST RPI HDR mailbox failed with status sshdr status add status sshdr add status mbx status lt rc gt DESCRIPTION The mailbox command sent to post the RPUI header pages to the firmware has failed DATA None ACTION None reguired elx mes2515 ADD FCF RECORD mailbox failed with status lt rc gt DESCRIPTION The mailbox command to add the FCF record has failed DATA None ACTION None reguired elx mes2516 DEL FCF of default FCF Index failed mbx status lt rc gt status lt shdr_status gt d_status lt shdr_add_status gt DESCRIPTION The mailbox command to delete the FCF record has failed DATA None ACTION None required elx_mes2517 Unregister FCFI command failed status d mbxStatus x x rc bf_get Ipfc_mqe_status amp mbox gt u mqe DESCRIPTION The driver was unable to unregister the FCFI from the firmware DATA None ACTION None required Driver for VMware ESX 4 1 Troubleshooting Section Page 54 5G EMULEX elx_mes2519 Unable to allocate memory for issuing NOP mailbox command DESCRIPTION Memory allocation for this mailbox command has failed DATA None ACTION None required elx_mes2521 READ_FCF_RECORD mailbox failed with status lt shdr_status gt add_status lt shdr_a

Emulex Drivers for VMware User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents