Home

ESX/ESXi 4.1 - User Manual

1. 23 Multipath 23 Configuring and Enabling Support for ESX MPIO on Non boot Targets 23 Configuring and Enabling Support for ESX MPIO on BootTargets 23 Logging into Targets Using vSphere 24 Error Handling Under Multipath MPIO and Cluster Configurations 24 Managing Devices using CIM eee eeeeeeeeeeeee 25 Be ruepgMee 26 veio M 26 Troubleshooting the FC FCOE 26 General Situ ations eniin t nana cet Ru ka uen de t au aaa e 26 lfe LOG MESSAGES lene tete RS 27 gt 27 Message Log Example read 28 ELS Events 0100 0199 nnn 28 Link Discovery Events 0200 0299 30 Mailbox Events 0300 0339 36 Initialization Events 0400 0599 Hee 43 Node Table Events 0900 0999 ANAN RKRN NRNANRNANA 53 Miscellaneous and FCoE Events 1200 1299
2. 53 Link Event 1300519399 ee 53 Reserved 1400 1499 esses 54 IOCTL Events 1600 1699 nennen nennen 58 VPort Events 1800 seris enne 58 ELS EVENS 18392600 toe ro eu uten EE E 61 INGW ENON ERR E SERRE RES 77 Drivers for VMware ESX ESXi 4 1 User Manual Page v Troubleshooting the NIC Driver 80 NIC Event Error Logging 81 Retrieving ESX Server NIC Error Log 81 ESX Server NIC Event Log Entries 81 NIC Adapter Firmware Error 83 Troubleshooting the iSCSI Driver 83 Retrieving iSCSI Error Log 84 iSCSI Error Log Code Entries ssssssssssssssseennnnn 84 Additional iSCSI Driver 5 87 Description of Mandatory and Optional 88 CIM Provider Troubleshooting 89 Appendix A Configuring iSCSI Through DHCP 91 Dynamic Host Configuration Protocol DHCP Recommendations 91 Vendor Specific Option 43 91
3. eee 2 NSSWOS 2 Installing the FC FCOE Driver ceeccceeceeeceeeeeeeeccaeeeeeeeeeeeeeeeencaaaeeeeeeesetenncseeeeeees 2 Introduction RR 2 Installing the FC FCoE Driver and Management Software 2 Uninstalling the FC FCOE nnne 2 Installing the FC FCoE Utilities 2 Uninstalling the FC FCOE Utilities 3 Installing the NIC Driver sssssssseeeeeenennnnnn nennen nnne n nnn niens nis 3 Introduccion 3 Installing the NIC Driver and Management Software 3 Uninstalling the NIC Driver sssssseeeeeeeeeeeennnnn nennen nnn 4 Installing the iSCSI Driver nennen nnne 4 4 Performing a Fresh Installation of ESX 4 Adding or Upgrading the iSCSI Driver in an Existing ESX Server 4 Performing Silent Unattended Installation 5 Invoking Silent Install in ESX 5 qaev ee 5 Uninstalling the iSCSI Driver 6 Removing the iSCSI Driver from 6 Invoking Silent Uninstall nnns 6 Uninstall Exit C
4. status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to delete the receive queue has failed DATA None ACTION None required elx mes2511 POST SGL mailbox failed with status shdr status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to post the SGL pages to the firmware has failed DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 66 EMULEX elx_mes2513 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 mailbox command sent to post the SGL pages to the firmware has failed DATA None ACTION None required elx mes2514 POST RPI 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 post the RPUI header pages to the firmware has failed DATA None ACTION None required elx mes2515 ADD FCF RECORD mailbox failed with status rc DESCRIPTION The mailbox command to add the FCF record has failed DATA None ACTION None required 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 shdr status add status s
5. Note If the value of ETO is set to a number between 0 and 19 the driver will assume the value to 20 secs internally You will not see any modification to the registry LDTO and ETO values are configurable during insmod time The ETO value specified during insmod is the default ETO value that is applied to all targets 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 4 esxcfg module s ldto 25 be2iscsi usr sbin esxcfg boot r reboot Multipath I O Support This section describes the installation and login processes for multipath I O support Configuring and Enabling Support for ESX MPIO on Non boot Targets To configure and enable support for ESX MPIO on non boot targets Connect your configuration for multipath 2 Loginto your targets with all paths using vSphere Client or iSCSISelect For more information see Logging Into Targets Using vSphere Client For information about using using iSCSISelect see the Emulex Boot Manual Configuring and Enabling Support for ESX MPIO on BootTargets To configure and enable support for ESX MPIO on boot targets 1 Connect your configuration for multipath Multipath can be configured before or after installation Drivers for VMware ESX ESXi 4 1 Configuration Section
6. 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 vpi 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 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 error 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 59 J gt G EMULEX e
7. EMULEX Emulex Drivers for VMware 4 1 User Manual Emulex Connects P007000 01A Rev A Servers Storage and People gt G EMULEX Copyright 2011 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this manual as is without any warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product described in this manual at any time and without any notice Emule
8. elx mes0207 Device DID lt WWN3 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 never got a response back DATA None 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 fc max ns retry ACTION Check Fabric configuration The driver recovers from this and continues with device discovery 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 t
9. elx mes2022 INIT VPI Mailbox failed status status 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 management array of size els xri cnt 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 status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to create the event queue has failed DATA None ACTION None required elx mes2501 CQ CREATE mailbox failed with status shdr status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to create the completion queue has failed DATA None ACTION None required elx mes2502 MQ CREATE mailbox failed with status shdr status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to create the mailbox queue has failed DATA None ACTION None required elx mes2503 CREATE mailbox failed with status lt status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to create the work queue has failed DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 65 EMULEX elx_mes2504 RQ_CREATE mailbox failed with sta
10. 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_mes1801 Create vport work array FAILED cannot do scsi_host_get DESCRIPTION Driver failed to create working list of vports DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1802 index local hbqGetldx index 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 elx mes1803 Bad hbq tag Data tag count 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 elx mes1804 Invalid asynchronous event code evt code DESCRIPTION
11. fc flag fc rscn id cnt DESCRIPTION The nameServer GFF CT request failed DATA 1 VPorts fc flag 2 VPorts fc 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 nlp DID event evt state nlp state Data lt nlp_rpi gt nlp 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 elx mes0272 Illegal State Transition node nlp DID event evt state nlp state Data nlp rpi nlp flag 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 port state 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 gt DID void ndlp Ipfc init c ndlp 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
12. Format of Vendor Specific Option 43 91 Drivers for VMware ESX ESXi 4 1 User Manual Page vi gt G EMULEX Installation Driver Information Supported Features Supports the Emulex OneConnect family of UNCAs and Emulex HBA adapters e Supports dynamic parameter setting using the OneCommand Manager application version 5 2 from Emulex It is a GUI and CLl based configuration utility used as part of a master kit enabling driver configuration including Supports the CIM interface through OneCommand Manager to manage ESX ESXi Out of band TCP IP remote SAN management capability Diagnostics loopback and diagnostic dump except for OneConnect adapters Virtual port NPIV view vports only See the OneCommand Manager User Manual for a complete list of supported features e Supports the following protocols iSCSI hardware offload NIC Fibre Channel FC Fibre Channel over Ethernet FCoE 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 Point to point Fabric with auto topology negotiation e Supports FC in band management 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 Tested with up to sixteen adapter ports e Support for Common HBA API Batch firmware download c
13. ulpStatus 2 ulpWord 4 3 ulpTimeout ACTION This error could indicate a fabric configuration error or internal driver issue If problems persist report 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 did in Loop Mode DESCRIPTION While in Loop Mode an unknown or unsupported ELS command was received DATA None ACTION Check device DID elx mes0115 Unknown ELS command lt elsCmd gt received from N Port did DESCRIPTION Received an unsupported ELS command from a remote N Port DATA None ACTION Check remote N Port for potential problem elx mes0122 FDISC Failed x x Fabric Detected Bad WWN DESCRIPTION Driver s FDISC failed Switch reported a bad WWN in FLOGI request DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes0124 Retry illegal cmd x x retry x x delay x x DESCRIPTION Port rejected ELS command as illegal Driver retrying Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 28 EMULEX DATA ACTION Software driver error If this problem persists report these errors to Technical Su
14. 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 Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 43 EMULEX elx_mes0423 Vport Attribute Instance Error Defaulting lpfc_ attr to d error value d 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 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 lpfc_ 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 inter
15. 43 and includes guidelines for creating the data string iscsi lt TargetIP gt lt TargetTCPPort gt lt LUN gt lt TargetName gt lt Initiator Name gt lt HeaderDigest gt lt DataDigest gt lt AuthenticationType gt e Strings shown in quotes are part of the syntax and is therefore mandatory Fields enclosed in angular brackest including the angular brackets should be replaced with their corresponding values Some of these fields are optional and may be skipped e optional field is skipped a colon must be used as a placeholder to indicate the default value for that field When specified the value of each parameter should be enclosed in double quotes See Examples All options are case sensitive Drivers for VMware ESX ESXi 4 1 Appendix Page 91
16. 64 256 No Configures the maximum number of scatter gather elements the driver accepts in a single SCSI command Drivers for VMware ESX ESXi 4 1 Configuration Section Page 15 gt G EMULEX Table 1 FC FCoE Driver Configuration Parameters Continued Variable Default Min Max Dynamic Comments Ipfc_iocb_cnt 1 1 5 No IOCBs allocated for ELS CT ABTS in 1024 increments Default is 1 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 Managing ESX ESXi Server Through the CIM Interface This manual also describes how OneCommand Manager can be configured to manage VMware ESX and ESXi servers through the CIM interface Please note that the management of adapters in the VMware ESX ESXi hosts through the CIM interface is enabled only for the OneCommand Manager applications running on the Windows environment Installing the Emulex CIM Provider To install the Emulex CIM provider use the esxupdate utility provided by VMware in ESX and ESXi platforms For information on the esxupdate procedure refer to esxupdate Procedure on page 7 for more details CIM Provider The Emulex CIM Provider is available as a core kit rpm in ESX platforms and as an offline bundle in ESXi platforms To install the CIM Provider core ki
17. Adapter Hardware Error Data x x x x DESCRIPTION Driver detected a hardware error in an SLI4 capable port DATA 1 error 1 2 error 2 ACTION Software driver error If this problem persists report these errors to Technical Support Link Discovery Events 0200 0299 elx mes0200 CONFIG LINK bad hba state hba state DESCRIPTION A CONFIG LINK mbox command completed and the driver was not in the right state DATA None ACTION Software driver error If this problem persists report these errors to Technical Support elx mes0203 Devloss timeout on WWPN address N Port nlp DID DESCRIPTION A remote N Port that was discovered by the driver disappeared for more than Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 30 J gt G EMULEX lpfc devloss tmo seconds DATA 1 flag 2 state 3 ACTION If the device generating this message is not a target to which the adapter 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
18. For ESX Server systems the NIC driver generates error codes to the var log vmkernel log file The vmkernel log file is an ASCII text file that 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 an integer To search the log file for error messages at the command prompt type fcd var log less vmkernel For example you might see the following message Sep 9 19 48 04 esx server vmkernel WARNING Found a OneConnect card in Gen 1 x8 PCI e slot Should be in Gen 2 x8 slot for best performance ESX Server 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 message log proc vmware log and report any of these entries that may be present Note In the following table D lt DD gt or lt DDD gt in the Message Displayed column refers to decimal values that appear in the error messages Table 5 ESX Server NIC Event Log Entries Severity Message Displayed Description Error OneConnect 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 OneConnect initia
19. Manual for instructions on how to install the application on the ESX COS Note Before installing the Emulex OneCommand Manager Kit you must install the Ipfc driver from the VMware website Note Before installing OneConnect network drivers and management software verify that the firmware version is correct 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 Installing the FC FCoE Utilities Follow these instructions to install the OneCommand Manager application Note The FC FCoE utilities are installable on ESX only For ESXi download and install the OneCommand Manager for VMware vCenter software plug in To install the OneCommand Manager agent Drivers for VMware ESX ESXi 4 1 Installation Section Page 2 EMULEX 1 Log in as root 2 Copy the elxocmcore esx41 lt kit version gt x86_64 rpmfile to directory on the install machine 3 CD to the directory to which you copied the RPM file Install the RPM file Type rpm U elxocmcore esx4l kit version gt x86_64 rpm For example rpm U elxocmcore esx41 5 2 12 1 1 x86 64 rpm The RPM file contents are installed in usr sbin ocmanager The CLI utility is also located in this directory Uninstalling the FC FCoE Ut
20. Page 23 2 gt G EMULEX Log into your targets with all paths using vSphere Client or iSCSISelect For more information see Logging Into Targets Using vSphere Client For information about using using iSCSISelect see the Emulex Boot Manual Logging into Targets Using vSphere Client To log into targets using the vSphere Client follow these steps 1 NOOR ON 9 10 11 12 Log into the server that you would like to configure from the vSphere Client and select the Configuration tab In the Hardware section select the Storage Adapters link Select the OneConnect host adapter in the Storage Adapters list Select the initiator port and then click Properties From the iSCSI Initiator Properties screen click the Dynamic Discovery tab Click Add to display the Add Send Target Server menu Type in the IP address of the first target portal and click OK The initiator finds the target machines Click the Static Discovery tab to find all target portals Click Close A dialog box indicates that a rescan is needed Click Yes The configured LUNs are displayed Repeat the steps to log into the other target portal to set up MPIO To check that both paths are connected to the same LUN follow these steps a Select the LUN and right click b Click Manage Paths Multipaths on the LUN are displayed For example Error Handling Under Multipath MPIO and Cluster Configurations In an MPIO or cluster configuration
21. 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 command status queue num 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 58 J gt G EMULEX elx mes1806 Mbox command failed No 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 value 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 Technical Support elx mes1808 Create VPORT failed NPIV is not enabled SLImode mode 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
22. The default TCP port 3260 is assumed if not specified Optional lt LUN gt It is hexadecimal representation of Logical Unit number of the boot device If not provided LUN 0 is assumed to be the boot LUN It is an eight byte number which should be specified as a hexadecimal number consisting of 16 digits with an appropriate number of 0 s padded to the left if required Optional lt TargetName gt Replace it with a valid iSCSI target iqn name of up to 223 characters Mandatory lt InitiatorName gt Replace it with a valid iSCSI iqn name of up to 223 characters If not provided the default Initiator name generated by the UCNA based on the board s MAC address will be used Optional lt HeaderDigest gt Replace it with either E or D E denotes header digest is enabled D denotes that it is disabled Optional lt DataDigest gt Replace it with either E or D E denotes data digest is enabled and D denotes that it is disabled If not provided it is assumed that Data Digest is disabled by default Optional lt AuthenticationType gt If applicable replace it with D or M D denotes authentication is disabled E denotes that one way CHAP is enabled the username and secret to be used for oneway CHAP must be specified by non DHCP means M denotes that MutualCHAP is enabled user name and passwo
23. 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 website 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 fabric 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 Driver Configuration Configuring NIC Driver Options The following table lists the user configurable NIC driver options It includes a description of the parameter and its default value Parameter Default Value Description The size of
24. a period exceeding the Extended Timeout ETO The error log entry immediately following this entry will indicate the session ID of 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 l 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 I O 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 The operating system version is not supported The be2iscsi driver received a Task Management Function Abort request for an I O request that is not present with the driver This message may indicate a slow connection to the target Check network connectivity to the target for any errors The be2iscsi driver encountered a mismatched version of the firmware running on the board 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 driver version that is running on the system does not match the version of the firmware flashed on the board Fix this by installing the desired
25. 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 required 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 Invalid adapter PCl device group detected DATA None ACTION None required elx mes1430 Failed to initialize sgl list DESCRIPTION Failed to initialize SGL list DATA None ACTION None required elx_mes1431 Invalid HBA PCI 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 57 gt G EMULEX
26. application for use in lockdown mode This document describes how to configure parameters using native ESX tools For a more comprehensive description of ESX tools refer to VMware s public website If you have further questions contact a VMware technical support representative See the OneCommand Manager Command Line User Manual for information about the OneCommand Manager application See the OneCommand Manager for VMware vCenter User Manual for information about the OneCommand Manager for VMware vCenter software plugin 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 sxcfg firewall openPort 23333 tcp in onecommand sxcfg firewall openPort 23333 tocp out onecommand To verify that the correct port is open run the following command sxcfg 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 Temporary FC FCoE Configuration Methods Using Native ESX Tools There are four ways to configure the driver parameters Permanent global Permanent per adapter Temporary global Temporary per adapter Note The OneCommand Manager application version 5 2 also supports all four ways to configure driver parameters This is the preferred method of setting configuration par
27. can only show 139 targets even if up to 256 are supported To 139 targets only 139 targets log into more than 139 targets and allowing these targets to appear in appear in vmkernel vmkernel you need to configure the tunable parameter vmklinuxHeapMaxSizeMB There are two methods to set this tunable parameter on the command line or with VI Client To set the parameter by the command line option set the value esxcfg advcfg k MBs vmklinuxHeapMaxSizeMB For example esxcfg advcfg k 48 vmklinuxHeapMaxSizeMB To set the parameter by using VI Client Under Configuraton tab gt Advanced Settings gt vmkernel set VMKernel Boot vmklinuxHeapMaxSizeMB to 48 Note After you complete setting the value you must reboot the ESX machine Mutual CHAP authentication One way CHAP is the only authentication method that can be configured with cannot be configured with the the vSphere Client In order to set Mutual CHAP authentication you must use vSphere client iSCSISelect Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 83 gt G EMULEX Retrieving iSCSI Error Log Codes The iSCSI driver generates error codes to the var log vmkernel log file The vmkernel log file is an ASCII text file that 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 an integer To search the log file for
28. driver could not set the MAC address filter failed filter on 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 the firmware revision number failed The version number is not shown The device will continue to work Warning Did not receive completions for While the driver was unloading some all TX requests outstanding transmit requests were 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 will continu to work You may not be able to use HBACMD to interact with the device Warning alloc skb failed Try increas Could not allocate the skb structure to send a ing netPktHeapMaxSize frame received from the network to the operating system This is a transient failure that can be ignored If this message appears continually you may need to allocate more memory to the network heap For example to increase the heap size to 128MB run esxcfg advcfg k 128 netPk tHeapMaxSize Warning Invalid MTU requested MTU must Invalid MTU size in MTU configuration ioctl be between 64 and 9000 bytes The MTU will not be changed Warning Invalid vlan priority labeled
29. elx mes0283 Failed to allocate 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 memo rysize lt reqlen gt DESCRIPTION Memory allocation was truncated DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 34 gt G EMULEX elx mes0286 Ipfc state cleanup 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 mes0287 Ipfc alloc bucket failed to allocate statistical data buffer nlp DID DESCRIPTION Memory allocation failed for node s statistical data DATA None ACTION None required elx mes0288 Unknown FCoE event type event type event tag event tag 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 rc DESCRIPTION The driver could not register the Virtual Fabric Index for the FCFI DATA None ACTION Check the switch and port configurations 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 required elx mes0291 Allocated DMA memory size alloc len is less than the reque
30. error messages at the command prompt type fcd var log vim vmkernel For example you may see the following message Sep 9 19 48 04 esx server vmkernel OneConnect 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 iSCSI Error Log Code Entries 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 7 iSCSI Error Log Code Entries Message Recommended Resolution The be2iscsi driver failed to This failure may be due to the firmware not being present or running currently load because initialization This failure may also indicate a hardware problem failed during a power management bootup The be2iscsi driver failed was This failure may indicate a low memory condition or a hardware error unable to map one or more PCI Base Address Register and hence failed to load The be2iscsi driver ignored a Check the registry configuration for any new entries added for driver configuration entry since the parameters The invalid entry must be removed or corrected entry was invalid The bee2iscsi driver failed to This failure occurred due to a failed memory allocation in the driver Check low load due to
31. 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 cfg use msi 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 sli rev DESCRIPTION The adapter does not support SLI 3 or SLI 4 DATA None ACTION This adapter does not support msi Set Ipfc 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 mes0482 Illegal interrupt mode DESCRIPTION Driver could not set MSI X MSI or INTX interrupt modes DATA ACTION This could be a server issue Reboot If this problem persists report these errors to Technical Support elx mes0483 Invalid link attention link speed x x bf get lpfc acqe link speed acqge link DESCRIPTION The link speed reported in the link attention interrupt is invalid DATA None ACTION Check the switch configuration elx m
32. experience problems when adding the host execute the following commands on the ESXi host and send the output to the Emulex Technical Support team vm support dump esxcfg module 1 esxcfg scsidevs a esxupdat vib view query grep be2 esxupdat vib view query grep lpfc esxupdat vib view query grep emu esxcfg nics 1 lspci Send the var log messages file for all of the above operations Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 90 gt G EMULEX APPENDIX A Configuring iSCSI Through DHCP Dynamic Host Configuration Protocol DHCP Recommendations If you are using the DHCP server to obtain an IP address for your iSCSI initiator it is recommended that you set up a reservation A reservation will assign a specific IP address based on the MAC address of your iSCSI function If you do not reserve an IP Address through DHCP then you must set the lease length for the iSCSI initiator IP address to unlimited This allows the IP address lease not to expire Vendor Specific Option 43 The following section describes the format for the data returned in DHCP vendor specific option 43 The method and format for specifying the Vendor ID is outside the scope of this User s Guide and is not included here The Initiator offers this Vendor ID to the DHCP server to retrieve data in the format described in the following section Format of Vendor Specific Option 43 The following describes the format of option
33. fault tolerant software is present on the system that makes the iSCSI driver error handling redundant These configurations also require that I O errors be reported as soon as they are detected so that the software can failover to an alternate path or an alternative node as quickly as possible When the iSCSldriver is run under these configurations the error handling implemented in the iSCSI driver must be turned off by setting the default value of LDTO and ETO to 0 The changes will take effect during the next driver load Drivers for VMware ESX ESXi 4 1 Configuration Section Page 24 gt G EMULEX Managing Devices using CIM VMware on the Visor based ESX platforms uses the Common Interface Model CIM as the only standard management mechanism for device management The OneCommand Manager application uses the standard CIM interfaces to manage the adapters in the ESX COS and Visor environments The OneCommand Manager application supports the CIM based device and adapter management in addition to the existing adapter management functionality around its proprietary management stack along with the standard HBAAPI interface Refer to the OneCommand Manager Application User Manual for more information Drivers for VMware ESX ESXi 4 1 CIM Section Page 25 Troubleshooting Introduction EMULEX There are several circumstances in which your system may operate in an unexpected manner The Troubleshooting section explains many of these ci
34. following exit codes in VMware ESX Server Note that all values are in decimal 0 Success All software was installed correctly with no errors A system reboot is not required 10 Success All software was installed correctly with no errors A system reboot is required 12 OneConnect firmware update failed 13 OneConnect not detected in the system 14 The installer was executed on a board with an unsupported configuration 15 Insufficient disk space to install OneConnect software 17 The Installer was executed by a system user that is not a superuser Drivers for VMware ESX ESXi 4 1 Installation Section Page 5 EMULEX 18 Operating system you are using is not supported by installer 20 Invalid command syntax Uninstalling the iSCSI Driver The uninstall file is copied to your system during the OneConnect Server Software installation process for the ESX Server After you have installed the Server software you can find the uninstall sh file on your local system in the following location opt Emulex OneConnect uninstall sh Removing the iSCSI Driver from initrd When uninstalling OneConnect Server software from your system the iSCSI driver will remain in the initrd To completely remove the OneConnect software from your system you will need to manually remove the iSCSI driver from initrd To do this follow these steps 1 From the uninstall sh location uninstall the driver by typing sh uninstall sh 2 U
35. handle unsolicited buffers DATA None ACTION None required elx mes0344 Ring ringno 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 complete The driver is resetting the port DATA None ACTION If the mailbox command fails again set the Ipfc log verbose to LOG MBOX and retry Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 38 EMULEX elx_mes0346 Ring lt ring number gt handler unexpected ASYNC_STATUS evt_code lt evicode gt WO hex w0 W1 hex w1 W2 hex W2 W3 hex W3 W4 hex W4 W5 hex Z5 W6 hex W6 gt W7 hex W7 W8 hex W8 W9 hex W9 W10 hex W10 W11 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 elx_mes0349 rc should be MBX_SUCCESS DESCRIPTION The next mailbox comma
36. load Contact Emulex Technical Support elx mes0582 Error rc 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 EVENT entry DATA None ACTION None required elx mes0603 Invalid work queue subtype subtype DESCRIPTION Invalid work queue CQE DATA None ACTION None required FCP Traffic History 0700 0799 elx mes0700 Bus Reset on target i failed DESCRIPTION The bus reset for the specified target failed DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 51 J gt G EMULEX 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 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 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 mes071
37. management interface is marked as blocked in preparation for an online or offline state transition All user space access to the HBA via libdfc interface will be blocked DATA None ACTION None Notification of a run state change only elx mes2822 IOCB failed 96s iotag 0x x xri Ox xX DESCRIPTION The driver is attempting to drain an internal queue and failed The failure reason and some state variables are written to the console DATA None ACTION None required This should be a transient condition If not please contact technical support elx_mes2823 txq empty and txq_cnt is d DESCRIPTION The driver has detected a discrepancy between the elements queued to the txq and the counter tracking the number or items DATA None ACTION None required There is nothing for the driver to do except correct the counter the txq is empty elx_mes2824 Cannot re enable interrupt after slot reset DESCRIPTION The driver failed to re enable interrupts following a PCI slot reset command DATA None ACTION A system reboot may be required to fully recover Contact technical support if problems persist elx_mes2825 Unknown PCI error state x x n state DESCRIPTION The driver writes this message to the console when the PCI subsystem has detected an error on an Emulex port and called the driver The driver reacts by resetting the port DATA None ACTION None required The driver resets the device in an attempt to recover Contact technical
38. memory allocation memory conditions failure The be2iscsi driver failed to This failure may be due to the firmware not being present or running currently load because initialization This failure may also indicate a hardware problem failed during normal bootup An internal API failed in This failure may indicate a low memory condition be2iscsi driver during initialization Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 84 gt G EMULEX Table 7 iSCSI Error Log Code Entries Continued Message Recommended Resolution 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 OneConnect s firmware limit Following this error log entry the next entry will indicate the IOCTL opcode and the payload length requested The be2iscsi driver detected an error during offloading the iSCSI connection The operation will be retried again Following this error log entry the next entry will indicate the session handle and the OneConnect firmware error code This error may indicate an incorrect configuration option for the iSCSI driver It may also indicate a low memory c
39. 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 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 Driver resource initialization failed Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 54 J gt G EMULEX 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 ni
40. 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 DATA None ACTION None required 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 rc parsing 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 rc during queue setup DESCRIPTION Could not set up all the queues that driver requires to exchange IOs with the adapter DATA None ACTION Reload the driver elx mes0382 READ SPARAM command failed status issue status mbxStatus mailbox status 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 fo
41. scan but failed to send the mailbox command due to state of the adapter DATA None ACTION None required elx mes2748 Failed to prepare for unregistering HBA s FCF record rc d DESCRIPTION Driver encountered an initialization error when preparing to rescan the FCF tables and needed to unregister an old FCF record DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes2749 Failed to prepare for unregistering HBA s FCF record rc d DESCRIPTION Driver encountered an initialization error when preparing to unregister an FCF and needed to prepare the command Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 75 gt G EMULEX DATA ACTION Software driver error If this problem persists report these errors to Technical Support 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 sta
42. support if problems persist elx_mes2826 PCI channel disable preparing for reset DESCRIPTION The driver writes this message to the console when it is preparing the port for a reset operation DATA None ACTION None required This message is notification of a corrective measure Contact technical support if problems persist Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 78 J gt G EMULEX elx_mes2827 PCI channel permanent disable for failure DESCRIPTION The driver writes this message to the console when a recovery mechanism has failed and the driver wants to mark the port with a permanent failure DATA None ACTION A system reboot may correct the failure If not contact technical support elx_mes2828 PCI channel I O abort preparing for recovery DESCRIPTION The driver writes this message to the console when it is preparing the port for a recovery operation DATA None ACTION None required This is a notification message for the recovery action elx mes2831 FLOGI response with cleared Fabric bit fcf index 0x x Switch Name 02 02 02 02 02 02 02 02 Fabric Name 02 02 02 02 02 02 02 02 DESCRIPTION When the driver completed a FLOGI the common service parameters did not indicate an FPort or NPort remote node The driver treats this as an error DATA None ACTION Validate the external cable connection and FPort Nport configuration Contact technical support if prob
43. the memory heap in bytes that should be initially allocated for the driver heap initial 32 MB The maximum possible size heap max 38 MB to which the driver heap is allowed to grow Drivers for VMware ESX ESXi 4 1 Configuration Section Page 17 EMULEX The following command line shows how to load the diver with initial heap size as 40 MB vmkload_mod be2net heap_initial 41943040 To configure the NIC driver to load with this value as the initial heap size after each reboot run the following command and reboot the system esxcfg module s heap initial 41943040 be2net Performance Tuning Network driver performance tuning improves performance of the network and the TCP Offload driver The OneConnect 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 and Enabling Jumbo Frames and TSO Note You can configure TSO TCP Segmentation Offload and jumbo frames using the vSphere client 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 Log into the console operating system 2 Locate the vmx file in the path vm s
44. 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 None ACTION ELS Events 1833 2800 elx_mes1835 Vport discovery quiesce failed state lt port_state gt fc_flags lt fc_flag gt wait msecs jiffies to msecs jiffies start time DESCRIPTION Could not pause discovery on this VPort DATA None ACTION None required elx mes1836 Could not issue unreg login all rpis status rc DESCRIPTION The unreg login cannot be issued DATA None ACTION None required elx mes1837 vport delete failed Cannot delete static vport DESCRIPTION Static VPorts cannot be deleted DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 61 J 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_mes1839 Create VPORT failed vname allocation failed DESCRIPTION Driver failed to allocate buffer for Virtual Machine name DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1920 Exec format error Dropping Link state event DESCRIPTION No dfchba instance available for Link State event dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Su
45. volumes VM NAME VM NAME 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 NIC driver interface thernetO features 15 4 To enable vmxnet emulation add the following line for the NIC driver interface ethernetO virtualDev vmxnet 5 Restart the VMs Steps 1 through 5 assume that ethO 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 The NIC driver supports Maximum Transmission Units MTUs between 64 bytes and 9000 bytes For the best combination of performance and resource use set the MTU to the maximum supported by the driver which is 9000 bytes This requires the MTU to be changed in the virtual switch as well as the guest operating systems Note You can configure TSO TCP Segmentation Offload and jumbo frames using the vSphere client Drivers for VMware ESX ESXi 4 1 Configuration Section Page 18 EMULEX Setting the MTU Size in the vSwitch To change the MTU to 9000 run the following
46. 048 or 4096 elx mes0445 Firmware initialization failed DESCRIPTION The driver was unable to initialize the hardware DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 45 gt G EMULEX elx_mes0446 Adapter failed to init moxCmd 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 elx mes0448 Adapter failed to init moxCmd mbxCommand 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 lpfc_ 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 9eattr attribute cannot be set to d allowed range is max DESCRIPTION Sysfs attribute value written excee
47. 2 UNREG FCFI issue mbox failed rc rc HBA state port 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 memory for fcf record DESCRIPTION DATA None ACTION None required elx mes2555 UNREG_VFI mbxStatus error lt u mb mbxStatus gt HBA state port state DESCRIPTION The unregister VFI mailbox command has failed DATA None ACTION None required elx mes2556 UNREG_VFI mbox allocation failed HBA state port state DESCRIPTION Could not allocate memory for UNREG_VFI mailbox command DATA None ACTION None required elx mes2557 UNREG VFI issue mbox failed rc rc HBA state port state DESCRIPTION Could not issue the UNREG_VFI mailbox command DATA None ACTION None required elx mes2558 ADD FCF RECORD mailbox failed with status shdr status add status shdr add status DESCRIPTION The ADD FCF RECORD mailbox command has failed DATA None ACTION None required elx mes2560 Failed to allocate mbox cmd memory DESCRIPTION Failed to allocate mailbox command memory DATA None ACTION None required 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 XR
48. 4 1 Troubleshooting Section Page 26 gt G 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 are 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 require a single block of 100 message numbers however some groups INIT FCP require two blocks Table 3 the Message Log table shows the groups and defines the associated number ranges Table 3 Message Log Table LOG Message Verbose Mask Definition Verbose Bit verbose Description LOG_ELS 0 1 ELS events LOG_DISCOVERY 0x2 Link discovery events LOG MBOX 0 4 Mailbox events LOG_INIT 0x8 Initialization events LOG LINK EVENT 0x10 Link events LOG FCP 0x40 FCP traffic history LOG NODE 0x80 Node tab
49. 8 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 cmd 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 status ID target id LUN lun id snum serial number DESCRIPTION The abort handler timed out waiting for abort to complete DATA None ACTION None required elx mes0798 Device Reset rport failure rdata x p DESCRIPTION Driver failed a device reset no rdata buffer DATA ACTION Software driver error If this problem persists report these errors to Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 52 gt G EMULEX Node Table Events 0900 0999 elx mes0915 Register VPI failed lt mbxStatus gt DESCRIPTION Could n
50. A request to set a VLAN priority tag was Must be 0 7 made with an invalid value Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 82 gt G EMULEX Table 5 ESX Server NIC Event Log Entries Continued Severity Message Displayed Description Warning Failed to allocate memory for The memory allocation for a pass through pass through command command failed The driver will continue to function The configuration utility that issued the pass through ioctl will fail Warning Pass through command failed opcode The pass through firmware command with lt DDD gt status 0x lt XXX gt the indicated opcode failed The driver should continue to function The configuration utility that issued the pass through ioctl will fail Warning Command to modify EQ delay failed The firmware command to change the EQ delay failed The driver will continue to function 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 Firmware halted This firmware does not support this controller Troubleshooting the iSCSI Driver The following table provides information on troubleshooting the iSCSI driver Table 6 iSCSI Troubleshooting Information Problem Solution When logging into more than By default ESX
51. 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 mes2729 Unable map single request buffer x x DESCRIPTION Driver unable to map SCSI command scatter gather buffer DATA 1 dma mapping error ACTION Software driver error If this problem persists report these errors to Technical Support 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 mes2745 Failed to allocate mbox for requesting FCF rediscover DESCRIPTION Driver is trying to rediscover FCF table but failed to allocate memory needed DATA ACTION Software driver error If this problem persists report these errors to Technical Support 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
52. ESCRIPTION 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 ELS CMD to remote DESCRIPTION DATA 1 ulpStatus 2 ulpWord 4 ACTION None required elx mes0138 ELS rsp Cannot issue reg login for DID DESCRIPTION REG LOGIN mailbox command failed Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 29 EMULEX DATA 1 nlp_DID 2 nlp state 3 nlp flag 4 nlp rpi 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 Completion Code 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 mes0150 SLI4
53. ESCRIPTION Could not issue an ELS PLOGI to the nameserver DID 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 IOCBs are in use DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 32 J gt G EMULEX elx_mes0256 Issue FDISC Cannot send IOCB 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 faile
54. ESCRIPTION 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 required 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 hex link fault DESCRIPTION The attempt to read the link attention register has returned an unknown value DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 42 EMULEX 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 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 bu
55. ION Driver failed to get DMA buffers needed for loopback test DATA 1 2 3 ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1957 EPERM Illegal BDE count d DESCRIPTION Driver received too many receive buffers for loopback operation DATA 1 receive buffer count ACTION Software driver error If this problem persists report these errors to Technical Support 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 63 EMULEX ACTION None required 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_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 alloca
56. Interrupt Moderation policy parameter configures the OneConnect driver to use different settings for Interrupt Moderation An im policy value of 1 achieves the highest interrupt rate whereas the value 4 provides the least interrupt rate The default value is 2 An im policy of 0 turns off the Interrupt Moderation algorithm in the driver Drivers for VMware ESX ESXi 4 1 Configuration Section Page 20 gt G EMULEX The large_io option can be used to modify the maximum transfer size in a single SCSI command By default the OneConnect iSCSI driver in ESX supports up to 128KB and 32 Scatter Gather entries in a single SCSI command If applications issue I O requests that are larger than 128KB or need more than 32 Scatter Gather entries the request will be split into multiple requests by the driver By specifying large_io 512 the iSCSI driver can support up to 512KB of data and a total of 128 Scatter Gather entries in a single SCSI command Note that by setting the option to 512 the amount of physical memory consumed by the driver increases Also though intermediate values between 64 and 512 will be accepted the memory used by the driver will be the same as what will be used for large io 512 To set the large io parameter in ESX type the following commands esxcfg module s large io 512 be2iscsi gt to set the parameter esxcfg module g be2iscsi to view the parameter value esxcfg module i be2iscsi to view the opti
57. Is that are attempting to be posted DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 70 J gt G EMULEX 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 allocated 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 sli4 hba scsi xri max 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 status add status shdr add status mbx status rc DESCRIPTION The list of XRI SGEs failed to be registered with the firmware DATA None ACTION None required 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
58. 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 moxCmd mbxCommand 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 mes0332 IOCB wait issue failed Data x x DESCRIPTION Driver issued IO failed to complete in polling mode DATA 1 error value ACTION Software driver error If this problem persists report these errors to Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 37 J gt G EMULEX elx_mes0334 Unknown IOCB command DESCRIPTION Received an unknown IOCB command completion DATA 1 type 2 ulpgCommand 3 ulpStatus 4 ulploTag 5 ulpContext ACTION This error could indicate a software driver or firmware problem If these problems persist report the
59. a response Drivers for VMware ESX ESXi 4 1 Troubleshooting Section gt G EMULEX Page 62 gt G EMULEX DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes1936 ENOMEM Kernel resource unavailable DESCRIPTION Driver failed to allocate DMA buffer during loopback test DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1944 ENOMEM kernel memory resource unavailable DESCRIPTION Driver failed to allocate kernel buffer for timed out IO request DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1949 ENOEXEC NULL parameter passed to function DESCRIPTION Driver tried to post receive buffer but no receive buffers available DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1950 ENOMEM IOCB resource not available DESCRIPTION Driver could not allocate IOCBs needed to post loopback receive buffers DATA 1 2 3 ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1951 ENOMEM MBUF resource not available DESCRIPTION Driver failed to get memory buffer needed for loopback test DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1952 ENOMEM DMA resource not available DESCRIPT
60. all drivers using the offline bundle ap OO gt esxupdate bundle offline bundle zip update Updating or Adding Drivers on Existing ESX and ESXi Installations Using vihostupdate ESX and ESXi 1 Power on the or ESXi host 2 Insert the driver CD in the CD ROM drive of the host where either the vSphere CLI package is installed or vMA is hosted 3 Mount the driver CD Navigate to cd mount point gt offline bundle and locate the lt offline bundle gt zip file 5 Run the vihostupdate command to install drivers using the offline bundle vihostupdate conn options install bundle offline bundle zip For more details on vihostupdate see the vSphere Command Line Interface Installation and Reference Guide 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 in ESX Server The NetQueue feature is enabled by default To determine if NetQueue is enabled run the following command from the ESX Server console 4 esxcfg advcfg j netNetqueueEnabled If netNetqueueEnabled FALSE is returned the feature is disabled e To enable NetQueue run the following command esxcfg advcfg k TRUE netNetqu
61. allocate iocb Rctl lt fh_rctl gt Type fh type received DESCRIPTION Could not allocate an IOCB with which to associate this received frame DATA None ACTION None required elx mes2710 PCI channel disable preparing for reset DESCRIPTION Driver is resetting the PCI slot for this port starting preparations DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes2711 PCI channel permanent disable for failure DESCRIPTION Driver has detected a fatal port error disabling PCI channel DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes2718 Clear Virtual Link Received for VPI index tag event tag DESCRIPTION A Clear virtual link was received from the Fabric for this VPI DATA None ACTION None required elx mes2719 Invalid response length xTGT ID lun LUN 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_mes2723 PCI channel I O abort preparing for recovery DESCRIPTION Driver is preparing port PCI channel for reset recovery after IO error DATA ACTION Software driver error If this problem persists report these errors to Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 74 J gt G EMULEX elx_mes2726 READ_FCF_RECORD Indicates empty FCF table
62. ameters Refer to the OneCommand Manager 5 2 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 changes that impact all adapters in the system global changes follow these steps See FC FCoE Driver Configuration Parameters on page 14 for parameter names and values Parameter values are in both hexadecimal and decimal Drivers for VMware ESX ESXi 4 1 Configuration Section Page 12 EMULEX 1 From the Console Operating System COS terminal window type esxcfg module s param value param2 value driver name The driver name is obtained from the vmk1oad mod 1 call Look for the Ipfc prefix 2 Rebootthe 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 service Refer to the VMware documentation for more information Example of Permanent Global Configuration The following example sets lun queue 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 Locate the parameter Ipfc lun qu
63. apability e PCI hot plug support vendor specific e VPD Vital Product Data support NPIV ID Virtualization support Adapter personality change support New Features in this Release e Supports OneConnect OCe11102 xT 10GBASE T UCNAs Prerequisites There are no prerequisites at this time Drivers for VMware ESX ESXi 4 1 Installation Section Page 1 EMULEX Compatibility e For alist of adapters that are compatible with this driver see the driver Downloads page on the Emulex website For compatible firmware versions see the Downloads page for the specific adapter Things to Know Before You Download The driver is matched to a particular version of the Emulex Core Kit the adapter firmware and the NIC driver Refer to the Downloads page on the Emulex website 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 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 driver is available through the VMware support site Refer to the VMware support website for further details See the OneCommand Manager Command Line User Interface
64. ate virtual machine network VMNetO and add it to vSwitch0 esxcfg vswitch L vmnicO vSwitchO link vmnicO to vSwitchO0 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 VLAN filtering is supported in the hardware To configure VLANs create the vSwitch with the required VLAN 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 The amount of memory allocated by default for a network heap depends on the amount of memory configured in the system The ESX Server network stack allocates a minimum of 64 MB to the network heap to handle network data More memory is allocated to the network heap if the system is configured with more memory If the network load requires more than 64 MB of memory the NIC 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 You can allocate more memory for the network heap using the esxcfg advcfg command in the following example To read the current size of the network heap run 4 esxcfg advcfg j netPktHeapMaxSize netPktHeapMaxSize 0 If the defau
65. ck Add to eject the ESX installation DVD Insert the driver CD in the DVD drive of the ESX host Select driver module to import drivers to the ESX host o I OY ume ee Click Next to continue A dialog box displays the following message Load the system drivers Click Yes After loading the driver module continue installing ESX After the drivers are installed you are prompted to swap the driver CD with the ESX installation DVD Complete the installation of ESX 11 After the operation system installation is complete and the system has rebooted run the following from the console command line rpm e vmwar sx drivers scsi be2iscsi 12 Insert the driver CD into CD ROM drive of the ESX host 13 Mount the driver CD 14 Navigate to cd mount point gt offline bundle and locate the lt offline bundle gt zip file 15 Run the esxupdate command to install the drivers using the offline bundle esxupdate maintenancemod bundle offline bundle zip update Drivers for VMware ESX ESXi 4 1 Installation Section Page 8 gt G EMULEX Updating or Adding Drivers on Existing ESX Installations Using esxupdate ESX Only Power on the ESX host and log into an account with administrator capability Place the driver CD in the CD ROM drive of the ESX host Mount the driver CD Navigate to lt cd mount point gt offline bundle and locate the lt offline bundle gt zip file Run the esxupdate command to inst
66. command for each switch in the console operating system esxcfg vswitch vSwitch lt N gt m 9000 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 NIC driver interface in each Linux Guest operating system to 9000 run the following command ifconfig eth N mtu 9000 where N is the number of the Ethernet interface on which you are working Setting the MTU Size for a Windows Guest Operating System To set the MTU in each Windows guest operating system 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 select jumbo e1000 emulation or set the MTU value VMware PCI Adapter emulation momo mec iSCSI Driver Configuration Configuring iSCSI Driver Options The following table lists the user configurable iSCSI driver options on ESX Server 4 1 It includes a description of the parameters default values and the limits within which they can be configured Note If the value given for a parameter is outside the supported range MIN and MAX values then the driver will log an error in the Event Log and continue to load by taking the default value of the parameter Drivers for VMware ESX ESXi 4 1 Configuration Section Page 19 gt G EMULEX Default Minimum Maximum nan Paramete
67. d for the nameserver DATA None ACTION Check the switch configuration 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 port state sparam mbox 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 rc Data fc flag fc rscn id cnt DESCRIPTION The driver was not able to send the nameserver CT command Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 33 EMULEX 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 un ulpWord 4 Data
68. d indicate a software driver firmware or hardware problem Report these errors to Technical Support 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 mbxcommand 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 mes0311 Mailbox command x x cannot issue Data x x DESCRIPTION The driver detected an HBA error and can t issue the mailbox DATA 1 sli flags 2 hba flags ACTION Software driver error If this problem persists report these errors to Technical Support elx mes0312 Ring lt ringno gt handler portRspPut rspPu
69. ds 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 to init mbxCmd mbxCommand 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 moxCmd mbxCommand 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 46 J gt G EMULEX to Technical Support elx_mes0472 Unknown PCI
70. e bundle file name varies depending on the package that is to be installed the example below uses the name offline bundle zip please replace this file name with the name of the offline bundle to be installed An offline bundle can be installed on a VMware ESX server locally using the esxupdate command The following example uses the offline bundle file name offline bundle zip when using this example as a reference make sure to use the file name of the offline bundle to be installed note the maintenance parameter is required for FCoE NIC and iSCSI driver installations root testmachine esxupdate nosigcheck maintenancemod bundle lt offline bundle zip gt Reboot the VMware ESX server to activate the new drivers LPFC Driver The LPFC driver is the driver used for HBA adapters and the UCNA adapter FCoE ports To install the Ipfc driver execute the following command in the command prompt of the ESX ESXi host mkdir tmp mountpoint mount r o loop path to driver iso tmp mountpoint esxupdate maintenancemode update bundle lpfc driver zip gt where lpfc driver zip gt is the Ipfc driver released as zip file NIC Driver The NIC driver is the driver for the NIC ports of the UCNA adapters To install the NIC driver execute the following command in the command prompt of the ESX ESXi host mkdir tmp mountpoint mount r o loop path to driver iso tmp mountpoint 4 esxupdate maintenancemode
71. elx mes2543 Mailbox command vpi mbxCommand 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 mbxCommand cannot issue DESCRIPTION The adapter cannot be accessed on the PCI bus DATA 1 5114 mbx opcode 2 sli flag 3 flag ACTION None required elx mes2546 New FCF found index index tag event tag DESCRIPTION A new FCF has been found DATA None ACTION None required elx mes2547 Read FCF record failed DESCRIPTION Could not read the FCF record from the firmware DATA None ACTION None required elx mes2548 FCF Table full count count tag event tag DESCRIPTION The FCF table is full DATA None ACTION None required elx mes2549 FCF disconnected from network index index tag event tag DESCRIPTION The FCF has disconnected from the network DATA None ACTION None required elx mes2550 UNREG FCFI mbxStatus error lt u mb mbxStatus gt HBA state port state DESCRIPTION The unregistered FCFI has failed DATA None ACTION None required elx mes2551 UNREG FCFI mbox allocation failed HBA state port state DESCRIPTION The allocation for the UNREG FCFI mailbox command has failed DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 69 EMULEX elx mes255
72. er guest OS s may also need to be tuned similarly Consult the tuning guides that accompany those operating systems Drivers for VMware ESX ESXi 4 1 Configuration Section Page 21 gt G EMULEX Interrupt Moderation Policy Settings Interrupt Moderation Policy settings control the rate of interrupts for OneConnect hardware By default the driver implements an Interrupt Moderation scheme that is based on the I O load and the interrupt rate The default setting for Interrupt Moderation Policy tries to vary the interrupt rate between 3500 to 10000 interrupts per second In addition the OneConnect driver allows other configuration settings which are listed in the following table Setting Parameter Description Disabled im_policy 0 Interrupt Moderation algorithm is turned off in the driver adressive im gt 1 Achieves the highest interrupt rate among all available gg po icy settings Moderate im_policy 2 Is also the default value Conservative im_policy 3 Achieves a lower interrupt rate than Moderate Very Achieves the minimum interrupt rate among all available im policyz4 Conservative settings While the default setting of Moderate may work for most configurations there are instances when the setting may need to be altered Changing the Interrupt Moderation Policy setting should be based on the initiator system configuration the number of iSCSI targets that will be connected the I O load a
73. ersists report these errors to Technical Support 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 New Events elx_mes2796 Mailbox memory allocation failed DESCRIPTION The driver failed to get memory resources to release an RPI DATA None Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 77 EMULEX ACTION None The driver s heap is exhausted A server reboot is required to fix the exhaustion Contact technical support if the problem persists elx mes2798 Unreg_vpi failed vpi mb status DESCRIPTION The driver attempted to unregister a virtual port index and failed The failure status is printed DATA None ACTION This condition is not catastrophic but is unexpected If problems persist contact technical support elx_mes2813 Mgmt IO is Blocked x mbox cmd still active DESCRIPTION The HBA s
74. es 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 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 73 gt G EMULEX 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 elx_mes2705 Failed to enable interrupt DESCRIPTION Driver to enable any interrupt mode fatal driver unloads DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes2707 Ring lt Ring gt handler Failed to
75. es0492 Unable to allocate memory for issuing SLI CONFIG SPECIAL mailbox command DESCRIPTION A memory allocation fault occurred when issuing a mailbox DATA ACTION This could be a transient error If this problem persists report these errors to Technical Support elx mes0493 SLI CONFIG SPECIAL mailbox failed with status rc DESCRIPTION Mailbox command failed DATA None Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 47 J gt G EMULEX ACTION Ensure the adapter s firmware is current Unload and reload the driver elx mes0494 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 shdr status add status shdr add status mbx status rc DESCRIPTION Mailbox command failed DATA None ACTION The driver fails to load Contact Emulex Technical Support 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 DESCRIPTION The completion queue event for the fast
76. eue depth in Table 1 on page 14 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 lpfc820 Example of Permanent Per Adapter Configuration The following example sets lun queue depth to 20 default is 30 for adapter 1 1 Set the adapter specific value Type esxcfg module s lpfcl lun queue depth 20 lpfc820 2 Reboot the server Type reboot The new setting is used when the driver reloads To verify the setting type esxcfg module g lpfc820 The following example sets lun queue depth to 20 default is 30 for adapter 1 and lun queue depth to 10 default is 30 for adapter 2 1 Set the adapter specific value Type esxcfg module s lpfcl lun queue depth 20 lpfc2 lun queue depth 10 lpfc820 Note Type the command all on one line without a carriage return Drivers for VMware ESX ESXi 4 1 Configuration Section Page 13 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 EMULEX For instructions on dynamically adding LUNs and targets refer to the Using Rescan section of the VMware SAN Config documentation FC FCoE Driver Configuration Parameters All adapter specific parameters have an IpfcX pre
77. eueEnabled Reboot the ESX Server for the change to take effect Drivers for VMware ESX ESXi 4 1 Installation Section Page 9 EMULEX How an ESX Server Creates and Names Interfaces The NIC driver supports a maximum of four UCNAs per system For dual channel UCNAs running in 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 When vNIC mode is enabled in the adapter BIOS and the UCNA is in NIC only mode the driver creates eight interfaces four for each physical port When vNIC mode is enabled in the adapter BIOS and the UCNA is in FCoE or iSCSI mode the driver creates only 6 NIC interfaces The other two interfaces are reserved for the FCoE and iSCSI The interfaces are labeled vmnicO 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 esxcfg nics 1 list recognized nics esxcfg vswitch 1 list available vswitches 4 esxcfg vswitch a vSwitchO0 create vSwitchO0 esxcfg vswitch A VMNetO0 vSwitchO0 cre
78. ffer 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 to val allowed range is LPFC MIN DEVLOSS TMO LPFC MAX DEVLOSS TMO 5 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 96s 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 96s 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 temperature 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
79. fix where X is the driver instance number For example setting IpfcO 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 O Dynamic parameters do not require a system reboot for changes to take effect Table 1 FC FCoE Driver Configuration 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 ack0 0 0 Off 1 On No Use ACKO for class 2 Ipfc discovery threads 32 1 64 No Specifies the maximum number of PLOGI commands that can be outstanding for a discovery Ipfc fcp class 3 2 3 No FC class for FCP data transmission Ipfc fdmi on 0 0 2 Yes False 0 if disabled 1 or 2 if enabled depending on type of support needed Ipfc link speed 0 O auto select No Sets link speed 121 Gb s Note Not supported for 2 2 Gb s FCoE 4 4 Gb s 8 8 Gb s Ipfc log verbose 0x0 0x0 Ox7fffffff Yes Extra activity logging bit mask Ipfc lun queue depth 30 1 128 Yes Default max commands sent to a single logical unit disk Drivers for VMware ESX ESXi 4 1 Configuration Section Page 14 Table 1 FC FCoE Driver Configuration Parameters Continued gt G EMULEX Variable Default Min Max Dynamic Comments Ipfc max scsicmp
80. g ACTION None required elx mes2530 Mailbox command vpi 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 cpi cannot issue DESCRIPTION DATA 1 mb mbxCommand 2 sli flag 3 flag ACTION None required elx mes2532 Mailbox command lt vpi gt mbxCommand cannot issue DESCRIPTION The mailbox bootstrap code detected that the SLI layer is active DATA 1 5114 mbox opcode 2 sli flag 3 MBX POLL ACTION None required elx mes2533 Mailbox command vpi mbxCommand cannot issue DESCRIPTION DATA 1 sli4_mbox_opcode 2 sli flag 33 MBX NOWAIT ACTION None required elx mes2535 Unsupported RQ count entry count DESCRIPTION The receive queue ring can only be 512 1024 2048 or 4096 DATA None ACTION None required elx mes2536 Unsupported RQ count entry count 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 68 EMULEX ACTION None required elx mes2541 Mailbox command lt vpi gt mbxCommand cannot issue DESCRIPTION DATA 1 sli4 mbx opcode 2 sli flag 3 flag ACTION None required
81. hdr add status mbx DESCRIPTION The READ FCF RECORD mailbox command has failed DATA None ACTION None required elx mes2522 Synchronous READ FCF RECORD mailbox failed with status x x add status X X DESCRIPTION Driver failed to read the active FCF Record on an FCoE link FCF may not be available DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes2523 Allocated DMA memory size lt alloc_len gt is less than the requested DMA memory size req len 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 67 J gt G EMULEX 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 vpi cannot issue DESCRIPTION DATA 1 mbxCommand 2 sli flag 3 fla
82. ilities Follow these instructions to uninstall the Emulex configuration utilities To uninstall the OneCommand Manager agent Log in as root 2 Type rpm qa grep 1 to verify that this kit is installed This command should list elxocmcore esx41 lt kit version gt for the current release 3 Type rpm e elxocmcore esx4l kit version Installing the NIC Driver Introduction This part of the guide provides installation 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 and the fundamentals of network storage devices Installing the NIC Driver and Management Software The Emulex NIC driver for VMware ESX 4 1 is available through the VMware support site The VMware support website also includes a documentation link to the correct installation procedures for this driver Follow the installation instructions provided on the VMware support website See the OneCommand Manager Command Line User Manual for instructions on installing the Emulex core kit Note Before installing the Emulex OneCommand Manager Kit you must install the Ipfc driver from the VMware website Note Before installing OneConnect network drivers and management software verify that the firmware version is correct If it is proceed with the installation If it is not update the firmware using the OneCommand Manager app
83. imeout DESCRIPTION The driver issued a CLEAR LA that never completed DATA None ACTION None required The driver should recover from this event elx mes0230 Unexpected timeout hba linkstate link state DESCRIPTION Discovery has timed out and the adapter state is not ready DATA None Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 31 J gt G EMULEX ACTION None required elx_mes0231 RSCN timeout DESCRIPTION The driver has lost track of what 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 unloaded 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 err 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 elx mes0252 Cannot issue NameServer login D
84. ink 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 eventTag 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 53 EMULEX 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 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 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 required elx mes1309 Link Down Event x9ex received Data x x x9 ex DESCRIPTION The port generated a link down event to the host DATA 1 fc eventTag 2 port state 3 VPort fc flag ACTION None required 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
85. ization failed to sysfs attribute DATA None ACTION None required elx mes1418 Invalid HBA PCI device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx mes1419 Invalid HBA PCI device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required elx mes1420 Invalid HBA PCI device group lt dev_grp gt DESCRIPTION Invalid adapter PCl device group detected DATA None ACTION None required 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 uerr_hi_reg lt ue hi onlineO_reg lt OnlineO 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 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 onlineO_reg lt OnlineO gt online1_reg lt Online1 gt DESCRIPTION The adapter has notified the driver that it has encountered an unrecoverable error DATA None Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 56 gt G EMULEX ACTION A dump from the OneCommand Manager application should be taken Then unload
86. l time 0 0 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 scan down 0 Off 1 On No Select a method for scanning ALPA to assign a SCSI ID Ipfc tgt queue depth 8192 10 8192 No Default maximum number of commands sent to a single target By default there is no effective limit at the target level Ipfc topology 0x0 loop then P2P 0x1 internal loopback Ox2 P2P only 0x4 loop only Ox6 P2P then loop No FC link topology Defaults to loop If that fails the driver attempts to link in point to point mode Note Not supported for FCoE Ipfc use adisc 0 Off 1 On Yes Send ADISC instead of Port Login PLOGI for device discovery or Registered State Change Notification RSON Ipfc devioss 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 use INTX min 1 use MSI 2 use MSI X max No Selects which interrupt mode to use By default the driver uses INTX VMware guidance is to use MSI X but MSI is available Ipfc fcp wq count No Configures the number of fast path work queues used by the host and port Ipfc fcp eq count No Configures the number of fast path event queues used by the host and port Ipfc sg seg count 64
87. le proc vmware log for example 128 MB run esxcfg advcfg k 128 netPktHeapMaxSize After configuring the size reboot the system A value of 0 indicates default 64 MB To increase the size to netPktHeapMaxSize can also be configured through VI Client using Configuration gt Advanced Settings gt VMKernel Unable to ping from one VM to another The NIC driver creates two vmnic interfaces one for each port VM 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 80 gt G EMULEX Table 4 Troubleshooting the NIC Driver Continued Problem Answer Solution 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 ESX Server NIC Error Log Codes
88. le events LOG TEMP 0x100 Temperature sensor events LOG MISC 0x400 Miscellaneous and FCoE events LOG SLI 0x800 SLI events LOG FCP ERRORLOG 0x1000 Selective FCP events LOG LIBDFC 0x2000 IOCTL events LOG VPORT 0x4000 NPIV events LOF EVENT 0x10000 IOCTL event LOG DAEMON 0x20000 IOCTL Daemon events LOG FIP 0x40000 FIP event LOG PROC 0x80000 Procfs events LOG ALL MSG Oxffffffff Log all messages Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 27 EMULEX Message Log Example The following is an example of a LOG message Jul 2 04 23 34 daffy kernel lpfc 0000 03 06 0 0 1305 Link Down Event x2f2 received Data x2f2 x20 x110 In the above LOG message e 0000 03 06 0 identifies the identifies the PCI location of the particular Ipfc hw port 0 identifies Emulex HBAO e 1305 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 status extended status TMO lt timeout gt DESCRIPTION An ELS FLOGI command that was sent to the fabric failed DATA 1
89. lems persist elx mes2858 FLOGI failure Status x x x x TMO x x DESCRIPTION The driver issued a FLOGI but never received any completion with the timeout period The driver is marking the FLOGI as failed and stops discovery DATA None ACTION Please check your fabric to ensure it it operating correctly Contact technical support if problems persist elx mes2862 FCF x x matches property of in use FCF x x DESCRIPTION The driver has found an FCF record that matches the properties of the current FCF record except for the VLAN id and Index The driver will attempt to use this FCF DATA None ACTION None required The driver is in its FCF discovery phase and is trying to recover a match to its in use FCF elx_mes2863 New FCF x x matches property of in use FCF x x DESCRIPTION The driver has found a new FCF record that matches the properties of the current FCF record but the record instance numbers don t match DATA None ACTION None required The driver is in its FCF discovery phase and is trying to recover a match to its in use FCF elx_mes2877 FCP XRI exchange busy wait time d seconds DESCRIPTION An FCP exchange cannot be released no port completion Driver is waiting DATA ACTION Software driver error If this problem persists report these errors to Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 79 gt G EMULEX elx_mes2878 2878 ELS XRI exchange busy wait time d seco
90. lication and reboot your system before proceeding with the installation Drivers for VMware ESX ESXi 4 1 Installation Section Page 3 EMULEX Uninstalling the NIC Driver See the VMware Patch Download page for instructions Installing the iSCSI Driver Introduction This part of the guide provides installation information for the Emulex OneConnect UCNA Before using this product you need a working knowledge of iSCSI TOE TCP offload engine technology and the fundamentals of network storage devices To install the driver for ESX Server you must use the ESX installation DVD and the ESX driver ISO image provided on the Emulex website To use the driver ISO images you must first burn the ISO image file to a CD ROM Performing a Fresh Installation of ESX Server To do a fresh install of ESX Server 4 1 in a server with OneConnect hardware you will need the ESX installation DVD and the ESX driver CD you created to begin driver installation If OneConnect is the only network interface in your server or if you wish to install ESX Server in an iSCSI target drive connected to the OneConnect the OneConnect iSCSI driver must be loaded from the driver CD during ESX Server installation Follow these steps to do this 1 Before you begin make sure that the Emulex firmware version matches the ESX Server 4 1 driver version 2 Place the ESX installation DVD in the DVD drive of the host to start the installation of ESX Server 4 1 Fol
91. lization 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 81 Table 5 ESX Server NIC Event Log Entries Continued gt G EMULEX Severity Message Displayed Description Warning Using INTx interrupts Net The driver could not allocate MSIx vector for Queues feature will be disabled interrupt The driver may continue to work but the performance may be impacted Warning WARNING Found a OneConnect The OneConnect UCNA is an x8 Gen2 PCI card in Gen lt D gt x lt D gt PCI e e device For best performance the UCNA slot Should be in Gen 2 x8 should be installed in a Gen2 PCl e slot 8 or slot for best performance 16 channels wide The driver displays this warning if it finds the device in a slower or narrower PCl e slot The device continues to work with reduced 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 The
92. low the on screen prompts to continue the installation process When prompted for Custom Drivers select Yes to install custom drivers Click Add to eject the ESX installation DVD Place the driver CD in the DVD drive of the ESX host and select driver module to import the drivers pcr ADD Click Next to continue When prompted to load the system drivers click Yes 9 After loading the drivers follow the prompts to continue installing ESX Server After the drivers are installed you will be prompted to swap the driver CD with the ESX installation DVD 10 After you install ESX Server you can create your Virtual Machines VMs by following the VMware instructions Refer to the VMware ESX Server 4 1 documentation for more information Adding or Upgrading the iSCSI Driver in an Existing ESX Server You can add the OneConnect adapter and driver to an existing ESX Server installation or upgrade a local or an iSCSI boot installation of an ESX Server with the OneConnect controller to a newer version of OneConnect software To do this run the install sh script To install the OneConnect and ESX Server with the install sh script do the following 1 Insert the Install CD into your CD ROM drive Drivers for VMware ESX ESXi 4 1 Installation Section Page 4 gt G EMULEX 2 Change directory from where the CD was mounted to CD1 ESX Installer For example home sengines cd CD1 ESX Installer 3 From the installer directory type sh Ins
93. lt value of 64 MB is in effect this command shows the PktHeapMaxSize as 0 If any other value is in effect the command returns that value For example to set the heap size to 128 MB run the command X 4 esxcfg advcfg k 128 netPktHeapMaxSize esxcfg advcfg j netPktHeapMaxSize netPktHeapMaxSize 128 Drivers for VMware ESX ESXi 4 1 Installation Section Page 10 EMULEX The new value takes effect after a reboot Note Although ESX supports up to 256 iSCSI targets it can only display up 139 targets For information on displaying more that 139 targets see the ESX Server iSCSI in the Troubleshooting section Interrogating the NIC Driver To get information on the installed NIC driver enter esxupdate query vib view grep be2net This is a sample output root8bladel0 esxupdate query vib view grep be2net CrOSS vmwar sx drivers net be2net 400 2 102 225 12 1 0 4 164009 installed 2010 04 05T11 28 38 540372 07 00 CrOSS vmwar sx drivers net be2net 400 2 102 200 10 1 0 4 164009 retired 2010 03 18T713 59 02 520994 07 00 Drivers for VMware ESX ESXi 4 1 Installation Section Page 11 EMULEX Configuration FC and FCoE Driver Configuration You can configure driver parameters using native ESX tools the Emulex OneCommand Manager command line interface CLI application for use in non lockdown mode or the OneCommand Manager for VMware vCenter
94. lx_mes1814 Mbox u mb mbxCommand failed no 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 mbxECmd mailbox command READ SPARM mbxStatus mailbox status rc status 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 configured 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 name Xx XX XX XX XX XX XX XX DESCRIPTION An in
95. 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 DESCRIPTION Failed to allocate memory for MSI X interrupt vector entries DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 71 EMULEX elx_mes2574 Not enough EQs lt sli4_hba max_cfg_param max_eq gt from the pci function for supporting FCP EQs cfg fcp eq count 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 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 sli4 hba max cfg param max wq from the pci function for supporting FCP WGs cfg fcp wq count DESCRIPTION The driver was not configured with the minimum number of fast path work queues DATA None ACTION None required elx mes2597 Mailbox co
96. 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 completion queue DATA None ACTION None required elx_mes0366 Not a valid fast path completion event majorcode lt major code hex gt minor code 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 fcpcqid 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 40 J gt G EMULEX elx_mes0371 No entry from the CQ identifier lt queue_id gt type lt type gt DESCRIPTION There was no completion
97. mmand lt vpi gt mbxCommand 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 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 rc 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 72 EMULEX 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 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 go
98. nd on the throughput and latency offered by these iSCSI targets On systems capable of sustaining a higher interrupt rate and when the number of targets that will be connected is less up to 8 the more Aggressive setting will result in lower latency and higher values of I O operations per second IOPs But the higher interrupt rate could also result in system stalls and freezes especially during higher values of queue depth and smaller sized I O requests Though on a configuration that involves a large number of iSCSI targets more than 32 or 64 and higher values of queue depth the default setting may prove to be too aggressive and the Interrupt Moderation setting may need to be changed to Conservative or Very Conservative Though this will increase latency of an I O request the lower interrupt rate may allow the system to be functional under a high load 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 Loss of immediate link to the initiator e g cable disconnect port failure The OneConnect firmware detects and notifies the driver of a loss of the link When this hap pens the driver will queue the I O requests internally up to a configured timeout periodso that the operating system does not see I O erro
99. nd on the mailbox queue 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 moxCmd lt u mb mbxCommana gt mbxStatus lt 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 mes0359 Not a valid slow path completion event majorcode x x minorcode x x n bf get lpfc ege major code bf get lpfc ege minor code eqe DESCRIPTION SLI 4 The EQE is not valid DATA None ACTION None required elx mes0360 Unsupported EQ count entry count DESCRIPTION Cannot create an event queue of this size DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 39 J gt G EMULEX elx_mes0361 Unsupported CQ count lt entry_count gt DESCRIPTION Cannot create a completion queue of this size DATA None ACTION None required elx_mes0362 Unsupported MQ count lt entry_count gt DESCRIPTION Cannot create MQ count of this size DATA None ACTION None required elx_mes0364 Invalid param DESCRIPTION SLI 4 The post SGL function was passed an invalid XRI DATA None ACTION None required elx
100. nds DESCRIPTION An ELS exchange cannot be released no port completion Driver is waiting DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes2881 RRQ failure DID 06X Status x x x x DESCRIPTION Driver RRQ request failed driver write target DID and status values DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes2882 RRQ completes to NPort x x with no ndlp Data x x x x x x DESCRIPTION Driver completes a RRQ but there is no node association DATA 1 Status 2 Reason 3 loTag ACTION Software driver error If this problem persists report these errors to Technical Support elx_mes2884 Vport array allocation failed DESCRIPTION Driver could not create a buffer list of vports DATA ACTION Software driver error If this problem persists report these errors to Technical Support Troubleshooting the NIC Driver The following table providestroubleshooting information for the NIC driver Table 4 Troubleshooting the NIC Driver 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 network connectivity the current value run 2 Several alloc skb failed messages esxcfg advcfg j netPktHeapMaxSize appear in the log fi
101. ne 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 50 EMULEX 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 elx mes0543 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 bad information header Ox x le32 to cpu vport info signature le32 to cpu vport info rev amp VPORT INFO REV MASK DESCRIPTION Invalid information header the signature or revision is invalid DATA None ACTION Static VPorts does not
102. ng Native ESX Tools 12 Dynamically Adding LUNs and 14 FC FCoE Driver Configuration Parameters 14 Creating a Fibre Channel Remote Boot 16 Managing ESX ESXi Server Through the CIM 16 Installing the Emulex CIM Provider seeesseeennnnnn 16 CIN PIOVIOOR Sunset eene e eR ER 16 Working with VPorts Virtual Ports 17 Creating Deleting and Displaying VPorts 17 NIC Driver nnne nnns 17 Configuring NIC Driver Options sssssssseseeeeenenne nenne 17 18 Using vmxnet Emulation and Enabling Jumbo Frames and TSO 18 Configuring a Virtual Switch to Use Jumbo 18 iSCSI Driver Configuration ssssssssssssssssssseeneeeeee nennen nennen 19 Configuring iSCSI Driver 19 Interrupt Moderation Policy 5 22 ISCSI Error Handling sssssssssssseeeeeeeeeenne nennen 22 Configuring LDTO and on ESX
103. odes 6 Installing er ercerrrecet 7 esx pdate Pro d re uan iati iiti dai 7 LPR DUNO 7 7 PGS NIV 8 Installing the Out of Box Driver ssssssssssssseeeeenennn enne nnne 8 Installing Drivers for Devices as Part of a New ESX Installation ESX Only 8 Updating or Adding Drivers on Existing ESX Installations Using esxupdate ESX OMY RR 9 Updating or Adding Drivers on Existing ESX and ESXi Installations Using vihostupdate ESX and 9 Virtualization FeatUl OS Ru Rn ERN RERERERERNRIRERIAKRKRERAERKRERYARREREAYRRRERER 9 Enabling the NetQueue Feature 9 How an ESX Server Creates and Names 10 Gontiguring b E a 10 Configuring Network Heap Size in ESX Server 10 Interrogating the NIC 11 Drivers for VMware ESX ESXi 4 1 User Manual Page iv Configuration mee aa aes 12 FC and FCoE Driver Configuration nennen 12 Temporary FC FCoE Configuration Methods Using Native ESX Tools 12 Permanent FC FCoE Configuration Methods Usi
104. ondition This may indicate a target is in error or may point to transient network connectivity issues It may also indicate a firmware error The be2iscsi driver did not receive an iSCSI command window update up to 25 seconds during I O operations Following this error log entry the next entry will indicate the session handle where this error occurred The be2iscsi driver will trigger a session recovery on the session and continue Check for any errors reported at the target The iSCSl initiator is only supported with certified Targets Check for software updates at the target vendor s website Check for software updates at the Emulex website If the above fails contact technical support The be2iscsi driver received an invalid iSCSI Command Sequence Number update from the target Following this error log entry the next three entries will indicate the session handle and the iSCSI parameters MaxCmdSN and ExpCmdsSN respectively Check for any errors reported at the target The iSCSl initiator is only supported with certified targets Check for software updates at the target vendor s website Check for software updates at the Emulex website If the above fails contact technical support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 85 gt G EMULEX Table 7 iSCSI Error Log Code Entries Continued Message Recommended Resolution A connection to the target was lost for
105. ons Even though the VMware operating system can be tuned to accept larger I O sizes from guest operating systems the guest operating systems will also often need to be tuned to create those larger I Os For example a Windows 2003 32 bit guest will by default have a maximum transfer size of 64KB even if the VMware kernel is tuned to allow 512KB IO transfers You will need to modify the guest registry in order to achieve the maximum transfer rate set in the VMware kernel To do this use the registry editor to add or modify the following entry to change the maximum transfer size for the Windows guest HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Symmpi Param ters Device MaximumSGList The formula used to calculate the proper value for MaximumSGList is For a 32 bit Windows guest use the following formula MaximumSGList Maximum Transfer Size 4 1 For a 64 bit Windows guest use the following formula MaximumSGList Maximum Transfer Size 8 1 For example to allow a 256 Kbyte transfer size on a 32 bit guest this would be the formula to use 256 4 64 1 65 decimal or 0x41 hexadecimal The maximum value allowed for MaximumSGList is 255 or OxFF For the particular value of OxFF the internal value passed to Windows is increased to 0x101 allowing support for a full 1 Mbyte transfer 2 Mbytes for 64 bit The MaximumSGList is 129 for a 512K transfer Oth
106. ot register the VPI DATA None ACTION None required Miscellaneous and FCoE Events 1200 1299 elx mes1201 Failed to allocate dfc host DESCRIPTION Driver failed to allocate a dfc host and bind it to the management stack DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1209 CT Request error Data x x x x DESCRIPTION IOCTL CT response error driver is failing the IOCTL request DATA 1 response buffer flag 2 Data Size ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1262 Failed to allocate dfc host DESCRIPTION Could not allocate memory the dfc host struct DATA None ACTION None required Link Events 1300 1399 elx mes1300 Link Down Event in loop back mode DESCRIPTION Driver received a link down event while in loopback mode unexpected event DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1302 Invalid speed for this board Reset link speed to auto x x DESCRIPTION Driver detected an invalid link speed Resetting Link to Auto mode DATA 1 Invalid speed detected ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1303 Link Up Event eventTag received Data x x x x X X DESCRIPTION A link up event was received It is also possible for multiple l
107. p reg lt 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 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 resource 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 55 gt G EMULEX 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 Initial
108. 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 Support 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 WQ DATA None ACTION The driver fails to load Contact Emulex Technical Support Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 48 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 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 slo
109. pdate the initrd by typing the command esxcfg boot b 3 Reboot the system Invoking Silent Uninstall The OneConnect software installation utility also supports Silent Uninstall mode for ESX Server To invoke silent uninstall do the following 1 Run the following command line to start Silent Uninstall sh Uninstall sh s 2 Run this command to get the exit code echo Uninstall Exit Codes The OneConnect Server Software Installer implements the following exit codes in VMware ESX Server Note that all values are in decimal 0 RPM not found 10 Success All software was un installed correctly with no errors A system reboot is required 17 The Installer was executed by a system user that is not a superuser 20 Invalid command syntax Drivers for VMware ESX ESXi 4 1 Installation Section Page 6 gt G EMULEX Installing All the Drivers To install all drivers use the esxupdate utility provided by VMware in ESX and ESXi platforms The drivers and components that can be installed include LPFC NIC iSCSI esxupdate Procedure For esxupdate installs perform the following procedure Directly mount the ISO image in this manner root testmachine mkdir tmp mountpoint root testmachine mount r o loop path to driver iso tmp mountpoint Once the ISO image is mounted you can access the offline bundle in the tmp mountpoint offline bundle directory Since the offlin
110. pport elx mes0125 FDISC Failed x x Fabric out of resources DESCRIPTION The fabric rejected an FDISC because the switch can not support any more Virtual ports DATA 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 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 nlp 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 DID completion D
111. pport elx_mes1923 Exec format error Dropping rscn event DESCRIPTION No dfchba instance available for RSCN event dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1926 Exec format error DESCRIPTION No dfchba instance available for IOCTL loopback test dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1927 Exec format error Dropping temp event DESCRIPTION No dfchba instance available for Temperature event dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1928 Exec format error Dropping dump event DESCRIPTION No dfchba instance available for Dump event dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1929 Exec format error DESCRIPTION No dfchba instance available for IOCTL loopback xri read dropping DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1934 ENOMEM DMA coherent resource unavailable DESCRIPTION Driver failed to allocate a DMA buffer for an IOCTL request DATA ACTION Software driver error If this problem persists report these errors to Technical Support elx mes1935 Loopback test did receive any data DESCRIPTION Driver ran loopback test but did not receive
112. r Description Value Value Value Link Down Timeout seconds This determines the amount of time the 20 30 initiator driver will wait for LDTO Seconds 0 seconds Seconds the controller s physical link to become available before reporting that the LUNs are unavailable to the operating system 0 seconds Extended Timeout in Seconds This determines 19 driver will the amount of time the 30 assum the 30 initiator driver will wait for seconds value of 20 seconds the target to become internally No available once it has lost connection to the target 5 during an IO operation will be seen in registry If set between 0 ETO 30 Controls the rate of interrupts for the UCNA For im_policy 2 0 4 more information see Interrupt Moderation Policy Settings Maximum transfer size in a single I O request in kilobytes By default the iSCSI driver supports a maximum of 128 KB of data in a single I O request This option can be used to enable support for 512 KB of data in a single I O request large I O 128 128 512 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 be2iscsi driver with this value after each reboot run the following commands and reboot the system 4 esxcfg module s ldto 25 be2iscsi usr sbin esxcfg boot r reboot The im policy
113. r 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 ACTION None required elx mes0387 Failed to allocate an iocbq DESCRIPTION Failed to get an IOCBQ from the list of available IOCBQs DATA None Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 41 J gt G EMULEX ACTION None required elx mes0388 Not a valid WCQE code hex cqe code DESCRIPTION The event code is invalid This event is dropped DATA None ACTION Ensure the adapter s firmware is current 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 rc during 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 D
114. r failed to setup Completion Queue Failure code is reported DATA ACTION Software driver error If this problem persists report these errors to 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 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 fcp eqidx not allocated DESCRIPTION The fast path FCP WQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx mes0535 Failed setup of fast path FCP WQ lt fcp_waqidx gt rc rc DESCRIPTION The fast path FCP WQ 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 WQ is not allocated DATA None ACTION The driver fails to load Contact Emulex Technical Support elx mes0537 Failed setup of slow path ELS WQ rc 0x x DESCRIPTION Driver failed to setup Work Queue Failure code is reported DATA 1 2 3 ACTION Software driver error If this problem persists report these errors to Technical Support elx mes0538 Slow path MQ not allocated DESCRIPTION The slow path MQ is not allocated DATA No
115. range Valid Range is 0 30 Using Default Value 30 WARNING Idto value d out of range Valid Range is 0 30 Using DefaultValue 20 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 KByte Using Default Value 256 WARNING WARNING tmf reset value 96d out of range Valid Range is 1 3 Using Default Value 1 ddm value 96d out of range Valid Range is 0 1 Using Default Value 0 Note d represents a signed integer outside of the valid range The driver will return a number in the Warning message Any other messages will be returned 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 87 EMULEX Description of Mandatory and Optional Parameters The following table describes the parameters used in the data string for option 43 Table 9 Data String Parameters for Option 43 Parameter Description Type of Field lt TargetIP gt Replace it with a valid IPv4 address in dotted decimal notation Mandatory lt TargetTCPPort gt Replace it with a decimal number ranging from 1 to 65535 inclusive
116. rcumstances and offers one or more workarounds for each situation Troubleshooting the FC FCoE Driver General Situations Table 2 General Driver Situations 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 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 lpfc820 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 Drivers for VMware ESX ESXi
117. rds required for mutual CHAP authentication must be specified by non DHCP means If not specified this field defaults toauthenticationdisabled Optional Examples The following is an example of Default Initiator name and Data Digest Settings iscsi 4 com 1234567890 E p Drivers for VMware ESX ESXi 4 1 Troubleshooting Section 192 168 0 2 3261 000000000000000E ign 2009 Page 88 J gt G EMULEX where the following is Target IP address 192 168 0 2 Target TCP port 3261 Target boot LUN 0x0E Target iqn name iqn 2009 04 com 1234567890 Initiator name Not specified Use the Initiator name already configured Use the default name if none was configured Header Digest Enabled Data digest Not specified Assume disabled Authentication Type 1 way CHAP The following is an example of Default TCP Port and Mutual CHAP Settings iscsi 192 168 0 2 000000000000000E ign 2009 4 1234567890 where the following is Target IP address 192 168 0 2 Target TCP port Use default from RFC 3720 3260 Target boot LUN OxOE Target iqn name iqn 2009 04 com 1234567890 Initiator name Not specified Use the Initiator name already configured Use the default name if none was configured Header Digest Enabled Data digest Data Digest disabled Authentication Type Mutual CHAP CIM Provider Troubleshooting The following e
118. rror message may appear if the CIM hosts are not properly added to the OneCommand Manager Unknown or invalid host specified There could be instances when even with all the drivers CIM Provider and the CIM Client on a Windows machine are properly installed the CIM hosts might still not get added to OneCommand Manager Listed below are the most common reasons for this machine with the specified IP is not reachable Try pinging the machine specified protocol HTTP HTTPS is not supported by the CIMOM Most often the CIMOM will be configured to use HTTPS So if you are trying to connect with HTTP you might get an error Try using HTTPS instead The namespace specified is wrong Make sure the namespace conforms to the Namespaces Used for Providers table in the OneCommand Manager Application User Manual The username or the password specified is wrong Verify that the username given is correct and try retyping the password Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 89 gt G EMULEX The CIMOM is not running on the ESX ESXi host Try restarting the CIMOM You can check whether the CIMOM sfcb is running by typing the below commands etc init d sfcbd watchdog status or fps ef grep sfcb Also if the CIMOM is listening to a different port than 5988 or 5989 the connection might not take place You can configure the sfcb CIMOM settings by editing etc sfcb sfcb cfg If you still
119. rs This timeout is known as Link Down Timeout LDTO 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 Drivers for VMware ESX ESXi 4 1 Configuration Section Page 22 gt G EMULEX 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 I O requests At this point I O errors will be seen by the application operating system Note Following a link up switch ports can take a long time to initialize and go to forwarding state Because of this additional time should be added to the ETO and LDTO settings to eliminate I O disruption and or target unavailability If the switch port is connected to a single host then PortFast mode can be enabled on the switch port to eliminate delays in transitioning to forwarding state Configuring LDTO and ETO on ESX Server The following table lists the default values of LDTO and ETO on ESX Server and the limits within which they can be configured Value Default Minimum Maximum LDTO 20 seconds 0 seconds 30 seconds ETO 30 seconds 0 seconds 30 seconds
120. rupt DESCRIPTION The driver failed to start the interrupt DATA None ACTION Unload and reload the driver elx mes0433 Wakeup on signal lt gt DESCRIPTION A signal other than the 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 rc 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 status DESCRIPTION The adapter failed during powerup diagnostics after it was reset Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 44 EMULEX DATA None ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support 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 stat
121. s 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 76 EMULEX ACTION None required 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 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_mes2765 Mailbox command READ_FCF_RECORD failed to retrieve a FCF record DESCRIPTION Driver failed to find an FCF record when the FCF table scan completed DATA ACTION Software driver error If this problem p
122. se 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 indicate a software driver or firmware problem If these problems persist report these errors to Technical Support elx mes0338 IOCB wait timeout error no wake response Data x x x x DESCRIPTION Driver issued IO did not get a wake signal in polling mode DATA 1 wait time 2 wake value ACTION Software driver error If this problem persists 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 elx mes0341 Ring ringno Cannot find buffer for an unsolicited iocb tag un ulpWord 3 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 ringno Cannot find buffer for an unsolicited iocb tag unsli3 sliSWords 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 ringno Cannot find buffer for an unsolicited iocb tag un ulpWord 3 DESCRIPTION There are no more pre allocated buffers available to
123. sted DMA memo rysize req len DESCRIPTION The asynchronous 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 elx mes0297 invalid device group pci dev grp 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 sli rev DESCRIPTION While processing a host attention or unrecoverable error the driver detected an invalid Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 35 EMULEX SLI revision DATA None ACTION None required Mailbox Events 0300 0339 elx_mes0300 LATT Cannot issue READ LA Data rc 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 coul
124. t which is only for ESX execute the following command in the command prompt of the ESX host rpm ivh lt CIM Provider rpm where CIM Provider rpm is the released CIM Provider rpm For example elxocmcore esx40 5 1 32 2 1 x86 64 rpm To install the CIM Provider offline bundle which is only for ESXi execute the following command in the command prompt of the ESXi host esxupdat maintenancemod nosigcheck update bundle offline bundle zip gt where lt offline bundle zip gt is the offline bundle for the Emulex CIM Provider For example ELX ESX 4 1 0 emulex cim provider 3 2 16 1 offline bundle 311859 zip Note You must reboot the system for the changes to be effective For more information about the ESX patch management activities see the document located at http www vmware com pdf vsphere4 r41 vsp 41 esxupdate pdf Drivers for VMware ESX ESXi 4 1 Configuration Section Page 16 EMULEX After the reboot is completed verify that the drivers and the CIM Provider are correctly installed by typing the following commands esxupdat vib view query grep be2 esxupdat vib view query grep lpfc esxupdat vib view query grep emu For additional configuration information refer to Managing Devices using on page 25 for more details Working with VPorts Virtual Ports Creating Deleting and Displaying VPorts The Emulex driver for VMware supports NPIV by default
125. tall sh The RPM files will install automatically as well as the firmware 4 The system will prompt you to reboot Type y or n 5 After the system reboots you can create your VMs by following the VMware instructions Refer to the VMware ESX Server 4 1 documentation for more information If you want to load the drivers during boot initrd follow these steps 1 From the installer directory type sh Install sh The RPM files will install automatically as well as the firmware 2 Update the initrd by typing the command esxcfg boot b 3 Reboot the system Performing Silent Unattended Installation The OneConnect software installation utility supports Silent Installation or Unattended mode for ESX Server Silent installation is a script file driven mode of installation that does not require any user input to complete This section describes how to invoke the installation utility in silent mode When running in silent mode the installation utility will install all software automatically Upon completion the installation utility provides an exit code describing the outcome of the update Invoking Silent Install in ESX Server To invoke Silent install in ESX Server do the following 1 Run the following command line where Install sh is located to start Silent Install sh Install sh s 2 Run this command to get the exit code echo Exit Codes The OneConnect Server Software Installer implements the
126. te mailbox for ADD FCF command DATA None ACTION None required elx mes2010 Resume RPI Mailbox failed status status mbxStatus mbx status 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 SPECIAL mailbox command DATA None ACTION None required elx mes2012 Mailbox failed mbx cmd READ CONFIG mbxStatus lt mbx status DESCRIPTION The READ CONFIG mailbox command failed DATA None ACTION None required elx mes2013 Could not manually add FCF record 0 status rc DESCRIPTION Could not add FCF record to the FCF list DATA None ACTION None required elx mes2014 Invalid command iocb ulpCommand DESCRIPTION The IOCB command is invalid DATA None ACTION None required Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 64 EMULEX elx_mes2015 Invalid CT x command 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 mbx status HBA state port state DESCRIPTION The REG FCFI mailbox command has failed DATA None ACTION None required elx mes2018 REG VFI mbxStatus error mbx status HBA state port state DESCRIPTION The REG VFI mailbox command has failed DATA None ACTION None required
127. tlnx 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 36 gt G EMULEX elx mes0315 Ring lt ringno gt issue portCmdGet local getidx is bigger then cmd ring lt max_cmd_idx gt DESCRIPTION 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 ulp loTag is out of range max iotag max iotag 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 mes0319 READ SPARAM mbxStatus error mbxStatus hba state hba state 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 mbxsStatus error mbxStatus hba state hba state DESCRIPTION The driver issued a CLEAR LA 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 mes0323 Unknown
128. tus 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 shdr add status mbx status rc 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 status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to delete the completion queue has failed DATA None ACTION None required elx mes2507 DESTROY mailbox failed with status lt status add status shdr add status mbx status rc 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 shdr status add status shdr add status mbx status rc 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 status add status shdr add status mbx status rc DESCRIPTION The mailbox command sent to delete the receive queue has failed DATA None ACTION None required elx mes2510 RQ DESTROY mailbox failed with status lt
129. tus 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 extended status 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 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 1 0 op tgt tgt ID lun LUN cmnd lt CMDs gt rsplnfo3 lt rspInfo3 gt DESCRIPTION The FCP response from a target indicated that the response length is valid but rspInfo3 indicates that there is no Failure This i
130. update bundle offline bundle zip where offline bundle zip is the be NIC driver released as an zip file Drivers for VMware ESX ESXi 4 1 Installation Section Page 7 EMULEX iSCSI Driver The iSCSI driver is the driver for the iSCSI ports of the UCNA adapters To install the iSCSI driver execute the following command in the command prompt of the ESX ESXi host mkdir tmp mountpoint mount r o loop path to driver iso tmp mountpoint esxupdat maintenancemode updat bundle lt be2iscsi zip gt where lt be2iscsi zip gt is the iSCSI driver released as zip file Installing the Out of Box Driver Use the VMware ESX driver CD to install drivers on ESX or ESXi installations You can use the driver CD e To install drivers for devices as part of a new ESX installation To update existing drivers or install new drivers for an existing ESX installation with esxupdate To update existing drivers or install new drivers for an existing ESX or ESXi installation with vihostupdate Installing Drivers for Devices as Part of a New ESX Installation ESX Only Note This procedure has changed since the 3 5 version of driver CD You will need the ESX installation DVD to begin Insert the ESX installation DVD in the DVD drive of the host Restart the host Accept the terms of the license agreement Select a keyboard type When prompted for Custom Drivers select Yes to install custom drivers Cli
131. us 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 mes0439 Adapter failed to init moxCmd 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 moxCmd mbxCommand 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 2
132. valid 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 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 mes1825 Vport Created DESCRIPTION This message is displayed 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 60 EMULEX 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_mes1830 Signal aborted mbxCmd command DESCRIPTION A pending mailbox command was aborted because the thread received a signal DATA None ACTION The command is retried elx_mes1831 Create VPORT Interrupted DESCRIPTION The port creation process was unexpectedly interrupted at a critical
133. version 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section Page 86 gt G EMULEX Table 7 iSCSI Error Log Code Entries Continued Message Recommended Resolution Both Port 0 and Port 1 links Check the links to the OneConnect UCNA If the link is reestablished any were down for a period sessions that existed previously will be reestablished and the devices will be exceeding the Link Down available for I O Timeout LDTO If the initiator has connection to the target 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 are down Both Port 0 and Port 1 links Check the links to the OneConnect UCNA Additional iSCSI Driver Messages The following iSCSI error messages are returned when you specify illegal options when loading the driver Table 8 Additional iSCSI Driver Messages WARNING dic value 96d out of range Valid Range is 0 1 Using Default Value 1 WARNING eto value d out of
134. w 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 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 elx mes0527 Failed setup of fast path FCP CQ lt fcp_cqidx gt rc rc 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 Drivers for VMware ESX ESXi 4 1 Troubleshooting Section J gt G EMULEX Page 49 J gt G EMULEX ACTION The driver fails to load Contact Emulex Technical Support elx_mes0529 Failed setup of slow path mailbox CQ rc 0x x DESCRIPTION Drive
135. x 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 Emulex 3333 Susan Street Costa Mesa CA 92626 Drivers for VMware ESX ESXi 4 1 User Manual Page ii Supported Driver Versions Driver Version Comments FC FCoE Drivers 8 2 1 86 26 8 2 1 90 28 8 2 1 105 34 NIC Drivers 2 102 518 0 2 102 554 0 2 103 377 0 4 0 306 0 2 104 277 3 iSCSI Drivers 2 102 525 9 Drivers for VMware ESX ESXi 4 1 User Manual 4 0 317 0 gt G EMULEX Page iii Installation met nee 1 Briver informatio NM e EE OO 1 Supported nennen nennen isset nn nennen nnns nnn 1 New Features in this He 1 Prerequisites 1 IN Ae S 2 Things to Know Before You Download

ESX/ESXi 4.1 - User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents