Home

Emulex Drivers for VMware ESX 3.5

1. 4 New VMware Systems 4 VMware Systems with an Existing HBAnyware CLI Kit Installed 4 Uninstalling Older HBAnyware Kits on VMware 5 eene cuente 6 2 6 LPFC Driver Configuration Methods Using Native ESX Tools 6 Permanent Configuration Methods sse 6 Dynamically Add LUNs and 8 Creating a Fibre Channel Remote Boot 8 Virtualization FOalulG5S c RR IR EXRERNENEXRNRRARRNRKRNRNRNRRRRRNRKRKRRRERRRRRRRRRRRRRRRRRRRE 8 Configuring Multiple NIC Interfaces with OneConnect UCNAS 8 Enabling the NetQueue Feature ssssssssssnm 8 How ESX Server Creates and Names Interfaces Jia ee sene nente 8 Configuring VEAN EE 9 Configuring Network Heap Size in ESX 9 ESX Server Network Driver eeesssssssssssseseseeeeeeenenenn nennen nennen nnns 9 Enabling vmxnet Emulation Jumbo Frames and TSO 9 Configuring the Virtual Switch to Use Jumbo 10 Setting the MTU Size essssssssssssssssseneeseeeeenenneerene nennen nennen 10
2. Ipfc mes0432 WWPN binding entry node table full DESCRIPTION More bindings entries were configured than the driver can handle DATA None SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file so that fewer bindings are configured Emulex Drivers for VMware ESX 3 5 User Manual Page 50 EMULEX lpfc mes0433 WWNN binding entry node table full DESCRIPTION More bindings entries were configured than the driver can handle DATA None SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file so that fewer bindings are configured Ipfc mes0434 DID binding entry num Syntax error code lt code gt DESCRIPTION A syntax error occurred while parsing DID binding configuration information DATA None Detail Binding syntax error codes 0 FC SYNTAX OK 1FC SYNTAX OK BUT NOT THIS BRD 2 FC SYNTAX ERR ASC CONVERT 3 FC SYNTAX ERR EXP COLON 4 FC SYNTAX ERR EXP LPFC 5 FC SYNTAX ERR INV LPFC NUM 6 FC SYNTAX ERR EXP T 7 FC SYNTAX ERR INV TARGET NUM 8 FC SYNTAX ERR EXP D 9 FC SYNTAX ERR INV DEVICE NUM 10 FC SYNTAX ERR INV RRATIO NUM 11 FC SYNTAX ERR EXP NULL TERM SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file lpfc mes0435 DID binding entry node table full DESCRIPTION More bindings entries were configured than the driver can handle DATA None S
3. ACTION No action need informational Emulex Drivers for VMware ESX 3 5 User Manual Page 26 gt G EMULEX Ipfc mes0130 Xmit Fabric LOGO ELS command to fabric DESCRIPTION A vport is sending a LOGO for its FDISC to the switch DATA 1 vport DID 2 vport vpi 3 vport state SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes131 Fabric LOGO Completes DESCRIPTION The vport s fabric LOGO failed to complete successfully DATA 1 vport DID 2 vport VPI 3 ulpStatus 4 iocb word 4 SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes132 Fabric acknowledging NPIV 0 1 DESCRIPTION If the fabric supports NPIV a 1 is printed O if not DATA 1 max vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational However if the fabric NPIV support is incorrect contact Emulex Technical Support Ipfc mes133 FLOGI failure DESCRIPTION An ELS FLOGI command timed out and CLEAR LA cannot be issued DATA mbox error reason code 0 means no resources SEVERITY error LOG LOG ELS verbose ACTION No action needed informational Link Discovery Events 0200 0299 Ipfc 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 SEVERITY Error LOG Always ACTION Software driver error If this problem persi
4. DATA None SEVERITY Warning LOG LOG DISCOVERY verbose ACTION None required The driver recovers from this condition by issuing a FLOGI to the fabric Ipfc mes0222 Initial FLOGI timeout DESCRIPTION The driver sent the initial FLOGI to fabric and never got a response back DATA None SEVERITY Error LOG Always ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0223 Timeout while waiting for NameServer login DESCRIPTION Our login request to the NameServer was not acknowledged within RATOV DATA None SEVERITY Error LOG Always ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Emulex Drivers for VMware ESX 3 5 User Manual Page 30 EMULEX Ipfc mes0224 NameServer Query timeout DESCRIPTION Node authentication timeout node Discovery timeout A NameServer Query to the fabric or discovery of reported remote NPorts is not acknowledged within R A TOV DATA 1 fc ns retry 2 fc max ns retry SEVERITY Error LOG Always ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0225 Device Discovery completes on vpi lt vpi gt DESCRIPTION This indicates successful completion of device re discovery after a link up DATA None SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informationa
5. Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0471 Unsupported CQ count of d DESCRIPTION The event queue cannot be initialized with the specified count DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0472 CQ CREATE mailbox failed stat lt gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be created DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 56 EMULEX Ipfc mes0473 Unsupported MQ count of d DESCRIPTION The queue cannot be initialized with the specified count DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0474 MQ CREATE mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be created DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0475 Unsupporte
6. Event code SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4542 CT Resp iocb timeout DESCRIPTION CT Response IOCB timeout DATA 1 IOCB s iotag 2 tag 3 Nport SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4543 CT Resp iocb error DESCRIPTION CT Response IOCB error DATA 1 rc 2 IOCB s iotag 3 tag 4 Nport SEVERITY Information LOG LOG INIT verbose Emulex Drivers for VMware ESX 3 5 User Manual Page 81 EMULEX ACTION None required Ipfc mes4544 Failed to get the non embedded SGE virtual address DESCRIPTION Failed to get the SGE virtual address for the non embedded mailbox command DATA None SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary This is an unlikely error If this condition persists contact Technical Support Ipfc mes4545 READ FCF RECORD mailbox failed DESCRIPTION Issue READ FCF RECORD mailbox returned status failure DATA 1 status 2 add status SEVERITY Error LOG Always ACTION This is part of the driver s basic discovery process It may be a critical problem as long as at least one of the FCF records reads back successfully However if none of the FCF records reads back successfully reboot the system as necessary If the problem persists contact Technical Support Ipfc mes4546 FCP complete error DESCRIPTION FCP work queue complete entry error DAT
7. LOG DISCOVERY LOG FCP verbose ACTION Check persistent binding information Ipfc mes0231 RSCN timeout DESCRIPTION The driver has lost track of what NPorts have RSCNs pending DATA 1 fc ns retry 2 fc max ns retry SEVERITY Error LOG Always ACTION None required The driver should recover from this event Ipfc mes0232 Continue discovery with num disc nodes PLOGIs to go DESCRIPTION Device discovery is in progress DATA 1 plogi cnt 2 flag 3 vport port state SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0234 ReDiscovery RSCN DESCRIPTION The number type of RSCNs has forced the driver to go to the nameserver and re discover all NPorts DATA 1 fc defer rscn q cnt 2 fc flag 3 hba state SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0235 Deferred RSCN DESCRIPTION The driver has received multiple RSCNs and has deferred the processing of the most recent RSCN DATA 1 fc defer rscn q cnt 2 fc flag 3 hba state SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0236 NameServer req DESCRIPTION The driver is issuing a NameServer request to the fabric DATA 1 cmdcode 2 fc flag 3 fc rscn id cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0237 Pending Link Ev
8. This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0496 SLI FUNCTION RESET mailbox failed DESCRIPTION Mailbox command to reset function failed DATA 1 status 2 add status 3 rc SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0497 Failure HBA POST DESCRIPTION HBA POST failure DATA 1 sta reg 2 perr 3 sfi 4 nip 5 ipc 6 xrom 7 dl 8 pstatus SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 59 EMULEX Ipfc mes0498 Device Info ChipType lt val gt SLIRev lt val gt FeatureL1 lt val gt FeatureL2 lt val gt DESCRIPTION Device information reported by adapter DATA None SEVERITY Information LOG LOG_INIT verbose ACTION No action needed informational Ipfc mes0499 HBA Unrecoverable error DESCRIPTION HBA POST failure DATA 1 uerr_lo_reg 2 uerr_hi_reg 3 ue_mask_lo_reg 4 ue_mask_hi_reg SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support IP Log Events 0600 0699 Ipfc mes0600 FARP RSP receiv
9. report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 52 EMULEX Ipfc mes0446 Adapter failed to init mbxCmd cmd CFG RING mbxStatus status ring num DESCRIPTION Adapter initialization failed when issuing a CFG_RING mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0447 Adapter failed init mbxCmd cmd CONFIG_LINK mbxStatus status DESCRIPTION Adapter initialization failed when issuing a CONFIG LINK mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0448 Adapter failed to init mbxCmd cmd READ SPARM mbxStatus status DESCRIPTION Adapter initialization failed when issuing a READ SPARM mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0451 Enable interrupt handler failed DESCRIPTION The driver attempted to register the HBA interrupt service routine with the host operating System but failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or driver problem If the problem
10. ACTION None required Ipfc mes4563 LPFC create port vmk fc attach transport failed DESCRIPTION The driver failed to attach to the FC transport layer DATA None SEVERITY Error LOG Always ACTION Reboot the system If problems persist contact Technical Support Ipfc mes4564 Clear Virtual Link Received for lt VPI gt tag DESCRIPTION A Clear Virtual Link event was received DATA None SEVERITY Error LOG Always ACTION If numerous link events are occurring check physical connections to Fibre Channel network Ipfc mes4565 READ FCF RECORD indicates empty FCF table DESCRIPTION The firmware was unable to find FCF RECORD DATA None SEVERITY Error LOG Always ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 85
11. COND ERR 2 DELAY RSP ERR 3 Ip SEVERITY Information LOG LOG FCP LOG CHK COND verbose ACTION None required Ipfc mes0738 Scheduler received Queue Full status from FCP device lt tgt gt lt lun gt DESCRIPTION The scheduler received a Queue Full error status from the specified FCP device DATA 1 afull retry count 2 qfull retries 3 currentOutstanding 4 maxOutstanding SEVERITY Information LOG LOG FCP verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 62 gt G EMULEX lpfc_mes0747 Completed target reset DESCRIPTION Target reset completed DATA 1 tgt id 2 lun id 3 Status SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0748 Completed LUN reset DESCRIPTION LUN reset completed DATA 1 tgt id 2 lun id 3 Status 4 command frag SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0749 Completed abort task set DESCRIPTION Abort task set completed DATA 1 tgt id 2 lun id 3 cmpl time mS SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0750 Failed Abort Task Set Data x x x ld DESCRIPTION Abort Task Set completed DATA 1 tgt id 2 lun id 3 timeout mS SEVERITY Error LOG Always ACTION This error could indicate a software driver problem If problems persist report these errors to Technical Support Ipfc mes0754 SCSI timeout DESCRIPTION An FCP
12. FCP WQ Id Emulex Drivers for VMware ESX 3 5 User Manual Page 77 EMULEX SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4517 Invalid Completion event code DESCRIPTION An invalid fast path completion event was received DATA 1 majorcode 2 minorcode SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4518 Fast path EventQ has a different Queue Id DESCRIPTION Fast path EventQ has a different Queue ID DATA 1 Event Queue ld 2 FCP Q Id SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4519 New FCF Index was discovered DESCRIPTION A new FCF index was discovered DATA 1 fcf index 2 event tag SEVERITY Information LOG LOG DISCOVERY verbose ACTION None required Ipfc mes4520 FCF Table full DESCRIPTION The FCF table is full DATA 1 count 2 event tag SEVERITY Warning LOG LOG DISCOVERY verbose ACTION None required If problem persists contact Technical Support Ipfc mes4521 FCF disconnected from network DESCRIPTION FCF disconnected from the network DATA 1 fcf index 2 event tag SEVERITY Warning LOG LOG DISCOV
13. Ipfc discovery threads 30 64 No Specifies the maximum number of ELS commands that can be outstanding for a discovery Ipfc dgfull throttle up inc 128 Yes Amount to increment LUN queue depth each time Ipfc dafull throttle up time 30 Yes Time interval in seconds to increment LUN queue depth Ipfc extra io tmo 255 Yes Extra FCP cmd timeout when connected to a fabric in seconds Ipfc fcp bind DID inactive N A N A No Bind specific SCSI IDs to targets based on Fibre Channel FC Port ID Ipfc fcp bind method No Specifies the bind method WWWN WWPN DID ALPA map to be used Ipfc fcp bind WWNN inactive N A N A No Bind specific SCSI IDs to targets based on FC WWNN Ipfc fcp bind WWPN inactive N A N A No Bind specific SCSI IDs to targets based on FC WWPN Ipfc fcp class Yes FC class for FCP data transmission Emulex Drivers for VMware ESX 3 5 User Manual Page 12 Table 2 LPFC Driver Configuration Parameters Continued gt G EMULEX Variable Default Min Max Dynamic Comments Ipfc fcp imax 10000 636 651042 Yes Set the maximum number of fast path FCP interrupts per second Note This parameter only applies to Emulex UCNAs Ipfc fdmi on 0 0 2 No False 0 if disabled 1 or 2 if enabled depending
14. Ipfc mes1217 Find ndlp returned NULL DESCRIPTION Find NDLP returned NULL to a CT ABTS context DATA 1 oxid 2 SID SEVERITY Error LOG Always ACTION None required The received unsolicited event ABTS will be ignored Link Events 1300 1399 Ipfc mes1300 Re establishing Link timer expired DESCRIPTION The driver detected a condition where it had to re initialize the link DATA 1 fc flag 2 fc ffstate SEVERITY Error LOG Always ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network Ipfc mes1301 Re establishing Link DESCRIPTION The driver detected a condition in which it had to re initialize the link DATA 1 status 2 status1 3 status2 SEVERITY Information LOG LOG LINK EVENT verbose ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network Emulex Drivers for VMware ESX 3 5 User Manual Page 69 EMULEX Ipfc mes1302 Reset link speed to auto 1G HBA cfg d for 2G DESCRIPTION The driver is reinitializing the link speed to auto detect DATA 1 current link speed SEVERITY Warning LOG LOG LINK EVENT verbose ACTION None required Ipfc mes1303 Link Up Event lt eventTag gt received DESCRIPTION A link up event was received It is also possible for multiple link events to be received together DATA 1 fc eventTag 2 granted AL PA 3 UlnkSpeed 4 alpa map 0 DE
15. Pinning VM and Interrupts to 5 10 Emulex LPFC Driver Configuration 11 Troubleshooting 15 MMOD rej OTs EEEE 15 Unusual Situations and Their Resolutions 15 General Situations ssssssssssssssssssseenenee enne nnne nnn nennen nnns 15 ESX Server NIC tcc deve dde edi aee ee een doute ade e uda 16 ESX Server Event Error Log 16 Retrieving ESX Server NIC Error Log Codes 16 ESX Server NIC Event Log Entries 17 LPFC Log 20 INMFODUCTION p 20 Severity Codes sssssssssssssssssssseesseeee 20 ETRACE Logging 20 Message Group Masks sssssssssssssseeeeeeeeee nennen nennen nennen 21 Message Log 22 ELS Events 0100 0199 atate aet Eee inet eaaet 22 Emulex Drivers for VMware ESX 3 5 User Manual Page iii Table of Contents Link Discovery Events 0200 0299 27 M
16. SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0286 Failed to allocate init_vpi mailbox DESCRIPTION Failed to allocate memory for issuing init vpi mailbox command DATA 1 vpi SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0287 Failed to issue init vpi mailbox DESCRIPTION Failed to issue init vpi mailbox command DATA 1 vpi SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0288 No NPIV Fabric support DESCRIPTION The switch fabric does not support NPIV DATA 1 vpi SEVERITY Error LOG Always ACTION Check the fabric capability and configuration for NPIV support Ipfc mes0289 Adapter message DESCRIPTION When the response IOCB carrys an unknown IOCB type and the upper layer command is an adapter message it logs the adapter message returned from the adapter DATA Message returned from the adapter SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed the driver will recover from this and continue with normal operation Emulex Drivers for VMware ESX 3 5 User Manual Page 39 EMULEX Mailbox Events 0300 0399 Ipfc mes0300 READ no bu
17. error may indicate a software driver problem If problems persist report these errors to Technical Support Ipfc mes4506 Work Queue Full DESCRIPTION Unable to add element to work queue because the adapter has not processed the oldest element DATA 1 host index 2 entry count 3 hba index SEVERITY Warning LOG LOG 510 verbose ACTION None required Ipfc mes4508 FCP complete w o iocb DESCRIPTION Cannot find the FCP command IOCB using the iotag lookup DATA 1 iotag SEVERITY Error LOG Always ACTION This error may indicate a hardware firmware or driver problem If problems persist report these errors to Technical Support Ipfc mes4509 ELS complete w o iocb DESCRIPTION Cannot find the ELS command IOCB using the iotag lookup DATA 1 iotag SEVERITY Error LOG Always ACTION This error may indicate a hardware firmware or driver problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 76 EMULEX Ipfc mes4510 Unrecoverable Adapter Error DESCRIPTION Error Attention reported by the adapter DATA 1 uerr lo 2 uerr_hi 3 ue mask lo reg 4 ue mask hi reg SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4511 Cannot issue mailbox cmd lt opcode gt DESCRIPTION Mailbox command cannot be issu
18. firmware or hardware problem Report these errors to Technical Support Ipfc mes0320 CLEAR LA mbxStatus error lt mbxStatus gt hba state lt hba_state gt DESCRIPTION The driver issued a CLEAR LA mbox command to the HBA that failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a firmware or hardware problem Report these errors to Technical Support Ipfc mes0321 Unknown IOCB command DESCRIPTION Received an unknown IOCB command completion DATA 1 ulpCommand 2 ulpStatus 3 ulploTag 4 ulpContext SEVERITY Error LOG Always ACTION This error could indicate a software driver or firmware problem If these problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 43 gt G EMULEX lpfc mes0322 Ring lt ringno gt handler unexpected completion loTag lt loTag gt DESCRIPTION The driver could not find a matching command for the completion received on the specified ring DATA 1 ulpStatus 2 ulpWord 4 3 ulgCommand 4 ulpContext SEVERITY Warning LOG LPFC_SLI verbose ACTION This warning is benign during ELS disturbances and unexpected for FCP I O In the absence of any SAN disturbances this error could indicate a software driver or firmware problem If problems persist report these errors to Technical Support Ipfc mes0323 Unknown Mailbox command cmd DESCRIPTION An unknown mailbox command completed DAT
19. gt lt EMULEX Emulex Drivers for VMware ESX 3 5 FC and FCoE version 7 4 0 54 NIC version 2 101 455 0 User Manual One Network One Company P005645 01A Rev A Connect with Emulex gt G EMULEX Copyright 2003 2010 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Corporation Connect Emulex Corporation Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company One Network One Company Connect with Emulex 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 purpo
20. kit from the Emulex Web site Log on to the ESX Server host Install the specific driver binary RPM file e For the FC FCoE driver type rpm i VMware esx drivers scsi lpfc elx v740 350 driver version gt 001 1386 rpm e For the NIC driver type rpm i VMware esx drivers net be2net 2 101 driver version i386 rpm Note In band management FC based management is not supported on VMware ESX 3 5 servers Use out of band management TCP IP based management to remotely manage adapters on ESX 3 5 servers Opening the ESX Server Firewall For the VMware ESX 3 5 Server the firewall on the ESX Server must be opened to manage systems remotely using TCP IP based management To enable TCP port 423333 run the following commands esxcfg firewall openPort 23333 tcp in OneCommand esxcfg firewall openPort 23333 tcp out OneCommand To verify that the correct port is open run the following command esxcfg firewall q The TCP port number can be changed If it is not changed the default is 23333 Refer to the VMware Server Configuration Guide for more details on how to configure the ESX firewall Emulex Drivers for VMware ESX 3 5 User Manual Page 3 gt G EMULEX Uninstalling the Drivers To uninstall a specific driver binary RPM file e For the FC FCoE driver type rpm e VMware esx drivers scsi lpfc elx v740 350 driver version e For the NIC driver type rpm e VMware esx drivers be2net 2 101 driver version
21. persists report the error to Technical Support Ipfc mes0452 Adapter failed to init mbxCmd cmd CONFIG_HBQ mbxStatus status DESCRIPTION Adapter initialization failed when issuing CONFIG mailbox command DATA 1 mbx Command 2 mbx Status 3 hbq entry SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0453 Adapter failed to init mbxCmd cmd READ CONFIG mbxStatus status DESCRIPTION Adapter initialization failed when issuing a READ CONFIG mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 53 gt G EMULEX Ipfc mes0454 Adapter failed to init mbxCmd cmd INIT LINK mbxStatus status DESCRIPTION Adapter initialization failed when issuing an INIT LINK mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0455 Vital Product DESCRIPTION Vital product data VPD contained in the HBA flash DATA 1 vpd 0 2 vpd 1 3 vpd 2 4 vpd 3 SEVERITY Information LOG LOG INIT verbose ACTION No action needed informational Ipfc mes0456 Adapte
22. state port state DESCRIPTION A request to delete a vport is executing The driver dumps the vport s state and node counts DATA 1 plogi cnt 2 adisc cnt 3 unmapped cnt 4 mapped cnt SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1812 VPort fabric LOGO didn t complete treating as failure DESCRIPTION The VPort s fabric logout didn t complete Continuing teardown DATA 1 vport DID SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Ipfc mes1813 VPort could located target node binding DESCRIPTION The vport was called to remove a target given a target ID but the vport could not locate a node binding by TGTID DATA 1 vpi 2 vport DID 3 tgtid SEVERITY Error LOG Always ACTION Contact Emulex Technical Support lpfc mes1814 Vport discovery quiesce wait on vpi DESCRIPTION The vport node discovery is active DATA 1 port state 2 fc flag 3 num disc nodes 4 fc plogi cnt 5 fc adisc cnt 6 fc map cnt SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1815 Vport discovery quiesce cmplt on vpi lt vpi gt DESCRIPTION The vport node discovery has completed DATA 1 port state 2 fc flag 3 fc map cnt SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1816 Vport discovery quiesce timeout on vpi lt vpi gt DESCRIPTION The vport node discovery timed out waiting t
23. 04 Stray mailbox interrupt mbxCommand cmd mbxStatus status DESCRIPTION Received a mailbox completion interrupt and there are no outstanding mailbox commands DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0305 Mbox cmd cmpl error RETRYing DESCRIPTION A mailbox command completed with an error status that causes the driver to reissue the mailbox command DATA 1 mbxCommand 2 mbxStatus 3 word1 4 hba state SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 40 gt G EMULEX Ipfc 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 HBA that failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a firmware or hardware problem Report these errors to Technical Support Ipfc mes0307 Mailbox cmd cmd cmpl lt mbox_cmpl gt lt pmbox gt lt varWord gt lt varWord gt lt varWord gt lt varWord gt lt varWord gt lt varWord gt lt varWord gt lt varWord gt DESCRIPTION A mailbox command completed DATA IOCTL opcode varWord 0 varWord 7 SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Ipfc mes0308 Mbox cmd issue BU
24. 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0125 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 nlp DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0126 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 nlp DID 2 state 3 flag 4 Rpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc 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 did 3 ulpcommand 4 iotag SEVERITY Error LOG Always ACTION If no ELS command is going through the adapter reboot the system If problem persists contact Technical Support Ipfc mes0128 FDISC failed DESCRIPTION An FDISC failed DATA None SEVERITY Error LOG Always ACTION Make sure the switch supports NPIV If problem persists contact Technical Support Ipfc mes0129 FDISC succeeded DESCRIPTION An FDISC succeeded DATA 1 DID SEVERITY Information LOG LOG ELS verbose
25. A 1 Mailbox Command 2 mbStatus SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support Ipfc mes0324 Adapter initialization error cmd READ NVPARM mbxStatus status DESCRIPTION A read nvparams mailbox command failed during port configuration DATA 1 Mailbox Command 2 Mailbox Command Status SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem Report these errors to Technical Support Ipfc mes0325 Rsp ring lt ringno gt error IOCB DESCRIPTION Received an IOCB response error DATA 1 2 wd1 3 wd2 4 5 wd4 6 wd5 7 8 wd7 SEVERITY Warning LOG LOG_SLI verbose ACTION This error could indicate a software driver problem If problems persist report these errors to Technical Support Ipfc mes0326 Reset HBA DESCRIPTION The HBA has been reset DATA 1 hba_state 2 sli_flag SEVERITY Information LOG LOG_SLI verbose ACTION No action needed informational Ipfc mes0327 High priority IOCB cmd x x completed in jiffies DESCRIPTION Make all high priority IOCBs completion times available to console DATA 1 ulpCommand 2 wait time in jiffies SEVERITY Information LOG LOG SLI ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 44 EMULEX Ipfc mes0328 High pr
26. A 1 wcqe status 2 hardware status 3 total data placed 4 word3 of the wcqe SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4547 Read serdes parameter failed to allocate mailbox memory DESCRIPTION Read SerDes parameter failed to allocate mailbox memory DATA None SEVERITY Error LOG Always ACTION The driver failed to allocate mailbox command memory for reading the adapter region 23 to determine whether the link has been disabled This may result in enabling the adapter port which may have been permanently disabled by the management stack If this condition persists contact Technical Support Ipfc mes4548 Read link state failed to read config region 23 DESCRIPTION Read link state failed to issue read config region 23 mailbox command DATA 1 rc 2 status SEVERITY Error LOG Always ACTION The driver failed to issue a mailbox command for reading the adapter region 23 to determine whether the link has been disabled This may result in enabling the adapter port which may have been permanently disabled by the management stack If this condition persists contact Technical Support Ipfc mes4549 ReceiveQ error DESCRIPTION Put Receive Queue Entry RQE to Receive Queue returned error DATA 1 rc SEVERITY Error LOG Always Emulex Drivers for VMware ESX 3 5 User Manual Page 82 gt G EMULEX ACTION None required However if problems persist reset the HBA or reboot the s
27. C to hex Output buffer too small DESCRIPTION ASCII string to hexadecimal conversion failed The output buffer byte size is less than half of the input byte count Every two input characters bytes require one output byte DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver problem If the problem persists report the error to Technical Support Ipfc mes1213 Convert ASC to hex Input char seq not ASC hex DESCRIPTION The ASCII hexadecimal input string contains a non ASCII hexadecimal character DATA None SEVERITY Error configuration LOG Always ACTION Make necessary changes to the Ipfc configuration file Emulex Drivers for VMware ESX 3 5 User Manual Page 68 EMULEX Ipfc mes1214 Xmit CT ABTS DESCRIPTION Information on transmit CT ABTS ACC DATA 1 bls rsp command 2 oxid 3 sid 4 hba state SEVERITY Information LOG LOG MISC verbose ACTION None required Ipfc mes1215 Ignoring unsolicited CT No DESCRIPTION Information on the CT ABTS buffer when there is no HBQ associated with it DATA 1 iocb ulpStatus SEVERITY Information LOG LOG MISC verbose ACTION None required Ipfc mes1216 Ignoring unsolicited CT No DESCRIPTION Information on the CT ABTS buffer when there is no HBQ associated with it DATA 1 size of HBQ buffer 2 iocb_ulpStatus SEVERITY Information LOG LOG MISC verbose ACTION None required
28. DATA 1 rpi 2 flags SEVERITY Information LOG LOG FCP verbose ACTION Check the state of the target in question Ipfc mes0703 Issue LUN Reset to num LUN num DESCRIPTION The SCSI layer detected that it must abort all I O to a specific device This results in an FCP Task Management command to abort the I O in progress DATA 1 scsi id 2 lun id 3 rpi 4 flags SEVERITY Information LOG LOG FCP verbose ACTION Check the state of the device in question Ipfc mes0712 SCSI layer issued abort device DESCRIPTION The SCSI layer is requesting the driver to abort I O to a specific device DATA 1 target 2 lun 3 Ipfc cmd 4 iocbq SEVERITY Error LOG Always ACTION Check the state of the device in question Ipfc mes0714 SCSI layer issued bus reset DESCRIPTION The SCSI layer is requesting the driver to abort all I Os to all targets on this HBA DATA 1 tgt 2 lun 3 rc success failure SEVERITY Error LOG Always ACTION Check the state of the targets in question Ipfc mes0716 FCP Readl Underrun expected len residual lt resid gt DESCRIPTION An FCP device provided less data than was requested DATA 1 2 0 3 underflow SEVERITY Information LOG LOG FCP verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 61 gt G EMULEX Ipfc mes0717 FCP command cmd residual underrun converted to error DESCRIPT
29. ERY verbose ACTION None required If problem persists contact Technical Support Ipfc mes4522 Unknown FCoE event received from network DESCRIPTION The network received an unknown FCoE event DATA 1 fcf event type 2 acqe event tag SEVERITY Warning LOG LOG DISCOVERY verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 78 Ipfc mes4523 Invalid CT command DESCRIPTION Invalid CT command DATA 1 ct 2 command SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4524 Failed to allocate CQ EVENT entry DESCRIPTION Failed to allocate EVENT entry DATA None SEVERITY Warning LOG LOG INIT verbose ACTION None required If problem persists contact Technical Support Ipfc mes4525 Invalid work queue subtype DESCRIPTION Invalid work queue CQE subtype DATA 1 CQE subtype SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4526 Not a valid WCQE code DESCRIPTION Not a valid WCQE code DATA 1 WCQE code SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4527 Receive Frame Truncated DESCRIPTION Receive Frame is truncated DATA None SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4528 Invalid completion queue type DESCRIPTION Invalid completion queue type DATA 1 Completion Queue Type SEVERITY Warning LOG LOG INIT verbose ACTION None re
30. EVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file so that fewer bindings are configured lpfc mes0436 Adapter failed to init timeout status reg status DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support lpfc_mes0437 Adapter failed to init chipset status reg status DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 51 EMULEX lpfc mes0438 Adapter failed to init chipset status reg status DESCRIPTION The adapter failed during powerup diagnostics after it was reset DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0439 Adapter failed to init mbxCmd cmd READ REV mbxStatus status DESCRIPTION Adapter initialization failed when issuing a READ REV mailbox command DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware pr
31. HBA Try to re configure the device configure region 23 if necessary If problems persist contact Technical Support Ipfc mes4558 Init VPI mailbox failed DESCRIPTION Initialize VPI mailbox command completion returned failure DATA 1 mbox cmd status SEVERITY Error LOG Always ACTION The specific vport will be put into an error state May need to reset HBA or reboot system to recover If problems persist contact Technical Support Ipfc mes4559 No NPIV Fabric support DESCRIPTION The switch fabric does not support NPIV DATA None SEVERITY Error LOG Always ACTION Check the fabric capability and configuration for NPIV support Ipfc mes4560 UNREG_FCFI mbox allocation failed DESCRIPTION Failed to allocate memory for issuing UNREG FCFI mailbox command DATA None SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Technical Support Ipfc mes4561 UNREG FCFI issue mbox failed DESCRIPTION Failed to issue UNREG FCFI mailbox command to the HBA DATA None SEVERITY Error Emulex Drivers for VMware ESX 3 5 User Manual Page 84 EMULEX LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Technical Support Ipfc mes4562 Received unknown vport command DESCRIPTION The driver received an unknown vport command DATA 1 vport cmd 2 arg SEVERITY Warning LOG LOG INIT verbose
32. IOCB command was posted to a ring and did not complete within ULP timeout seconds DATA 1 did 2 sid 3 command 4 iotag SEVERITY Error LOG Always ACTION If I O is not going through the adapter reboot the system If problems persist report these errors to Technical Support Ipfc mes0755 Invalid tag id sent by the mgmt layer or tag id not in use DESCRIPTION An invalid tag id was sent by the management layer or the tag id is not in use DATA 1 tag id 2 in use field SEVERITY Error LOG Always ACTION This error could indicate a driver and or management stack problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 63 EMULEX Ipfc mes0756 Null NDLP for oxid DESCRIPTION Null NDLP for oxid DATA 1 oxid 2 sid 3 tag SEVERITY Error LOG Always ACTION This error could indicate a driver and or management stack problem If problems persist report these errors to Technical Support Ipfc mes0757 IOCB Data DESCRIPTION Log IOCB data fields DATA 1 vip 2 context2 3 context3 4 remotelD SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0758 Failed to allocate iocb DESCRIPTION Failed to allocate IOCB for passing unsolicited receive sequence to upper layer protocol DATA 1 els ring number 2 fh r ctil 3 fh type SEVERITY Error LOG Always ACTION None required just o
33. ION Make necessary changes to the Ipfc configuration file Emulex Drivers for VMware ESX 3 5 User Manual Page 49 gt G EMULEX Ipfc mes0430 WWPN binding entry num Syntax error code lt code gt DESCRIPTION A syntax error occurred while parsing WWPN binding configuration information DATA None Detail Binding syntax error codes 0 FC SYNTAX OK 1FC SYNTAX OK BUT NOT THIS BRD 2 FC SYNTAX ERR ASC CONVERT 3 FC SYNTAX ERR EXP COLON 4 FC SYNTAX ERR EXP LPFC 5 FC SYNTAX ERR INV LPFC NUM 6 FC SYNTAX ERR EXP T 7 FC SYNTAX ERR INV TARGET NUM 8 FC SYNTAX ERR EXP D 9 FC SYNTAX ERR INV DEVICE NUM 10 FC SYNTAX ERR INV RRATIO NUM 11 FC SYNTAX ERR EXP NULL TERM SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file Ipfc mes0431 WWNN binding entry num Syntax error code lt code gt DESCRIPTION A syntax error occurred while parsing WWNN binding configuration information DATA None Detail Binding syntax error codes 0 FC SYNTAX OK 1FC SYNTAX OK BUT NOT THIS BRD 2 FC SYNTAX ERR ASC CONVERT 3 FC SYNTAX ERR EXP COLON 4 FC SYNTAX ERR EXP LPFC 5 FC SYNTAX ERR INV LPFC NUM 6 FC SYNTAX ERR EXP T 7 FC SYNTAX ERR INV TARGET NUM 8 FC SYNTAX ERR EXP D 9 FC SYNTAX ERR INV DEVICE NUM 10 FC SYNTAX ERR INV RRATIO NUM 11 FC SYNTAX ERR EXP NULL TERM SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file
34. ION The driver converted this underrun condition to an error based on the underflow field in the SCSI command DATA 1 len 2 resid 3 underflow SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0729 FCP cmd lt failed lt target gt lt lun gt DESCRIPTION The specified device failed an FCP command DATA 1 cmnd 2 scsi id 3 lun id 4 status 5 result 6 iotag SEVERITY Warning LOG LOG FCP verbose ACTION Check the state of the target in question Ipfc mes0730 FCP command failed RSP DESCRIPTION The FCP command failed with a response error DATA 1 Status2 2 Status3 3 Resld 4 SnsLen 5 RspLen 6 Info3 SEVERITY Warning LOG LOG FCP verbose ACTION Check the state of the target in question Ipfc mes0734 FCP read check error DESCRIPTION The issued FCP command returned a read check error DATA 1 fcpDI 2 rspResld 3 fcpi parm 4 cdb 0 SEVERITY Warning LOG LOG FCP verbose ACTION Check the state of the target in question Ipfc mes0735 FCP read check error with check condition DESCRIPTION The issued FCP command returned a read check error and a check condition DATA 1 fcpDI 2 rspResld 3 fcpi parm 4 cdb 0 SEVERITY Warning LOG LOG FCP verbose ACTION Check the state of the target in question Ipfc mes0737 ASC ASCQ gt Check condition received DESCRIPTION The issued FCP command resulted in a check condition DATA 1 CFG CHK
35. Installing the OneCommand Manager Application CLI New VMware Systems To install the OneCommand Manager application CLI on a new system install the specific rpm file for your VMware driver version Prerequisites The LPFC driver version 7 4 or later must be loaded Note In band management FC based management is not supported on VMware ESX 3 5 servers Use out of band management TCP IP based management to remotely manage adapters on ESX 3 5 servers For VMware ESX 3 5 servers the firewall on the ESX Server must be opened to man age systems remotely using TCP IP For instructions see Opening the ESX Server Firewall on page 3 Procedures To install the OneCommand Manager application CLI Log on to the ESX Server host Copy the elxocmcore esxNN lt kit version gt i386 rpm file to a directory on the install machine CD to the directory to which you copied the rpm file Do Install the rpm Type rpm U elxocmcore esx35 kit version i386 rpm The rpm contents are installed in usr sbin hbanyware The OneCommand Manager application CLI is also located in this directory VMware Systems with an Existing HBAnyware CLI Kit Installed To install the OneCommand Manager application CLI on a VMware system with an existing HBAnyware CLI installed 1 Install the RPM by entering the following command all on one line rpm U elxocmcore esx35 lt kit version 1386 rpm Emulex Drivers for VMware ESX 3 5 User Manual Pag
36. OG LOG NODE verbose ACTION None required Ipfc mes0934 func FREE node did did on vpi lt vpi gt DESCRIPTION The driver searched for a node table entry based on the DID and did not find the entry DATA 1 did 2 rpi 3 vpi 4 flag SEVERITY Information LOG LOG NODE verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 67 EMULEX Miscellaneous Events 1200 1299 Ipfc mes1206 Dropped frame rctl lt str gt type lt str gt DESCRIPTION Dropped an unsolicited frame DATA None SEVERITY Information LOG LOG MISC verbose ACTION None required lpofc mes1207 Received frame rctl lt str gt type lt str gt DESCRIPTION Received an unsolicited frame DATA None SEVERITY Information LOG LOG MISC verbose ACTION None required Ipfc mes1208 CT request error DESCRIPTION The CT response returned more data than the user buffer could hold DATA 1 dfc flag 2 4096 SEVERITY Information LOG LOG MISC verbose ACTION Modify the user application issuing a CT request to allow for a larger response buffer Ipfc mes1210 Convert ASC to hex Input byte cnt 1 DESCRIPTION ASCII string to hexadecimal conversion failed The input byte count is less than 1 DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver problem If the problem persists report the error to Technical Support Ipfc mes1212 Convert AS
37. ON None required Ipfc mes0462 Too many rsp ring entries in SLI 2 SLIM DESCRIPTION The configuration parameter for Scan down is out of range DATA 1 totiocb 2 MAX SLI2 IOCB SEVERITY Error LOG Always ACTION This is a software driver error If this problem persists report these errors to Technical Support Ipfc mes0463 Port max temp exceeded temp taking port offline DESCRIPTION The HBA port is in an overtemperature condition and must be shutdown DATA 1 status 2 status1 3 status2 SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0464 Adapter failed to init Retry in SLI 2 mode mbxCmd cmd CONFIG_PORT mbxsStatus status DESCRIPTION Adapter initialization failed when issuing CONFIG PORT mailbox command DATA 1 hbainit SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If this problem persists report these errors to Technical Support Ipfc mes0465 Adapter failed to init retry mbxCmd cmd CONFIG PORT mbxstatus status DESCRIPTION Adapter initialization failed when issuing a CONFIG PORT mailbox command DATA 1 hbainit SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0466 Defer error condit
38. PTION The driver Discovery State Machine is processing an event DATA 1 nlp flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0212 DSM OUT vpi lt vpi gt state rc on NPort nlp DID DESCRIPTION The driver Discovery State Machine completed processing an event DATA 1 nlp flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0213 Reassign scsi id sid to NPort nlp DID DESCRIPTION A previously bound FCP Target has been rediscovered and reassigned a SCSI ID DATA 1 nlp bind type 2 nlp flag 3 nlp state 4 nlp rpi SEVERITY Information LOG LOG DISCOVERY LOG verbose ACTION No action needed informational Ipfc mes0214 RSCN received DESCRIPTION An RSCN ELS command was received from a fabric DATA 1 fc flag 2 i 3 Ip 4 fc rscn id cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0215 RSCN processed DESCRIPTION An RSCN ELS command was received from a fabric and processed DATA 1 flag 2 cnt 3 fc rscn id cnt 4 fc ffstate SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0216 Assign scandown scsi id sid to NPort nlp DID DESCRIPTION A SCSI ID is assigned due to BIND ALPA DATA 1 nlp bind type 2 nlp flag 3 nlp state 4 nlp rpi SEVERITY In
39. SY DESCRIPTION The driver attempted to issue a mailbox command while the mailbox was busy processing the previous command The processing of the new command will be deferred until the mailbox becomes available DATA 1 mbxCommand 2 hba state 3 sli flag 4 flag SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Ipfc mes0309 Mailbox cmd cmd issue DESCRIPTION The driver is in the process of issuing a mailbox command DATA 1 hba state 2 sli flag 3 flag SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Ipfc mes0310 Mailbox command cmd 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 SEVERITY Error LOG Always 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 Ipfc mes0311 Mailbox command cmd cannot issue DESCRIPTION The driver is in the wrong state to issue the specified command DATA 1 hba state 2 sli flag 3 flag SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 41 gt G EMULEX lofc__mes0312 Ring ringno handler portRspPut lt portRspPut gt is bigger then rsp ring lt portR
40. TA 1 ulpStatus 2 ulpWord 4 3 nlp DID 4 nlp flag 5 nlp state 6 nle nlp rpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0111 Dropping received ELS cmd DESCRIPTION The driver decided to drop an ELS response ring entry DATA 1 ulpStatus 2 ulpWord 4 SEVERITY Error LOG Always Emulex Drivers for VMware ESX 3 5 User Manual Page 23 gt G EMULEX ACTION This error could indicate a software driver or firmware problem If problems persist report these errors to Technical Support _ 50112 ELS command lt elsCmd gt on vpi lt vpi gt received from NPORT did DESCRIPTION Received the specific ELS command from a remote NPort DATA 1 fc_ffstate SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Ipfc 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 SEVERITY Error LOG Always ACTION Check device DID Ipfc mes0114 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0115 Unknown ELS command lt elsCmd gt
41. TAIL If link events received log 1 last event number received 2 ALPA granted 3 Link speed 4 number of entries in the loop init LILP ALPA map An ALPA map message is also recorded if LINK EVENT verbose mode is set Each ALPA map message contains 16 ALPAs 5 mm 6 ft SEVERITY Error LOG Always ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network Ipfc mes1304 Link Up Event ALPA map DESCRIPTION A link up event was received DATA 1 wd1 2 wd2 3 wd3 4 wd4 SEVERITY Warning LOG LOG LINK EVENT verbose ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network Ipfc mes1305 Link Down Event lt eventTag gt received DESCRIPTION A link down event was received DATA 1 fc eventTag 2 hba state 3 fc flag SEVERITY Error LOG Always ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network Ipfc mes1306 Link Down timeout DESCRIPTION The link was down for greater than the configuration parameter Ipfc linkdown tmo in seconds All I O associated with the devices on this link will fail DATA 1 hba state 2 fc flag 3 fc ns retry SEVERITY Warning LOG LOG LINK EVENT LOG DISCOVERY verbose ACTION Check the HBA cable connection to the Fibre Channel network Ipfc mes1307 READ LA mbox error mbxStatus state hba state DESCRIPTION The dr
42. a supported driver that corrects the DMA transfer issue In addition the adapter may require a firmware upgrade The minimum firmware revisions are LP10000 series HBA 1 92a1 LP11000 series HBA 2 72a2 If you have any questions on the minimum firmware revision contact Emulex Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 15 ESX Server NIC Table 4 ESX Server NIC gt G EMULEX Situation Resolution During boot the system hangs after the OneConnect BIOS banner is displayed The firmware may be corrupted and must be re flashed Contact Emulex Technical Support for additional assistance A Iot of alloc_skb failed messages appear in the log file proc vmware log This could be due to low configured value for netPktHeapMaxSize Try increasing it to a higher value To read the current value run esxcfg advcfg j netPktHeapMaxSize A value of 0 indicates default 64MB To increase the size to for example 128 MB run esxcfg advcfg k 128 netPktHeapMaxSize netPktHeapMaxSize can also be configured through VI Client using Configuration Advanced Settings VMKernel After configuring the size reboot the system Unable to ping from one VM to another VM The OneConnect driver creates two vmnic interfaces one for each port If these interfaces are configured as uplinks in two separate vSwitches the VMs in each of these switches are in separate
43. able to get BE Firmware The firmware command to get the version Version number failed Most likely due to incompatible firmware Emulex Drivers for VMware ESX 3 5 User Manual Page 18 Table 5 ESX Server NIC Event Log Entries Continued EMULEX Severity Message Displayed Description Warning alloc skb failed Try The driver could not allocate an skb to pass a increasing received frame to the stack A transient failure netPktHeapMaxSize can be ignored If this message is often observed try increasing netPktHeapMaxSize For example to set the size to 256MB run esxcfg advcfg k 256 netPktHeapMaxSize then reboot the system Warning Invalid MTU requested An invalid MTU size is in the MTU Must be between DDD and configuration ioctl The MTU will not be DDD bytes changed Information MTU changed from DDD to The MTU size changed as requested lt DDD gt Warning Unable to get pause frame The firmware command to get the pause settings frame settings failed Warning Unable to set pause frame The firmware command to set the pause settings frame settings failed Information Active port changed due The active port of the OneConnect UCNA to VLD on switch changed and the change was triggered by a VLD message from the switch The current link status follows this message Information Active port changed due The active port of the OneConnect UCNA to port link sta
44. adapter SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed the driver will recover from this and continue with normal operation Ipfc mes0268 FCFI information DESCRIPTION This message logs detailed FCF entry information upon the completion of a register FCFI mailbox command DATA 1 idx 2 fcfi 3 rq idO 4 rq idt 5 rq id2 6 id3 7 tp matchO0 8 tp 9 rctl matchO 10 rctl mask SEVERITY Information LOG LOG DISCOVERY verbose ACTION Information only no action needed Ipfc mes0269 REG VFI Data DESCRIPTION This messages logs the entire register VFI mailbox command payload DATA REG VFI mailbox payload word15 SEVERITY Information LOG LOG DISCOVERY verbose ACTION Information only no action needed Ipfc mes0270 REG VFI mbxStatus error DESCRIPTION Register VFI mailbox failed DATA 1 mbxStatus 2 HBA state 3 RPI bitmap SEVERITY Error LOG Always ACTION Check the fabric configuration and reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0271 Issue Register VFI failed DESCRIPTION Issue register VFI mailbox failed DATA 1 vpi 2 err SEVERITY Error Emulex Drivers for VMware ESX 3 5 User Manual Page 36 EMULEX LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc m
45. ailbox Events 0300 0399 40 Initialization Events 0400 0499 48 IP Log Events 0600 0699 nnns 60 FCP Traffic History 0700 0799 nnns 61 Node Table Events 0900 0999 65 Miscellaneous Events 1200 1299 68 Link Events 1300 1399 e enne 69 LIBDFC Events 1600 1699 72 VPort Events 1800 1899 nennen nennen 72 Initialization Events 4500 4599 ee 75 Emulex Drivers for VMware ESX 3 5 User Manual Page iv EMULEX Installation Driver Information Supported Features Protocols SCSI FCP Fibre Channel over Ethernet FCoE FC initiator mode and NIC Supports 256 0 255 logical unit numbers LUNs Supports dynamically adding LUNs and targets Topology support Fibre Channel Arbitrated Loop FC AL point to point fabric with auto topology negotiation Support for 1 2 4 8 and 10 Gb s capable adapters with auto rate negotiation Support for up to sixteen adapter ports Remote monitoring and parameter configuration using Emulex s OneCommand Manager application and the OneCommand Manager application Command Line Interface CLI Support for C
46. ask SEVERITY Information LOG LOG DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0207 Issue Report LUN on NPort nlp DID DESCRIPTION The driver issued a REPORT LUN SCSI command to an FCP target DATA 1 failMask 2 nlp state 3 SEVERITY Information LOG LOG DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0208 Failmask change on NPort nlp DID on vpi lt vpi gt DESCRIPTION An event was processed that indicates the driver may not be able to communicate with the remote NPort DATA 1 nlp failMask 2 bitmask 3 flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0209 RFT request completes ulpStatus lt ulpStatus gt CmdRsp lt CmdRsp gt DESCRIPTION A RFT request that was sent to the fabric completed DATA 1 nlp failMask 2 bitmask 3 flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0210 Continue discovery with num disc nodes ADISCs to go DESCRIPTION A device discovery is in progress Emulex Drivers for VMware ESX 3 5 User Manual Page 28 EMULEX DATA 1 fc adisc cnt 2 fc flag 3 vport port state SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0211 DSM IN vpi lt vpi gt event evt on NPort nlp DID in state cur state DESCRI
47. at lt gt DESCRIPTION The queue cannot be destroyed mailbox command failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0480 DESTROY mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be destroyed mailbox command failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0481 RQ DESTROY mailbox failed stat lt gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be destroyed mailbox command failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0482 CREATE mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt gt DESCRIPTION The queue cannot be created DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0483 POST SGL mailbox failed stat lt x x gt stat lt x x gt mbx stat lt x x gt DESCRIPTION The POST SGL mailbox command failed DATA None SEVERITY Error LOG Alway
48. ate MSI X IRQ vectors for each of the interfaces Pinning VMs and the IRQ vector to a CPU core provides the best performance for OneConnect UCNAs With a multi core CPU pinning a VM and the MSI X vector of the OneConnect driver interface configured in that VM to two cores sharing an L2 cache provides the best performance Emulex Drivers for VMware ESX 3 5 User Manual Page 10 gt G EMULEX For example in a quad core Xeon CPUO and CPU1 share a 4MB L2 cache If vmnic07 is configured in VM1 for the best performance pin VM1 to CPUO and the IRQ corresponding to vmnic07 to CPU1 To pin a VM to a CPU in the VI Client Power OFF the VM Click Edit Settings for that VM then select the Resources tab Select Advanced CPU in the left pane In the Scheduling Affinity frame select the CPU to pin it to 5 Power ON the VM To pin IRQ vector on CPU run the following command in the console operating system echo move IRQ NO lt CPU ID gt gt proc vmware intr tracker You can find the IRQ NO corresponding to a vmnic by running cat proc vmware interrupts To see all IRQ Vectors and the CPU they are pinned to run cat proc vmware intr tracker Emulex LPFC Driver Configuration Parameters All adapter specific LPFC driver parameters have an IpfcX prefix where X is the driver instance number for example setting IpfcO lun queue depthz20 makes 20 the default number of maximum commands which can be sent t
49. ation LOG LOG NODE verbose ACTION None required lpfc mes0901 FIND node DID mapped DESCRIPTION The driver is searching for a node table entry on the mapped node list based on the DID DATA 1 nlp 2 DID 3 flag 4 data1 SEVERITY Information LOG LOG NODE verbose ACTION None required lpfc mes0902 FIND node DID mapped DESCRIPTION The driver is searching for a node table entry on the mapped node list based on the DID DATA 1 nlp 2 DID 3 flag 4 data1 SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0903 Add scsiid sid to BIND list DESCRIPTION The driver is putting the node table entry on the binding list DATA 1 bind cnt 2 nlp DID 3 bind type 4 blp SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0904 Add NPort did to PLOGI list on vpi lt vpi gt DESCRIPTION The driver is putting the node table entry on the PLOGI list DATA 1 plogi cnt 2 blp SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0905 Add NPort did to ADISC list DESCRIPTION The driver is putting the node table entry on the ADISC list DATA 1 adisc cnt 2 blp SEVERITY Information LOG LOG NODE verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 65 EMULEX Ipfc mes0906 Add NPort did to UNMAP list DESCRIPTION The driver is putting the
50. ck if NetQueue is enabled run the following command from the ESX Server console ESXH esxcfg advcfg j netNetqueueEnabled If it prints netNetqueueEnabled FALSE the feature is disabled To enable NetQueue run the following command ESX esxcfg advcfg k TRUE netNetqueueEnabled Reboot the ESX Server for the change to take effect How ESX Server Creates and Names Interfaces The OneConnect NIC driver supports a maximum of four UCNAs per system For dual channel UCNAs running in standard operating mode the OneConnect 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 system BIOS When vNIC mode is enabled in the system BIOS for those boards that support vNIC the OneConnect driver creates eight interfaces four for each physical port The interfaces are labeled vmnicO through vmnic7 assuming there are no other network interfaces in your configuration All 8 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 Emulex Drivers for VMware ESX 3 5 User Manual Page 8 EMULEX esxcfg nics 1 list recognized nics d esxcfg vswitch 1 list available vswitches 4 esxcfg vswitch a vSwitcho create vSw
51. d RQ count of d at d DESCRIPTION The queue cannot be initialized with the specified count DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0476 CREATE mailbox failed stat lt gt add stat lt x x gt mbx stat lt gt DESCRIPTION The queue cannot be initialized with the specified count DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0477 EQ DESTROY mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be destroyed mailbox command failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0478 CQ DESTROY mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt x x gt DESCRIPTION The queue cannot be destroyed mailbox command failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 57 gt G EMULEX Ipfc mes0479 MQ DESTROY mailbox failed stat lt x x gt add stat lt x x gt mbx st
52. e 2 Ipfc 7 4 0 13 2 2 4 and 8 Gb s Asynchronous CNA Release for ESX 3 5 Update 2 Ipfc 7 4 0 31 FCoE ESX 3 5 Update 4 Ipfc 7 4 0 40 2 4 8 Gb s Asynchronous CNA Release for ESX 3 5 Update 4 Ipfc 7 4 0 41 FCoE ESX 3 5 Update 5 Ipfc 7 4 0 52 FC FCoE be2 2 101 374 0 NIC Compatibility For a list of adapters that are compatible with this driver see the driver s Downloads page on the Emulex Web site For compatible firmware versions see the Downloads page for the specific adapter Known Issues Refer to the product release notes for the latest information Emulex Drivers for VMware ESX 3 5 User Manual Page 2 EMULEX Installing the Drivers There are two Emulex drivers FC FCoE and NIC available through the Emulex Web site Note The NIC driver must be installed to manage OneConnect FCoE or NIC UCNAs using the OneCommand Manager application To install the Emulex drivers for VMware 1 Install a supported Emulex adapter in the system Refer to the adapter s Installation manual for specific hardware installation instructions 2 Remove any previously installed drivers and or utilities such as HBAnyware that were installed from the Emulex CD or downloaded from the Emulex Web site before proceeding Refer to Uninstalling the Drivers on page 4 and Uninstalling Older HBAnyware Kits on VMware on page 5 for more information 3 Download the specific driver
53. e 4 gt G EMULEX Uninstalling Older HBAnyware Kits on VMware To uninstall an older HBAnyware Kit on VMware Log on to the ESX Server host 2 Type rpm qa grep elx and locate either of the following rpm files elxvmwarecorekit kit version Or elxocmcore esx35 kit version 3 Type rpm e elxvmwarecorekit kit version Or rpm e elxocmcore esx35 kit version Emulex Drivers for VMware ESX 3 5 User Manual Page 5 gt G EMULEX Configuration Introduction You can configure the driver parameters using native ESX tools or Emulex s OneCommand Manager application This section describes how to configure parameters using native ESX tools For a more comprehensive description of ESX tools refer to the vi3 server config pdf documentation If you have further questions contact a VMware technical support representative Note VMware does not officially support unloading the driver via vmkload mod u If you must unload the driver contact VMware customer support Emulex recommends using the OneCommand Manager application to set the configuration parameters Refer to the Emulex OneCommand Manager Application User Manual for more information about the utility Note NPIV port creation and deletion are performed by VMware s Infrastructure Client VIC Refer to VMware s Infrastructure Client documentation for more information Note In band management FC based management is not supported on VMwa
54. ed DATA 1 vpi 2 rc SEVERITY Warning LOG LOG MBOX LOG SLI verbose ACTION None required Ipfc mes4512 Cannot issue sync mailbox cmd lt opcode gt DESCRIPTION Synchronous mailbox command cannot be issued DATA 1 vpi 2 rc SEVERITY Warning LOG LOG MBOX LOG SLI verbose ACTION None required Ipfc mes4513 ELS has a different Queue ld DESCRIPTION The event ID consumed by the adapter does not match the intended ELS WQ ID DATA 1 Event Queue Id 2 ELS WQ Id SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4514 Invalid Completion event code DESCRIPTION An invalid slow path completion event was received DATA 1 majorcode 2 minorcode SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4515 Invalid Completion Queue Id DESCRIPTION An invalid Completion Queue ID was received DATA 1 Completion Queue ID received from the firmware SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4516 Fast path has a different Queue Id DESCRIPTION The event ID consumed by the adapter does not match the intended FCP WQ ID DATA 1 Event Queue Id 2
55. ed from DID lt did gt DESCRIPTION A FARP ELS command response was received DATA None SEVERITY Information LOG LOG_IP verbose ACTION No action needed informational Ipfc mes0601 FARP REQ received from DID did DESCRIPTION A FARP ELS command request was received DATA None SEVERITY Information LOG LOG verbose ACTION No action needed informational Ipfc mes0610 FARP Request sent to remote DID DESCRIPTION A send to a remote IP address has no node in the driver s nodelists Send a FARP request to obtain the node s HW address DATA 1 IEEE 0 2 IEEE 1 3 IEEE 2 4 IEEE 3 5 IEEE 4 6 IEEE 5 SEVERITY Information LOG LOG verbose ACTION Issue FARP and wait for PLOGI from remote node Emulex Drivers for VMware ESX 3 5 User Manual Page 60 EMULEX FCP Traffic History 0700 0799 Ipfc mes0701 Issue Abort Task Set to TGT num LUN num DESCRIPTION The SCSI layer detected that it needs to abort all I O to a specific device This results in an FCP Task Management command to abort the I O in progress DATA 1 scsi id 2 lun id 3 rpi 4 flags SEVERITY Information LOG LOG FCP verbose ACTION Check the state of the device in question Ipfc mes0702 Issue Target Reset to TGT num DESCRIPTION The SCSI layer detected that it needs to abort all I O to a specific target This results in an FCP Task Management command to abort the I O in progress
56. eeded Informational Ipfc mes0343 Mailbox cmd lt x x gt Status lt x x gt Data lt x x gt DESCRIPTION Results of read rcoe parameter mbox command DATA MBOX 0 16 50 mcge wordO mcqe tag0 mcqe tag1 mcqe trailer SEVERITY Information LOG LOG MBOX verbose ACTION No action needed informational Ipfc mes0344 Restart HBA PCI function DESCRIPTION The HBA PCI function has been killed DATA 1 HBA state 2 sli flag SEVERITY Information LOG LOG_SLI verbose ACTION No action needed informational Ipfc mes0345 Synchronous IOCB timeout d seconds DESCRIPTION A synchronous IOCB has not completed DATA None SEVERITY Warning LOG Always ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 46 EMULEX Ipfc mes0346 Mailbox fail cmd opcode stat mbox stat mcqe stat DESCRIPTION A mailbox command failed DATA varWord 0 varWord 7 SEVERITY Error LOG Always ACTION This error could indicate a software driver or firmware problem If this problem persists report these errors to Technical Support Ipfc mes0347 Mailbox cmd x x lt x x gt x9ex sent data DESCRIPTION Issue a mailbox command DATA varWord 0 varWord 7 SEVERITY Information LOG LOG MBOX ACTION No action needed informational Ipfc mes0348 Mailbox cmd lt opcode gt cmpl DESCRIPTION A mailbox command completed DATA varWord 0 varWord 7 SEVERITY I
57. ent during Discovery DESCRIPTION Received link event during discovery Causes discovery restart DATA 1 hba state 2 ulploTag 3 ulpStatus 4 ulpWord 4 SEVERITY Warning LOG LOG DISCOVERY verbose ACTION None required unless problem persists If persistent check cabling Emulex Drivers for VMware ESX 3 5 User Manual Page 32 EMULEX Ipfc mes0238 NameServer Rsp DESCRIPTION The driver received a NameServer response DATA 1 Did 2 nlp flag 3 fc flag 4 fc rscn id cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0239 NameServer Rsp DESCRIPTION The driver received a NameServer response DATA 1 Did 2 ndlp 3 fc flag 4 fc rscn id cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0240 NameServer Rsp Error DESCRIPTION The driver received a NameServer response containing a status error DATA 1 CommandResponse bits CmdRsp 2 ReasonCode 3 Explanation 4 fc flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0241 NameServer Rsp Error DESCRIPTION The driver received a NameServer response containing a status error DATA 1 CommandResponse bits CmdRsp 2 ReasonCode 3 Explanation 4 fc flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION C
58. es0272 Failed to allocate mbox for READ FCF DESCRIPTION Failed to allocate memory for issuing READ FCF mailbox command DATA None SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0O273 Allocated DMA memory size 96d is less than the requested DMA memory size DESCRIPTION Failed to allocate DMA memory for issuing READ mailbox command DATA 1 Allocated DMA memory size 2 Requested DMA memory size SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0274 Failed to get the non embedded SGE virtual address DESCRIPTION Failed to get the SGE virtual address for the non embedded mailbox command DATA None SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary This is an unlikely error If this condition persists contact Emulex Technical Support Ipfc mes0275 Failed to create mbox command for READ FCF cmd DESCRIPTION Failed to construct READ FCF mailbox command for discovery data DATA None SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0276 Failed to create mbox command for READ FCF cmd DESCRIPTION Failed to construct READ FCF mailbox command for managemen
59. ex Drivers for VMware ESX 3 5 User Manual Page 6 EMULEX To make changes that impact all adapters in the system global changes follow these steps See LPFC Driver Configuration Parameters on page 11 for parameter names and values Parameter values are hexadecimal and decimal 1 From the Console Operating System COS terminal window type esxcfg module s param value param2 value driver name gt The driver name is obtained from the vmkload mod 1 call Look for the Ipfc prefix 2 Rebuild the ESX bootstrap settings Type esxcfg boot b 3 Reboot the server Type reboot Example of Permanent Global Configuration The following example sets lun queue depth to 20 default is 30 for all Emulex adapters in your system Locate the parameter in Table 2 on page 11 2 Setthe permanent value Type esxcfg module s lpfc lun queue depth 20 driver name gt 3 Rebuild the ESX bootstrap settings Type esxcfg boot b 4 Rebootthe server Type reboot The new setting is used when the driver reloads To verify the setting type esxcfg module g lpfc 740 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 driver name 2 Rebuild the ESX bootstrap settings Type esxcfg boot b 3 Reboot the server Type reboot The new setting is used when the drive
60. ffers DESCRIPTION The driver attempted to issue a READ LA mailbox command to the HBA but there were no buffers available DATA None SEVERITY Warning LOG LOG MBOX verbose ACTION This message indicates 1 a possible lack of memory resources Try increasing the Ipfc num bufs configuration parameter to allocate more buffers 2 A possible driver buffer management problem If this problem persists report the error to Technical Support Ipfc mes0301 READ SPARAM no buffers DESCRIPTION The driver attempted to issue a READ SPARAM mailbox command to the HBA but there were no buffers available DATA None SEVERITY Warning LOG LOG MBOX verbose ACTION This message indicates 1 a possible lack of memory resources Try increasing the Ipfc num bufs configuration parameter to allocate more buffers 2 A possible driver buffer management problem If the problem persists report the error to Technical Support Ipfc mes0302 REG LOGIN no buffers DESCRIPTION The driver attempted to issue a REG LOGIN mailbox command to the HBA but there were no buffers available DATA 1 did 2 rpi 3 vpi 4 flag SEVERITY Warning LOG LOG MBOX verbose ACTION This message indicates 1 a possible lack of memory resources Try increasing the Ipfc num bufs configuration parameter to allocate more buffers 2 A possible driver buffer management problem If the problem persists report the error to Technical Support Ipfc mes03
61. fg j netPktHeapMaxSize netPktHeapMaxSize 0 If the default value of the 64MB is in effect this command shows the size as 0 If any other values are in effect it prints the current value ESX Server Network Driver The following section includes examples of the various configuration parameters for improving the performance of the OneConnect network drivers for ESX Server Enabling vmxnet Emulation Jumbo Frames and TSO The OneConnect UCNA supports jumbo frames and TSO Both jumbo frames and TSO are necessary for optimal performance with the OneConnect UCNA Also using the vmxnet NIC emulator can provide a significant performance boost These features are not enabled by default in ESX Server To enable these features 1 Log into the console operating system COS 2 For each guest operating system there is a vmx file in the path vm s volumes VM NAME VM NAME vmx where lt VM NAMESs is the name of the VM Emulex Drivers for VMware ESX 3 5 User Manual Page 9 gt G EMULEX 3 For each VM edit this file and add the following line for the OneConnect driver interface ethernet0 features z 5 4 To enable vmxnet emulation add the following line for the OneConnect driver interface ethernetO0 virtualDev vmxnet 5 Restart the VMs The above steps 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 gue
62. formation LOG LOG DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0217 Unknown Identifier in RSCN payload DESCRIPTION Typically the identifier in the RSCN payload specifies a domain area or a specific NPort ID If neither of these are specified a warning will be recorded Emulex Drivers for VMware ESX 3 5 User Manual Page 29 EMULEX DATA 1 didp gt un word DETAIL 1 Illegal identifier SEVERITY Error LOG Always ACTION Potential problem with the fabric Check with the fabric vendor Ipfc mes0218 FDMI Request DESCRIPTION The driver is sending an FDMI request to the fabric DATA 1 flag 2 hba state 3 cmdcode SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0219 Issue FDMI request failed DESCRIPTION Cannot issue FDMI request to HBA DATA 1 cmdcode SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0220 FDMI rsp failed DESCRIPTION An error response was received to FDMI request DATA 1 be16 to cpu fdmi cmd SEVERITY Information LOG LOG DISCOVERY verbose ACTION The fabric does not support FDMI check fabric configuration Ipfc mes0221 FAN timeout DESCRIPTION A link up event was received without the login bit set so the driver waits E D TOV for the fabric to send a FAN If no FAN is received a FLOGI will be sent after the timeout
63. g 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 Messages Displayed column refers to decimal values that appear in the actual error messages Table 5 ESX Server NIC Event Log Entries failed Not using MSIx Severity Message Displayed Description Warning Could not get link status The firmware command to get the Link status for nmnic lt D gt returned an error Error Cannot create more than The OneConnect UCNA supports a maximum 17 interfaces of 17 interfaces This error is reported when the driver is loaded with a value more than 17 for the module parameter rings Warning add async event callback The firmware command to register for link failed Link status status changes failed Messages indicating changes may not be link status change will not appear If the link is reflected up the driver should work properly Warning Cannot support more than The driver supports up to a maximum of three 3 BE Adapters adapters More than three adapters were detected The first three adapters should work correctly The rest cannot be used Warning Did not receive Some transmit requests that were started did completions for all TX not complete in a reasonable time during requests unloading of the driver This is most likely due to a fatal fault in the adapter Warning VMware doesn t support The driver
64. g SEVERITY Information LOG LOG DISCOVERY verbose ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0263 NameServer Rsp Error DESCRIPTION The driver received a nameserver response containing a status error DATA 1 CommandResponse bits CmdRsp 2 ReasonCode 3 Explanation 4 fc flag SEVERITY Information LOG LOG DISCOVERY verbose ACTION Check the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0265 Vport NameServer login no memory DESCRIPTION Remote node memory allocation failed for logging into name server for a VPort Emulex Drivers for VMware ESX 3 5 User Manual Page 35 EMULEX DATA 1 vid SEVERITY Error LOG Always ACTION Check the driver memory utilization and reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0266 Vport cannot issue NameServer login DESCRIPTION Issue PLOGI to VPort remote nameserver failed DATA 1 vid SEVERITY Error LOG Always ACTION Check the fabric configuration and reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0267 Adapter message DESCRIPTION When the response IOCB carrys an unknown IOCB type and the upper layer command is an adapter message it logs the adapter message returned from the adapter DATA Message returned from the
65. heck the fabric configuration The driver recovers from this and continues with device discovery Ipfc mes0242 Abort outstanding I O to the Fabric DESCRIPTION All outstanding I Os to the fabric are cleaned up DATA 1 Fabric DID SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0243 Issue FDMI request failed DESCRIPTION Cannot issue an FDMI request to HBA DATA 1 cmdcode SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0244 Issue FDMI request failed DESCRIPTION Cannot issue an FDMI request to the HBA DATA 1 cmdcode SEVERITY Information LOG LOG Discovery verbose Emulex Drivers for VMware ESX 3 5 User Manual Page 33 EMULEX ACTION No action needed informational Ipfc mes0245 ALPA based bind method used on an HBA which is in a nonloop topology DESCRIPTION ALPA based bind method used on an HBA which is not in a loop topology DATA 1 topology SEVERITY Warning LOG LOG DISCOVERY verbose ACTION Change the bind method configuration parameter of the HBA to 1 WWNN 2 WWPN or S DID lpfc mes0246 RegLogin failed DESCRIPTION The firmware returned a failure for the specified RegLogin DATA Did mbxStatus hbaState vpi SEVERITY Error LOG Always ACTION This message indicates that the firmware could not do RegLogin for the specified DID There may be a limitation on how man
66. hreads 2 1 32 Yes NPIV Number of concurrent NameServer requests allowed to be outstanding Ipfc pci max read 0 0 driver default No The maximum number of 512 512 bytes bytes transferred per pci 1024 1024 bytes DMA read The default 2048 2048 bytes value 0 means the driver 4096 4096 bytes will automatically determine the correct value Update1 only Ipfc peer vport login 0 0 1 Yes NPIV Allows peer vports to log into each other Ipfc scan down 1 0 Off 1 On Yes Select method for scanning ALPA to assign a SCSI ID Ipfc scsi req tmo 30 0 255 Yes Time out value in seconds for SCSI passthrough requests Ipfc tgt queue depth Oxffff 1 Oxffff Yes Default max commands sent to a single target Value not to exceed what the adapter supports minus ten see Ipfc hba queue depth For example if the adapter supports 512 the target will default to 502 Ipfc topology 0 0x0 loop No FC link topology defaults to then P2P loop if it fails attempts 0x2 P2P only point to point mode 0x4 loop only Note This parameter only 0x6 P2P applies to SLI 3 then loop based adapters lpfc use adisc 0 0 Off 1 On Yes Send ADISC instead of PLOGI for device discovery or RSCN Emulex Drivers for VMware ESX 3 5 User Manual Page 14 Troubleshooting Introduction EMULEX There are several circumstances in which your system may operate in an unexpected manner The Troubleshooting section explains many of these circumstances a
67. ion har Host Att Reg hsr Host Stat Reg DESCRIPTION Defer error condition detected DATA None SEVERITY Error LOG Always ACTION This error indicates that this port is temporarily going offline If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 55 gt G EMULEX Ipfc mes0467 Defer error condition cleared har Host Att Reg hsr Host Stat Reg DESCRIPTION Defer error condition cleared DATA None SEVERITY Error LOG Always ACTION This error indicates that this port is no longer offline due to the defer error condition Recovery will be attempted If problems persist report these errors to Technical Support Ipfc mes0468 Error during rpi post operation DESCRIPTION Unable to create an RPI header DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0469 Unsupported EQ count of lt d gt DESCRIPTION The event queue cannot be initialized with the specified count DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0470 EQ CREATE mailbox failed stat lt x x gt add stat lt x x gt mbx stat lt gt DESCRIPTION The queue cannot be created DATA None SEVERITY Error LOG
68. iority IOCB cmd x x exceeded allotted wait time of d jiffies DESCRIPTION The driver didn t get a completion for a high priority IOCB within the wait time allotted DATA 1 ulpCommand 2 allotted wait time in jiffies SEVERITY Error LOG Always ACTION Depending on the ulpCommand and the associated task command there could be an oversubscription condition in the SAN If problems persist report these error to Technical Support Ipfc mes0329 Ring d handler unexpected ASYNC STATUS evt code 0x x DESCRIPTION The port has issued an unexpected asynchronous event code to the driver DATA IOCB 0 15 SEVERITY Error LOG Always ACTION This error could indicate a driver or firmware problem If problems persist report these error to Technical Support Ipfc mes0330 Command IOCB lookup miss on Fast lookup array DESCRIPTION The loTag provided did not result in a valid command IOCB in the fast lookup array DATA 1 loTag 2 Ring number SEVERITY Error LOG Always ACTION This error could indicate a driver or firmware problem If problems persist report these error to Technical Support Ipfc mes0331 Ring d handler unexpected ASYNC STATUS iocb received evt code 0x x DESCRIPTION The port has issued an unexpected asynchronous event code to the driver DATA IOCB 0 15 SEVERITY Error LOG LOG SLI ACTION This error could indicate a hardware firmware problem If problems persist report these error to Technical Suppor
69. itcho esxcfg vswitch A VMNet0O vSwitcho create virtual machine network VMNetO and add it to vSwitchO d esxcfg vswitch L vmnicO vSwitcho link vmnicO to vSwitcho The only difference being that in vNIC mode each of the four vNICs tied to a physical port share the port s 10GbE bandwidth Configuring VLANs The OneConnect NIC driver is programmed to perform VLAN filtering in the hardware To configure VLANs on a OneConnect NIC driver interface create the vSwitch with the required VLAN ID and this interface as an adapter to this vSwitch Native VLAN configuration in the guest operating system for example using vconfig in the Linux guest operating system is not supported Configuring Network Heap Size in ESX Server By default the ESX Server network stack allocates 64MB of buffers to handle network data If the network load requires more than 64MB of memory to hold the in transit network data the OneConnect NIC driver cannot allocate memory for posting receive buffers When this happens the NIC driver logs messages in the file proc vmware log indicating that the alloc_skb call failed This impacts the network performance considerably e To increase the network heap size to a larger value for example 128MB run esxcfg advcfg k 128 netPktHeapMaxSize d esxcfg advcfg j netPktHeapMaxSize netPktHeapMaxSize 128 The new value takes effect after a reboot To read the current size of the network heap run d esxcfg advc
70. iver cannot determine what type of link event occurred DATA None SEVERITY Information LOG LOG LINK EVENT verbose ACTION If numerous link events are occurring check the physical connections to the Fibre Channel network May indicate a possible hardware or firmware problem Emulex Drivers for VMware ESX 3 5 User Manual Page 70 EMULEX Ipfc mes1308 Menlo Maint Mode Link Up Event lt eventTag gt rcvd DESCRIPTION The driver received a Menlo Maint Mode Link Up Event DATA link event tag SEVERITY Information LOG LOG LINK EVENT verbose ACTION None required lpfc mes1309 Menlo Maint Mode Link Down Event evTag rcvd Data fc evTag hba state fc flag DESCRIPTION The driver received a Menlo Maint Mode Link down Event DATA link event tag SEVERITY Information LOG Always ACTION None required Ipfc mes1310 FCoE is running golden firmware Update immediately DESCRIPTION The FCoE card requires a firmware update DATA link event tag SEVERITY Error LOG Always ACTION Firmware update required Ipfc mes1311 FCoE hba port in diagnostic mode Operational use suspended DESCRIPTION The HBA port is not operational while in diagnostic mode DATA None SEVERITY Error LOG Always ACTION Firmware update required Ipfc mes1312 FCoE chip is running unknown firmware ft DESCRIPTION The FCoE card requires a firmware update DATA firmware tag SEVERITY Error LOG Alwa
71. ivers for VMware ESX 3 5 User Manual Page 34 EMULEX LOG Always ACTION If this condition persists contact Emulex Technical Support Ipfc mes0252 Unrecognized event type found in task list DESCRIPTION An event posted to the task list wasn t recognized DATA 1 evt 2 arg1 3 arg2 SEVERITY Error LOG Always ACTION If this condition persists contact Emulex Technical Support Ipfc mes0256 Start nodev timer DESCRIPTION A target disappeared from the Fibre Channel network If the target does not return within nodev tmo timeout all I O to the target will fail DATA 1 DID 2 flag 3 state 4 SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0260 Stop Nodev timeout on NPort nlp DID DESCRIPTION The FCP target was rediscovered and I O can be resumed DATA 1 DID 2 flag 3 state 4 nlp SEVERITY Information LOG LOG DISCOVERY verbose ACTION Check Fabric configuration The driver recovers from this and continues Ipfc mes0261 FAN received DESCRIPTION A FAN was received from the fabric DATA NONE SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0262 NameServer Rsp Error DESCRIPTION The driver received a nameserver response containing a status error DATA 1 CommandResponse bits CmdRsp 2 ReasonCode 3 Explanation 4 fc fla
72. l Ipfc mes0226 Device discovery completion error DESCRIPTION This indicates that an uncorrectable error was encountered during device re discovery after a link up Fibre Channel devices will not be accessible if this message is displayed DATA None SEVERITY Error LOG Always ACTION Reboot the system If the problem persists report the error to Technical Support Run with verbose mode on for more details Ipfc mes0227 Node Authentication timeout DESCRIPTION The driver has lost track of what NPorts are being authenticated DATA None SEVERITY Error LOG Always ACTION None required The driver should recover from this event Ipfc mes0228 CLEAR LA timeout DESCRIPTION The driver issued a CLEAR LA that never completed DATA None SEVERITY Error LOG Always ACTION None required The driver should recover from this event Ipfc mes0229 Assign scsi ID sid to NPort nlp DID DESCRIPTION The driver assigned a SCSI ID to a discovered mapped FCP target DATA 1 nlp bind type 2 nlp flag 3 nlp state 4 nlp rpi SEVERITY Information LOG LOG DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0230 Cannot assign scsi ID on NPort nlp DID DESCRIPTION The driver cannot assign a SCSI ID to a discovered mapped FCP target DATA 1 nlp flag 2 nlp state 3 nlp rpi Emulex Drivers for VMware ESX 3 5 User Manual Page 31 EMULEX SEVERITY Information LOG
73. lue The request is ignored and the QoS setting is not changed Error betx ether frame The driver received a transmit request with Exceeds Max Tx Frags more than 30 fragments The request failed since the OneConnect UCNA does not support more than 30 SG elements in a TX request This should not normally happen in ESX Server 3 5 Error Bnilnit failed Error Initialization of the host data structures to lt DDD gt access the network function of the OneConnect UCNA reported an error Error Interface initialization Allocation of resources for the network failed interface failed Warning MSIX Request IRQ failed Request for MSI X interrupt registration for for pd id DD Errno the interface vmnicO DD failed The lt DDD gt OneConnect NIC driver interface should still work with INT X interrupts Error INTx Request IRQ failed Request for INT X interrupt registration failed Errno lt DDD gt This error is caused by system resource limitations The OneConnect NIC driver interface is unusable Warning Failed to register char Could not create the char device used for device certain management functions The driver must still work Error pci enable device for The operating system call to enable the BE adapter lt DD gt failed OneConnect UCNA failed Error Could not set PCI DMA The operating system call to set the DMA Mask mask failed Error BladeEngine init failed The initialization of the OneConnect UCNA failed Warning Un
74. mational Ipfc mes0105 LOGO completes to NPort nlp DID DESCRIPTION The HBA performed a LOGO to a remote NPort DATA 1 ulpStatus 2 ulpWord 4 3 num disc nodes SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0106 ELS cmd tag lt ulploTag gt completes DESCRIPTION The specific ELS command was completed by the firmware DATA 1 ulpStatus 2 ulpWord 4 SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Ipfc mes0107 Retry ELS command lt elsCmd gt to remote NPort lt did gt DESCRIPTION The driver is retrying the specific ELS command DATA 1 retry 2 delay SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Ipfc mes0108 No retry ELS command lt elsCmd gt to remote NPort did DESCRIPTION The driver decided not to retry the specific ELS command that failed DATA 1 retry 2 nlp flag SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0109 ACC to LOGO completes to NPort nlp DID DESCRIPTION The driver received a LOGO from a remote NPort and successfully issued an ACC response DATA 1 nlp flag 2 nlp state 3 nlp rpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0110 ELS response tag ulploTag completes DESCRIPTION The specific ELS response was completed by the firmware DA
75. meters match this HBA Request can be accepted DATA 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0121 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0122 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0123 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA 1 DID 2 state 3 flag 4 Rpi 5 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 25 EMULEX Ipfc mes0124 PLOGI chkparm DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service parameters match this HBA Request can be accepted DATA
76. ms persist contact Technical Support Ipfc mes4555 Config region 23 has bad version DESCRIPTION Config region 23 has bad version DATA None SEVERITY Error LOG Always ACTION It may not be a critical problem for the driver and HBA s normal operation if configure region contains a bad version However it may result in some of the management stack functionality not Emulex Drivers for VMware ESX 3 5 User Manual Page 83 gt G EMULEX working properly to manage the HBA Try to re configure the device configure region 23 if necessary If problems persist contact Technical Support Ipfc mes4556 Config region 23 has bad signature DESCRIPTION Config region 23 has bad signature DATA None SEVERITY Error LOG Always ACTION It may not be a critical problem for the driver and HBA s normal operation if configure region contains a bad signature However it may result in some of the management stack functionality not working properly to manage the HBA Try to re configure the device configure region 23 if necessary If problems persist contact Technical Support Ipfc mes4557 Config region 23 has bad version DESCRIPTION Config region 23 has bad version DATA None SEVERITY Error LOG Always ACTION It may not be a critical problem for the driver and HBA s normal operation if configure region contains a bad version However it may result in some of the management stack functionality not working properly to manage the
77. n maskable ACTION No action needed informational Ipfc mes0410 Cannot find virtual addr for mapped buf on ring num DESCRIPTION The driver cannot find the specified buffer in its mapping table Therefore the driver cannot find the virtual address needed to access the data DATA 1 first 2 first 3 last 4 cnt SEVERITY Error LOG Always ACTION This error could indicate a software driver or firmware problem If problems persist report these errors to Technical Support lpfc mes0411 fcp bind method is 4 with Persistent binding ignoring fcp bind method DESCRIPTION The configuration parameter for fcp bind method conflicts with Persistent binding parameter DATA 1 a current 2 fcp mapping SEVERITY Error config LOG Always ACTION Make necessary changes to the Ipfc configuration file Ipfc mes0412 Scan down is out of range ignoring scan down DESCRIPTION The configuration parameter for scan down is out of range DATA 1 clpgJCFG SCAN DOWN a current 2 fcp mapping SEVERITY Error LOG Always ACTION Make necessary changes to the Ipfc configuration file Ipfc mes0413 Configuration parameter out of range resetting to default value DESCRIPTION User is attempting to set a configuration parameter to a value not supported by the driver Resetting the configuration parameter to the default value DATA 1 a string 2 a low 3 a hi 4 a default SEVERITY Error config LOG Always ACT
78. nd offers one or more workarounds for each situation Unusual Situations and Their Resolutions General Situations Table 3 General Situations Situation Resolution Vports created on an adapter are not re created if the adapter is replaced VPorts are assigned to a specific adapter only They cannot be transferred to a new adapter You must create new VPorts if an adapter is replaced NPIV configuration not working as expected Check for a message similar to the following message in the VMkernel log The Adapter failed to init retry in SLI 2 mode This error could indicate a hardware or firmware problem Try reflashing your up to date FW or upgrade to the latest firmware If this problem persists report the error to Technical Support Emulex PCI X adapters and PCI X bridge chipsets DMA size transfer issue Sun Emulex and VMware have worked together to identify an issue with certain PCI X bridge chipsets The issue is currently limited to Sun Fire X4100 and X4200 servers Note The Sun Fire X4100 M2 and X4200 2 servers are not affected The issue is centered around the size of a DMA transfer that works repeatedly and successfully from the AMD chipset versus the maximum DMA transfer size supported by the adapter The primary symptoms are hung VMs and a large number of SCSI commands timed out by the Emulex driver If you are experiencing these symptoms contact VMware Technical Support for
79. ne sequence got dropped However if the problem persists it might have impact on inband management Reboot the system if necessary Ipfc mes0759 Outstanding SCSI command in the scheduler DESCRIPTION Log HBA information when there are outstanding SCSI commands in the scheduler DATA 1 hba cr 2 max 3 hba stsx 4 trgt Ic 5 tgt cr 6 tgt max 7 t sts 8 lun cr 9 lun max 10 lun st SEVERITY Information LOG LOG FCP verbose ACTION None required Ipfc mes0760 SCSI buffer to be freed has null pointer DESCRIPTION The SCSI buffer to be freed has a null pointer so a potential issue exists DATA None SEVERITY Error LOG Always ACTION None required if it only happened once or so However if the problem persists reset the HBA or reboot the system Ipfc mes0761 SCSI buffer count out of range DESCRIPTION The SCSI buffer count in the SCSI command is out of range DATA 1 count SEVERITY Error LOG Always ACTION A SCSI command returned with a busy state No action is required if it only happened once or so However if the problem persists reboot the system Emulex Drivers for VMware ESX 3 5 User Manual Page 64 gt G EMULEX Node Table Events 0900 0999 Ipfc mes0900 Cleanup node for NPort lt nlp_DID gt on vpi lt vpi gt DESCRIPTION The driver node table entry for a remote NPort was removed DATA 1 flag 2 state 3 4 status SEVERITY Inform
80. networks with no network path between them and pinging between the VMs in two groups will fail If you want all these VMs to be in the same network configure them as teaming uplinks to one vSwitch option Each of the vmnics vmnicO to vmnic7 must be configured in a separate vSwitch In this configuration there is no network path between the vSwitches and pinging between these VMs will not work ESX Server Event Error Log Messages Retrieving ESX Server NIC Error Log Codes For ESX Server systems the OneConnect NIC be2net driver generates error codes to the var log vmkernel log file The vmkernel log file is an ASCII text file and can be viewed and searched with a text editor such as vi The vmkernel log file is automatically rotated as it gets larger and the rotated log files are named vmkernel x where x is an integer To search the log file for error messages at the command prompt type var log dvi vmkernel For example you may see the following message Sep 9 19 48 04 esx server vmkernel BladeEngine 2 Net Driver Did not receive completions for all TX requests Emulex Drivers for VMware ESX 3 5 User Manual Page 16 ESX Server NIC Event Log Entries gt G EMULEX The following is a list of ESX Server 3 5 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 lo
81. nformation LOG LOG MBOX ACTION No action needed informational Ipfc mes0349 Mailbox sync cmd opcode lt ioctl gt cmpl DESCRIPTION A synchronous mailbox command completed DATA varWord 0 varWord 12 cqe 0 cqe 3 SEVERITY Information LOG LOG MBOX ACTION No action needed informational Ipfc mes0350 REG FCFI returned an error DESCRIPTION REG FCFI mbx returned an error DATA 1 mbxStatus 2 vport state SEVERITY Error LOG LOG MBOX ACTION No action needed Ipfc mes0351 Mailbox command timed out DESCRIPTION Indicates mailbox command timeout for SLI 4 HBA and no action was taken by the driver DATA 1 mbxCmd SEVERITY Error LOG Always ACTION If the system stopped working after this message was logged reboot the system Otherwise no action is needed If the problem persists contact Emulex Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 47 EMULEX Initialization Events 0400 0499 Ipfc mes0400 Ipfc 740 load failed reason DESCRIPTION An Ipfc 740 driver instance failed to load DATA function reason value SEVERITY Information LOG LOG INIT ACTION No action needed informational Ipfc mes0401 Detected Emulex PCI X DESCRIPTION An Emulex PCI X HBA was detected during initialization DATA 1 jedec_id 2 pci device id Severity Information Log LOG_INIT verbose Action No action needed informa
82. node table entry on the unmap list DATA 1 unmap cnt 2 3 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0907 Add NPort did to MAP list scsiid sid DESCRIPTION The driver is putting the node table entry on the mapped list DATA 1 map cnt 2 3 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0908 FIND node DID bind DESCRIPTION The driver is searching for a node table entry on the binding list based on the DID DATA 1 nlp 2 DID 3 flag 4 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0909 Removing default rpi on vpi lt vpi gt DESCRIPTION The driver is searching for a node table entry on the binding list based on the DID DATA 1 vport DID 2 rport DID 3 nlp flag 4 status SEVERITY Information LOG NODE verbose ACTION None required Ipfc mes0910 FIND node DID unmapped DESCRIPTION The driver is searching for a node table entry on the unmapped node list based on the DID DATA 1 nlp 2 DID 3 flag 4 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required lpfc mes0911 FIND node DID unmapped DESCRIPTION The driver is searching for a node table entry on the unmapped node list based on the DID DATA 1 nlp 2 DID 3 flag 4 state xri t
83. o a single logical unit disk for Ipfc instance 0 Dynamic parameters do not require a system reboot for changes to take effect Table 2 LPFC Driver Configuration Parameters Variable Default Min Max Dynamic Comments Ipfc hba queue depth Oxffff 1 Oxffff Yes Maximum number of FCP commands that can queue to an Emulex adapter The value cannot exceed what the adapter supports Ipfc initiator login 0 0 Off 1 On Yes Enables logins to other virtual initiators Ipfc_ackO 0 0 Off 1 On No Use ACKO for class 2 Ipfc automap 1 0 Off 1 On No Automatically assign SCSI IDs to FCP targets detected Ipfc check cond err 0 0 Off 1 On Yes Treat certain FCP check conditions as FCP RSP errors Emulex Drivers for VMware ESX 3 5 User Manual Page 11 Table 2 LPFC Driver Configuration Parameters Continued gt G EMULEX Variable Default Min Max Dynamic Comments Ipfc cr count 1 255 No This parameter determines the values for I O coalescing for cr delay msec or cr count outstanding commands Note This parameter only applies to SLI 3 based adapters Ipfc cr delay 63 No This parameter determines the values for I O coalescing for cr delay msec or cr count outstanding commands Note This parameter only applies to SLI 3 based adapters Ipfc delay rsp err 0 Off 1 On Yes Treat FCP RSP errors like no device delay
84. o quiesce DATA 1 port state 2 fc flag 3 num disc nodes 4 fc plogi cnt 5 fc adisc cnt 6 fc map cnt SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1817 Target d assigned to vpi d DID s WWPN s WWNN 5 DESCRIPTION Target mapping info for vport DATA 1 Target number 2 vpi number 3 DID d id 4 WWPN lt wwpn gt 5 WWNN lt wwnn gt Emulex Drivers for VMware ESX 3 5 User Manual Page 74 gt G EMULEX SEVERITY Information LOG LOG_VPORT verbose ACTION None required Ipfc mes1818 Failed to INIT_VPI DESCRIPTION VPI activation failed DATA 1 vpi 2 rc SEVERITY Warning LOG LOG VPORT verbose ACTION None required Ipfc mes1819 Revd an event with vport not null DESCRIPTION Received an event with the VPort not null DATA 1 event 2 vpi SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1820 ELS Ring rcvd an unexpected type DESCRIPTION ELS ring received an unexpected RCTL type DATA 1 ELS ring number 2 fh r ctl 3 fh type SEVERITY Warning LOG LOG VPORT verbose ACTION None required Initialization Events 4500 4599 Ipfc mes4500 iotag out of range DESCRIPTION The iotag lookup failed because it is outside the allowable range DATA 1 iotag 2 max 3 iocb 7 SEVERITY Error LOG Always ACTION This error may indicate a hardware firmware or driver problem If problems persist report these e
85. oblem If the problem persists report the error to Technical Support Ipfc mes0440 Adapter failed to init mbxCmd cmd READ REV detected outdated firmware DESCRIPTION Outdated firmware was detected during initialization DATA 1 read rev reset SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem Update the firmware If the problem persists report the error to Technical Support Ipfc mes0441 VPD not present on adapter mbxCmd cmd DUMP VPD mbxStatus status DESCRIPTION The DUMP VPD mailbox command failed DATA None SEVERITY Information LOG LOG INIT verbose ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support Ipfc mes0442 Adapter failed to init moxCmd cmd CONFIG PORT mbxStatus status DESCRIPTION Adapter initialization failed when issuing a CONFIG PORT mailbox command DATA 1 hbainit SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support lpfc mes0443 Failed to attach to Ipfc adapter bus bus device device irq lt irq gt DESCRIPTION An Ipfc adapter was found in the PCI config but the Ipfc driver failed to attach DATA 1 bus 2 device 3 irq SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist
86. of Data is intended for Emulex technical support engineering use only ELS Events 0100 0199 Ipfc mes0100 FLOGI failure DESCRIPTION An ELS FLOGI command that was sent to the fabric failed DATA 1 ulpStatus 2 ulpWord 4 SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0101 FLOGI completes successfully DESCRIPTION An ELS FLOGI command that was sent to the fabric succeeded DATA 1 ulpWord 4 2 e d tov 3 r a tov 4 edtovResolution SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0102 PLOGI completes to NPort nlp DID on vpi lt vpi gt DESCRIPTION The HBA performed a PLOGI into a remote NPort DATA 1 ulpStatus 2 ulpWord 4 3 disc 4 num disc nodes SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0103 PRLI completes to NPort nlp DID DESCRIPTION The HBA performed a PRLI into a remote NPort DATA 1 ulpStatus 2 ulpWord 4 3 num disc nodes SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0104 ADISC completes to NPort nlp DID DESCRIPTION The HBA performed an ADISC into a remote NPort DATA 1 ulpStatus 2 ulpWord 4 3 disc 4 num disc nodes SEVERITY Information LOG LOG ELS verbose Emulex Drivers for VMware ESX 3 5 User Manual Page 22 gt G EMULEX ACTION No action needed infor
87. ommon HBA API Supports NPort ID Virtualization NPIV Technology New Features in this Release This ESX 3 5 release includes the following enhancements Supports OneConnect universal converged network adapters UCNAs for FC FCoE and NIC including the OneConnect 10100 Supports the OneCommand Manager application and the OneCommand Manager application CLI The VMware Tools link on the VMware portion of the Emulex Web site Visit the link to see the available tools Support for the ANSI INCITS t11 standard for NPIV deployment in ESX starting with release 3 5 For LP11 and LPe11 series adapters the version 2 72a2 firmware increases the number of vports from 8 to 16 Supports NPIV for CNAs Emulex Drivers for VMware ESX 3 5 User Manual Page 1 Prerequisites gt G EMULEX The following table lists the support relationship between VMware ESX releases and Emulex drivers Refer to VMware s vi3 io guide pdf for more detailed information Table 1 Emulex Driver Support in ESX Releases VMware ESX Release Emulex Driver Version ESX 2 5 4 Ipfc 7 3 2 vmw3 4 Gb s provided with ESX 2 5 4 Patch 4 ESX 2 5 5 Ipfc 7 3 2 vmw4 2 and 4 Gb s ESX 3 0 0 Ipfc 7 1 14 vmw1 2 Gb s Ipfc 7 3 2 vmw1 4 Gb s ESX 3 0 1 Ipfc 7 3 2 vmw2 2 and 4 Gb s ESX 3 0 2 Ipfc 7 3 2 vmw4 2 and 4 Gb s ESX 3 5 0 Ipfc_7 4 0 13 2 and 4 Gb s ESX 3 5 Update 1 Ipfc_7 4 0 13 1 2 and 4 Gb s ESX 3 5 Updat
88. on type of support needed Ipfc iocb wdog tmo 40 0 55 No Timeout value for pending FC I O in the driver Ipfc linkdown tmo 30 0 255 Yes seconds How long the driver waits before deciding that the FC link is down Ipfc link speed 0 O auto select No Sets link speed 121 Gb s Note This parameter is 2 2 Gb s only applicable to 4 4 Gb s SLI 3 based 8 8 Gb s adapters Ipfc log verbose 0x0 0x0 bit mask Extra activity logging Ipfc lun queue depth 30 1 128 Yes Default max commands sent to a single logical unit disk Ipfc lun skip 0 0 Off 1 On No Allows SCSI layers to detect all LUNs if there are LUN holes on a device Ipfc max lun 256 1 256 Yes Specifies the maximum number of LUNs per target A value of 20 means LUNs from 0 to 19 are valid Ipfc max target 256 1 256 No This configuration parameter limits how many targets the driver will support Ipfc max vpi Oxffff 0 Oxffff No NPIV Maximum number of vpis available per physical port lpfc nodev holdio 0 0 Off 1 On Yes If the device disappears hold I O until it comes back Ipfc no device delay 1 0 30 Yes Delay to fail back an I O in seconds Ipfc nodev tmo 30 0 255 Yes Seconds to hold I O err if device disappears Emulex Drivers for VMware ESX 3 5 User Manual Page 13 Table 2 LPFC Driver Configuration Parameters Continued gt G EMULEX Variable Default Min Max Dynamic Comments Ipfc ns t
89. ort these errors to Technical Support Ipfc mes4535 Invalid link fault code DESCRIPTION Invalid link fault code DATA 1 Link fault code SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4536 vmk fc attach transport failed DESCRIPTION Failed to attach adapter instance to transport DATA None SEVERITY Error LOG Always Emulex Drivers for VMware ESX 3 5 User Manual Page 80 gt G EMULEX ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4537 Invalid link attention type DESCRIPTION Invalid link attention type DATA 1 Link attention type SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4538 Invalid link attention link speed DESCRIPTION Invalid link attention link speed DATA 1 Link speed SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4539 SLI4 DCBX asynchronous event is not handled yet DESCRIPTION The SLI 4 DCBX asynchronous event is not handled yet DATA 1 Event tag SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4540 Read FCF record failed DESCRIPTION Read FCF record failed DATA 1 Return value from mailbox cmd SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes4541 Invalid asynchronous event code DESCRIPTION Invalid asynchronous event code DATA 1
90. quired Ipfc mes4529 No event queue entry from the CQ DESCRIPTION No event queue entry from the CQ DATA 1 Completion Queue Id 2 Completion Queue Type SEVERITY Information LOG LOG INIT verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual gt G EMULEX Page 79 EMULEX Ipfc mes4530 Invalid WCQE code DESCRIPTION Invalid WCQE code DATA 1 Invalid Work Queue Completion code SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4531 Fast path completion queue does not exist DESCRIPTION Fast path completion queue does not exist DATA None SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4532 No entry from fast path completion queue DESCRIPTION No entry from fast path completion queue DATA 1 Completion queue id SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4533 FCoE Function not supported by firmware DESCRIPTION Firmware does not support FCoE DATA 1 Function mode SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4534 Init link mailbox command failed DESCRIPTION Failed to initialize the FCoE link DATA 1 mbx status SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist rep
91. r failed to issue ASYNCEVT ENABLE mbox DESCRIPTION The HBA port failed to enable asynchronous mailbox events DATA 1 mailbox response status SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0457 Adapter Hardware Error DESCRIPTION The driver received an interrupt indicating a possible hardware problem Data 1 status 2 status1 3 status2 SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If the problem persists report the error to Technical Support lpfc mes0458 Bring adapter online DESCRIPTION The FC driver has received a request to bring the adapter online This may occur when running Iputil DATA None SEVERITY Warning LOG LOG INIT verbose ACTION None required Ipfc mes0459 HBA heartbeat failure DESCRIPTION The HBA has not responded to a heartbeat command in the time allotted DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 54 EMULEX Ipfc mes0460 Bring adapter offline DESCRIPTION The FC driver has received a request to bring the adapter offline This may occur when running Iputil DATA None SEVERITY Warning LOG LOG INIT verbose ACTI
92. r reloads To verify the setting type esxcfg module g lpfc 740 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 lpfcl1 lun queue depth 20 lpfc2 lun queue depth 10 driver name gt Note Type the command all on one line without a carriage return Emulex Drivers for VMware ESX 3 5 User Manual Page 7 EMULEX 2 Rebuild the ESX bootstrap settings Type esxcfg boot b 3 Reboot the server Type reboot The new settings are used when the driver reloads To verify the settings type esxcfg module g lpfc 740 Dynamically Add LUNs and Targets For instructions on dynamically adding LUNs and targets refer to the Using Rescan section in VMware s vi3 esx san cfg pdf Creating a Fibre Channel Remote Boot Disk For instructions on creating a Fibre Channel remote boot disk refer to VMware s vi3 esx san cfg pdf Chapter 6 Using Boot from SAN with ESX Server Systems Virtualization Features For instructions on how to install the VMware Tools in guest operating systems refer to the Support section of the VMware Web site Configuring Multiple NIC Interfaces with OneConnect UCNAs Enabling the NetQueue Feature To use the multiple interface feature in ESX Server 3 5 you must enable the NetQueue feature in ESX Server which is disabled by default e che
93. re ESX 3 5 servers Use out of band management TCP IP based management to remotely manage adapters on ESX 3 5 servers For the VMware ESX 3 5 Server the firewall on the ESX Server must be opened to manage systems remotely using TCP IP based management For instructions see Opening the ESX Server Firewall on page 3 LPFC Driver Configuration Methods Using Native ESX Tools There are two methods for configuring the Fibre Channel LPFC driver parameters using the native ESX tools Permanent global configuration Permanent per adapter configuration Note In addition to the permanent methods the OneCommand Manager application also supports temporary methods both global and per adapter for configuring driver parameters Emulex recommends using the OneCommand Manager application to set the configuration parameters Refer to the OneCommand Manager Application User Manual for more information Note Any settings configured using the native ESX tools will not take effect until the server is rebooted However any changes to dynamic parameters made using the OneCommand Manager application CLI immediately take effect See Emulex LPFC Driver Configuration Parameters on page 11 for more information on driver parameters Permanent Configuration Methods Permanent configuration requires that the new values be saved in the ESX environment These changes are considered permanent because they persist across system reboots Emul
94. received a packet larger than 8192 multiple frags Dropping bytes in multiple fragments Since VMware the pkt Len d frag does not support such fragments in skb this size 8192 packet is ignored Since the OneConnect interfaces do not accept MTUs larger than 8178 packets larger than 8192 are not expected Warning Invalid value of bps An ioctl to set the QoS parameter bits Must be 0 to 100 seconds encoding value outside of 0 to 100 was attempted The request is ignored and the QoS setting is not changed Warning pci enable msix The call to enable MSI X for the OneConnect UCNA NIC driver interface failed In ESX Server 3 5 update 1 and later versions MSI X is not enabled if NetQueues are not enabled Try enabling NetQueues Even if MSI X is not enabled the driver can continue to work using INT X interrupts Emulex Drivers for VMware ESX 3 5 User Manual Page 17 Table 5 ESX Server NIC Event Log Entries Continued gt G EMULEX Severity Message Displayed Description Error Failed to map PCI BARS Call to map PCI BAR registers of the OneConnect UCNA failed This is a rare failure that may occur due to system resource limitations Warning Invalid EQ ResourceID The OneConnect UCNA reported an event lt DDD gt with an invalid resource ID This error should not happen normally Warning Wrong PD ID lt DD gt An ioctl to configure QoS was issued with a wrong PD ID va
95. received from NPort did DESCRIPTION Received an unsupported ELS command from a remote NPort DATA None SEVERITY Error LOG Always ACTION Check remote NPort for potential problem Ipfc mes0116 Xmit ELS command lt elsCmd gt SID sid DID did on vpi lt vpi gt DESCRIPTION Xmit ELS command to remote NPort DATA 1 binfo gt fc_ffstate 2 ulpContext SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Ipfc mes0117 Xmit ELS response lt elsCmd gt SID sid DID did on vpi lt vpi gt DESCRIPTION Xmit ELS response to remote NPort DATA 1 size 2 ulpContext SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 24 EMULEX Ipfc mes0118 Xmit CT response on exchange lt xid gt DESCRIPTION Xmit a CT response on the appropriate exchange DATA 1 ulploTag 2 state 3 SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0119 Issue GEN REQ IOCB for NPort lt did gt DESCRIPTION Issue a GEN REQ IOCB for remote NPort These are typically used for CT requests DATA 1 ulploTag 2 fc ffstate 3 vpi SEVERITY Information LOG LOG ELS verbose ACTION No action needed informational Ipfc mes0120 PLOGI chkparm OK DESCRIPTION Received a PLOGI from a remote NPort and its Fibre Channel service para
96. rface configuration Ipfc mes0281 Failed to allocate mbox for UNREG_VFI cmd DESCRIPTION Failed to allocate memory for issuing UNREG VFI mailbox command DATA 1 HBA state SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0282 Failed to issue UNREG VFI mailbox command DESCRIPTION Failed to issue UNREG VFI mailbox command to the HBA DATA 1 rc 2 HBA state SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0283 Failed to allocate mbox for UNREG FCFI cmd DESCRIPTION Failed to allocate memory for issuing UNREG FCFI mailbox command DATA 1 HBA state SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 38 EMULEX Ipfc mes0284 Failed to issue UNREG FCFI mailbox command DESCRIPTION Failed to issue UNREG FCFI mailbox command to the HBA DATA 1 rc 2 HBA state SEVERITY Error LOG Always ACTION Driver failure reboot the system if necessary If this condition persists contact Emulex Technical Support Ipfc mes0285 UNREG FCFI failed to read FCF record DESCRIPTION UNREG FCFI failed to read FCF record from HBA DATA HBA state
97. rrors to Technical Support Ipfc mes4501 READ CONFIG failed DESCRIPTION The READ CONFIG mailbox command failed DATA 1 mbxCmd 2 mbxStatus SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4502 Config Params XRI B val M lt val gt VPI B lt val gt M lt val gt VFI B lt val gt M lt val gt RPI B lt val gt M lt val gt FCFI B lt val gt M lt val gt DESCRIPTION Configuration parameters reported by adapter Each parameter listed has a B base value and a M max value DATA SEVERITY Information Emulex Drivers for VMware ESX 3 5 User Manual Page 75 EMULEX LOG LOG INIT verbose ACTION None required Ipfc mes4503 IOCB Rsp Err ring no tag no DESCRIPTION IOCB error response DATA iocb 0 iocb 15 SEVERITY Information LOG LOG_SLI verbose ACTION None required Ipfc mes4504 lt string gt mbox failed DESCRIPTION Failed mailbox command occurred in the function lt string gt DATA 1 shdr_status 2 shdr add status 3 rc SEVERITY Error LOG Always ACTION This error may indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes4505 Failed to allocate XRI DESCRIPTION Unable to allocate an XRI DATA 1 next xri 2 max xri 3 xri used SEVERITY Error LOG Always ACTION This
98. rt create failed because the vport could not be allocated DATA 1 vport instance SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Ipfc mes1807 VPort FDISC did not complete in time allotted DESCRIPTION The VPort s FDISC did not complete in the timeout period DATA None SEVERITY Warning LOG LOG VPORT verbose ACTION This could be a fabric issue with a large vport count If problems persist contact Emulex Technical Support Ipfc mes1808 Successfully created VPort vpi lt vpi gt DID vport DID Type port type State port state DESCRIPTION Successfully created vport display vital data DATA 1 vpi 2 vport DID 3 port type 4 port state SEVERITY Information LOG LOG VPORT verbose ACTION None required Ipfc mes1809 Unallowed delete of physical vport from vport delete DESCRIPTION The physical vport belongs to the physical host DATA 1 vport DID 2 port type 3 port state SEVERITY Error LOG Always ACTION None required Ipfc mes1810 Vport getinfo on vpi vpi DID DID DESCRIPTION The vport is returning vport data elements to the caller DATA 1 fail reason 2 prev fail reason 3 vports max 4 inuse 5 linktype 6 port state SEVERITY Information Emulex Drivers for VMware ESX 3 5 User Manual Page 73 EMULEX LOG LOG VPORT verbose ACTION None required Ipfc mes1811 VPort delete requested on DID DID vpi lt vpi gt
99. s ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0484 READ REV Error SLI Level d DESCRIPTION The SLI Level should be SLI 4 and FCoE should be supported DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 58 EMULEX Ipfc mes0485 Adapter firmware version s fcphHi x fcphLo x lt gt flLo lt x gt DESCRIPTION Adapter firmware version is logged DATA None SEVERITY Information LOG LOG INIT verbose ACTION No action needed informational Ipfc mes0486 No support for fcpi mode DESCRIPTION The port must support FCP initiator mode DATA None SEVERITY Error LOG Always ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc mes0487 Feature Mismatch DESCRIPTION The port cannot support the host s requested features DATA 1 REQUEST FEATURES Word 2 2 REQUEST FEATURES Word 3 3 max vpi SEVERITY Information LOG LOG INIT verbose ACTION No action needed informational Ipfc mes0488 READ SPARAM command failed DESCRIPTION The port must support FCP initiator mode DATA 1 Issue status 2 mbxStatus SEVERITY Error LOG Always ACTION
100. s1801 Failed to create Incorrect SLI revision DESCRIPTION The FW must report 511 3 capable for creation DATA 1 sli rev SEVERITY Warning LOG LOG VPORT verbose ACTION Check FW revision and contact Emulex Technical Support Ipfc mes1802 VMKernel issued unknown VPORT command rejecting DESCRIPTION The VMKernel issued an unknown vport command error command DATA 1 vport cmd SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Ipfc mes1803 VPort unreg login to all rpis failed trying single unreg DESCRIPTION The vport s unreg login to all rpis failed defaulting to sequential unreg login per rpi DATA 1 vport DID SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 72 EMULEX Ipfc mes1804 VPort unreg vpi failed DESCRIPTION The VPort s unreg login didn t complete treating as a failure and defaulting to sequential unreg login per rpi DATA 1 vport DID SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Ipfc mes1805 Failed to create scsi host for VPort instance d DESCRIPTION The VPort create failed because the scsi register failed to create a SCSI host DATA 1 vport instance SEVERITY Error LOG Always ACTION Contact Emulex Technical Support Ipfc mes1806 Failed to allocate VPort memory resources instance d DESCRIPTION The VPo
101. sage Log Table LOG Message Preamble men Verbose Mask String From To Bree Verbose Description bo it Definition LOG ELS ELx 0100 0199 0 1 ELS events LOG DISCOVERY DIx 0200 0299 0x2 Link discovery events LOG MBOX MBx 0300 0399 0 4 Mailbox SLI events LOG SLI LOG INIT INx 0400 0499 0x8 Initialization events Future 0500 0599 LOG IP 0600 0699 IP Log events LOG FCP FPx 0700 0799 0x40 FCP traffic history Future 0800 0899 LOG NODE NDx 0900 0999 0x80 Node table events Reserved 1000 1099 0x100 Reserved TMx 1100 1199 0x200 LOG MISC MIx 1200 1299 0x400 Miscellaneous events LOG_LINK_EVENT LKx 1300 1399 0x10 Link and FCoE events FCoE Future 1400 1499 LOG_LIBDFC 1600 1699 0 2000 IOCTL events LOG VPORT VPx 1800 1899 0x4000 Vport events LOG INIT 4500 4599 Initialization events LOG ALL MSG Log all messages Emulex Drivers for VMware ESX 3 5 User Manual Page 21 EMULEX Message Log Example The following is an example of a LOG message Jul 12 16 30 26 node kernel 1pfc0 0234 DIi Device Discovery completes In the above LOG message pfcO identifies the LOG message as coming from EMULEX adapter e 0234 identifies the LOG message number Dli identifies the LOG message as a DISCOVERY DI INFORMATION i message Note If the word Data is present in a LOG message any information to the right
102. se Emulex may make improvements and changes to the product described in this manual at any time and without any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this manual Emulex disclaims any undertaking to give notice of such changes Emulex 3333 Susan Street Costa Mesa CA 92626 Copyright 2003 2009 ServerEngines Corporation TRADEMARKS ServerEngines the ServerEngines logo and BladeEngine 2 are trademarks or registered trademarks of ServerEngines Corporation Microsoft Windows Windows XP Windows 2003 and Windows 2008 are U S registered trademarks of Microsoft Corporation Emulex Drivers for VMware ESX 3 5 User Manual Page ii Table of Contents 74 EMULEX TEE D I T 1 Driver Information 1 Supported Features ssssssssssssssssssseeeene eene n nennen nnne 1 New Features in this 1 SO 2 COImpatibilily der op 2 155065 2 installing 3 Opening the ESX Server Firewall eese 3 Uninstalling the Drivers 4 Installing the OneCommand Manager Application
103. spMax gt DESCRIPTION The port rsp ring put index is larger than the size of the rsp ring DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support lpfc mes0313 Ring ringno handler unexpected Rctl lt Rctl gt Type Type received DESCRIPTION The Rctl Type of a received frame did not match any for the configured masks for the specified ring DATA 1 ring number 2 rctl 3 type SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support Ipfc mes0314 Ring lt ringno gt issue portCmdGet lt portCmdGet gt is bigger then cmd ring lt portCmdMax gt DESCRIPTION The port cmd ring get index is greater than the size of cmd ring DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support Ipfc mes0315 Ring lt ringno gt issue portCmdGet lt portCmdGet gt is bigger then cmd ring lt gt DESCRIPTION The port ring get index is greater than the size of cmd ring DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support Ipfc mes0316 ring ringno put iotag lt io
104. st operating systems For instructions on how to install the VMware Tools in guest operating systems refer to the Support section of the VMware Web site Configuring the Virtual Switch to Use Jumbo Frames To use jumbo frames you must increase the Maximum Transmission Unit MTU in the vSwitch and the guest operating system For the best performance and resource utilization set the MTU in the virtual switch and guest operating system to the maximum 8179 bytes supported by the OneConnect driver Setting the MTU Size In a vSwitch To change the MTU to 8179 in the COS run the following command for each switch in the console operating system esxcfg vswitch vSwitch N m 8179 where N is the number of the switch In a Linux Guest Operating System To set the MTU of the OneConnect driver interface in each Linux guest operating system to 8179 run the following command ifconfig eth N mtu 8179 where N is the number of the Ethernet interface on which you are working In a Windows Guest Operating System To set the MTU in each Windows guest operating system From the Start menu select Control Panel System Select the Hardware tab and open Device Manager Expand the Network Adapters heading Right click the NIC and select Properties Select the Advanced tab and set the MTU value op um Pinning VM and Interrupts to CPUs The OneConnect NIC interface driver supports MSI X interrupts The driver requests separ
105. sts report these errors to Technical Support Ipfc mes0201 Abort outstanding I O on NPort nlp DID DESCRIPTION All outstanding I Os are cleaned up on the specified remote NPort DATA 1 nlp flag 2 nlp state 3 nlp rpi SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0202 Start Discovery on vpi vpi hba state hba state DESCRIPTION Device discovery rediscovery after FLOGI FAN or RSCN has started DATA 1 tmo 2 plogi cnt 3 fc adisc cnt 4 fc rscn id cnt Emulex Drivers for VMware ESX 3 5 User Manual Page 27 gt G EMULEX SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational lpfc_mes0204 Create SCSI Target lt tgt gt DESCRIPTION A mapped FCP target was discovered and the driver has allocated resources for it DATA None SEVERITY Information LOG LOG_DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0205 Create SCSI LUN lun on Target lt tgt gt DESCRIPTION A LUN on a mapped FCP target was discovered and the driver has allocated resources for it DATA None SEVERITY Information LOG LOG DISCOVERY LOG FCP verbose ACTION No action needed informational Ipfc mes0206 Report Lun completes on NPort nlp DID DESCRIPTION The driver issued a REPORT LUN SCSI command to a FCP target and it completed DATA 1 ulpStatus 2 rspStatus2 3 rspStatus3 4 nlp failM
106. t Ipfc mes0332 REG VPI failed DESCRIPTION reg rpi mailbox failed DATA 1 status SEVERITY Error LOG Always ACTION Delete VPorts or increase Ipfc max vpi Ipfc mes0333 UNREG VPI failed DESCRIPTION Unreg vpi mailbox failed DATA 1 status SEVERITY Error LOG Always ACTION This error could indicate a driver or firmware problem If problems persist report these error to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 45 EMULEX Ipfc mes0339 Port temp ld Celsius critical Corrective action required DESCRIPTION The HBA port is at a critical temperature and must be cooled down DATA 1 temperature SEVERITY Error LOG Always ACTION This error could indicate a hardware or system problem Stop all traffic and check system fans If problems persist report these errors to Technical Support Ipfc mes0340 Port temp ld Celsius has returned to normal DESCRIPTION The HBA port temperature has decreased to a normal value DATA 1 temperature SEVERITY Information LOG LOG TEMP verbose ACTION No action needed Informational Ipfc mes0341 Restart HBA DESCRIPTION The has been restarted DATA 1 state 2 sli flag SEVERITY Information LOG LOG SLI verbose ACTION No action needed Ipfc mes0342 Restart HBA DESCRIPTION The HBA has been killed DATA 1 HBA state 2 sli flag SEVERITY Information LOG LOG_SLI verbose ACTION No action n
107. t plane query DATA None SEVERITY Error LOG Always ACTION This is not part of the driver basic discovery process and only affects the management stack query to obtain FCF entries No action needed Ipfc mes0277 Failed to get the non embedded SGE virtual address DESCRIPTION Failed to get the SGE virtual address for the non embedded mailbox command for management plane query DATA None SEVERITY Error LOG Always Emulex Drivers for VMware ESX 3 5 User Manual Page 37 gt G EMULEX ACTION This is not part of the driver basic discovery process and only affects the management stack query to obtain FCF entries No action needed Ipfc mes0278 READ FCF RECORD mailbox failed DESCRIPTION Issue READ FCF RECORD mailbox returned status failure for management plane query DATA 1 status 2 add status SEVERITY Error LOG Always ACTION This is not part of the driver basic discovery process and only affects the management stack query to obtain FCF entries No action needed Ipfc mes0279 UNREG_VFI mbxStatus error DESCRIPTION Unregister VFI mailbox command returned with failure status DATA 1 mbxStatus 2 HBA state SEVERITY Error LOG Always ACTION Check fabric and interface configuration Ipfc mes0280 UNREG FCFI mbxStatus error DESCRIPTION Unregister mailbox command returned with failure status DATA 1 mbxStatus 2 HBA state SEVERITY Error LOG Always ACTION Check fabric and inte
108. tag gt greater then configured max fast iotag wd0 icmd DESCRIPTION The assigned I O iotag is greater than the allowed maximum DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support Emulex Drivers for VMware ESX 3 5 User Manual Page 42 gt G EMULEX Ipfc mes0317 Rsp ring lt ringno gt get iotag lt iotag gt greater then configured max lt fast_iotag gt wd0 lt irsp gt DESCRIPTION The assigned I O iotag is greater than the maximum allowed DATA None SEVERITY Error LOG Always ACTION This error could indicate a software driver firmware or hardware problem Report these errors to Technical Support lpfc_mes0318 Outstanding I O count for ring lt ringno gt is at max lt fast_iotag gt DESCRIPTION An I O tag cannot be assigned because none are available The maximum number of allowed I Os are currently outstanding DATA None SEVERITY Error LOG Always ACTION This message indicates the adapter HBA I O queue is full Typically this happens when heavy I O is running on a low end 3 digit adapter Emulex suggests you upgrade to a higher end adapter lpfc_mes0319 The driver issued a READ SPARAM mbox command to the HBA that failed DESCRIPTION The driver issued a READ SPARAM mbox command to the HBA that failed DATA None SEVERITY Error LOG Always ACTION This error could indicate a
109. tional Ipfc mes0402 Max DMA Length mailbox command failed DESCRIPTION The driver could not set the limit the max DMA length DATA 1 mbxCommand 2 mbxStatus SEVERITY Information LOG LOG_INIT verbose ACTION Check the FW revision and contact Technical Support Ipfc mes0403 Max DMA Length mailbox command successful DESCRIPTION The driver successfully set the max DMA length DATA 1 mbxCommand 2 mbxStatus SEVERITY Information LOG LOG_INIT verbose ACTION No action needed informational Ipfc mes0404 HBA setup complete SLI rev sli rev DESCRIPTION The driver finished configuring the HBA Final setup values are written to the console DATA 1 max vpi 2 sli 3 options SEVERITY Information LOG LOG INIT verbose ACTION No action needed informational Ipfc mes0405 Service Level Interface SLI selected DESCRIPTION A CONFIG PORT SLI mailbox command was issued DATA None SEVERITY Information LOG LOG INIT verbose ACTION No action needed informational Emulex Drivers for VMware ESX 3 5 User Manual Page 48 EMULEX Ipfc mes0406 HBA Heartbeat disabled DESCRIPTION The driver will issue heartbeat messages to the HBA DATA None SEVERITY Information LOG LOG INIT non maskable ACTION No action needed informational Ipfc mes0407 reset disabled DESCRIPTION On error the driver will not reset the HBA DATA None SEVERITY Information LOG LOG INIT no
110. tus changed and the change was triggered by a change change in the link status of the one of the two ports of the OneConnect UCNA This could be due to a cable being connected or disconnected on one of the ports or one of the ports failing The current link status follows this message Information Link status update There was a change in the link status There is no change in the active port This could be due to a cable being connected or disconnected on one of the ports or one of the ports failing The current link status follows this message Information Link Properties for An informational message that both ports of vmnic D Both ports are the OneConnectare down down Emulex Drivers for VMware ESX 3 5 User Manual Page 19 gt G EMULEX LPFC Log Messages Introduction Log messages are organized into logical groups based on code functionality within the Fibre Channel driver Each group consists of a block of 100 log message numbers Most groups require a single block of 100 message numbers however some groups INIT FCP require two blocks The groups and the associated number ranges are defined in the Message Log table below The preamble string shown in the Message Log table is displayed as part of the log message The lower case x of the preamble string defines the severity of the log message The x will be replaced by one of five lower case letters Those letters are defined in the Severity Code table Severit
111. y Codes Information and warning messages can be turned ON or OFF by setting resetting the appropriate mask bit s in the variable Ipfc log verbose located in the driver configuration module Ipfc conf c By default both information and warning messages are disabled Configuration error c error e and panic p messages can not be disabled Table 6 Severity Code Table Code Severity i Information w Warning c Configuration Error e Error p Panic ETRACE Logging Mechanism The U4 Async LPFC driver includes a new logging mechanism called ETRACE The ETRACE mechanisms are embedded in the code to capture information during any unexpected failures or events The ETRACE mechanism displays information in the following format func name hba boardno ETRACE no Line where func name the function name hba boardno the HBA model number no Line the line number in the code where this ETRACE occurs Emulex may use ETRACES to troubleshoot customer issues Emulex Drivers for VMware ESX 3 5 User Manual Page 20 Message Group Masks gt G EMULEX Table 7 defines the log message groups and the associated number ranges The preamble string shown in this table is displayed as part of the log message The lower case x of the preamble string defines the severity of the log message and represents one of five lower case letters defined in the severity codes table Table 7 Mes
112. y nodes an HBA can see Ipfc mes0247 Start Discovery Timer state hba state DESCRIPTION Start the device discovery RSCN rescue timer DATA 1 tmo 2 disctmo 3 fc plogi cnt 4 fc adisc cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0248 Cancel Discovery Timer state hba state DESCRIPTION Cancel the device discovery RSCN rescue timer DATA 1 fc flag 2 rc 3 fc plogi cnt 4 fc adisc cnt SEVERITY Information LOG LOG DISCOVERY verbose ACTION No action needed informational Ipfc mes0249 Unsupported Addressing Mode lt i gt on NPort nlp DID Tgt sid DESCRIPTION The driver issued a REPORT LUN SCSI command to a FCP target DATA None SEVERITY Warning LOG LOG DISCOVERY LOG FCP verbose ACTION Check configuration of target Driver will default to peripheral addressing mode Ipfc mes0250 EXPIRED nodev timer DESCRIPTION A device disappeared for greater than the configuration parameter Ipfc nodev tmo seconds All I O associated with this device will fail DATA 1 did 2 scsi id 3 SEVERITY Error LOG Always ACTION Check physical connections to Fibre Channel network and the state of the remote PortID Ipfc mes0251 Unrecognized event type while flushing task list DESCRIPTION The driver found an unsupported event type when flushing the event list DATA 1 evt 2 arg1 3 arg2 SEVERITY Error Emulex Dr
113. ype rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Emulex Drivers for VMware ESX 3 5 User Manual Page 66 EMULEX lpfc mes0929 FIND node DID unmapped DESCRIPTION The driver is searching for a node table entry on the unmapped node list based on the DID DATA 1 nlp 2 DID 3 flag 4 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required lpfc mes0930 FIND node DID mapped DESCRIPTION The driver is searching for a node table entry on the mapped node list based on the DID DATA 1 nlp 2 nlp DID 3 flag 4 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0931 FIND node DID bind DESCRIPTION The driver is searching for a node table entry on the binding list based on the DID DATA 1 nlp 2 nlp DID 3 flag 4 state xri type rpi SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0932 FIND node did did NOT FOUND on vpi lt vpi gt DESCRIPTION The driver searched for a node table entry based on the DID and did not find the entry DATA 1 order SEVERITY Information LOG LOG NODE verbose ACTION None required Ipfc mes0933 func ALLOC node did did on vpi lt vpi gt DESCRIPTION The driver allocated a node table entry based on the DID and did not find the entry DATA 1 func 2 did 3 vpi SEVERITY Information L
114. ys ACTION Firmware update may be required Ipfc mes1313 Invalid FRU data found on adapter DESCRIPTION Return adapter to Emulex for repair DATA None SEVERITY Error LOG Always ACTION Return adapter to Emulex for repair Ipfc mes1314 Adapter Link is disabled DESCRIPTION The software has disabled the adapter link DATA None SEVERITY Error LOG Always ACTION Use the management software to re enable the link Emulex Drivers for VMware ESX 3 5 User Manual Page 71 EMULEX Ipfc mes1315 Adapter failed DOWN LINK DESCRIPTION The adapter was unable to disable the link DATA mailbox status SEVERITY Error LOG Always ACTION May indicate a hardware or firmware problem If this problem persists report these errors to Technical Support LIBDFC Events 1600 1699 Ipfc mes1600 ioctl entry DESCRIPTION Use to trace IOCTLs from LIBDFC Logged on completion DATA 1 cmd code 2 return code 3 return count SEVERITY Information LOG LOG LIBDFC verbose ACTION None required VPort Events 1800 1899 Ipfc mes1800 Failed to create Insufficient DESCRIPTION There are no VPIs available to create a vport Either the physical port does not support VPIs or all available VPls are in use DATA 1 vpi 2 max vpi 3 avail vpi SEVERITY Error LOG Always ACTION Delete unused unneeded vports If problems persist report error to Emulex Technical Support Ipfc me
115. ystem when necessary Ipfc mes4550 Reset HBA DESCRIPTION The driver invoked an HBA reset DATA 1 port_state 2 sli_flag SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4551 Performing PCI function reset DESCRIPTION The driver invoked a PCI function reset DATA None SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4552 Restart HBA DESCRIPTION The driver invoked an HBA restart DATA 1 port state 2 sli flag SEVERITY Information LOG LOG INIT verbose ACTION None required Ipfc mes4553 Failed to allocate connection table entry DESCRIPTION Failed to allocate connection table entry DATA None SEVERITY Error LOG Always ACTION It may not be a critical problem if the driver failed to allocate memory for some of the FCF connection table entries for the driver discover process However failure of the driver to allocate kernel memory may indicate a serious problem Reboot the system if necessary Ipfc mes4554 Config region 23 has bad signature DESCRIPTION Config region 23 has bad signature DATA None SEVERITY Error LOG Always ACTION It may not be a critical problem for the driver and HBA s normal operation if configure region contains a bad signature However it may result in some of the management stack functionality not working properly to manage the HBA Try to re configure the device configure region 23 if necessary If proble

Emulex Drivers for VMware ESX 3.5

Contents

Download Pdf Manuals

Related Search

Related Contents