Home

windows manual elx

1. ccccceccseeeeee sense sense eennenenneneas 20 Installing the Emulex PLUS ElxPlus Driver for the First Time ccce 21 Updating the Emulex PLUS EIXPIUS DriVer cccccceeeceee reece eect ee eee ee ee ee ene ees 21 Installing or Updating the FC FCoE Storport Miniport Driver cccceceeeeeeeee eens 22 Installing or Updating the iSCSI Driver ccccccccecccee eee e sees eeeaeeeeneeeeaeenenae reas 23 Installing or Updating the NIC Driver ccccccccee cece eee eeeeeeeeeeeeeneeeeneeeenanenes 24 Windows Server 2008 cece cece cece cece eee EEEE EEE EEEE eee EEEE EEEE EEEE 24 Windows Server 2012 wiisc ces erini oiior rintt aE rE E cade EE EErEE EEO 25 Removing Emulex Driver Kits and DriverS ssssussssnsnnnsnssnunnnnnnnnnnnnnnnnnnnnnnnnn 26 Uninstalling Emulex Driver KItS ssssssssssrrrrrerrersrrrrrrrrrrrrrsrrsrrrrrrereresrrrrr 26 Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Table of Contents gt G EMULEX Windows Server 2008 erriusririarerarsic veineuse ni Tertia na a a a 26 Windows Server 2012 aueri siier sinear n A REE EREEREER IARE RATRE ERRA 27 Uninstalling the Emulex Drivers ssssssssssrrrrrerrrrsrsrrrrrrrrresrrsrrrrrrrrrrerrrrrr 27 Windows Server 2008 nesti 0s nasiti t iseitu stia ANEA aa 27 Windows Server 202 eri rier nearr a ARARE ERARA EIR ARERR AREER 28 2 Configuration ssssssssuunnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnna OO FC FCOE
2. Giens ALIO 11 05 04 DEON Neon 10025 YA SERVEREM j gt Dimens irizon 11 05 04 everitiog teon 0S WA SERVEREN x T aaa Figure A 2 iSCSI Error Because the UCNAs are dual PCI function adapters the Device RaidPort lt n gt value changes depending on the device that observed the error iSCSI Error Log on Windows Server 2008 The following is a brief description of the error log codes generated by the iSCSI driver for Windows Server 2008 It includes the error code the message displayed and the meaning of the message and the recommended resolution Table A 13 iSCSI Error Log Entries on Windows Server 2008 Message ID Message Description Recommended Resolution 0x348d0008 The iSCSI driver failed a WMI IOCTL This failure indicates that an operation request from the port driver because attempted from the Microsoft WMI application the request was failed by the ARM resulted in an error Check the operation being firmware This error is immediately attempted for user or configuration errors followed by another error code entry indicating the WMI request code in error Emulex Drivers for Windows User Manual P008011 01A Rev A 116 gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 117 Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x348d0007 The iSCSI
3. Network Address Valid MAC Address The default setting is None Emulex Drivers for Windows User Manual Windows 2008 Window 2008 R2 Windows 2012 This overrides the permanent MAC address for the interface The MAC address should follow this format XX XX XX XX XX XX where X is a hex digit 0 9 or A F e The address cannot be a multicast address which has the lowest bit in the first byte set The address cannot be all zeros For example 01 00 00 00 00 00 is not valid while 02 00 00 00 00 00 is valid P008011 01A Rev A gt G EMULEX 2 Configuration 44 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Packet Size Acceptable Values 1514 default 9014 4088 8222 Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012 Definition Configuration packet size for OneConnect NIC only Limit normal sized frames and one value for jumbo packet This parameter determines the maximum packet size transmitted and received on the interface A 1514 byte frame size is standard while larger packets are called jumbo frames Using a higher frame size is generally more efficient but it uses more system memory A larger frame size also requires support on the network switch RSS Receive Side Scaling Disabled Enabled default Windows 2008 Window 2008 R2 Windows 2012 Support for mu
4. Warning Encountered an error offloading an iSCSI connection error code N Emulex Drivers for Windows User Manual The iSCSI driver detected an error while offloading the iSCSI connection The operation is retried up to five times The session handle and the UCNA firmware error code are included in the event log message This may indicate a target is in error or it may point to transient network connectivity issues It may also indicate a UCNA firmware error P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information 122 iSCSI Error and Event Log Table A 14 iSCSI Error Log Entries on Windows Server 2008 R2 and 2012 Continued Message ID Severity Message Recommended Resolution 0x11 Warning The IOCTL opcode A requires The iSCSI driver failed an IOCTL request more scatter gather elements because the number of scatter gather elements than allowed Transfer length required for the IOCTL buffer exceeded the is B UCNA firmware limit The IOCTL opcode and the payload length requested are included in the event log entry This error may indicate an incorrect configuration option for the iSCSI driver It may also indicate a low memory condition 0x12 Error Unrecoverable error detected An unrecoverable error was detected by the UE Low A UE High B FW Line iSCSI driver C This may be caused by hardware errors or by unhandled exceptions in the hardware or firmware
5. occfg a emulex x Displaying All Parameters To display the current value of all parameters use either p or q command line options This shows the registry value or driver value of the parameter or both when using pq together For example occfg a emulex p Emulex OneConnect OCe11102 I NIC TOE 2 Local Area Connection 2 Display all properties Registry Class of Service 802 1p 1 Auto Priority Pause Registry Flow Control 3 Tx Enable Rx Enable Registry IPv4 IP Checksum Offload 3 Tx Enable Rx Enable Registry IPv4 Large Send Offload vl 1 Enable Registry IPv4 Large Send Offload v2 1 Enable Registry IPv4 TCP Checksum Offload 3 Tx Enable Rx Enable Registry IPv4 TCP Connection Offload 0 Disable Registry IPv4 UDP Checksum Offload 3 Tx Enable Rx Enable Registry IPv6 Large Send Offload v2 1 Enable Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration gt EMULEX NIC TOE Driver Configuration Registry IPv6 TCP Checksum Offload 3 Tx Enable Rx Enable Registry IPv6 UDP Checksum Offload 3 Tx Enable Rx Enable Registry Interrupt Moderation 4 3 Adaptive Default Registry Network Address lt not set gt Registry Packet Size 9014 9014 Registry Preferred NUMA Node lt not set gt Registry RSS 1 Ena
6. Appendix C Port Speed Specifications 128 gt EMULEX Negotiating Speed on a Mezzanine Card Appendix C Port Speed Specifications A UCNA can support only one Ethernet port speed at a time and the preference is always for 10 Gb s The type of module used copper or optical does not make a difference As soon as a 10 Gb module is plugged into one of the ports the UCNA switches to a 10 Gb speed no matter what speed the other port is running or even if I O is running on that port This behavior is a per UCNA constraint another UCNA can be running on a different speed Table C 1 lists negotiated speed specifications per an adapter s port connection Table C 1 Negotiated Speed Specification per Adapter Port Connection Port 0 Port 1 Port Link Status Speed 10 Gb s 10 Gb s Both ports link up 10 Gb s 10 Gb s 1Gb s Only Port 0 links up 10 Gb s 1Gb s 10 Gb s Only Port 1 links up 10 Gb s 1Gb s 1Gb s Both ports link up 1 Gb s 1Gb s Only Port 0 links up 1 Gb s 1Gb s Only Port 1 links up 1 Gb s 10 Gb s Only Port 0 links up 10 Gb s 10 Gb s Only Port 1 links up 10 Gb s Negotiating Speed on a Mezzanine Card A mezzanine card retains the first negotiated speed This could be either 10 Gb s or 1 Gb s depending on the switch connected To change the speed on a mezzanine card 1 Remove the switch from both the ports 2 Insert the switch on one port and wait for the link to come up 3 After the link is up
7. Appendix D AutoPilot Installer Command Line and Configuration File Parameters 130 gt G EMULEX AutoPilot Installer Syntax You can specify a non default directory for the driver kit by specifying an installation folder on the command line For example lxdrv fc fcoe lt version gt exe install C Emulex This option can be used in conjunction with the APArgs directive AutoPilot Installer Syntax The syntax used to run AutoPilot Installer silently from a command line or script is APInstall silent parameter setting parameter setting The silent switch and parameter settings can occur in any order One or more spaces must separate the switch and each parameter setting The syntax of a parameter setting is parameter_name Jvalue Double quotes are required only around values that contain spaces Spaces may separate parameters equal signs and values Parameter names and values are not case sensitive The APInstall command may contain the settings listed below Each setting except ConfigFileLocation may also be specified in the AutoPilot Configuration file For descriptions of each parameter see Software Configuration Parameters on page 131 Settings specified in the APInstall command override those specified in the configuration file ConfigFileLocation path specifier NoSoftwareFirstInstalls TRUE FALSE
8. Definition Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets lt Packet Size that may be transmitted This segmentation increases transmit efficiency for TCP applications that send large buffers During segmentation the hardware computes the IPv4 and TCP checksums for each individual packet The Windows Version 1 LSO supports only IPv4 Large Send Offload LSO v2 IPv4 Disable Enable default Windows 2008 Window 2008 R2 Windows 2012 Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets lt Packet Size that may be transmitted This segmentation increases transmit efficiency for TCP applications that send large buffers During segmentation the hardware computes the IPv4 and TCP checksums for each individual packet The Windows Version2 LSO supports larger offload sizes Large Send Offload LSO v2 IPv6 Disabled Enabled default Windows 2008 Window 2008 R2 Windows 2012 Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets less than the MTU that may be transmitted This segmentation increases transmit efficiency for TCP applications that send large buffers During segmentation the hardware computes the TCP checksums for each individual packet IPv6 support requires LSO Version 2 included in Windows 2008 and later
9. Statistic SGEMULEX Device Statistics Units Transmit Throughput Receive Throughput Transmit Bytes Receive Bytes Transmit Packet Rate Receive Packet Rate Transmit Packets Receive Packets RSS Receive Packets Receive Flow Control Pause Requests TCP Offloads Currently Established TCP Offloads TCP Offload Retransmits TCP Offload Receive Drops TCP Offload Transmit Rate TCP Offload Receive Rate VMQs Allocated Interrupt Rate Transmit How Control Pause Requests packets bits sec bits sec bytes bytes packets sec packets sec packets packets packets packets connections connections packets packets bits sec bits sec queues int sec Receive Drops No Memory DMA limited i packets Recei Figure 2 3 NIC TOE Statistics Properties in Windows Server 2008 Table 2 4 NIC TOE Driver Properties Statistics Statistic Name Description Transmit Throughput The data rate for this adapter on the network including all packet headers It is expressed in terms of bits sec where 1 byte 8 bits This is computed as the average over approximately 3 seconds Receive Throughput The receive rate for this adapter Transmit Bytes The total number of bytes transmitted by this adapter since the last statistics reset or the last driver reload Receive Bytes The total number of bytes received by this adapter Transmit Packet Rate The rate of transmit packets
10. removed so you can still view installation history and the drivers that have been installed on the system You can delete the reports folder at any time if you want Uninstalling the Emulex Drivers The Emulex Storport Miniport and PLUS ElxPlus drivers are uninstalled using the Device Manager Windows Server 2008 Note On Windows 2008 after the message Warning you are about to uninstall this device from your system is displayed You must select the checkbox Delete the software for this device in order to uninstall the driver Emulex Storport Miniport Driver To uninstall the Emulex Storport Miniport driver 1 Select Start gt All Programs gt Administrative Tools gt Computer Management 2 Click Device Manager Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 28 Removing Emulex Driver Kits and Drivers 3 Double click the adapter from which you want to remove the Storport Miniport driver A device specific console window is displayed Select the Driver tab 4 Click Uninstall and then click OK to uninstall ElxPlus Driver To uninstall the ElxPlus driver uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled 1 Run the Device Manager steps 1 and 2 above 2 Click the plus sign next to the Emulex PLUS driver class 3 Right click the Emulex driver and click Uninstall 4 Click OK in the Confirm Device Removal wind
11. 0x13 Error Hardware initialization failed The iSCSI driver detected a failure in the failing driver load hardware during initialization This failure indicates that the hardware has not been initialized or is malfunctioning This may also indicate that the firmware is not running correctly 0x14 Warning Failed to retrieve scatter The iSCSI driver failed an I O request because it gather list for an SRB an IO __ failed to retrieve a scatter gather list from the has failed Storport driver This failure occurred because of a failed memory allocation in the operating system Check low memory conditions 0x15 Error ACIT library table An internal API failed in the iSCSI driver during initialization failed initialization This failure may indicate a low memory condition 0x16 Error An ACIT API failed An internal API failed in the iSCSI driver during initialization This failure may indicate a low memory condition 0x17 Error Unsupported hardware failing Driver loading failed because the PCI Vendor ID driver load and Device ID are not supported Check the UCNA configuration 0x18 Error Memory could not be This failure occurred because of a failed allocated failing driver load Emulex Drivers for Windows User Manual memory allocation in the driver This failure may indicate a low memory condition P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information 123 iSCSI Error and Event Log Table A 14 i
12. Adaptive 12k Int sec Adaptive 10k Int sec Adaptive 7k Int sec Adaptive 5k Int sec Receive 64 16384 inclusive Windows 2008 This determines the number of Ethernet receive Buffers The default value is Window 2008 R2 buffers allocated per receive queue If RSS is 896 enabled 4 or more receive queues are used Windows 2012 Otherwise a single queue is enabled Decreasing this value will reduce the required system memory but performance may decrease Each buffer is the size of the Packet Size parameter IP Checksum Disabled Windows 2008 This offloads the transmit and or receive IPv4 Offload IPv4 RX and TX Enabled default RX Enabled TX Enabled Window 2008 R2 Windows 2012 checksum computation Offloading checksums increases system efficiency IP Checksum Offload IPv6 Disabled RX and TX Enabled default RX Enabled TX Enabled Emulex Drivers for Windows User Manual Windows 2008 Window 2008 R2 Windows 2012 This offloads the transmit and or receive IPv6 checksum computation Offloading checksums increases system efficiency P008011 01A Rev A gt G EMULEX 2 Configuration 43 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Large Send Offload LSO v1 IPv4 Acceptable Values Disabled Enabled default Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012
13. Additional Sense Code Additional Sense Code Qualifier information can be found in any SCSI specification document these codes contain detailed information about the status condition of the SCSI device in question Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix A Error and Event Log Information f 110 gt lt EMULEX FC FCoE Error and Event Logs Additional Notes on Selected Error Codes These are error codes which may be seen more frequently than others or which indicate conditions that you might be able to solve by investigation and correction of problems in the SAN configuration Note The nomenclature of 0x is used as the prefix for the byte code fields because those byte codes are actually hex values Node Timeout Code 0xAA This event code indicates that a particular device has not been found if the message is logged during device discovery or that a particular device has been removed from the fabric If this message is seen determine if there is something wrong with the connection of that device to the SAN cables switches or switch ports status of the target device itself SCSI Command Error 0x9A and SCSI Check Condition code 0x9B Code 0x9A indicates that the SCSI command to a particular device was responded to with an error condition the target and LUN information along with the SCSI status are provided In the specific case of code 0x9B this code indicates that the device respo
14. Follow steps 1 3 for Running a Software Installation Interactively on page 15 2 Clear the Run AutoPilot Installer check box on the Finish dialog box 3 Choose one of the following options Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 20 Manually Installing or Updating the Emulex Protocol Drivers e Run the AutoPilot Installer from a command prompt or script with the silent option APInstall exe silent e Edit the AutoPilot Installer configuration file before running the AutoPilot Installer The configuration file is typically located in C Program Files Emulex AutoPilot Installer APInstall cfg Uncomment the line that sets SilentInstallEnable to True There are other settings in the same section of the configuration file related to unattended installations that you may also want to edit See Software Configuration Parameters on page 131 for more information After editing the file you can run the AutoPilot Installer from the Start menu a command prompt or a script Installation Failure If the installation fails the Diagnostics window opens showing that the adapter failed If the adapter fails 1 Select the adapter to view the reason for the failure The reason and suggested corrective action are displayed 2 Perform the suggested corrective action and run AutoPilot Installer again Note You can run AutoPilot Installer again from the Start menu Programs gt
15. I O Coalescing I O Coalescing is enabled and controlled by two driver parameters CoalesceMsCnt and CoalesceRspCnt The effect of I O Coalescing will depend on the CPU resources available on the server With I O Coalescing turned on interrupts are batched reducing the number of interrupts and maximizing the number of commands processed with each interrupt For heavily loaded systems this will provide better throughput With I O Coalescing turned off the default each I O processes immediately one CPU interrupt per I O For systems not heavily loaded the default will provide better throughput The following table shows recommendations based upon the number of I Os per adapter Table 2 2 Recommended Settings for I O Coalescing I Os per Second Suggested CoalesceMsCnt Suggested CoalesceRspCnt I Os lt 10000 0 8 10000 lt I Os lt 18000 1 8 18000 lt 1 Os lt 26000 1 16 1 Os gt 26000 1 24 CoalesceMsCnt The CoalesceMsCnt parameter controls the maximum elapsed time in milliseconds that the adapter waits before it generates a CPU interrupt The value range is 0 63 decimal or 0x0 0x3F hex The default is 0 and disables I O Coalescing CoalesceRspCnt The CoalesceRspCnt parameter controls the maximum number of responses to batch before an interrupt generates If CoalesceRspCnt expires an interrupt generates for all responses collected up to that point With CoalesceRspCnt set to less than 2 response coalescing
16. Ox1A Port in on line state LightPulse 0x1B Port in off line state LightPulse OxA7 Data underrun 0xDO NPIV Virtual Port creation success Virtual Port Did in bits 8 31 0xD1 NPIV Virtual Port creation failed Virtual Port index in bits 8 31 0xD2 NPIV Virtual Port FDISC failed Virtual Port index in bits 8 31 0xD4 Exceeded max Virtual Port supported Virtual Port index in bits 8 31 0xD5 NPIV Virtual Port removal Virtual Port Did in bits 8 31 OxEO Authenticated successfully remote Did in bits 8 31 OxE1 Failed to authenticate remote Did in bits 8 31 OxE2 Authentication not support remote Did in bits 8 31 OxE3 Authentication ELS command timeout remote Did in bits 8 31 OxE4 Authentication transaction timeout remote Did in bits 8 31 OxE5 LS RJT other than Logical Busy received for Authentication transaction remote Did in bits 8 31 OxE6 LS RJT Logical Busy received for Authentication Transaction remote Did in bits 8 31 OxE7 Received Authentication Reject other than Restart remote Did in bits 8 31 OxE8 Received Authentication Reject Restart remote Did in bits 8 31 OxE9 Received Authentication Negotiate remote Did in bits 8 31 OxEA Authentication spurious traffic remote Did in bits 8 31 OxEB Authentication policy has been changed remote Did in bits 8 31 0OxED Same passe
17. lt EMULEX FC FCoE Error and Event Logs Appendix A Error and Event Log Information FC FCoE Error and Event Logs Viewing the FC FCoE Error Log The system event log is a standard feature of Windows Server software All events logged by the Emulex Storport Miniport will be Event ID 11 with source elxstor To view the error LOG 1 Open the Event Viewer window e Click Start gt Programs gt Administrative Tools gt Event Viewer Or e Right click My Computer Manage and Event Viewer in Computer Management The Event Viewer window is displayed 2 Double click any event with the source name ELXSTOR 3 Examine the entry at offset 0x10 and Event ID 11 The Emulex event code is found in byte 0010 and supplementary data is in the byte offsets 0011 through 0013 in example Figure A 1 byte 0010 9b byte 0011 00 byte 0012 29 and byte 0013 00 Event Properties 2 x Event Date WAAT Source elxstor Time amp 52 19PM Categoyr None Type Error EventID 11 User N A Ba Computer EMULEX D4C6E5BE Description The description for Event ID 11 in Source elxstor cannot be found The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer You may be able to use the AUXSOURCE flag to retrieve this description see Help and Support for details The following information is part of the event Device RadPortd Data Bytes O
18. since the last statistics reset or the driver was reloaded TCP Offload Retransmits The number of packets retransmitted for TCP offloaded connections TCP Offload Receive Drops The number of packets dropped by in the offloaded TCP stack These drops may the result of TCP protocol errors or bottlenecks in the system for consuming receive data TCP Offload Transmit Rate The transmit data rate of the offloaded TCP connections This is the portion of the total Transmit Throughput contributed by offloaded TCP connections TCP Offload Receive Rate The receive data rate of the offloaded TCP connections VMQs Allocated The current number of Virtual Machine Queues allocated Interrupt Rate Emulex Drivers for Windows User Manual The number of interrupts per second generated by the adapter The interrupt rate may be tuned by modifying the Interrupt Moderation parameter P008011 01A Rev A gt EMULEX 2 Configuration NIC TOE Driver Configuration Table 2 4 NIC TOE Driver Properties Statistics Continued Statistic Name Receive Drops No Memory DMA Limited Description The number of packets dropped as a result of insufficient buffers posted by the driver This is generally the result of the CPU core used for any receive queue reaching 100 The system may lack sufficient CPU cycles to post receive buffers at the necessary rate A lot of small packets lead to this behavior on almo
19. 125 Format of Vendor Specific Option 43 ccccccccceecee reese eeeeeeeeaeeeeaeeseaeeeeanes 125 Description of Mandatory and Optional Parameters cccccceeeeeene eset eeeae ees 126 EXQMiDIGS vos2ceccramedeschcesoudiureataraarivedetocsercecsdyeiecredersossdraueusslivvhdarse iene 126 Appendix C Port Speed Specifications ssssssnnnnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 128 Negotiating Speed on a Mezzanine Card sssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 128 Appendix D AutoPilot Installer Command Line and Configuration File Parameters 129 AParg Driver Kit Parameter and Appending to the APinstall exe File secccsereees 129 AutoPilot Installer Sy nt aK vassanssessssnspcincsnaueocianessamendanesimesnsmnenenapeetauneneeianasan 130 Path SUGCHICNS acc ccccwrecestaseedeevianeee denise deb E E A EEEE aaa 131 Configuration File Location ssssssssrsrrrererrerrsrsrrrrrrerrrrrtrrrrrrrrrrrtrrrrrrrr 131 Software Configuration Parameters ccccceeecee eect ee eeeeeeeeeeeeeee tenes eeneenenes 131 DiagEnable Running Diagnostics cccecceeeeeeeeeeeeeeeeeeeateseteceeeeeesnteaeenas 131 ForceDriverTypeChange Forcing a Driver Type Change ceceeeeee eee eee eee 131 ForceDriverUpdate Forcing a Driver Version Update ccceeceeeeeeseeeeeeeeneees 132 ForceRegUpdate Forcing an Update of an Existing Driver Parameter Value 132 LocalDriverLocation Specifying Location to Search for
20. 99 DG EMULEX Troubleshooting the iSCSI Driver Table 3 5 Troubleshooting the iSCSI Driver Continued Problem Answer Solution When software based iSCSI targets This occurs caused because of an issue with the data reported by are logged into the UCNA Event ID the iSCSI target in the Product Identification field in response to 56 Driver SCSI 000000 Appears in the standard inquiry from the UCNA This field should be unique the Windows event viewer This issue among different targets LUNs but software based targets report has been observed on Windows 2008 the same pre formatted data for all the LUNs across all targets R2 under the following conditions When Windows encounters the same Product Identification field The iSCSI target is a for different LUNs with the same Bus Target Lun field it records software based target MSISCSI error in the event log No other effect has been found as a result IET StarWind that uses a local of this behavior hard drive or a RAM disk for its The workaround for this error is to use non overlapping LUN backend LUN numbers for the various LUNs across the various iSCSI targets On e Different UCNA ports are involved the iSCSI target system LUNs can be numbered sequentially in the login they do not have to start at zero A SAS controller is present on the system Emulex Drivers for Windows User Manual P008011 01A Rev A se Appendix A Error and Event Log Information 100 gt
21. A gt EMULEX 3 Troubleshooting 82 Troubleshooting the FC FCoE Driver Ipfc_mes0225 Device Discovery completes Description Severity Log Action This indicates successful completion of device re discovery after a link up Information LOG_DISCOVERY verbose No action needed informational Ipfc_mes0229 Assign SCSIid x x to WWN word 0 x x WWN word 1 x x NPortid x x Description Severity Log Action The driver assigned a SCSI ID to a discovered mapped FCP target BindType 0 DID 1 WWNN 2 WWPN Information LOG_DISCOVERY verbose No action needed informational Ipfc_mes0230 Cannot assign SCSIIid to WWN word 0 x WWN word 1 x x NPortid x amp x Description Severity Log Action SCSI ID assignment failed for discovered target Warning LOG_ELS verbose Review system configuration Ipfc_mes0232 Continue discovery at sequence number d PLOGIs remaining d Description Severity Log Action NPort discovery sequence continuation Information LOG_ELS verbose No action needed informational Ipfc_mes0235 New RSCN being deferred due to RSCN in process Description Severity Log Action Emulex Drivers for Windows User Manual An RSCN was received while processing a previous RSCN Information LOG_ELS verbose No action needed informational P008011 01A Rev A gt EMULEX 3 Troubleshooting 83 Troubleshooting the FC FCoE Driver Ipf
22. Configuration File Parameters 136 AutoPilot Configuration File answer 0 DriverParameter Paraml value answer 1 DriverParameter Paraml value answer n DriverParameter Paraml value Param2 value Param2 value Param2 value Example of STORPORT CONFIGURATION section STORPORT CONFIGURATION The first section contains the driver parameters common to all configurations DriverParameter EmulexOption 0 no matter what answers are given QUESTIONS question What is your link speed Note select Auto detect if you are unsure about the answer 4GB 2GB 1GB Auto detect ANSWER 0 DriverParameter LinkSpeed 4 4 GB ANSWER 1 DriverParameter LinkSpeed 2 2 GB ANSWER 2 DriverParameter LinkSpeed 1 1 GB ANSWER 3 DriverParameter LinkSpeed 0 Auto detect question Describe the topology of your storage network Note Select Arbitrated Loop when directly connected to the array no fibre switch Select Point to Point when connected to a SAN fibre switch Arbitrated Loop Point to Point ANSWER 0 DriverParameter Topology 2 ANSWER 1 DriverParameter Topology 3 ENDQUESTIONS m END STORPORT CONFIGURATION QFE Checks STORPORT QFES This section specifies an additional Quick Fix Engineering QFE check also known as KB Knowledge Base updates during in
23. Manual P008011 01A Rev A 4 SXC EMULEX Table of Contents Using the Microsoft iSCSI Initiator Service 0 eect eee 72 Logging into a Target Using the Microsoft Software Initiator c cccceeeeeeeeeeeees 72 Windows Multipath I O SUppOre lt xcsv lt cccscxaaveacehexgeycaddseuteresseetwiadeidacatedeaaeaten 73 Multipath Support on Windows Server 2008 2008 R2 and 2012 ccccceeee seen ees 73 Logging into Targets for Multipath Support ccc cee cee cece teeta need 74 Maximum Transmission Unit MTU for iSCSI Connections cccccceeeeeeeeeeeeeeeees 74 iSCSI Error Handling ccitcrteserhermenssresemreieciestciweiautshetviveney a a a ea 74 Configuring LDTO and ETO on Windows SerVel ccccceceeeeeeeeeeeteeeteeeeeeeteeutens 75 Error Handling Under MultiPath MPIO and Cluster Configurations 0eeee 76 3 Troubleshooting iii OR A General Troubleshooting cssccccccstcccccssescsncscssnstanascnsanensossd eas tnecaesensennaecses ease 77 Troubleshooting the FC FCOE Driver ssssssssnnsssssnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 77 Troubleshooting the Cisco Nexus Switch Configuration c ccc ceeeee cece ee eae 77 Event Trace Message S iticndescnteamnnransiemendsiietnrncenieewesenenasnniamesoumruck antag 78 ELS Log Messages 0100 0130 c cccccccc cee eee tesa tease eeeeeeee sate sateseeeeeeeenenaaees 78 Discovery Log Messages 0202 0262 c cece cette teen rtr
24. Network Connections applet ncpa cpl The most typical scenario involves setting parameters the same for all ports of a network adapter This is accomplished by specifying a emulex Often it is convenient to rename the connections to have a common name to easily operate on a group For example naming the network connections dot1 dot2 dot3 allows operating on all adapters using the substring dot or on any individual adapter by specifying the exact name such as dot1 Configuring Device Parameters OneConnect Config is used to query and modify registry parameters for Emulex network devices The registry keys are stored at HKLM System CurrentControlSet Control Class 4D36E972 E325 11CE BFC 108002bE10318 where is the device instance number Emulex Drivers for Windows User Manual P008011 01A Rev A f 2 Configuration 56 DG EMULEX NIC TOE Driver Configuration The occfg program allows you to modify registry keys on a set of network devices Once modified the driver must be restarted to apply these parameters In batch mode occfg will automatically restart the driver when changing a parameter and in interactive mode there is a menu item to select to restart the driver In batch mode the commands to modify parameters will look like the following examples occfg a emulex s rss 0 occfg a emulex s Interrupt Moderation 4 Flow Control 3 The parameter name must uniquel
25. P008011 01A Rev A 114 Appendix A Error and Event Log Information 115 gt lt EMULEX iSCSI Error and Event Log iSCSI Error and Event Log Viewing the iSCSI Error and Event Log on Windows Server 2008 The iSCSI driver generates error codes in the system event log in the form of Event ID 11 errors These error codes can be viewed by using the Event Viewer application To view the error codes 6 See Click the Start tab on the bottom of the screen Click Run Type event vwr and click OK Click Windows Log Click System Click the be2iscsi error under System Events to show the details of the event The iSCSI driver logs errors with the port driver error code of SP_INTERNAL_ADAPTER_ERROR which translates to an Event ID 11 entry in the system event log The following is an example of the iSCSI driver error code 0x11800003 viewed with the Event Viewer application The window shows the driver generated error code in the fifth DWORD offset 0x10 of the word dump Note To improve the visibility of the error code in the Data field of the Event Properties window select the Words option Emulex Drivers for Windows User Manual P008011 01A Rev A gt lt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log E Computer management i TE S Be edon yew yindw tep le x es OBO OOOO By Coree Management locs npa OMe te Joe Jon ee Ue computer ih System
26. Rev A 2 Configuration gt lt EMULEX iSCSI Driver Configuration 12 aggressive interrupt rate can also result in system stalls and freezes especially if queue depth values are high and I O requests are small In a configuration that involves a large number of iSCSI targets more than 32 or 64 and higher values of queue depth the default setting may prove to be too aggressive In such a case you may need to change the im_policy parameter setting to 3 or 4 Although this increases latency of an I O request the lower interrupt rate may allow the system to be functional under a high load Creating Non Bootable Targets To set up non bootable targets proceed with the driver and operating system installation then download and use the Microsoft iSCSI Initiator Service to configure and manage the adapter Using the Microsoft iSCSI Initiator Service You can use the Microsoft iSCSI Initiator Service to configure and manage the UCNA The Microsoft Initiator Service is available as a free download from www microsoft com See the documentation that accompanies it for detailed information Note When you install the Microsoft iSCSI Initiator Service you need to select only the Initiator Service check box and not the Software Initiator check box The Microsoft iSCSI Initiator Service sets its own initiator name Once you have installed it you must replace this with your chosen initiator name To do this 1 In the Microsoft iSCSI Initiat
27. SCSI status returned from a SCSI device which receives a SCSI command Table A 9 SCSI Status Codes Explanation Code GOOD 0x00 CHECK CONDITION 0x02 BUSY 0x08 RESERVATION CONFLICT 0x18 QUEUE FULL 0x28 Emulex Drivers for Windows User Manual P008011 01A Rev A 108 sc Appendix A Error and Event Log Information 1Q9 gt lt EMULEX FC FCoE Error and Event Logs Local Reject Status Codes Codes supplied by the Emulex adapter firmware which indicate why a command was failed by the adapter Table A 10 Local Reject Status Codes Explanation Code SEQUENCE TIMEOUT Possible bad cable link noise 0x02 INVALID RPI Occurs when link goes down 0x04 NO XRI Possible host or SAN problem 0x05 TX_DMA FAILED Possible host system problem 0x0D RX_DMA FAILED Possible host system problem Ox0E ILLEGAL FRAME Possible bad cable link noise Ox0F NO RESOURCES Port out of exchanges or logins 0x11 LOOP OPEN FAILURE FC_AL port not responding 0x18 LINK DOWN Queued cmds returned at link down 0x51A OUT OF ORDER DATA Possible bad cable or noise 0x1D SRB Status Codes SCSI Request Block status provided by the driver to the operating system based upon response from SCSI device in the SAN Table A 11 SRB Status Codes Explanation Code ERROR 0x04 BUSY 0x05 TIMEOUT 0x09 SELECTION TIMEOUT 0x0A COMMAND TIMEOUT 0x0B BUS RESET 0x0E DATA OVERUN 0x12 ASC ASCQ
28. TOE e No more than one VLAN can be used with each universal multichannel UMC virtual channel e You cannot run Link Aggregation Control Protocol LACP when UMC is enabled e UMC is not supported by TOE For additional information on UMC refer to the Boot for NIC iSCSI and FCoE Protocols User Manual For more information on the options see Network Driver Performance Tuning on page 59 Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 2 Configuration 41 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Option Name Class of Service 802 1p Acceptable Values Automatic Priority default Filtered Priority User Priority Disable Priority Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012 Definition The following modes are supported for selecting 802 1p priority tags e Automatic Priority The DCBX standard allows the network adapter to negotiate priority class usage with DCBX aware endpoints such as switches or network cards If the peer indicates that priority pause is supported for a non zero priority the NIC automatically inserts the default priority in all transmitted packets This is the default mode allowing priority pause to operate for both storage and network traffic If the peer indicates a zero default priority such as when the peer does not support priority pause the device us
29. The network device is operating in For best performance install the Emulex Drivers for Windows User Manual Genl mode and installed in a 4x PCI Express slot UCNA in an 8x Gen1 PCle slot Note A 16x slot will not provide any additional performance P008011 01A Rev A 112 gt G EMULEX Table A 12 NIC TOE Event Log Entries Continued Appendix A Error and Event Log Information 113 NIC TOE Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x001d 29 Informational The network device is operatingin For best performance install the Gen1 mode and installed in a 1x UCNA in an 8x Gen1 PCle slot Note PCI Express slot A 16x slot will not provide any additional performance 0x001c 28 Error Vital product data is not initialized Use the offline flash utility to correctly reconfigure the device 0x000c 12 Informational The Ethernet link is down This message is informational 0x000b 11 Informational The Ethernet link is up This message is informational 0x000a 10 Error The network device detected an A hardware error occurred Verify error that the firmware flash image is not corrupted Contact Emulex Technical Support 0x0015 21 Error Firmware version does not match The firmware version and driver driver version must match This is a warning message but it is recommended that you reinstall matching versions of the firmware
30. Tools GP Error MINDA MIA beses None 1 WA SERVEREN SHEJ Event Viewer Bere MISO 11 3923 beet teen WA SERVEREN 1j Appkcation iranan iI 11 90 23 bedrot Sonn 1 Wa SERVEREN Secaky gem LIDO 11 9023 bedret tere cs KWA SERVEREN la oa Erro LIO 81 97 23 bedene Nene KA SERVEREN Qicduasedcose T 7i x1 gt E Performance Logs and Alert A pl vee Bh ovce Evert KA SERVEREN fj Storage r HO OA SERVEREN EP Removable Stay J Dye fouce bedicsi N NA SERVEREN Ok Defragmenter l Tam NIRHUA Cegar None XOS SYSTEM SERVEREN Disk Management Qype Ena Evert D 11 cal 7006 NA SERVEREN Ea Services and Appibcatioers d Uses NA Ra XS SYSTEM SERVEREN I Comeuter SERVERENPTSAW NS NA SERVEREN Q 735 SYSTEM SERVEREN G Resesption X NA SERVEREN g The diver detected a comtsobet esar on Derace R tut 7035 NETWORK SER SERVEREN A frepoetomsin peste Q a5 NA SERVEREN Q u na SERVEREN G 15 nA SERVEREN HO NA SERVEREN G 1 NA SERVER DV a SERVEREN 0000 oz 00 10 oO ol pb a anehi 0008 00 00 00 co oD a ot aa o010 5 00 80 43 o vee G 1 WA SEAVEREN 2 WA SEAVEREN WA SERVEREN 13 WA SERVEREN Bere ALSO 11 05 10 OOM Nene 10016 NETWORKSER SERVEREN Qie ALIO 11 05 10 OCOM tere 10016 NETWORK SER SERVEREN Dintoemascn ALIO 11 05 08 AgtociapSve teon 3 wA SERVEREN
31. Words oooo Of 00 10 00 01 00 68 00 h a 0008 00 00 00 00 Ob 00 O04 cO 0010 9b 00 29 00 00 00 00 00 A eaa v l OK Cancel Figure A 1 Event Properties Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix A Error and Event Log Information gt lt EMULEX FC FCoE Error and Event Logs Severity Scheme When the Event Viewer is launched there are three branches Application Security and System All ELXSTOR error log entries are found under the System branch and all ELXSTOR error log entries have the Event Viewer severity level of error e A severe error code indicates that the driver firmware or adapter is behaving abnormally and your intervention is required to correct the problem e A malfunction error code indicates that there is a problem with the system but your intervention is not required e Acommand error code indicates that an event has transpired but does not require your intervention An event may be problem oriented such as an invalid fabric command sub type An event may not be problem oriented such as exhausted retries on PLOGI or PDISC Related Driver Parameter LogError The LogError driver parameter determines the minimum severity level to enable entry of a logged error into the system See the Configuration Section for instructions on how to set driver parameters e If set to 0 all errors regardless of severity are logged e Ifset to 1 severe malfunctio
32. adapter Warning LOG_FCP verbose Review system configuration Possible side effect of cluster operations Ipfc_mes0713 Ipfc_mes0716 FCP Read Underrun expected d residual d Description Severity Log Action See Also FCP device provided less data than was requested Supplement Information LOG_FCP verbose No action needed informational Ipfc_mes0730 Ipfc_mes0729 FCP command error ulpStatus x x ulpWord 4 x x XRI x x ulpWord 7 x x Description Severity Log Action Remarks Emulex Drivers for Windows User Manual The specified device failed an I O FCP command Warning LOG_FCP verbose Check the state of the target in question Ipfc_mes0730 is also recorded if it is a FCP Rsp error P008011 01A Rev A gt EMULEX 3 Troubleshooting 89 Troubleshooting the FC FCoE Driver Ipfc_mes0730 FCP response error Flags x x SCSI status x x Residual d Description Severity Log Action Remark See Also The FCP command failed with a response error Warning LOG_FCP verbose Check the state of the target in question lpfc_mes0716 lpfc_mes0734 lpfc_mes0736 or lpfc_mes0737 is also recorded for more details if the corresponding SEVERITY level is set Ipfc_mes0729 Ipfc_mes0734 Read Check fcp_ parm x x Residual x x Description Severity Log Action See Also The issued FCP command returned a Read Check Error Warning LOG_FCP verbose Check the state of the ta
33. and driver 0x0015 21 Warning Firmware version does not match The firmware version and driver driver version must match This is a warning message but it is recommended that you reinstall matching versions of the firmware and driver 0x0014 20 Error Failed to read registry The registry is corrupted Reinstall configuration the driver and or operating system 0x0013 19 Error Resource conflict The operating system failed to allocate resources for the device Check low memory conditions and operating system hardware resource conflicts 0x0012 18 Error Failed to enable bus mastering Verify that the BIOS allows bus mastering and that no resource conflicts exist 0x0011 17 Error The driver is incompatible with the The driver is loaded on the incorrect device hardware device Verify that the correct driver is installed 0x0010 16 Warning The network driver was reset This may indicate a system hang or hardware problem Verify other system devices are working properly 0x0009 Error Failed to register interrupt service Thisis an NDIS error Verify that routine hardware resource conflicts do not exist Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX Table A 12 NIC TOE Event Log Entries Continued Appendix A Error and Event Log Information NIC TOE Error and Event Logs Message ID Hexadecimal Decimal 0x0008 8 Severity Error Message Failed to get TCP offload handlers
34. and must be registry because the value was out of corrected Check the registry configuration for range The driver will use the default any new valid values added to the driver value for this configuration parameter parameters For more information on valid instead driver values see Driver Parameters for Windows on page 90 0x31840006 The iSCSI driver failed to load due to This failure occurred due to a failed memory memory allocation failure allocation in the driver Check low memory conditions 0x31840001 The iSCSI driver failed to load because This failure may be due to the firmware not initialization failed during normal being present or currently running This failure bootup may also indicate a hardware problem 0x31640004 An internal API failed in the iSCSI This failure may indicate a low memory driver during initialization condition 0x3164000D The driver failed to allocate its This message indicates a low memory complete memory requirement and condition will attempt to load with reduced capabilities Total number of targets available will be reduced 0x14831000 There was an Unrecoverable Error This may be due to hardware errors or due to detected by the iSCSI driver Following this error log entry the next 3 entries indicate the error codes Emulex Drivers for Windows User Manual unhandled exceptions in the hardware or firmware P008011 01A Rev A gt EMULEX Appendix A Error and Event Log Infor
35. for driver software Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All DC adapter models are displayed in the Device Manager as two adapters therefore you must update each adapter Click Let me pick from a list of device drivers on my computer and click Next Select the network adapter that matches your hardware and click Have Disk Direct the Device Wizard to the location of oemsetup inf If you have installed the driver installer kit to the default folder the path is e C Program Files Emulex AutoPilot Installer Drivers NDIS x86 NIC Windows Version for the 32 bit driver version Or Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 25 gt lt EMULEX Manually Installing or Updating the Emulex Protocol Drivers e C Program Files Emulex AutoPilot Installer Drivers NDIS x64 NIC Windows Version for the x64 driver version Or e C Program Files Emulex AutoPilot Installer Drivers NDIS IA64 NIC Windows Version for the Itanium driver version 10 Click OK The Windows Security dialog box opens 11 Click Install 12 When the device driver finishes installing click Close The driver installation is complete The driver should start automatically Windows Server 2012 1 AT PF WSN Select Server Manager gt Dashboard gt Tools gt Computer Management gt Device Manager No
36. for the adapter Receive Packet Rate The rate of receive packets for the adapter Transmit Packets The total number of packets transmitted by the adapter since the last statistics reset or the driver was reloaded Receive Packets Emulex Drivers for Windows User Manual The total number of packets received This includes both RSS and non RSS packets P008011 01A Rev A 51 gt EMULEX 2 Configuration 52 NIC TOE Driver Configuration Table 2 4 NIC TOE Driver Properties Statistics Continued Statistic Name RSS Receive Packets Description The number of receive packets that were suitable for RSS Transmit Flow Control Pause Requests The number of times the network adapter sent a PAUSE frame to request that the peer stop sending data temporarily This indicates a potential bottleneck in the system Typically this bottleneck is the result of the DMA of packets from the adapter to host memory Receive Flow Control Pause Requests The number of times the network adapter received a PAUSE frame from the peer This indicates a potential bottleneck in the attached switch or network peer device This statistic only increments when the switch is correctly configured for flow control TCP Offloads Current Established The current number of TCP connections offloaded to the adapter s TCP Offload Engine TOE TCP Offloads The total number of TCP connections that have been offloaded
37. gt lt EMULEX AutoPilot Installer Overview e Print Installation Report The Windows print dialog box is displayed to select options for printing the installation report 6 Click Finish to exit AutoPilot Installer If the system must be rebooted you are prompted to do so as indicated in step 4 you must reboot before using the drivers or utilities Software First Installation The driver kit installer must be downloaded from the Emulex website and installed Either the full or core driver package may be installed only one can be installed on a system To perform a software first installation 1 Run AutoPilot Installer using one of the two options listed in Running a Software Installation Interactively on page 15 The following message appears AutoPilot Installer cannot find any Emulex Fibre Channel HBAs in this system S AutoPilot Installer Warning AutoPilot Installer can perform a driver pre installation allowing you to install your HBAs later Click OK to pre instal drivers or click Cancel to stop the installation Figure 1 1 AutoPilot Installer Warning Software First Installation 2 Click OK A Welcome page appears 3 Click Next The installation automatically progresses Once the installation is completed successfully the Finish dialog box appears 4 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory configura
38. hardware reducing PCI Express bus usage and interrupts e TCP timers including delayed ACK push retransmit and keep alive are implemented in hardware This reduces host CPU usage e Retransmits are handled entirely in hardware e Packetizing data including segmenting checksums and CRC is supported The network driver can receive send and receive buffers that are larger than 1 MB for maximum efficiency e The driver provides efficient parallel processing of multiple connections TCP on multiple CPU systems The UCNA receive path is zero copy for applications that prepost receive buffers or that issue a socket read before the data arrives Ideal applications use Microsoft s Winsock2 Asynchronous Sockets API which allows posting multiple receive buffers with asynchronous completions and posting multiple send operations with asynchronous completions Applications that do not prepost receive buffers may incur the penalty of the data copy and the performance improvement is significantly less noticeable Applications that transmit large amounts of data show excellent CPU efficiency using TCP offload TCP offload allows the network driver to accept large buffers of data to transmit Each buffer is roughly the same amount of processing work as a single TCP packet for non offloaded traffic The entire process of packetizing the data processing the incoming data acknowledgements and potentially retransmitting any lost data is handled by th
39. have already connected the hardware and click Next Select Add a new hardware device and click Next Select Install the hardware that I manually select from a list Advanced and click Next Select Show All Devices and click Next Click Have Disk Direct the Device Wizard to the location of elxplus inf If you have installed the driver installer kit in the default folder and C is your Windows system drive the path is e C Program Files Emulex AutoPilot Installer Drivers Storport x86 HBA for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA for the x64 driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport I A64 HBA for the Itanium driver version Click OK Select Emulex PLUS Click Next and click Next again to install the driver Click Finish The initial ElxPlus driver installation is complete Continue with manual installation of the Storport Miniport Driver See Installing or Updating the FC FCoE Storport Miniport Driver on page 22 for this procedure Updating the Emulex PLUS ElxPlus Driver Note Only one instance of the ElxPlus driver should be installed even if you have multiple adapter ports installed in your system To update an existing ElxPlus driver from the desktop 1 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 15 for in
40. insert the switch on the other port The mezzanine card retains the speed of the first link until both links are down Emulex Drivers for Windows User Manual P008011 01A Rev A o Appendix D AutoPilot Installer Command Line and Configuration File Parameters 129 gt EMULEX AParg Driver Kit Parameter and Appending to the APInstall exe File Appendix D AutoPilot Installer Command Line and Configuration File Parameters The AutoPilot Installer can initiate an installation from a command prompt or script You can pass command line parameters to the AutoPilot Installer yet still have it run automatically by the driver kit if you run the driver kit installer from a command prompt or script If you specify the q switch with the driver kit installer command the driver kit installer runs in unattended mode and automatically invokes the APInstall exe with its silent switch See Unattended Driver Installation on page 19 for more information AParg Driver Kit Parameter and Appending to the APinstall exe File If you specify a value for the APargs driver kit parameter this value is appended to the APInstall exe command line For example if you execute this installer file as lxdrv fc fcoe lt version gt exe q APargs SilentRebootEnable True then after installing the AutoPilot Installer the driver kit automatically executes it as APInstall exe silent SilentRebootEnable True To specify more than one para
41. is See the Downloads section of the no longer operational Update all Emulex website for compatible drivers and firmware firmware and drivers 0x0002c 44 Warning Error recovery is disabled on the This message is informational system The device is no longer operational 0x0002b 43 Informational The driver successfully recovered This message is informational from an error 0x0002a 42 Warning Legacy driver loaded Move to the NDIS 6 20 driver for Windows 2008 R2 for best performance 0x0029 41 Warning Legacy driver loaded Move to the NDIS 6 x driver for Windows 2008 for best performance Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX Table A 12 NIC TOE Event Log Entries Continued Appendix A Error and Event Log Information NIC TOE Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x0028 40 Warning The firmware is outdated and does The firmware and the driver are not not support TOE offloads for this compatible versions See the driver Update the firmware Downloads section of the Emulex website for compatible firmware and drivers 0x0026 38 Warning The device firmware does not The firmware and the driver are not support RSS functionality for this compatible versions See the network adapter Downloads section of the Emulex website for compatible firmware and drivers 0x0025 37 Warning The device firmwa
42. log for the iSCSI driver with 0x31840006 in the 5th DWORD When an iSCSI UCNA is used to log in If an iSCSI target provides an asynchronous event notification to to an iSCSI target and the LUN the UCNA when its logical unit inventory has changed the iSCSI configuration on the target is driver initiates a bus rescan and the LUNs are updated changed neither the UCNA nor the dynamically However if an iSCSI target does not provide an WMI GUI see the updated LUN asynchronous event notification the LUN list is not updated configuration dynamically Perform a manual rescan in Disk Management A login to new target fails after When Microsoft iSCSI software is installed the service chooses a Microsoft iSCSI Initiator Service is default IQN name for the UCNA The Microsoft iSCSI service installed issues the request to the iSCSI driver via the WMI interface to set this new IQN name Therefore any IQN name that was configured earlier such as by using iSCSISelect will be overridden and the new IQN name will be in effect Although this will not affect existing boot sessions and persistent sessions new target logins could fail because the new IQN name does not match the incoming IQN name configured on the target After the Microsoft iSCSI Initiator Service is installed the initiator name must be renamed to the previous name configured from the WMI GUI Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting
43. n Class selects the class of service on FCP Dynamic FC Only commands If set to 2 class 2 If set to 3 class 3 Value 2 3 Default 3 CoalesceMsCnt n CoalesceMsCn specifies wait time in milliseconds Reset LightPulse Only to generate an interrupt response if CoalesceRspCnt has not been satisfied Zero specifies an immediate interrupt response notification A non zero value enables response coalescing at the specified interval in milliseconds Value 0 63 decimal or 0x0 0x3F hex Default 0 0x0 CoalesceRspCnt n CoalesceRspCn specifies the number of response Reset LightPulse Only entries that trigger an Interrupt response Value 0 255 decimal or 0x1 OxFF hex Default 8 0x8 Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX Table 2 1 Storport Miniport Driver Parameters Continued 2 Configuration FC FCoE Driver Configuration be the typical use case The ConfigScale parameter supersedes the ExtTransferSize parameter for OneConnect adapters and Emulex 16 Gb adapters For all values except 0 up to 1024 targets can be discovered and mapped If set to 0 only 128 targets can be discovered and mapped On a OneConnect adapter or an Emulex 16 Gb adapter a value of 0 limits max XRIs to 512 Use ConfigScale 0 to minimize the driver s per port memory foot print on any adapter model If set to 0 on a OneConnect adapter or an Emulex 16 Gb adapter the max t
44. or FCP command failed at the FC level Table A 5 ELS FCP Command Error Status Codes Explanation Code Remote Stop Remote port sent an ABTS 0x2 Local Reject Local Reject error detail 0x3 LS RJT Received Remote port sent LS RJT 0x9 A_RJT Received Remote port sent BA_RJT OxA CT Command Response Codes Codes that indicate the response to a FC Common Transport protocol command Table A 6 CT Command Response Codes Explanation Code FC Common Transport Reject 0x8001 FC Common Transport Accept 0x8002 Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX FC CT Reject Reason Codes Appendix A Error and Event Log Information FC FCoE Error and Event Logs Codes that indicate the reason a CT command was rejected Table A 7 FC CT Reject Reason Codes Explanation Code Invalid command code 0x01 Invalid version level 0x02 Logical busy 0x05 Protocol error 0x07 ELS Command Codes FC protocol codes that describe what particular Extended Link Services command was sent Table A 8 ELS Command Codes Explanation Code Link Service Reject LS RJT 0x01 Accept ACC 0x02 N_Port Login PLOGI 0x03 Fabric Login FLOGI 0x04 N_Port Logout LOGO 0x05 Process Login PRLI 0x20 Process Logout PRLO 0x21 Discover F_Port Service Params FDISC 0x51 Discover Address ADISC 0x52 Register State Change Notify RSCN 0x61 SCSI Status Codes The
45. receives one network message before posting the next message it is considered latency bound For latency bound applications an interrupt is required to proceed to the next work item so reducing the number of interrupts directly reduces the network throughput The Microsoft iSCSI Initiator is generally considered a latency bound application unless the I O sizes are very large When tuning the system you must balance the extra CPU usage caused by interrupts with the potential decrease in total throughput for latency bound applications CPU Binding Considerations Windows applications may set a processor affinity which binds a program to a particular CPU in a multiple processor computer However with the recent additions to the Windows networking stack manually configuring CPU affinity is not recommended The advantage of application affinity for network applications is based on choosing the ideal relationship between the DPC and application affinity to reduce processor cache coherency cycles The ideal mapping may require that both the DPC and application run on the same processor different processors or different cores of a dual core processor that share a common memory cache Even when the best affinity relationship is determined it is impossible to enforce this relationship because RSS or TCP offloading choose the DPC processor The driver uses multiple parallel DPCs that are explicitly assigned to particular CPUs for processing both
46. service that supports remote execution then you can create a command script to remotely update drivers for all of the systems on the storage net If Microsoft s Remote Command Service RCMD service was installed for example a script similar to the following would run remote execution remd serverl g autopilot x86_full_kit apinstall if errorlevel 1 goto serverlok echo AutoPilot reported an error upgrading Server 1 if not errorlevel 2147483650 goto unsupported echo Configuration file missing goto serverlok unsupported if not errorlevel 2147483649 goto older echo Unsupported operating system detected older Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters gt G EMULEX Command Script Example if not errorlevel 2001 goto none cho The driver found is the same or older than the existing driver goto serverlok none if not errorlevel 1248 goto noreport echo No Emulex adapter found goto serverlok noreport if not errorlevel 110 goto nocfg echo Could not open installation report file goto serverlok nocfg if not errorlevel 87 goto badcfg echo Invalid configuration file parameters goto serverlok badcfg if not errorlevel 2 goto serverlok echo No appropriate driver found serverlok remd server2 g autopilot ApInstall ConfigFileLocation g autopilot mysetup apinstall cfg if errorlevel 1 goto server2ok echo AutoPilot repo
47. the SilentInstallEnable parameter on the command line Default False Setting this parameter to true causes AutoPilot Installer to operate with no user interaction SilentRebootEnable Enabling Silent Reboot Default False AutoPilot Installer s default behavior in unattended installations is not to restart the system AutoPilot Installer continues with the installation Restarts often require you to log in as part of the Windows start up process If there is no login the installation process would hang if the system is restarted However Windows can be configured to start up without requiring you to log in You must make sure it is safe to restart the system during unattended installations if you are going to set this parameter to true Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 134 gt EMULEX AutoPilot Configuration File InstallWithoutQFE Enabling Installation if a QFE Check Fails Default False AutoPilot Installer checks for Microsoft s Quick Fix Engineering updates QFEs also known as KB Knowledge Base updates based on the checks you have specified in the STORPORT QFES section By default the installation terminates if the QFE check fails To enable a driver installation to proceed even if a check for QFEs fails set this parameter to true AutoPilot Configuration File The AutoPilot configuration file is organized int
48. the session and continue e Check for software updates at the Emulex website If applicable update the software 0x127b0012 The iSCSI driver received an invalid e Verify that the iSCSI target is certified by iSCSI Command Sequence Number Microsoft Check for errors reported at the update from the target Following this target The Emulex iSCSI UCNA is only error log entry the next three entries supported with certified targets will indicate the session handle and e Check for software updates at the target the iSCSI parameters MaxCmdSN and vendor s website If applicable update the ExpCmdSN respectively software e Check for software updates at the Emulex website If applicable update the software 0x12790006 Aconnection to the target was lost for Check the connection to the target or the state a period exceeding the Extended of the target device If the target is made Timeout ETO The error log entry available any sessions that existed previously immediately following this entry will are reestablished and the devices are available indicate the session ID of the target for I O that lost the connection There will be event log entries from the disk subsystem indicating that the drives were lost If any I Os were in progress the system may see I O errors or failures 0x11990007 The iSCSI driver received a Task The operating system version is not supported Management Function TMF that is not supported and rejected this requ
49. used to determine if the QFE applies to the operating system platform present The acceptable value is Win2008 For example STORPORT QFES qfe QFE 83896 system32 drivers storport sys 5 2 1390 176 Win2008 Setting Up FC Driver Parameters STORPORT PARAMS This section specifies driver parameters Parameters are read exactly as they are entered and are written to the registry To change driver parameters modify this section of the AutoPilot configuration file Locate the STORPORT PARAMS section in the AutoPilot configuration file This section follows Optional Configuration File Changes Under the STORPORT PARAMS heading list the driver parameters and new values for the driver to use For example Driver Parameter LinkTimeout 45 See Driver Parameters for Windows on page 90 for a listing of driver parameters defaults and valid values Setting Up System Parameters SYSTEM PARAMS To change the system parameters create a SYSTEM PARAMS section in the APInstall cfg file Create this section under the Optional Configuration File Changes heading in the AUTOPILOT CONFIG section For example you can adjust the operating system s global disk timeout The timeout is stored in the registry under the key HKML CurrentControlSet Services disk and is specified with the following string TimeOutValue 0x3C where the number is the timeout value in seconds Emulex Drivers for Windows U
50. 0 Note Microsoft currently does not schedule RSS processing on all hyper threaded CPUs For example only CPU 1 and 3 have RSS queues on a dual core hyperthreaded CPU Enabling Windows to Use Up to Eight Processors Windows Server 2008 uses only four processors by default It is possible for UCNAs to use up to eight processors In order for the OneConnect driver to use up to eight processors the registry must be changed and the system restarted For Windows Server 2008 set the registry keyword MaxNumRssCpus a DWORD type to 8 at the location HKEY_LOCAL MACHINE SYSTEM CurrentControlSet Services Ndis Parameters Note Do not set the registry keyword to a value greater than the number of processors in the system or 16 whichever is smaller For Windows Server 2008 R2 and Windows Server 2012 the operating system uses all available CPU cores for RSS without manual configuration TCP Offloading TOE The UCNA and drivers support TCP offload which provides significant performance improvements The performance improvements are Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 65 DG EMULEX NIC TOE Driver Configuration e A zero copy receive data path exists In contrast all non offloaded TCP packets are copied in the network stack This copy dramatically increases the memory bandwidth and CPU requirements for receive data e Sending and receiving of ACK packets is handled entirely in
51. 1 or 0x31880001 running correctly indicating that the iSCSI driver failed to load 0x11800005 Both Port 0 and Port 1 links were down Check the links to the UCNA If the link is for a period exceeding the Link Down reestablished any sessions that previously Timeout LDTO If the UCNA has existed are reestablished and the devices is connection to the target there will be available for O event log entries from the disk subsystem indicating that the drives were lost If any I Os were in progress the system may see I O errors or failures 0x11800003 Both Port 0 and Port 1 links are down Check the links to the UCNA 0x31840005 Driver load failed because the PCI Check the configuration on the UCNA Vendor ID and Device ID are not supported 0x1180000A The logical link on the OneConnect The iSCSI function may have been disabled in Port is down traffic is disallowed on this function Emulex Drivers for Windows User Manual the PXESelect application If you disabled it intentionally you can ignore this message P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log Viewing the iSCSI Error Log on Windows Server 2008 R2 and 2012 The iSCSI driver on the Windows Server 2008 R2 and 2012 operating systems support the new event logging mechanism introduced by Storport Custom event messages are logged for a variety of events with different severity such as informationa
52. 12 NIC TOE Driver Options 41 NIC TOE Driver Properties Statistics vii iccissevcsecichi ck cavve lasek cance canes Gases iaenes 51 Windows Server Performance Tuning Situations c cece eee eect eee ees 60 Statistics and Fine TUNING ccoctaeriaxeieienriwntinepriaveoricbteiaee Savers 60 iSCSI Driver ODUIOIIS sini sct ci ccmne ohne ew cesaneies sued sane semees naeesmmadeanstmnesenaks 70 IM p lICY SOREN NGS ersin aia aa E E A EENE a A 71 LDTO and ETO Information on Windows Server ssssssiseseeeseesrirrrrererrrre 75 General Troubleshooting sssssssssrrrrrerrerssssrrrrrrrrrrrrrsrrrrrrrrrrrrrrsrrrrr 77 Cisco Nexus Switch Situations 0 2iSzxskscdssscea vented cmeyesesepiavemindlatesadisaexs 77 Troubleshooting the NIC TOE Driver S siisccicsuciesieiasvertsreessversseveviewsesaera 94 Troubleshooting TCP Offload Failures ccccceceece eee ee eee a 96 Troubleshooting the iSCSI Driver cccccececeeee eee eee e seen ereee erent enene ees 97 Severe EMOMSiwacvuurvocs ri iner Ee TEENETE EEOAE EEE EEEE OEE EE TEUVA 102 Malfunction Errors cenvaice cnn citees eneeaeeneeen ceneues voncncmsretaeen cases eeececeneeees 104 Command EllOlScacesescecectteniiesnsccapbiceeercanbcoretacanebos eestenehoieanticaiatecs 105 Event INGICALIONS sicxmovi cis evoneutepeevobvirsuiaviorerss aaa o E ao aae 106 ELS FCP Command Error Status Codes cc cine ckons tycceswreshnnk chunedencaseweanies 107 CT Command Response Codes ccc
53. 2 7 lists the user configurable iSCSI driver options available on Windows Server It includes a description of the parameters their default values and the limits within which they can be configured Note Ifthe value given for a parameter is outside the supported range the driver logs an error in the Event Log and continues to load by using the parameter s default value Configuring iSCSI Driver Options To change the iSCSI driver s configuration parameters you must edit the registry Because there is the risk of corrupting your system and rendering it unusable Emulex recommends that you make a back up of your registry before you make any changes Caution Using registry editor can cause serious problems that may require you to reinstall the computer s operating system Emulex cannot guarantee that problems resulting from changes you make to the registry can be repaired Use the registry editor at your own risk Backing Up and Editing the Registry 1 Create a system restore point Open the registry editor by running regedit exe at the command prompt Select the hive the top level key and export it to a reg file Save the reg file to a location off of the server as a precaution g epN Navigate to HKEY_LOCAL_MACHINE System CurrentControlSet Services be2iscsi Parameters Device 6 Double click on DriverParameters to edit Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 2 Configuration 70 iSC
54. AD_CONFIG command failed reinitialization 0x13 CONFIG_RING 0 failed reinitialization 0x14 CONFIG_RING 1 failed reinitialization 0x15 CONFIG_RING 2 failed reinitialization 0x16 CONFIG_RING 3 failed reinitialization 0x17 Unresponsive adapter port SLI2 3 mode Ox1C Firmware trap infol SLI2 3 mode 0x1D Firmware trap info2 SLI2 3 mode Ox1E Over temperature error condition LightPulse Ox1F Firmware initiated adapter port reset LightPulse 0x20 Adapter port error attention LightPulse 0x22 Over temperature warning LightPulse 0x23 Returned to safe temperature LightPulse 0x24 Emulex Drivers for Windows User Manual P008011 01A Rev A Invalid response tag SLI2 3 mode 102 gt G EMULEX Appendix A Error and Event Log Information 103 Table A 1 Severe Errors Continued FC FCoE Error and Event Logs Bits 0 7 0x25 Interpretation Invalid response tag SLI2 3 mode 0x26 Invalid response tag SLI2 3 mode 0x27 Invalid response sequence SLI2 3 mode 0x28 Failure on REG_LOGIN mailbox command 0x29 Unable to initiate fabric binding operation 0x2A Attempted ADISC to non existent node 0x2B Failure on iocb context allocation 0x2C Unable to initiate nport unbinding operation 0x2D Unable to initiate nport binding operation 0x30 Failure on mailbox c
55. Driver ConfiGuratiom sesinsssdareainctinasseiaiernsstanascecsseenssemaseetaaemiesenasen 30 Configuring FC Driver Parameters siccsicvsssevesasiastiie en veseverstreceeresere casi eseenins 30 Server Performance with FC Drivers iscescxcextecesenneslaxeesanderadersanedesadvsanen sacks 38 I O Coalescing dic iteecuss sei seetsacccdoe usenet da bes wed oon eer a aa hie wed a PEPENE nha ae 38 Performance Testing ccccec eee ee cent eee cease eee eee e eet sees dees eS ESaE SSeS SSE ES eE EEE EEE EES 38 NIC TOE Driver Configuratio Msiri aa 40 Configuring NIC TOE Driver Options ccccccccecece cece eee eeeeeeeee esate esaetesneneennes 40 Configuring Windows Server NIC TOE Driver Parameters ccccceseeeeeeeeeeeenees 49 Modifying Advanced PropertieS ssssssssiiss strt tirrr ee enter tied 49 Statistics Property Page aitaids vis seieierniaenusiateetandetanieaianduswunnnbend iE E EA 50 Using OCCFG for Windows NIC TOE Driver Options ccccceeeeceeeeeeee sees eenee es 54 Displaying OCCEG Helpis enpiri niea aden EEEE R TER EEEE 54 S lectingaN Adapte wii jncse cide aacandaw tii a keane neved EEEE EEUE DEEE ENTE E ARE EAE 55 Configuring Device Parameters ccc cece cece eee nett ireen rnrn 55 Viewing Device Parameters cecce eeii cece eee EE EEEE EEEE EEEE EEEE 57 Resetting All Parameters c cece cece cee eee e eee eee tenet ease eee eeee esate sat eeaeeeeteeneeanees 57 Displaying All Parameters scncsssseinucersciravc
56. Drivers 0scceseeeeeeeeeees 132 NoSoftwareFirstInstalls Prohibiting Software First Installations eeeeee 133 ReportLocation Setting Up an Installation Report Title and Location 085 133 SilentInstallEnable Enabling Unattended Installation cece eect eee 133 SilentRebootEnable Enabling Silent Reboot ccccccceeceeeeeeeteeeeeeeeeeeeeeneees 133 InstallWithoutQFE Enabling Installation if a QFE Check Fails ceeceeeee eee 134 AutoPilot Configuration File ssssssssssunnnnnnnnnsnnnnunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 134 Using the Windows Environment Variable WProgramFiles ccc 134 Configuration Identification AUTOPILOT ID vcs ieicisecs ance caevetaees dance hoes rrr 135 Software Configuration AUTOPILOT CONFIG ccccccceeeeeeeeeeeeeeeeeeeeneeenaes 135 Configuration Prompts Vendor Specific Questions STORPORT CONFIGURATION 135 QFE Checks STORPOR QFES es reatcs tence ehonye secu cette taiene dere ktekehovaseSenesener bes 136 Emulex Drivers for Windows User Manual P008011 01A Rev A DE EMULEX Table of Contents 7 Setting Up FC Driver Parameters STORPORT PARAMS ncc 137 Setting Up System Parameters SYSTEM PARAMS ac 137 AutoPilot Installer Exit CodeS ssssssssssnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnuunnnnnnnnnnnnnnn 138 AutoPilot Installer Installation Reports s ssssssnsnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnn 139 Command Sc
57. EMULEX wW M Emulex Drivers for Windows User Manual FC and FCoE version 2 72 012 001 NIC version 4 2 313 0 iSCSI version 4 2 281 0 P008011 01A Rev A Emulex Connects Servers Storage and People gt EMULEX Copyright 2012 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this manual as is without any warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product d
58. Emulex gt AutoPilot Installer or you can run APInstall exe from a command prompt Manually Installing or Updating the Emulex Protocol Drivers You can install or update the Emulex protocol drivers and utilities manually without using AutoPilot Installer The Emulex PLUS ElxPlus driver supports the OneCommand Manager application persistent binding and LUN mapping and masking Note The ElxPlus driver must be installed before you install the Emulex protocol drivers Removing the Adjunct Driver Registry Key The ElxPlus driver replaces the adjunct driver that was used with Storport Miniport 1 11a3 or earlier If it is currently installed the adjunct driver registry key must be removed using the deladjct reg file before you install the ElxPlus driver Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 21 Manually Installing or Updating the Emulex Protocol Drivers Installing the Emulex PLUS EIxPlus Driver for the First Time Note Only one instance of the ElxPlus driver should be installed even if you have multiple adapter ports installed in your system To install the ElxPlus driver from the desktop 1 10 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 15 for instructions Select Start gt Settings gt Control Panel gt Add Hardware The Add Hardware Wizard window appears Click Next Select Yes I
59. Enabling certain Windows networking features such as network bridging VPN and routing may cause the operating system to enable IP NAT services and the IPSEC policy agent These services if enabled disallow connections from being offloaded to the UCNA To disable these functions use the Services Control panel or the following commands at the command line prompt net stop accesspolicy net stop sharedaccess net stop ipnat Windows TCP Parameters Emulex does not recommend modifying the TCP registry parameters such as TcpAckFrequency provided by Microsoft The default parameters are suitable for a wide variety of situations with or without using TCP offloading Receive Window Auto Tuning and Compound TCP Windows Server adds several features to the host TCP stack such as receive window auto tuning and Compound TCP CTCP These features affect only non offloaded TCP traffic Performance of some 10 Gb s stress applications may suffer with these features enabled In particular Emulex has seen some bi directional data stream test performance degradation when receive window auto tuning is enabled This is due to increased receive performance that adversely affects the same TCP connection s transmit performance To disable these features type these commands at the command line netsh interface tcp set global autotuning disabled netsh interface tcp set global congestionprovider none Interrupt Coalescing The Windows Server n
60. If multiple PCI functions are exposed for a single 10 Gb s flow control setting differs among Ethernet port such as in blade configurations the flow control PCI functions parameter must be set the same on all adapters for the port Results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10 Gb s port On servers that support PCle hot Hot unplug is not supported in this release unplug the system may hang or produce a bugcheck if a PCle hot unplug or replace is attempted When Wake on LAN is set through The system may not support Wake on LAN on the PCle slot in the advanced properties page the which the UCNA is installed Check the system documentation to system does not wake when determine whether the system is capable of Wake on LAN receiving a magic packet or a operation packet that would normally wake A system BIOS setting may not be correct for Wake on LAN to work the system as expected Check the system documentation to determine whether Wake on LAN must be enabled in the system BIOS The system may not go to a lower power state because another software component device or driver is preventing it from doing SO Microsoft provides several useful references for troubleshooting Wake on LAN configuration issues in the Microsoft TechNet Library on the Microsoft website Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting 905 DG EMU
61. LEX Troubleshooting the NIC TOE Drivers Table 3 3 Troubleshooting the NIC TOE Drivers Continued Problem Answer Solution When running Windows Server 2008 Apply the 979614 hotfix as described on the Microsoft website the computer restarts and shows various Stop error codes when performing one of the following operations e Enabling or disabling TCP Chimney Offload e Changing the network adapter settings Upgrading the NIC drivers When an NDIS driver is being Windows 2008 picks up the first available driver it finds when an installed manually on a Windows NDIS driver is being installed manually Thus an NDIS5 driver will 2008 system the installer installs be installed even if a Windows NDIS6 driver is available An event the first driver it finds even if it is log message advises you to update to the latest driver for best not the latest version of the driver performance The system crashes or appears to There are several possible causes for this problem hang In the case of a hang there e Certain systems require an updated BIOS to properly manage could be a message indicating that the power states of newer Intel and AMD processors Check the driver experienced a hardware with your OEM for information regarding BIOS and firmware malfunction updates that may be required to run well with the latest releases of the Windows operating systems Also certain BIOS settings may be required For example it is
62. LOG_ELS verbose Action No action needed informational Remarks Ipfc_mes0114 and Ipfc_mes0115 are also recorded for more details if the corresponding severity level is set You can use the XRI to match the messages Ipfc_mes0114 PLOGI chkparm OK Description Received a PLOGI from a remote NPORT and its FC service parameters match this adapter Request can be accepted Severity Information Log LOG_ELS verbose Action No action needed informational See Also Ipfc_mes0112 Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 3 Troubleshooting 80 Troubleshooting the FC FCoE Driver Ipfc_mes0115 Unknown ELS command x x received from NPortld x x n Description Severity Log Action See Also Received an unsupported ELS command from a remote NPORT Error LOG_ELS verbose Check remote NPORT for potential problem Ipfc_mes0112 Ipfc_mes0128 Accepted ELS command OpCode x x Description Severity Log Action Accepted an ELS command from a remote NPORT Information LOG_ELS verbose No action needed informational Ipfc_mes0129 Rejected ELS command OpCode x x Description Severity Log Action Rejected ELS command from a remote NPORT Information LOG_ELS verbose No action needed informational Ipfc_mes0130 ELS command error ulpStatus x x ulpWord 4 x x Description Severity Log Action Emulex Drivers for Windows User Manual ELS command fai
63. Parameters on page 129 for details Once you have finished this step you can run AutoPilot Installer at a later time using either of the following methods If you are supplying options via the command line you must run AutoPilot Installer from the command line e Select Programs gt Emulex gt AutoPilot Installer in the Start menu Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 17 AutoPilot Installer Overview e Run AutoPilot Installer from the command line Type C Program Files Emulex AutoPilot Installer APInstall exe Note The location of APInstaller exe may differ on your system depending on your system s Program Files location You may also specify a different location when you install the driver package Hardware First Installation or Driver Update The driver kit installer must be downloaded from the Emulex website and installed Note Updating the NIC protocol driver may temporarily disrupt operation of any NIC teams configured on the system Note To update the Emulex protocol drivers begin the procedure at step 2 To perform a hardware first installation 1 Install a new Emulex adapter and power on the system If the Windows Found New Hardware wizard is displayed click Cancel to exit AutoPilot Installer performs this function Note If there are multiple adapters in the system the Windows Found New Hardware wizard appears multiple times Click Cancel to exit the wiz
64. RSS and TCP offloading tasks Each TCP connection is assigned to a particular CPU for processing This provides the advantage of assigning CPU affinities by reducing CPU cache misses without any user configuration Explicit processor affinity assignments are not necessary for the driver because the advantages of assigning processor affinities are realized by using RSS The only reason to experiment with application and interrupt CPU affinity is when performing isolated networking benchmarks Emulex Drivers for Windows User Manual P008011 01A Rev A f 2 Configuration 69 DG EMULEX iSCSI Driver Configuration Single TCP Connection Performance Settings One common benchmark is to run a single TCP connection between two computers as fast as possible The following are a few suggestions to deliver the best possible performance e Use TCP window scaling with a 256 Kb or 512 Kb window This may be controlled with show socket applications such as ntttcp from Microsoft e Use send and receive buffers that are larger than 128 Kb with an efficient application such as ntttcp e Disable RSS and use an interrupt filter driver Experiment with all relative CPU affinities to find the best combination e Disable timestamps and SACK because the test should run without dropping any packets e Unbind unused network protocols in the Network Connections property page e Disable any firewall services IPSEC or NAT iSCSI Driver Configuration Table
65. Recommended Resolution This is an NDIS error Verify the NDIS version is valid for the driver 0x0007 7 Warning A memory allocation failure occurred during driver load Performance may be reduced This warning occurred due to a failed memory allocation Check low memory conditions Use a smaller MTU or disable TCP offload to reduce driver memory requirements 0x0006 6 Error Driver load failed due to memory allocation failure This failure occurred due to a failed memory allocation in the driver Check low memory conditions 0x0005 5 Error Failed to register scatter gather DMA This failure occurred due to a failed memory allocation in the operating system Check low memory conditions 0x0004 4 Error Failed to map device registers This failure occurred due to a failed memory allocation in the operating system Check low memory conditions 0x0003 3 Error Unsupported medium This is an internal NDIS error Check the operating system installation 0x0002 2 Error The network driver initialization failed This may be a firmware driver mismatch or corrupt installation Check the firmware version reinstall the firmware and try again This may also indicate a hardware problem 0x0001 1 Informational Emulex Drivers for Windows User Manual The driver successfully loaded This message is informational and indicates successful loading of the device driver
66. Removing Emulex Driver Kits and Drivers ElxPlus Driver To uninstall the ElxPlus driver uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled 1 Run the Device Manager step 1 above 2 Click the plus sign next to the Emulex PLUS driver class 3 Right click the Emulex driver and click Uninstall 4 Click OK in the Confirm Device Removal window Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 30 gt lt EMULEX FC FCoE Driver Configuration 2 Configuration FC FCoE Driver Configuration The Emulex Storport Miniport driver has many options that you can modify to provide different behavior You can set Storport Miniport driver parameters using the OneCommand Manager application Refer to the OneCommand Manager Application User Manual for information on using this utility to configure the driver Configuring FC Driver Parameters The parameters listed in Table 2 1 Storport Miniport Driver Parameters are applicable to the Storport Miniport driver versions 2 70 xxx or later The Driver Parameter table provides information such as the allowable range of values and factory defaults Parameters can be entered in decimal or hexadecimal format A parameter has one of the following activation requirements e Dynamic The change takes effect while the system is running e Reset Requires an adapter reset from the utility before the change takes e
67. Report file contains details 2399142048 0x8F0000A0 NIC or iSCSI adapters are installed but are not supported on IA64 systems AutoPilot Installer Installation Reports During each installation AutoPilot Installer produces a report describing events that occurred during the installation This report has several sections e The first section provides basic information including the time and date of the installation the name of the machine that the installation was performed on the version number of AutoPilot Installer and the identification of the configuration file that was used e The second section provides an inventory of the Emulex adapters as they were before AutoPilot Installer performed any actions e The third section lists the tasks that AutoPilot performs in the order they are done e The fourth section records the results of each task When all driver installation tasks are completed an updated adapter inventory is recorded Note If you cancel AutoPilot Installer that fact is recorded along with when you cancelled the installation The contents of any error dialogs that are displayed are also recorded Command Script Example Modify the configuration file to script the installation of a system s driver The following example command script batch file assumes that you have made mandatory changes to the AutoPilot configuration file as well as any desired optional changes If your systems were set up with a
68. S DVD CD ROM drives at Configuration U5 Human Interface Devices es Storage cg IDE ATA ATAPI controllers Y Windows Server Bacup EaD Keyboards ashe a Disk Management 1 P Mice and other pointing devices Monitors Network adapters 4 Emulex OneConnect OCe 11102 I1 NIC TOE 10 amp Y Emulex OneConnect OCe11102 1 NIC TOE 9 A Ports COM amp LPT cS m Processors lt Storage controlers lt Dell SAS 6 R Integrated Controller gt Emulex OneConnect OCe 11102 1 iSCSI Initiator 7 e lt gt Emulex OneConnect OCe11102 I iSCSI Initiator lt gt Microsoft iSCSI Initiator lt gt Microsoft MultiPath Bus Oriver E System devices Universal Serial Bus controllers Figure 2 1 Partial View of Windows Device Manager 2 Right click the network adapter for which you wish to modify advanced properties 3 Click Properties then click the Advanced tab Figure 2 2 on page 50 4 From the list of properties click the property parameter you want to modify then select the new value of the property by clicking the down arrow on the Value pull down field 5 Click OK Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 50 DG EMULEX NIC TOE Driver Configuration Note Modifying properties causes the network driver to reload and some Transmission Control Protocol TCP connections may be temporarily dropped x General Advanc
69. SCSI Error Log Entries on Windows Server 2008 R2 and 2012 Continued Message ID 0x19 Severity Warning Message WMI driver error code A Recommended Resolution The iSCSI driver failed a WMI IOCTL request from the port driver The event log entry includes the WMI request code in error An operation attempted from the Microsoft WMI application resulted in an error Check the operation being attempted for errors Oxla Warning WMI IOCTL error code A The iSCSI driver failed a WMI IOCTL request from the port driver because the request was failed by the ARM firmware The event log entry includes the request code in error An operation attempted from the Microsoft WMI application resulted in an error Check the operation being attempted for errors Ox1b Warning A configuration parameter is out of range The iSCSI driver failed to load a configuration value specified in the registry because the value was out of range The driver uses the default value for this configuration parameter The range specified for a configuration parameter is either too large or too small and it must be corrected Check the registry configuration for new driver parameter entries See Driver Parameters for Windows on page 90 for the correct range of values Ox1d Warning A configuration parameter is invalid The iSCSI driver ignored a configuration entry because the entry was invalid Check the reg
70. SI Driver Configuration 7 Enter the configuration parameter See Table 2 7 iSCSI Driver Options on page 70 for iSCSI configuration parameters For example eto 60 ldto 30 im_policy 3 Note A semicolon is required after every parameter 8 Reboot the system 9 If the system does not boot press lt F8 gt and select Previous Known Good or use the system restore function while booting from an operating system install disc or recovery disc 10 If the system boots but does not work properly restore from a previous restore point or import the saved reg file and reboot Table 2 7 iSCSI Driver Options Parameter Default Value LDTO 20 seconds 0 seconds Minimum Value Maximum Value 3600 seconds Description Link down timeout LDTO in seconds This parameter determines the amount of time the universal converged network adapter UCNA driver waits for the controller s physical link to be available before reporting that the logical unit numbers LUNs are unavailable to the operating system Note LDTO values are configurable via the Windows registry ETO 90 seconds 0 seconds 3600 seconds Extended timeout ETO in seconds This parameter determines the amount of time the UCNA driver waits for the target to be available after it has lost connection to the target during an I O operation Note ETO values are configurable via the Windows registry N oO im_policy The Interrupt Moderati
71. SilentRebootEnable TRUE FALSE ForceDriverUpdate TRUE FALSE ForceDriverTypeChange TRUE FALSE SkipDriverInstall TRUE FALSE InstallWithoutOFE TRUE FALSE ForceRegUpdate TRUE FALSE LocalDriverLocation path specifier ReportLocation path specifier Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 131 SG EMULEX AutoPilot Installer Syntax Path Specifiers Paths may be specified as e an explicit path ReportLocation C Program Files Emulex AutoPilot Installer Reports e arelative path LocalDriverLocation Drivers Storport Miniport assuming installation into C Program Files Emulex AutoPilot Installer this path would logically become C Program Files Emulex AutoPilot Installer Drivers Storport Miniport e with the ProgramFiles environment variable LocalDriverLocation SProgramFiles Emulex AutoPilot Installer Driver Configuration File Location The optional setting ConfigFileLocation contains the path to the configuration file that should be used If this parameter is not specified AutoPilot Installer uses the file named APInstall cfg in the same folder as APInstall exe The format is the same as that of the other path settings Example APInstall silent SkipDriverInstall True configFileLocation MyConfiguration cfg Software C
72. The firmware is corrupt or non responsive Using the OneCommand Manager application or one of the WinPE offline or online utilities install a version of firmware that is compatible with the driver The Emulex iSCSI BIOS banner is not displayed during system POST Table 3 2 Cisco Nexus Switch Situations Configure the motherboard BIOS to enable the Option ROM for the PCI E slot in which the UCNA is installed Troubleshooting the FC FCoE Driver Troubleshooting the Cisco Nexus Switch Configuration Problem 1 Windows creates the NTFS partition ok but then reports that The hard disk containing e the partition or free space you chose has a LUN greater than 0 Setup cannot continue Dell 1850 server N stuck during the GUI portion of the installation right from the beginning HP DL385G2 server Emulex Drivers for Windows User Manual Windows reboots successfully but then gets j Solution Set up the FCoE switch ports as follows no priority flow control mode on untagged cos 0 e flowcontrol receive on flowcontrol send on spanning tree port type edge P008011 01A Rev A 3 Troubleshooting 78 DG EMULEX Troubleshooting the FC FCoE Driver Event Trace Messages ELS Log Messages 0100 0130 Ipfc_mes0100 FLOGI failure ulpStatus x x ulpWord 4 x x Description An ELS fabric login FLOGI command that was sent to the fabric failed Severity Error Log LOG_ELS verbo
73. ait for the installer to finish before it continues For more information on command line installation and configuration parameters see appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 129 Running a Software Installation Interactively There are two options when performing an installation interactively Option 1 allows you to automatically run the AutoPilot Installer which completes a driver kit installation and AutoPilot installation with a few mouse clicks Option 2 allows you to run the AutoPilot Installer separately This option is recommended when o Changing installation settings for a limited number of systems Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 16 AutoPilot Installer Overview o Familiarizing yourself with AutoPilot Installer configuration options These options assume you have already downloaded the driver kit installer from the Emulex website Option 1 Automatically Run the AutoPilot Installer Use this option unless you have specific configuration needs 1 Double click the driver kit installer or run it from a command line See appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 129 for information on the command line options The command line parameter APargs allows you to specify arguments that are automatically passed to the AutoPilot Installer command A Welcome page is display
74. an be dumped for all parameters by specifying the h option The following is an example help text for the RSS parameter RSs Receive Side Scaling RSS scales receive processing over multiple CPUs in parallel This scaling typically improves application performance however it tends to increase CPU usage on low end machines Emulex Drivers for Windows User Manual P008011 01A Rev A 58 S lt 2 Configuration 59 EMULEX NIC TOE Driver Configuration RSS is only supported on two primary adapters per device It will appear disabled for additional PCI functions in blade server configurations RSS requires Windows 2008 and later Registry Key RSS Default Value 1 Enable Valid Values 0 Disable 1 Enable Network Driver Performance Tuning Network driver performance tuning improves performance of the network and TOE driver for the Windows Server operating system The OneConnect UCNA OCe111xx and OCe101xx is a x8 Generation 2 Gen 2 or Gen2 PCI Express device and requires substantial memory bandwidth in a system to support 10 Gb s data streams Optimizing Server Hardware and BIOS Configuration UCNA performance can be improved by selecting a more efficient PCI Express packet payload size If the system BIOS allows selection of a larger PCI Express packet size selecting at least a 512 byte PCIe packet payload size provides the best efficiency for PCIe data transfers This may be an option in the serv
75. and Severity Error Log LOG_INIT verbose Action This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc_mes0446 Adapter failed to init CONFIG_RING mbxStatus x x Description Adapter initialization failed when issuing CFG_RING mailbox command Severity Error Log LOG_INIT verbose Action This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc_mes0454 Adapter failed to init INIT_LINK mbxStatus x x Description Adapter initialization failed when issuing INIT_LINK mailbox command Severity Error Log LOG_INIT verbose Action This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc_mes0458 Bring Adapter online Description The FC driver has received a request to bring the adapter online This may occur when running HBAnyware Severity Warning Log LOG_INIT verbose Action None required Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 3 Troubleshooting 87 Troubleshooting the FC FCoE Driver Ipfc_mes0460 Bring Adapter offline Description Severity Log Action The FC driver has received a request to bring the adapter offline This may occur when running HBAnyware Warning LOG_INIT verbose None required Ipfc_mes0463 Adapter firmware error hostStatus x x Info1 0xA8 x
76. ard each time it appears 2 Run AutoPilot Installer using one of the two options listed in Running a Software Installation Interactively on page 15 3 When the AutoPilot Installer Welcome page appears select an adapter in the list and click Next The installation continues Consider the following e If you are replacing a SCSIport Miniport or FC FCoE Port driver an Available Drivers list is displayed Click OK in this window e If you are updating the driver the existing port settings are used unless otherwise specified in the configuration file These settings are pre selected but can be changed Set or change settings then click Next e If you are initially installing a vendor specific version of the Emulex driver installation program a Driver Configuration page may be displayed This page includes one or more windows with questions that you must answer before continuing the installation process In this case answer each question and click Next on each window to continue 4 Click Next The installation automatically completes A dialog box is displayed if Windows requires a reboot Once the installation is successful the Finish dialog box appears 5 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory configuration information and task results Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 18
77. at lost the connection Event log entries from the disk subsystem indicate that the drives were lost If any I O was in progress the system may see I O errors or failures Check the connection to the target or the state of the target device If the target is made available any sessions that previously existed are reestablished and the devices are available for I O 0x09 Error Task Management request N was unhandled Emulex Drivers for Windows User Manual The iSCSI driver received a Task Management Function that is not supported and it rejected this request An application or service that is installed on the system may not be compatible with the driver P008011 01A Rev A 120 gt G EMULEX Appendix A Error and Event Log Information 121 iSCSI Error and Event Log Table A 14 iSCSI Error Log Entries on Windows Server 2008 R2 and 2012 Continued Message ID Ox0a Severity Error Message Task Management Function abort was received on a task that is not present Recommended Resolution The iSCSI driver received a Task Management Function Abort request for an I O request that is not present with the driver This may indicate a slow connection to the target Check network connectivity to the target for any errors 0x0b Error Error in determining firmware configuration An error in determining the firmware configuration occurred The firmware on the UCNA may not be functioning
78. ble Registry Receive Buffers 896 Registry Receive CPU lt not set gt Registry TCP Offload Optimization 0 Optimize Throughput Registry Transmit Buffers 256 Registry Transmit CPU lt not set gt Registry VLAN Identifier 802 1q lt not set gt Registry Wake On LAN 0 Disabled Using Interactive Mode The occfg exe program also supports the interactive mode with a set of menus To start this utility in interactive mode run occfg exe from a command console and do the following 1 A list of adapters displays on which to operate Type either a number of the list or a substring from any part of the name for more information see Selecting an Adapter on page 55 2 The program prompts for an operation such as modifying or querying a parameter value Follow the prompt 3 The program provides a list of available registry parameters to modify or query Type either the number of the corresponding option or a substring in the parameter name The substring must uniquely identify the parameter or occfg will display all potential options 4 To apply the parameters select the menu item to exit and reload the drivers Pressing control c at any point may leave modifications in the registry but the driver does not use the new parameters until is reloaded Parameter Help In interactive mode setting a parameter will display help text and information regarding the legal values for each parameter This information c
79. bled at the command line type netsh interface tcp show global To enable Chimney offload at the command line type netsh interface tcp set global chimney enabled To disable Chimney offload at the command line type netsh interface tcp set global chimney disabled For Windows Server 2008 and Windows Server 2008 R2 To verify whether offloading is enabled type netstat nt This command displays a list of connections and their offloading state Offloads are disabled for specific ports or applications To view any TCP ports or applications that may be configured to disable TCP offload at the command line type netsh interface tcp show chimneyports netsh interface tcp show chimneyapplications A third party firewall is running The Windows firewall does not affect TCP offload but third party firewalls may prevent TCP offloads Uninstall third party firewall software to allow TCP offloads In the network properties some intermediate drivers prevent offloading Go to Network Connections gt Properties and clear check boxes for unused drivers In particular Network Load Balancing and some third party drivers prevent offloads IPSec is enabled Disable IPSec IP Network Address Translation NAT is enabled Disable IP NAT The driver supports an Advanced Property to disable TCP offloading Make sure TCP offloading is enabled The TCP connection uses using IPv6 The driver supports o
80. c_mes0236 Issuing command to name server type x x Description Severity Log Action See Also The driver is issuing a nameserver request to the fabric Also recorded if a GID_FT is sent Information LOG_DISCOVERY verbose No action needed informational Ipfc_mes0239 or Ipfc_mes0240 Ipfc_mes0238 NameServer response DID count d Description Severity Log Action Received a response from fabric name server with N DIDs Information LOG_ELS verbose No action needed informational Ipfc_mes0239 NameServer Response next DID value x x Description Severity Log Action See Also The driver received a nameserver response And this message is recorded for each DID included in the response data Information LOG_DISCOVERY verbose No action needed informational Ipfc_mes0236 Ipfc_mes0240 NameServer Response Error CmdRsp x x ReasonCode x x Explanation x x Description Severity Log Action See Also Emulex Drivers for Windows User Manual The driver received a nameserver response containing a status error Error LOG_DISCOVERY verbose Check Fabric configuration The driver recovers from this and continues with device discovery Ipfc_mes0236 P008011 01A Rev A 3 Troubleshooting 84 SG EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes0256 Start node timer on NPortld x x timeout value d Description Starting timer for disconnected target with NPo
81. ceeeeeee eee eee e eee eee e nae eeeeeae naan eae 107 PC CT Reject Reason Codes noidcvivasuvaavsiiswols ens vassew evnrawnndannstaswnetrhs 108 ELS COMM ANG COUGS ccs ecex canes ieee kanes dices cmees hoc enone a KAA came KANTE anne bees 108 SCSI Status COMES iriri ciii aue AEE aii aa EEEREN iiA AEA E 108 Local Reject Status Codes sa cciicncidsvevinceinaucneetvereedeaeiestediersiasweieens 109 SRB Status CodeS s poperin distor trkas ian EEE LAREI pan EER PET a unek ESPINA CEIA ETARA RE 109 NIC TOE Event Log Entries s ssssessssssrrrrrerrrerrrrrrrrrrrrrerrrrrrrrrrerrre 111 iSCSI Error Log Entries on Windows Server 2008 leccese rererere 116 iSCSI Error Log Entries on Windows Server 2008 R2 and 2012 120 Data String Parameters for Option 43 sssssssssresesersrrrrrerrerrrrsrrrrrrerree 126 Negotiated Speed Specification per Adapter Port Connection ss cc 128 Unattended Installation Error Cod S c2 c cccccce cs cee cn eseedcvtescbenteaeenetee anes 138 P008011 01A Rev A List of Tables Q SG EMULEX 1 Installation 10 Driver Information 1 Installation Driver Information This product supports the Emulex OneConnect families of universal converged network adapters UCNAs and Emulex LightPulse family of host bus adapters HBAs The Windows drivers support the Fibre Channel FC FC over Ethernet FCoE Ethernet NIC including TCP Offload Engine TOE and Internet Small Computer System Interface iSCSI protocols This
82. ceived data to be buffered until the application has pre posted a receive buffer Some applications intentionally are written this way to peek at incoming data to determine how large of a receive buffer to post The timings of such a usage semantic in some cases depending on factors such as CPU Memory performance line rates the sizes of the receive buffers and system loading at the time will result in no observable improvement It is recommend that you leave this parameter set to the default of Optimize Throughput Windows Networking and TOE If certain Windows Server 2008 and Windows Server 2008 R2 networking features are enabled TOE does not operate as expected and connections are not offloaded Installing or activating firewall applications causes no connections to be offloaded by the Windows Server 2008 and Windows Server 2008 R2 network stack By default Windows Firewall Services are enabled at operating system installation time and they must be explicitly disabled in order to use TOE Firewall services can be disabled through the Service Control panel or the following commands at the command line prompt Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 67 DG EMULEX NIC TOE Driver Configuration To set firewall services to load on sc config MpsSvc start demand demand To stop firewall services Net stop MpsSvc To temporarily disable firewall services netsh advfirewall set all state off
83. d be used to configure VLANs on each virtual machine P008011 01A Rev A gt EMULEX 2 Configuration 47 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Wake on LAN Acceptable Values Disabled default Enabled Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012 Definition Enabling Wake on LAN allows the network device to wake up the computer when a magic packet is received during standby In Blade server configurations Wake On Lan is only supported on two primary adapters per device Additional PCI functions appear disabled Recv Segment Coalescing IPv4 Disabled default on Windows 2008 2008 R2 Enabled default on Windows 2012 Windows 2008 Window 2008 R2 Windows 2012 Receive Segment Coalescing merges multiple TCP segments and identifies them as a single coalesced unit to the operating system s TCP IP stack This reduces the per packet receive processing overhead and CPU usage when standard 1514 byte sized frames are in use Recv Segment Coalescing IPv6 Disabled default on Windows 2008 2008 R2 Enabled default on Windows 2012 Windows 2008 Window 2008 R2 Windows 2012 Receive Segment Coalescing merges multiple TCP segments and identifies them as a single coalesced unit to the operating system s TCP IP stack This reduces the per packet receive process
84. d were set for both local and remote entities remote Did in bits 8 31 OxF1 Port shutdown event OneConnect OxF2 Port in off line state OneConnect OxF3 Port in on line state OneConnect Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix A Error and Event Log Information 107 gt lt EMULEX FC FCoE Error and Event Logs Viewing the FC FCoE Event Log Event Log Interpretation e All events logged by Emulex Storport Miniport are in Event ID 11 with source elxstor e The Storport Miniport driver parameter LogErrors determines what type of events are logged by the driver the default setting is 3 which logs only events of a SEVERE nature the optional setting of 2 logs events of both SEVERE and MALFUNCTION type the optional setting of 1 logs events of SEVERE MALFUNCTION and COMMAND type Note For troubleshooting SAN connectivity or device discovery issues set the LogErrors to 1 e The Emulex event code is found in byte 0010 and supplementary data is in byte offsets 0011 through 0013 Additional Event Log Information The following tables are not comprehensive but do include those codes which through Emulex s experiences in our support and testing environments we feel are most likely to show up in SAN environments where problems occur ELS FCP Command Error Status Codes Internal firmware codes posted by the adapter firmware that explain why a particular ELS
85. default value may be equivalent to deleting the key For example occfg a emulex s vlan delete occfg a emulex s rss default Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 57 DG EMULEX NIC TOE Driver Configuration Viewing Device Parameters The occfg exe program can query device parameters from either the registry or the device driver if running driver version gt 2 103 x x The registry and driver values may differ until the driver is reloaded If the driver reload fails for any reason such as another application has an open handle to the device driver it may be necessary to reboot the system to apply the registry changes Note If the driver has been disabled or if the driver failed to load due to any error the driver query will return the error Failed to query driver for the parameter The following are batch mode examples occfg a emulex g Interrupt Moderation occfg a Local Area Connection g interrupt rss Emulex OneConnect OCe11102 I NIC TOE Local Area Connection Registry Interrupt Moderation 4 Adaptive Default Driver Interrupt Moderation 4 Adaptive Default Emulex OneConnect OCe11102 I NIC TOE Local Area Connection Registry RSS 0 Disable Driver RSS 0 Disable Resetting All Parameters Resetting all parameters will restore the default values for each adapter This is accomplished by using the command
86. dix A Error and Event Log Information 105 gt lt EMULEX FC FCoE Error and Event Logs Table A 2 Malfunction Errors Continued Bits 0 7 Interpretation 0x77 Failed to allocate Node object Ox7A REG_VPI failed 0xA3 Command context allocation failure OxAB SCSI command error OxAC Read check error 0xBO Node timeout device removal signaled to Storport Command Errors Table A 3 Command Errors Bits 0 7 Interpretation 0x43 Fabric login succeeded 0x46 ELS command failed 0x47 Exhausted retries on ELS command 0x4A PLOGI accepted 0x56 LOGO accepted 0x59 PRLI accepted 0x63 Fabric name server response 0x6B ELS RSCN processed 0x71 LOGO received from fabric 0x79 FDISC accepted OxA2 SCSI address assigned to discovered target OxA4 Report LUNs error initial I O to discovered target 0xA5 Local error indication on FCP command 0xA8 Data overrun 0xA9 FCP command error OxAA SCSI check condition OxAD Local reject indication on FCP command OxAE Error on SCSI pass through command OxAF Error on Menlo CT command Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX Appendix A Error and Event Log Information 1Q6 FC FCoE Error and Event Logs Event Indicators Table A 4 Event Indications Bits 0 7 Interpretation 0x18 Port shutdown event LightPulse 0x19 Port in off line state LightPulse
87. document explains how to install the Windows drivers on your system and configure the drivers capabilities based on the supported networking protocols FC and FCoE o Configuring the FC FCoE driver parameters o Improving server performance with FC FCoE drivers Ethernet and TOE o Configuring NIC TOE driver options o Tuning network driver performance iSCSI o Configuring iSCSI driver options o Creating non bootable targets o Configuring Multipath I O Compatibility For a list of adapters that are compatible with this driver see the driver s Downloads page on the Emulex website For compatible firmware versions see the Downloads page for the specific adapter Operating System Requirements One of the following operating systems must be installed Windows Server 2008 running on an x86 or x64 server Server Core installation option of Windows Server 2008 running on an x86 or x64 server Windows Server 2008 R2 running on an x64 server Windows Server 2008 R2 SP1 Windows Server 2012 Windows 7 Ultimate Enterprise or Professional edition x64 only Note Windows 7 is only supported on OCe11102 UCNAs Windows Pre installation Environment PE 2 x 3 x or 4 x Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation SG EMULEX Driver Installation Options il Note AutoPilot Installer is not supported for use with Windows PE See the Windows Automated Installation Kit WAIK documentation for instructio
88. dress through DHCP then you must set the lease length for the UCNA IP address to unlimited This prevents the IP address lease from expiring Vendor Specific Option 43 This section describes the format for the data returned in DHCP vendor specific option 43 The method and format for specifying the Vendor ID is outside the scope of this document and is not included here The UCNA offers this Vendor ID to the DHCP server to retrieve data in the format described in this section Format of Vendor Specific Option 43 The following describes the format of option 43 and includes guidelines for creating the data string iscsi lt TargetIP gt lt TargetTCPPort gt lt LUN gt lt TargetName gt lt InitiatorName gt lt HeaderDigest gt lt DataDigest gt lt AuthenticationType gt Strings shown in quotes are part of the syntax and is therefore mandatory Fields enclosed in angular brackets including the angular brackets should be replaced with their corresponding values Some of these fields are optional and may be skipped If an optional field is skipped a colon must be used as a placeholder to indicate the default value for that field When specified the value of each parameter should be enclosed in double quotes See Examples on page 126 All options are case sensitive Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX Appendix B Configuring iSCSI through DHCP 126 Dynamic Host Conf
89. driver failed a WMI IOCTL This failure indicates that an operation request from the port driver This attempted from the Microsoft WMI application error is immediately followed by resulted in an error Check the operation being another error code entry indicating attempted for user or configuration errors the WMI request code in error 0x33900002 The iSCSI driver failed an I O request This failure occurred due to a failed memory because it failed to retrieve a scatter allocation in the operating system Check low gather list from the Storport driver memory conditions 0x31880001 The iSCSI driver failed to load because This failure may be due to the firmware not initialization failed during a power being present or currently running This failure management bootup may also indicate a hardware problem 0x3184000c The iSCSI driver was unable to map This failure may indicate a low memory one or more PCI Base Address condition or a hardware error Registers and failed to load 0x3184000b The iSCSI driver ignored a The invalid entry must be removed or configuration entry because the entry corrected Check the registry configuration for was invalid any new valid values added to the driver parameters For more information on valid driver values see Driver Parameters for Windows on page 90 0x31840009 The iSCSI driver failed to load a The range specified for a configuration configuration value specified in the parameter is too large or too small
90. ds appear as giant packets in the packet sniffer because the hardware has not yet segmented them For information on modifying the CheckSum Offload or Large Send Offload parameter see Configuring NIC TOE Driver Options on page 40 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic The UCNA can process TCP receive packets on multiple processors in parallel This is ideal for applications that are CPU limited Typically these applications have numerous client TCP connections that may be short lived Web servers and database servers are prime examples RSS typically increases the number of transactions per second for these applications Understanding RSS To better understand RSS it helps to understand the interrupt mechanism used in the network driver Without RSS a network driver receives an interrupt when a network packet arrives This interrupt may occur on any CPU or it may be limited to a set of CPUs for a given device depending on the server architecture The network driver launches one deferred procedure call DPC that runs on the same CPU as the interrupt Only one DPC ever runs at a time In contrast with RSS enabled the network driver launches multiple parallel DPCs on different CPUs Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 64 DG EMULEX NIC TOE Driver Configuration For example on a four processor server that interrupts all processors without RSS the DPC ju
91. e Emulex website The limitation of the single package is that you cannot perform pre installation tasks unattended installations or text only installations For these tasks use the AutoPilot Installer kits Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 12 gt G EMULEX Driver Installation Options Loading the Onelnstall Package To install the drivers using the Onelnstall Package 1 ae YN Navigate to the location of the Onelnstall package that you downloaded to your hard drive Double click the Onelnstall package The Welcome screen appears Click Next The Installation options screen appears Select the drivers and application that you want to install Click Next A progress screen appears while the Onelnstall installer loads the selected drivers and applications When the drivers and application software are loaded an Installation completed screen appears Click Finish AutoPilot Installer AutoPilot Installer is included with the Emulex drivers and utilities in Windows executable files kit installers that you can download from the Emulex website Each driver kit contains x86 x64 and A64 FC FCoE drivers and installs the correct files on a per system basis Run one of the following driver kit installers to extract the software needed for the driver installation e Fibre Channel FC driver package elxdrvr fc lt version gt exe e Fibre Channel over Ethernet FCoE driver package
92. e FC FCoE Storport Miniport Driver To update or install the FC FCoE Storport Miniport driver from the desktop 1 Sra Sa 9 10 Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click Device Manager Open the SCSI and RAID Controllers item Double click the desired Emulex adapter Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All dual channel adapter models are displayed in Device Manager as two adapters and each adapter must be updated Select the Driver tab Click Update Driver The Update Driver wizard starts Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Select Install from a list or specific location Advanced and click Next Select Don t search I will choose the driver to install and click Next Emulex Drivers for Windows User Manual P008011 01A Rev A Se EMULEX 1 Installation 11 12 13 14 Manually Installing or Updating the Emulex Protocol Drivers Note Using the OEMSETUP INF file to update Emulex s FC FCoE Storport Miniport driver overwrites customized driver settings If you are updating from a previous installation write down the settings Following installation use the OneCommand Manager application to restore the previous settings Click Have Disk Direct the Device Wizard to the location of oemsetup inf If you have ins
93. e hardware TCP Offload Exclusions Microsoft provides a method to exclude certain applications from being offloaded to the UCNA There are certain types of applications that do not benefit effectively from TCP offload These include TCP connections that are short lived transfer small amounts of data at a time exhibit fragmentation from end to end or make use of IP options If an application sends less data than the Max Segment Size MSS the driver like most TCP stacks uses a Nagling algorithm Nagling reduces the number of TCP packets on the network by combining small application sends into one larger TCP packet Nagling typically reduces the performance of a single connection to allow greater overall performance for a large group of connections During Nagling a single connection may have long pauses 200 ms between sending subsequent packets as the driver waits for more data from the application to append to the packet An application can disable Nagling using the TCP_NO_DELAY parameter TCP offload does not improve the performance for connections that Nagle because the performance is intentionally limited by the Nagling algorithm Telnet and SSH consoles are examples of connections that typically use Nagling Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 66 DG EMULEX NIC TOE Driver Configuration Windows Server has not optimized the connection offload path Some applications that use numerous sho
94. ed Status Statistics Diagnostics SSG EMULEX Advanced Property Configuration Class of Service 802 1p Enhanced Trensmission Selection Network Address Packet Size VLAN Identifier 802 1q Wake On LAN Configuration parameters must be set correctly for the device to operate on the network These parameters typically require corresponding changes to the network switch or network peer device OK Cancel Figure 2 2 NIC TOE Advanced Properties in Windows Server 2008 Statistics Property Page Use the Statistics Properties tab to view the performance of the device and network By viewing the statistics properties you can troubleshoot problems and performance tune the system for example you can assess how different device properties change the performance of the system To view the statistics properties 1 Enter the Windows Device Manager e Click Start gt Control Panel gt System and click the Device Manager hyperlink or e Click Start gt Run then type devmgmt msc and click OK The Windows Device Manager is displayed Figure 2 1 2 Right click the network adapter for which you wish to view the statistics properties 3 Click Properties then click the Statistics tab Figure 2 3 on page 51 Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 2 Configuration NIC TOE Driver Configuration 4 From the list of properties select the property parameter you want to view
95. ed with driver kit version information and Emulex contact information 2 Click Next to proceed to the Installation Options page For each installation option the default installation location for that option is displayed Browse to a different location if desired 3 Click Install to continue the installation The Progress dialog box is displayed After all tasks are completed the Finish dialog box is displayed The Start AutoPilot Installer box is automatically selected 4 Click Finish AutoPilot Installer runs automatically and completes one of the following installations e Hardware First Installation or Driver and Utility Update page 17 e Software First Installation page 18 Option 2 Run the AutoPilot Installer Separately To access these options run AutoPilot Installer after driver kit installation is complete This allows you to change the configuration options supplied to the AutoPilot Installer see below 1 Perform steps 1 through 3 for Option 1 Automatically Run the AutoPilot Installer 2 Clear the Run AutoPilot Installer check box on the Finish dialog box 3 Click Finish The driver kit installer exits After the driver kit installation is complete change the configuration in one of two ways e Change the configuration file See Software Configuration Parameters on page 131 for details e Supply parameters on the command line See appendix D AutoPilot Installer Command Line and Configuration File
96. elxdrvr fcoe lt version gt exe e Internet Small Computer System Interface iSCSI driver package elxdrvr iscsi lt version gt exe e Network Interface Card NIC driver package elxdrvr nic lt version gt exe Note Updating the NIC protocol driver may temporarily disrupt operation of any NIC teams configured on the system You can install a driver by any of the following methods Note These installation methods are not mutually exclusive e Hardware first installation At least one Emulex adapter must be installed before you can install the Emulex drivers and utilities e Software first installation You can install drivers and utilities using AutoPilot Installer prior to the installation of any adapters You do not need to specify the adapter models to be installed later The appropriate drivers and utilities automatically load when you install the adapters e Utility Only installation If the drivers in the driver kit share the same version with those already installed on the system you can reinstall or update the previously installed utility without reinstalling the drivers e Text Only installation Text based installation mode is used automatically when AutoPilot Installer is run on a Server Core system Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 13 Note Driver Installation Options Network installation You can place the driver kit installers on a shared network dr
97. en Updating the Emulex Storport Miniport FC FCoE Driver 13 Driver Kit Installer Overview sesicciacitieasimtiatscanendasinnasaditind aaa 14 Installing the Driver Rie siccscsecscs nse cacnseardeemeeseessereuseneaeseteaciswisvaeteenenebcedas 14 AutoPilot Installer Overview ssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 15 Starting Installers from a Command Prompt or Script cccceeeeee eee essen seen ees 15 Running a Software Installation Interactively ccccccceeeeeeeeeee eset ee eeeeeeae eens 15 Option 1 Automatically Run the AutoPilot Installer l 16 Option 2 Run the AutoPilot Installer Separately cccccceeeeeeeeeeeeeeeeeeeeeeneeanes 16 Hardware First Installation or Driver Update cccccccseeeeeeeeeeeeeeeeeeeeeeenee ens 17 Software First Installation cccccccece cece eee ee eee eee eee Ee eH EEE eH Eee EE Eee ES 18 Text Only Driver Inistallatnonvvsncc cant ots csavel chore anntieheedencnlshavacaxtee eeesmunnt eters 18 Unattended Driver InStallatiGn c eceia2ceeeosssrgeeeeneredeutenaeneteivendesaeesiensuraaasvedan 19 Option 1 Install the Driver Silently cc eee eee eeeeeeteneenee 19 Option 2 Run the Driver Kit Installer Separately nnec 19 installation Failure 2rrenessersuvenorteodirenseng atecenneedaleeugengneeeennetaaeunaazeneiaceens 20 Manually Installing or Updating the Emulex Protocol Drivers ccccccseeesceeesseeeeaes 20 Removing the Adjunct Driver Registry Key
98. er s system BIOS The current value is displayed in Device Manager on the Status property page for the adapter Most computers offer multiple distinct memory channels which should be configured for channel interleaving for optimal performance Optimal interleaving is achieved by using the exact same DIMM configuration for each memory channel Check the manufacturer s documentation and BIOS parameters for details about optimizing memory bandwidth Typically all the dual in line memory module DIMM slots must be populated to make use of all the memory channels As a general rule more DIMMs provide better performance by allowing a higher degree of memory access interleaving to occur However some servers decrease the memory speed if using more than 2 DIMMs per memory channel so it is important to understand the trade off for a particular server platform Some servers may allow memory mirroring or memory sparing where the total memory is divided in half and each location is stored twice This allows fault recovery if one memory location detects an error but it greatly reduces the perceived memory bandwidth of the system Nearly any desktop or low end server has enough memory bandwidth for the UCNA to support Direct Memory Access DMA at 20 Gb s of data 10 Gb s read 10 Gb s write However most of the memory demands come from the processor accessing the data for either packet copies in the non offloaded networking stack or application Increa
99. er size when non zero to Reboot selectable values Values 0 Port Default 1 64Kb 2 128 Kb 3 256Kb LinkSpeed n LinkSpeed has significance only if the adapter Reset FC Only supports speeds other than one Gb s Value Auto select 1 Gb s 2 Gb s 4 Gb s 8 Gb s Default Auto select Note Setting this option incorrectly can cause the adapter to fail to initialize Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 35 DG EMULEX FC FCoE Driver Configuration Table 2 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol LinkTimeOut n LinkTimeOut applies to a private loop only A Dynamic timer is started on all mapped targets using the link timeout value If the timer expires before discovery is re resolved commands issued to timed out devices returns a SELECTIION_ TIMEOUT The Storport driver is notified of a bus change event which leads to the removal of all LUNs on the timed out devices Value 1 500 seconds or 0x0 0xFE hex Default 30 0x1E LogErrors n LogErrors determine the minimum severity level Dynamic required to enable entry of a logged error into the system event log Errors are classified as severe malfunction or command level A severe error requires user intervention to correct a firmware or adapter problem An invalid link speed selection is an example of a severe error A malfunct
100. ers therefore you must update each adapter Select Install from a list or specific location Advanced and click Next Select Don t search I will choose the driver to install and click Next Emulex Drivers for Windows User Manual P008011 01A Rev A 23 gt EMULEX 1 Installation 24 11 12 13 14 Manually Installing or Updating the Emulex Protocol Drivers Click Have Disk Direct the Device Wizard to the location of oemsetup inf If you have installed the driver installer kit to the default folder the path is e C Program Files Emulex AutoPilot Installer Drivers Storport x86 iSCSI Windows Version for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport x64 iSCSI Windows Version for the x64 driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport IA64 iSCSI Windows Version for the Itanium driver version Click OK Select Emulex OneConnect OCmXXXXX iSCSI Initiator your adapter model is displayed here Click Next Click Finish The driver installation is complete The driver should start automatically Installing or Updating the NIC Driver Windows Server 2008 ON O e DS Select Start gt Settings gt Control Panel gt Device Manager Open the Network Adapters item Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Click Browse my computer
101. es an I O request that is larger than 64 KB or that needs more than 16 scatter gather entries the request is split into multiple requests by the Storport driver Note If the large_io parameter is set to 512 the amount of physical memory consumed by the driver increases Also although intermediate values between 64 and 512 are accepted the memory used by the driver is the same as is used if large_io is set to 512 Parameter Value Setting Description im_policy 0 Disabled The Interrupt rate algorithm is turned off in the driver im_policy 1 Aggressive The highest interrupt rate among all available settings im_policy 2 Moderate The default value im_policy 3 Conservative A lower interrupt rate than moderate im_policy 4 Very conservative The lowest interrupt rate among all available settings While the default setting may work for most configurations there are instances when the setting may need to be altered The im_policy parameter setting should be based on the UCNA system configuration the number of iSCSI targets to be connected the I O load and the throughput and latency offered by these iSCSI targets On systems that are capable of sustaining a higher interrupt rate and on which the number of connected targets is low eight or fewer setting the im_policy to 1 results in lower latency and higher values of I O operations per second IOPs But this Emulex Drivers for Windows User Manual P008011 01A
102. es environment variable For example ReportLocation ProgramFiles my company reports Note The contents of the ProgramFiles environment variable is not terminated with a slash so you must provide one in the string Windows environment variables are not case sensitive Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 135 gt G EMULEX AutoPilot Configuration File Configuration Identification AUTOPILOT ID This section appears at the beginning of every AutoPilot configuration file and contains revision and label information The revision entry identifies the file s version number and the date on which it was produced The label entry is used to identify the configuration that the file supports This section may appear only once in the APInstall cfg file Software Configuration AUTOPILOT CONFIG This section can contain settings that control and configure AutoPilot Installer and the OneCommand Manager application operation This section can appear only once in the AutoPilot configuration file See Software Configuration Parameters on page 131 for information about settings that may be specified in this section Configuration Prompts Vendor Specific Questions STORPORT CONFIGURATION Note You must remove or comment out the entire STORPORT CONFIGURATION section for an unattended installation A STORPORT CONFIGURATION section
103. es the Non Storage Priority mode discussed below e Filtered Priority This mode coerces the user priorities in each packet to avoid sending packets on the network function that may disrupt the converged adapter s storage traffic The network device uses the next lower priority if a conflict exists This mode is useful if multiple network priorities are necessary Only a limited number of classes are supported for priority pause so typically it does not function optimally in this mode e User Priority This mode allows any user specified priority value and should be limited to cases where storage functions are not used Disable Priority The adapter always transmits either untagged packets or VLAN ID 802 1q tagged packets with a priority value 802 1p of zero Flow Control Disabled RX and TX Enabled default Rx Enable Tx Disable Tx Enable Rx Disable Emulex Drivers for Windows User Manual Windows 2008 Window 2008 R2 Windows 2012 Flow control is almost always advantageous to avoid packet drops on the network The switch or network peer must also have flow control enabled The IEEE 802 3x Ethernet specification defines a control frame between peers that can request a pause in packet transmissions This allows one system to request a temporary halt of all incoming traffic when receive buffer space is exhausted The network device may be configured to respond to pause frames Rx Enable a
104. escribed 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 Emulex Drivers for Windows User Manual P008011 01A Rev A Table of Contents gt G EMULEX Table of Contents List Of FIQUIES a cisaisinnsa nmana ibe KES List OF TaDI6S sissiiscssctcciavridtntenssenncensnntndsstiens senior a iaa e 1 IRStAN AION cicsiccdatsscavansatcitertahenrassobaccdasssasivasebiiaeversniaiesseniseererasseasne LO Driver INFORMAEON cans scascnsdcpesnsnntaissaainnsdanssoinaransiaaianieansswinaiennaswiansanniemsnaen 10 COMPACIDINICY oo nes secavernmviunteneevewredeersiwer a e AEE a aa Vere 10 Operating System Requirements 25 ccccciseceseeeeerescerceeevecteneeceneeereeseanereenses 10 Driver Installation Options siicsccicsccstsscicscdessccacsevesssvacseesstscsevedsesecserensesennes 11 Onelnstall Installer assciircricinrenari nrima cee viewer nae aa cae 11 Loading the Onelnstall Package cccccce ccc cee eens esate eee sees eset tirrr rtr E EEEE EEEEE EEEE 12 AutoPilot Installer 2 sexceccccriiscdccsatsiastecesheiuntexsshesertecsisssiatseancgeasetuaagourescs 12 Special Consideration Wh
105. est The error log entry immediately following this entry will indicate the TMF function code that was rejected Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 119 Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x11940008 The iSCSI driver received a TMF Abort This may indicate a slow connection to the request for an I O request that is not target Check network connectivity to the present with the driver target for any errors 0x1184000B Firmware returned invalid data in its Reload the firmware configuration iSCSI login and offload are disabled 0x11840002 The iSCSI driver encountered a This failure indicates that the driver version mismatched version of the firmware that is running on the system does not match running on the board This error may the version of the firmware on the board be followed by error codes Correct this by running the installer from the 0x31840001 or 0x31880001 indicating desired version that the iSCSI driver failed to load 0x11840001 The iSCSI driver detected a failure in This failure indicates that the hardware has the hardware during initialization not been initialized or is malfunctioning This This error may be followed by error may also indicate that the firmware is not codes 0x3184000
106. et a jumbo packet value go to the Advanced Properties page in Windows Device Manager For information on how to configure the options through the Advanced Property page see Modifying Advanced Properties on page 49 The path MTU is the maximum MTU that can be used before IP fragmentation occurs taking into account the MTU for the endpoints and all routers between the endpoints To verify the path MTU ping a remote target with an increasing payload size Eventually the IP packet length exceeds the path MTU and the packet fragments This can be seen by using a packet sniffing application such as Ethereal Wireshark or Microsoft Network Monitor IP fragmentation degrades performance dramatically because all fragments must be received and reassembled before delivering the network packet to the upper layer protocol In many cases IP fragmentation may lead to a 10x performance degradation The MTU parameter should be modified on all systems to avoid IP fragmentation for optimal network throughput Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 62 gt lt EMULEX NIC TOE Driver Configuration Typical cases for using the MTU e Server interconnects are typically deployed using jumbo frames This is the most efficient configuration for high bandwidth server to server communication such as Network Attached Storage iSCSI and database transactions e Servers connected to client systems that run desktop o
107. etwork driver automatically performs adaptive interrupt coalescing During periods of low network usage the interrupt delay is set to a minimum for lower latency As the interrupt rate increases the delay is increased This allows the driver to perform more work in a single interrupt which reduces the amount of wasted cycles from additional interrupts The interrupt coalescing algorithm automatically tunes the system to maintain responsiveness and performance in a wide variety of situations including RSS and TOE traffic Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 68 gt lt EMULEX NIC TOE Driver Configuration On slower machines excessive interrupts cause user input to become non responsive and they may not allow sufficient CPU cycles for higher level drivers such as Microsoft iSCSI Initiator and applications This may result in timeouts in upper layer applications because they are never scheduled to run Increasing the level of interrupt coalescing can alleviate these problems Increasing interrupt coalescing may improve total bandwidth for applications that transfer large data buffers Additionally servers running numerous parallel TCP connections may benefit from higher interrupt coalescing Some applications run slower with interrupt coalescing enabled such as applications that depend on the completion of the current network transfer before they post additional work If an application sends and
108. ew statistics for each network device To view statistics for each network device 1 Click Start gt Run gt perfmon to launch the Windows Performance Monitor 2 Right click and select Add Counters to add additional statistics Table 2 6 lists a few statistics to use for troubleshooting performance issues For network performance all the counters from the table are useful Network Interface TCPv4 IPv4 and Processor Table 2 6 Statistics and Fine Tuning Situation Network Interface gt Packets Received Errors Answer Solution If this is incrementing even a small amount a physical problem may exist on the network such as a loose connection or bad cable causing CRC errors in Ethernet packets Find and eliminate the physical problem Network Interface gt Packets Received Discarded If this is incrementing dramatically the computer system may be receiving a lot of unsolicited traffic using network resources IPv4 gt Fragmented Datagrams sec Emulex Drivers for Windows User Manual If this is greater than 0 the computer system is sending or receiving IP fragments This is a serious performance problem See J umbo Packet on page 61 P008011 01A Rev A f 2 Configuration 61 DG EMULEX NIC TOE Driver Configuration Table 2 6 Statistics and Fine Tuning Continued Situation Answer Solution TCPv4 gt Segments Retransmitted sec TCP retransmits indicate that packets are being drop
109. ex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax 133 NoSoftwareFirstinstalls Prohibiting Software First Installations Default False When this parameter is set to true AutoPilot Installer prevents unattended installations from performing software first installations This way you can execute an automated installation on multiple machines in your network but only machines with Emulex adapters actually have Emulex drivers updated or installed If this parameter is omitted from the configuration file or explicitly set to true the page is not displayed AutoPilot Installer uses configuration file parameters to determine the appropriate management mode ReportLocation Setting Up an Installation Report Title and Location The automatically generated file name for this report is report_mm dd yy txt where mm is the month number dd is the day and yy indicates the year You can change only the installation report folder the file name is auto generated In the following example x could be any available drive ReportLocation x autopilot reports installs SilentinstallEnable Enabling Unattended Installation Note Setting the SilentInstallEnable parameter to true in the configuration file is functionally equivalent to supplying the silent switch on the command line You cannot specify
110. f these two driver parameters reduces the number of interrupts per second which improves overall CPU utilization However there is a point where the number of I Os per second is small relative to CoalesceMsCnt and this will slow down the completion process causing performance degradation Examples Test Scenario One e You execute IOMETER with an I O depth of 1 I O per device in a small scale configuration 16 devices In this case the test does not exceed the adapter s performance limits and the number of I Os per second are in the low thousands e Recommendation set CoalesceMsCnt to 0 or leave the default value Test Scenario Two e You execute IOMETER with an I O depth of 48 I Os per device in a small scale configuration 16 devices e Recommendation set QueueDepth to be greater than 48 for example 64 Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 40 gt G EMULEX NIC TOE Driver Configuration NIC TOE Driver Configuration Note Although TCP Offload Engine TOE is supported it is enabled by default Configuring NIC TOE Driver Options The Windows Server NIC TOE driver supports the following OneConnect configurable driver options through the Advanced Property page in Windows Device Manager For information on how to configure the options through the Advanced Property page see Modifying Advanced Properties on page 49 Considerations for Using Universal Multichannel UMC and NIC
111. failures are rare Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information NIC TOE Error and Event Logs Viewing the NIC TOE Error Log For Windows Server operating systems the OneConnect network driver generates error codes in the system event log These error codes can be viewed by using the Event Viewer application To view the error codes Click the Start tab on the bottom of the screen NIC TOE Event Log 1 2 Click Run 3 Type eventvwr and click OK 4 Click Windows Log 5 Click System 6 111 NIC TOE Error and Event Logs Click the be2net error under System Events to show the event details Windows Device Manager generates error log codes if any errors occur during the installation of the NIC driver Each log contains a Message Id Severity and Symbolic Link The Message Id is unique and tracks the error message if not displayed Table A 12 shows the list of error codes the severity of the error the message displayed the meaning of the error and recommended resolutions When reporting a problem with the UCNA to Emulex check the event log and report any of these entries that may be present Table A 12 NIC TOE Event Log Entries Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x0002e 46 Error Device is not supported on Windows 7 Operating System 0x0002d 45 Error Error recovery failed The device
112. ffect e Reboot Requires a reboot of the entire machine before the change takes effect In this case you are prompted to perform a reboot when you exit the utility Note If you are creating custom unattended installation scripts any driver parameter can be modified and included in the script Note If the Adapter Protocol is blank it indicates that the parameter is supported on both LightPulse as well as OneConnect adapters LightPulse only indicates parameters supported only on LightPulse and not on OneConnect adapters FC only indicates parameters supported on non LightPulse FC adapters Emulex Drivers for Windows User Manual P008011 01A Rev A S lt 2 Configuration 31 EMULEX FC FCoE Driver Configuration Most parameters default to a setting that optimizes adapter performance Table 2 1 Storport Miniport Driver Parameters Activation Parameter Definitions Requirement Adapter Protocol AutoMap n AutoMap controls the way targets are assigned Reboot SCSI IDs Discovered targets are assigned persistent SCSI IDs according to the selected binding method Persistent bindings do not take effect with the driver in stand alone mode If set to 0 automap is disabled The OneCommand Manager application persistently sets the SCSI address of a discovered FCP capable FC node target If set to 1 automap by WWNN If set to 2 automap by WWPN If set to 3 automap by DID Value 0 3 Default 2 Class
113. ffloading TCP connections only with IPv4 Note Packet sniffing applications such as Ethereal or Microsoft Network Monitor do not see TCP offloaded packets Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX 3 Troubleshooting 97 Troubleshooting the iSCSI Driver Troubleshooting the iSCSI Driver The following table provides troubleshooting information for the iSCSI driver Table 3 5 Troubleshooting the iSCSI Driver Problem Overall failure Answer Solution Use the iSCSISelect utility to clear the Adapter Configuration See the Emulex Boot Manual for instructions The driver loads successfully but there are event 11 entries in the event log for the iSCSI driver The most common cause is that the UCNA link is down See iSCSI Error Log on Windows Server 2008 on page 116 and look for specific event codes to confirm Unable to create a memory dump file on a system booted over iSCSI Make sure the disk has enough free disk space to create the dump file If a full memory dump is selected the disk must have free space at least equivalent to the amount of physical memory in the system Unable to log in to target from WMI e Ensure that the IP address on the UCNA is valid and the network connection has been set up to reach the target e If login is attempted after discovering the target ensure that the correct UCNA port has been selected for the login The iSCSI WMI GUI
114. g Virtual Port x x VPI x x Description Removing Virtual Port ID Severity Information Log LOG_NPIV verbose Action No action needed informational Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 3 Troubleshooting Q3 Troubleshooting the FC FCoE Driver ELS Messages 1900 1999 Ipfc_mes1900 x x sends ELS AUTH_CMD x with TID x x Description Severity Log Action An ELS_AUTH_CMD is sent Information LOG_FCSP verbose No action needed informational Ipfc_mes1901 x x sends ELS AUTH_RE J ECT x x x x to x x Description Severity Log Action An ELS_AUTH_REJECT is sent Information LOG_FCSP verbose No action needed informational Ipfc_mes1902 Receives x from x x in state x x Description Severity Log Action Receives an ELS_AUTH_CMD Information LOG_FCSP verbose No action needed informational Ipfc_mes1903 Receives ELS AUTH_RJ T x amp x x x Description Severity Log Action Receives an ELS_AUTH_REJECT Information LOG_FCSP verbose No action needed informational Ipfc_mes1904 Authentication ends for x x with status x x d d Description Severity Log Action Authentication is done Information LOG_FCSP verbose No action needed informational Ipfc_mes1905 Authentication policy change for local x 08x x 08x remote x 08x 08x Description Severity Log Action Emulex Drivers for Windows User Manual Authentication policy has been cha
115. iator name is different on multiple controllers You must enter iSCSISelect and save a new initiator name on the first iSCSISelect menu window so that the iSCSI initiator name on all controllers match All logins from the multiple controllers will use the new name See the Emulex Boot Manual for more information P008011 01A Rev A 3 Troubleshooting 98 DG EMULEX Troubleshooting the iSCSI Driver Table 3 5 Troubleshooting the iSCSI Driver Continued Problem Answer Solution When an iscsicli logouttarget This behavior is not specific to the OneConnect UCNA command is issued back to back in a script event 12 errors from the PlugPlayManager are seen in the Windows Event Viewer The error message is similar to this string The device SE ISCSI 00 SCSI Disk Device SCSI Disk amp Ven_SE_ ISCSI amp Prod_00 amp Rev_3 64 5 amp 17659873 amp 2 amp 020000 disappeared from the system without first being prepared for removal Pl On a system running Windows 2008 There is no workaround for this issue or Windows 2008 R2 the iSCSI driver fails to load after many iterations of enable disable from Device Manager Because the system failed to allocate contiguous uncached extension memory the iSCSI driver failed to load and an attention icon is displayed next to the OneConnect iSCSI device The Device Status shows This device cannot start Code 10 and an Event 11 error is logged in the Windows system event
116. iguration Protocol DHCP Recommendations Description of Mandatory and Optional Parameters Table B 1 describes the parameters used in the data string for option 43 Table B 1 Data String Parameters for Option 43 Parameter Description Field Type lt TargetIP gt A valid IPv4 address in dotted decimal notation Mandatory lt TargetTCPPort gt A decimal number ranging from 1 to 65535 inclusive Optional The default TCP port is 3260 lt LUN gt A hexadecimal representation of the LUN of the boot Optional device By default LUN 0 is assumed to be the boot LUN It is an eight byte number which should be specified as a hexadecimal number consisting of 16 digits with an appropriate number of zeroes padded to the left if required lt TargetName gt A valid iSCSI name of up to 223 characters Mandatory lt dinitiatorName gt A valid iSCSI iqn name of up to 223 characters If it is Optional not provided the default initiator name generated by the UCNA based on its MAC address is used lt HeaderDigest gt Either E the header digest is enabled or D the header Optional digest is disabled lt DataDigest gt Either E the data digest is enabled or D the data Optional digest is disabled lt AuthenticationType gt D authentication is disabled E one way CHAP is Optional Examples enabled the user name and secret must be specified by non DHCP means or M mutual CHAP is enabled the user name and passwo
117. imney enabled This parameter appears disabled if the firmware installed on your device does not support TCP connection offload Upgrading the firmware may resolve this issue View the Statistics property page to ensure that TCP connection offload is working UDP Checksum Offload IPv4 Disabled RX and TX Enabled default Windows 2008 Window 2008 R2 Windows 2012 User Datagram Protocol UDP offload checksum settings offload the transmit and or receive IPv4 UDP checksum computation RX Enabled Offloading checksums increases system efficiency TX Enabled UDP Checksum Disable Windows 2008 User Datagram Protocol UDP offload checksum Offload IPv6 RX and TX Enabled default RX Enabled TX Enabled Window 2008 R2 Windows 2012 settings offload the transmit and or receive IPv6 UDP checksum computation Offloading checksums increases system efficiency VLAN Identifier Not Present default 1 to 4094 Emulex Drivers for Windows User Manual Windows 2008 Window 2008 R2 Windows 2012 If selected the adapter adds a VLAN tag to all transmitted packets and only receives packets with the matching VLAN tag Note This property should not be used when the Emulex Teaming Driver is enabled In that case VLAN configuration should be performed in the Teaming Driver application Note This property should not be used with Hyper V In that case the Microsoft Hyper V Manager shoul
118. indow 2008 R2 and or receive IPv4 TCP checksum computation default Windows 2012 Offloading checksums increases system efficiency RX Enabled TX Enabled TCP Checksum Disable Windows 2008 TCP Checksum Offload IPv6 offloads the transmit Offload IPv6 RX and TX Enabled default RX Enabled TX Enabled Emulex Drivers for Windows User Manual Window 2008 R2 Windows 2012 and or receive IPv6 TCP checksum computation Offloading checksums increases system efficiency P008011 01A Rev A gt G EMULEX 2 Configuration 46 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name TCP Connection Offload IPv4 Acceptable Values Enabled Disabled default Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012 Definition If TCP offload is enabled the device offloads the entire TCP protocol including ACK processing retransmits and timers Applications that prepost receive buffers before the data arrives may avoid data copies in the receive path which substantially increases the system efficiency and data rates Windows does not offload TCP connections if any of the following are enabled e Network Load Balancing e IPSEC e Network Address Translation NDIS 5 1 Intermediate Drivers TCP offload must be enabled in the Windows operating system with the shell command netsh int tcp set global ch
119. ing overhead and CPU usage when standard 1514 byte sized frames are in use Maximum Number of RSS Queues 4 16 8 default Note For 0Ce11102 UCNAs only Windows 2008 R2 Windows 2012 When RSS is enabled this parameter controls the number of receive queues Typically this is left at the maximum value Windows reduces the number of queues as necessary based on the number of installed CPU cores This value may be reduced during performance tuning for a particular application It is possible that system performance may improve by limiting the number of RSS queues Greater than 4 RSS queues requires Advanced Mode Support be enabled in the BIOS controller configuration VMQ Enabled default Disabled Note For OCe11102 UCNAs only VMQs require Windows Server 2008 R2 or later with Hyper V Virtual Machine Queues are dedicated hardware receive queues for virtual machines that filter receive packets based on the destination MAC address and or VLAN Receive buffers can be allocated for each queue from VM memory This improves network throughput by distributing processing of network traffic for multiple VMs among multiple processors It reduces CPU utilization by offloading receive packet filtering to NIC hardware VMQs prove beneficial when 4 or more VMs are in use VMQ Lookahead Split Enabled default Disabled Emulex Drivers for Windows User Manual Note For 0Ce11102 UCNAs only Windo
120. installed 2399141920 0x8F000020 GUI Mode only You chose to stop installation because a recommended QFE or Service Pack was not installed 2399141899 0x8F00000B Unattended installation did not find any drivers of the type specified in the config file 2399141900 0x8F00000C A silent reboot was attempted but according to the operating system a reboot is not possible 2399141901 0x8F00000D GUI Mode only A driver package download was cancelled 2399141902 0x8F00000E Non Enterprise No adapters were found in the system 2399141903 0x8F00000F A required QFE or Service Pack was not detected on the system 2399141836 0x8F000030 AutoPilot Installer was not invoked from an account with Administrator level privileges 2391419952 0x8F000040 AutoPilot Installer has detected unsupported adapters on the system 2399141968 0x8F 000050 Unattended software first installations are disallowed 2399141984 0x8F000060 You cancelled APInstall before any driver utility installation occurred 2399142000 0x8F000070 You cancelled APinstall after driver utility installation occurred Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 139 gt G EMULEX AutoPilot Installer Installation Reports Table D 1 Unattended Installation Error Codes Continued Error Code Hex Description 2399142032 0x8F000090 APInstaller encountered an error while parsing the command line
121. ion error indicates that the system has problems but user intervention is not required An invalid fabric command type is an example of a malfunction error An object allocation failure is an example of a command error If set to 0 all errors are logged If set to 1 command level errors are logged If set to 2 malfunction errors are logged If set to 3 severe errors are logged Value 0 3 Default 3 NodeTimeout n The node timer starts when a node that is a Dynamic discovered target or UCNA becomes unavailable If the node fails to become available before the NodeTimeout interval expires the operating system is notified so that any associated devices if the node is a target can be removed If the node becomes available before NodeTimeout expires the timer is canceled and no notification is made Value 1 255 seconds or 0x0 OxFF hex Default 30 0x1E Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 36 DG EMULEX FC FCoE Driver Configuration Table 2 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol QueueDepth n QueueDepth requests per LUN target see Dynamic QueueTarget parameter If you expect the number of outstanding I Os per device to exceed 32 then you must increase to a value greater than the number of expected Os per device up to a value of 254 If the QueueDepth value is set too l
122. is disabled and an interrupt triggers for each response The value range for CoalesceRspCnt is 1 255 decimal or 0x1 OxFF hex The default value is 8 Note A system restart is required to make changes to CoalesceMsCnt and CoalesceRspCnt Performance Testing There are three driver parameters that need to be considered and perhaps changed from the default for better performance testing QueueDepth CoalesceMsCnt and CoalesceRspCnt Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration gt lt 39 gt lt EMULEX FC FCoE Driver Configuration QueueDepth If the number of outstanding I Os per device is expected to exceed 32 increase this parameter to a value greater than the number of expected I Os per device up to a maximum of 254 The QueueDepth parameter defaults to 32 If 32 is set and not a high enough value performance degradation may occur due to Storport throttling its device queue CoalesceMsCnt CoalesceMsCnt defaults to zero If you are using a performance evaluation tool such as IOMETER and if you expect the I O activity to be greater than 8000 I Os per second set CoalesceMsCnt to 1 and reinitialized with an adapter reset or system reboot CoalesceRspCnt CoalesceRspCnt defaults to 8 For all other values up to the maximum of 63 the adapter does not interrupt the host with a completion until either CoalesceMsCnt milliseconds has elapsed or CoalesceRspCnt responses are pending The value o
123. istry configuration for new driver parameter entries The invalid entry must be removed or corrected See Driver Parameters for Windows on page 90 for the correct range of values Oxle Error Failed to map Base Address Register failing driver load The iSCSI driver was unable to load because it was unable to map one or more PCI Base Address registers This failure may indicate a low memory condition or a hardware error Ox1f Error Hardware initialization has failed error code A Emulex Drivers for Windows User Manual The hardware initialization has failed This error causes the driver load to fail The error code included in the event log entry identifies the specific point of failure This failure indicates that the hardware has not been initialized or is malfunctioning This may also indicate that the firmware is not running correctly P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information 124 iSCSI Error and Event Log Table A 14 iSCSI Error Log Entries on Windows Server 2008 R2 and 2012 Continued Message ID Severity Message Recommended Resolution 0x20 Warning Initial memory allocation The driver failed to allocate its complete failed driver is running with memory requirement and attempts to load with reduced capabilities reduced capabilities The total number of targets available is reduced This message indicates a low memory c
124. ive and install them across your local area network LAN Network based installation is often used in conjunction with unattended installation and scripting This allows you to configure and install the same driver version on all the hosts in a storage area network SAN Unattended installation You can run the driver kit installers and AutoPilot installer with no user interaction from a command line or script Unattended installation works for both hardware first and software first installations and all driver kits An unattended installation operates in silent mode sometimes referred to as quiet mode and creates an extensive report file with installation status Complete driver and utilities documentation may be downloaded from the Emulex website www emulex com Special Consideration When Updating the Emulex Storport Miniport FC FCoE Driver Any pre existing SCSIport Miniport or FC FCoE Port drivers are replaced overwritten when you install the Emulex Storport Miniport FC FCoE driver The Emulex Storport Miniport FC FCoE driver is installed for every adapter on your server Installing the Emulex Storport Miniport FC FCoE driver also deletes all customized driver parameters persistent bindings logical unit number LUN masking and LUN mapping Emulex recommends that you make a note of your current settings before you install the Emulex Storport Miniport FC FCoE driver so that you can update your customized driver parameters Or you ca
125. iver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Preferred NUMA Node Acceptable Values Not present or a value from 0 65535 Optional No default setting is set Supported Operating Systems Windows 2008 Window 2008 R2 Windows 2012 Definition Most modern multi socket servers have separate memory controllers for each CPU socket These systems have non uniform memory access NUMA latencies for a given CPU core to access the local versus remote memory node By setting this property the driver attempts to use both memory and CPU cores from the given NUMA node If the Perferred NUMA node is not set the driver uses the preferred NUMA node as specified by the computer s BIOS For best performance the network applications should try to use memory and CPU affinity from the same NUMA node This level of tuning is primarily noticeable when multiple adapters are running Transmit CPU Not present or a value from 0 through number of CPUs 1 Optional No default setting is set Windows 2008 Window 2008 R2 Windows 2012 Sets the CPU to be used to process transmit completions By default the driver intelligently chooses a CPU in the system so this parameter should only be set for advanced performance tuning TCP Checksum Disable Windows 2008 TCP Checksum Offload IPv4 offloads the transmit Offload IPv4 RX and TX Enabled W
126. l warning or error The source of the events indicates the service name and every event includes a unique ID and a symbolic name Table A 14 iSCSI Error Log Entries on Windows Server 2008 R2 and 2012 Message ID 0x02 Severity Info Message Driver loaded successfully Recommended Resolution N A 0x04 Error Firmware version does not match with driver version The driver version that is running on the system does not match the version of the firmware on the UCNA Install a driver that is compatible with the firmware 0x05 Warning Port link is down check connection to UCNA Check the links to the UCNA 0x06 Info Port link is up N A 0x07 Error Link down timeout expired on the port all targets are lost The link on the UCNA is down for a period exceeding the link down timeout LDTO value If the UCNA has a connection to the target event log entries from the disk subsystem indicate that the drives were lost If any I O was in progress the system may see I O errors or failures Check the links to the UCNA If the link is reestablished any sessions that previously existed are reestablished and the devices are available for I O 0x08 Error Target with session id N failed to connect within the configured timeout A connection to the target was lost for a period exceeding the Extended Timeout ETO The error log entry includes the session ID of the target th
127. le on 1Gb s and 2 Gb s adapters Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 34 gt G EMULEX FC FCoE Driver Configuration Table 2 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol ExtTransferSize ExtTransferSize is an initialization time LightPulse adapters parameter that affects the maximum SGL that the only including the driver can handle which determines the LPe16000 HBAs maximum I O size that a port will support If set to 0 the maximum default transfer size is 512KB for all controller models If set to 1 the maximum transfer size is 1MB If set to 2 the maximum transfer size is 2MB If set to 3 the maximum transfer size is 4MB Value 0 3 Default 0 disabled FrameSizeMSB n FrameSizeMSB controls the upper byte of receive Reset FrameSize if issued in PLOGI This allows the FrameSize to be constrained on 256 byte increments from 256 1 to 2048 8 Value 0 8 Default 0 InitTimeout n Determines the number of time out seconds Reboot during driver initialization for the link to come up If the link fails to come up by InitTimeout driver initialization exits but is still successful If the link comes up before InitTimeout the driver sets double the amount for discovery to complete Value 5 30 seconds or 0x5 0x1E hex Default 15 seconds OxF LimTransferSize Limits maximum transf
128. lid Completion Queue Entry SLI4 mode Malfunction Errors Table A 2 Malfunction Errors Bits 0 7 0x05 Interpretation SET_VAR command failed 0x11 SET_VAR command failed reinitialization 0x21 Spurious mailbox command interrupt 0x31 Unrecognized mailbox command completion 0x32 Duplicate link attention event tag unchanged 0x33 Invalid link attention no link state indicated 0x34 Duplicate link attention link state unchanged 0x35 Error reading common service parameters for port 0x36 Error reading common service parameters for fabric 0x37 Error reading common service parameters for nport 0x3B Failed to create node object 0x3C PRLI initiation failure 0x42 Exhausted retries on FLOGI 0x45 ELS command rejected 0x49 Exhausted retries on PLOGI Ox4E World Wide Port Name mismatch on ADISC Ox4F World Wide Node Name mismatch on ADISC 0x50 ADISC response failure 0x55 LOGO response failure 0x57 PRLI to non existent node Ox5A PRLI response error Ox5F CT command error 0x62 Name server response error 0x66 State Change Notification registration failure Ox6A Unrecognized ELS command received Ox6F Received PRLI from un typed source 0x73 Failed to pend PRLI for authentication Emulex Drivers for Windows User Manual P008011 01A Rev A Appen
129. lot Installer later on your system See Option 2 on page 16 for more information Installing the Driver Kit To install the driver kit 1 Do one of the following e Download and install the single package from the Emulex website to your system e Download the driver kit installer from the Emulex website to your system Note The name of the driver kit installer depends on the current version identifier 2 If you plan to create Windows Pre installation Environment PE disk images or perform boot from SAN installations unpack all drivers On the driver kit installer Welcome page select the Unpack all drivers checkbox Checking this checkbox unpacks all the drivers into the My Documents directory 3 Choose one of three options e For an automatic interactive installation see Option 1 Automatically Run the AutoPilot Installer on page 16 e For control of all interactive installation settings see Option 2 Run the AutoPilot Installer Separately on page 16 e Foran unattended installation with AutoPilot Installer see Unattended Driver Installation on page 19 Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 15 gt lt EMULEX AutoPilot Installer Overview AutoPilot Installer Overview AutoPilot Installer runs after the driver kit and the OneCommand Manager application are installed AutoPilot Installer can be installed Immediately after the driver kit installation has com
130. low control to achieve loss less network traffic Using separate hardware interfaces in the driver allows each priority to progress at a different rate or pause temporarily without affecting the other priorities When ETS is enabled all configuration regarding bandwidth and priority flow control should be performed on the network switch The adapter will learn the configuration using the DCBx protocol P008011 01A Rev A 2 Configuration 49 DG EMULEX NIC TOE Driver Configuration Configuring Windows Server NIC TOE Driver Parameters The Windows Server NIC TOE drivers support driver options through the Advanced Property page in Windows Device Manager Modifying Advanced Properties Modify the advanced properties for the driver for Windows with the Windows Device Manager For more information on advanced properties see Network Driver Performance Tuning on page 59 To modify the advanced properties 1 Enter the Windows Device Manager e Click Start gt Control Panel gt System and click the Device Manager hyperlink Or e Click Start gt Run then type devmgmt msc and click OK The Windows Device Manager is displayed E Server Manager Acton View Hep AmE B fen ee e RS E eve aroge OaLsIONEDPD ions 7 scr yay DELL610 8E3 PA Device Manager je Diagnostics H UR Computer More Actions amp fE Event viewer Eca Disk drives By Display adapters GH Reliability and Performance fe A DEE a
131. ltiple RSS queues if enabled Receive Side Scaling RSS scales receive processing over multiple CPUs in parallel This scaling typically improves application performance however it tends to increase CPU usage on low end machines RSS is only supported on two primary adapters per device Note For additional PCI functions RSS does not appear in the Properties List TCP Offload Optimization Optimize Latency Optimize Throughput default Windows 2008 Window 2008 R2 Windows 2012 This parameter only applies to TCP connection offload which must be enabled in the Protocol Offloads section Most applications perform better with TCP Offload Optimization set to Optimize Throughput which handles large data transfers with minimal CPU impact Setting this parameter to Optimize Latency causes receive data to be delivered to the application without waiting for a TCP PSH This causes additional receive indications that typically decrease total throughput Transmit Buffers 64 256 inclusive The default setting is 256 Emulex Drivers for Windows User Manual Windows 2008 Window 2008 R2 Windows 2012 Transmit Buffers sets the number of Ethernet transmits that may be posted to the hardware at any given time The default value is sufficient to achieve maximum performance Reducing this value conserves system memory P008011 01A Rev A gt G EMULEX 2 Configuration 45 NIC TOE Dr
132. lure Error LOG_ELS verbose Check remote NPORT for potential problem P008011 01A Rev A aw 3 Troubleshooting 81 gt G EMULEX Troubleshooting the FC FCoE Driver Discovery Log Messages 0202 0262 Ipfc_mes0202 Start Discovery Link Down Timeout x x initial PLOGICount d Description Device discovery rediscovery after FLOGI FAN or RSCN has started TMO is the current value of the soft link time It is used for link discovery against the LinkDownTime set in parameters DISC CNT is number of nodes being discovered for link discovery RSCN CNT is number of nodes being discovered for RSCN discovery There will be value in either DISC CNT or RSCN CNT depending on which discovery is being performed Severity Information Log LOG_DISCOVERY verbose Action No action needed informational Ipfc_mes0204 Discovered SCSI Target WWN word 0 x x WWN word 1 x x DID x x RPI x x Description Device discovery found SCSI target Severity Information Log LOG_DISCOVERY verbose Action No action needed informational Ipfc_mes0214 RSCN received Word count d Description Received RSCN from fabric Severity Information Log LOG_DISCOVERY verbose Action No action needed informational Ipfc_mes0215 RSCN processed DID x x Description Processed RSCN from fabric Severity Information Log LOG_DISCOVERY verbose Action No action needed informational Emulex Drivers for Windows User Manual P008011 01A Rev
133. mation 118 iSCSI Error and Event Log Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x138e0103 The iSCSI driver failed an IOCTL This error may indicate an incorrect request because the number of scatter configuration option for the iSCSI driver It may gather elements required for the also indicate a low memory condition IOCTL buffer exceeded the firmware limit Following this error log entry the next entry will indicate the IOCTL opcode and the payload length requested 0x138d0101 The iSCSI driver detected an error This may indicate a target isin error or may offloading the iSCSI connection The point to transient network connectivity issues operation will be retried again It may also indicate a firmware error Following this error log entry the next entry will indicate the session handle and the firmware error code 0x12990013 The iscsi driver did not receive an e Verify that the iSCSI target is certified by iSCSI command window update within Microsoft Check for errors reported at the 25 seconds during I O operations target The Emulex iSCSI UCNA is only Following this error log entry the next supported with certified targets entry will indicate the session handle e Check for software updates at the target where this error occurred The iSCSI vendor s website If applicable update the driver will trigger a session recovery software on
134. may exist in the AutoPilot configuration file The first items in this section are the driver parameters to be used regardless of how the questions are answered This is followed by a subsection that contains questions these may be vendor specific questions A line containing QUESTIONS marks the start of the subsection and the end of it is marked by a line containing TENDQUESTIONS Within the question subsection there can be as many questions as needed Each question uses the format question question explanation answer0 answerl answer2 answern Where e question contains the text of the question to be asked e explanation contains brief text to help explain the question The explanation appears below the question in a smaller font If there is no explanatory text empty quotes must be used in its place e answer0 contains the 1st answer to be displayed in the drop down list e answerl contains the 2nd answer to be displayed in the drop down list e answern contains the nth answer to be displayed in the drop down list For each question there can be as many answers as needed For each answer there must S be a corresponding answer section with its corresponding driver parameters listed beneath it The answer uses the format Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX Appendix D AutoPilot Installer Command Line and
135. meter separate the settings by one or more spaces and put quotes around the entire APargs expression For example the command line all on one line lxdrv fc fcoe lt version gt exe APargs SilentRebootEnable True localDriverLocation d drivers new Storport results in the AutoPilot Installer being run as APInstall exe SilentRebootEnable True localDriverLocation d drivers new Storport Parameter values that contain spaces such as path names must be enclosed in quotes To add such a setting to APargs you must insert backslashes before the quotes around the value and then add quotes around the entire APargs expression For example the command line all on one line lxdrv fc fcoe lt version gt exe APargs ReportLocation C Documents and Settings Administrator My Documents reports results in AutoPilot Installer being run as APInstall exe ReportLocation C Documents and Settings Administrator My Documents reports If you have many parameters to pass to the AutoPilot Installer or if you want to do so repeatedly then it may be less error prone to run the utility kit installer interactively delay AutoPilot Installer execution and then run the AutoPilot Installer command yourself The procedure for doing so is described in Option 2 Run the AutoPilot Installer Separately on page 16 and Unattended Driver Installation on page 19 Emulex Drivers for Windows User Manual P008011 01A Rev A
136. meter Value Default False The ForceRegUpdate driver parameter setting determines whether existing driver parameters are retained or changed when you update the driver By default all existing driver parameter settings are retained The ForceRegUpdate parameter does not affect any existing persistent bindings To set up an installation to remove the existing driver parameters from the registry and replace them with parameters specified in the AutoPilot Configuration file set this parameter to true Note You can use this setting for attended installations with the AutoPilot Installer wizard if you modify the AutoPilot Configuration file in an AutoPilot Installer Kit LocalDriverLocation Specifying Location to Search for Drivers Default Drivers The default Drivers folder is located in the same folder as AutoPilot Installer You can specify a local location that is to be searched for drivers during unattended installations The location may be a local hard drive or a network share Removable media are not searched Example LocalDriverLocation d drivers new Storport Note On x64 and 32 bit systems the path specified by LocalDriverLocation must contain at least one instance of an FC FCoE iSCSI and NIC driver AutoPilot Installer automatically selects the most recent revisions that it finds For IA64 systems only FC and FCoE drivers are supported no iSCSI or NIC drivers are included for installation Emul
137. mmand line overriding the configuration file settings as appropriate e Opens the installation report file e Validates the operating system e Discovers adapters and records the adapter inventory in the report file e Verifies mandatory configuration file parameters e Searches for drivers to install based on the LocalDriverLocation setting in the configuration file e If appropriate verifies that the selected driver is a different type than the currently installed driver or a more recent version of the currently installed driver e Copies the driver parameters from the configuration file into the registry for the driver s coinstaller FC and FCoE drivers only e Installs or updates the driver e Rediscovers adapters and records the updated adapter inventory in the report file e Records the final results and closes the report file There are two ways to perform an unattended installation e Install the driver silently e Run the driver kit installer separately Option 1 Install the Driver Silently Run the driver kit installer from a command prompt or script Specify the q quiet command line option For example lxdrv fc fcoe lt version gt exe q Note The name of the driver kit installer depends on the current version identifier For other command line options see AutoPilot Installer Command Line and Configuration File Parameters on page 129 Option 2 Run the Driver Kit Installer Separately 1
138. module OptionFlags x x Description Driver discovery process is being initialized with internal flags as shown Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0401 Initializing SLI module Deviceld x x NumMSI d Description PCI function with device id and MSI count as shown is being initialized for service level interface Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0405 Service Level Interface SLI 2 selected n Description Service Level Interface level 2 is selected Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0406 Service Level Interface SLI 3 selected n Description Service Level Interface level 3 is selected Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0436 Adapter not ready hostStatus x x Description The adapter failed during powerup diagnostics after it was reset Severity Error Log LOG_INIT verbose Action This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting 86 DG EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes0442 Adapter failed to init CONFIG_PORT mbxStatus x x Description Adapter initialization failed when issuing CONFIG_PORT mailbox comm
139. mps from CPU to CPU but it only runs on one CPU at a time Each processor is busy only 25 percent of the time The total reported CPU usage of the system is about 25 percent perhaps more if other applications are also using the CPU This is a sign that RSS may help performance If the same four processor server uses RSS there are four parallel executing DPCs one on each processor The total CPU usage that is available for networking processing is increased from 25 percent to 100 percent Some server machines and some network traffic profiles do not benefit from RSS Because the non offloaded TCP stack includes a data copy during receive processing it is possible that memory bandwidth will limit performance before the CPU In this situation the CPU usage is very high while all processors wait for memory accesses To overcome this problem you can reduce the number of RSS CPUs or disable RSS entirely Poor RSS behavior is typical only in network performance testing applications that receive data but perform no other processing For other applications RSS allows the application to scale other processing tasks across all CPUs thereby improving overall performance RSS offers the most benefit for applications that create numerous short lived connections These applications are typically CPU limited instead of network bandwidth limited For information on modifying the RSS Queues parameter see Configuring NIC TOE Driver Options on page 4
140. n active path or active node as quickly as possible This configuration requires that the iSCSI driver s LDTO and ETO parameters be set to 0 If the iSCSI target is in Active Standby failover mode then the iSCSI driver must wait for the target side failover operation to complete before reporting device unavailability to the operating system For such configurations the driver s ETO must be set to the amount of time the iSCSI target needs to complete its failover operation Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting 77 General Troubleshooting gt EMULEX 3 Troubleshooting There are several circumstances in which your system may operate in an unexpected manner The Troubleshooting section contains reference tables on event codes and error messages and provides information regarding unusual situations Table 3 1 General Troubleshooting General Troubleshooting Problem The operating system fails to install or does not successfully install the driver Answer Solution Verify that the operating system is supported by the driver Windows Device Manager shows a code 10 or code 39 with a yellow or red exclamation point on the device The firmware image does not match the installed device drivers or the firmware is corrupt Using the OneCommand Manager application or one of the WinPE offline or online utilities install a version of firmware that is compatible with the driver
141. n and command level errors are logged e If set to 2 both severe and malfunction errors are logged e Ifset to3 only severe errors are logged Note Set LogError to 1 if you are troubleshooting SAN connectivity or device discovery issues Format of an Error Log Entry An error log entry will take the form of an event This event is described by e Date date entry was logged e Source elxstor e Time time entry was logged e Category none e Type error e Event id 0 e User N A e Computer name of computer Emulex Drivers for Windows User Manual P008011 01A Rev A 101 gt G EMULEX Appendix A Error and Event Log Information FC FCoE Error and Event Logs Error Codes Tables Severe Errors Table A 1 Severe Errors Bits 0 7 0x00 Interpretation Invalid link speed selection SLI2 3 mode 0x01 READ_REV failed SLI2 3 mode 0x02 Invalid adapter type LightPulse 0x03 Invalid adapter type LightPulse 0x04 CONFIG PORT failed 0x06 READ_CONFIG failed 0x07 CONFIG RING 0 failed 0x09 CONFIG_RING 1 failed 0x08 CONFIG RING 2 failed Ox0A CONFIG_RING 3 failed 0x0B INIT_LINK failed SLI2 3 mode 0x0C INIT_LINK failed SLI2 3 mode 0x0D READ_REV failed SLI2 3 mode Ox0E Invalid adapter type LightPulse OxOF Invalid adapter type LightPulse 0x10 CONFIG_PORT failed reinitialization 0x12 RE
142. n use the AutoPilot Installer default parameters Note This update process can leave files associated with older driver kits on your system After running AutoPilot Installer and restarting your system you may be required to uninstall old driver or utility program entries Follow the procedures in Uninstalling Emulex Driver Kits on page 26 Ensure you delete only previous driver versions Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 1 Installation 14 Driver Kit Installer Overview Driver Kit Installer Overview The driver kit installer is an executable file that self extracts and copies the following software onto your system e FC FCoE protocol drivers Manage communication and data transfer between applications and I O devices using Emulex adapters as agents There are four separate drivers for Emulex adapters o FC o FCoE o iSCSI o Ethernet e ElxPlus driver Supports the OneCommand Manager application persistent binding and LUN mapping and masking If you are creating Windows PE disk images or performing boot from SAN installation you must select the Unpack All Drivers option instead of running AutoPilot Installer See step 2 of Installing the Driver Kit in the following procedure After the driver kit is installed you have two options e Automatically run AutoPilot Installer immediately This is the default option See Option 1 on page 16 for more information e Run AutoPi
143. nadancad tsk EnA E E EE EA E EERE 57 Using Interactive Mod ssesiiiereianraverioi iaieaenii o inii kiaii nea EEEE ARENE i 58 Parameter Help sv scseeiasseckas nien yeacnuceedesednauewet bes E KESI E AEREA EEDE 58 Network Driver Performance Tuning cixvasccccdscerkbavedccsenetcidstdestdeediiaatarseekinerds 59 Optimizing Server Hardware and BIOS Configuration ccecceee cee eee eee e rneer 59 Windows Server Network Driver c cece eect eter tenia 60 Checksum Offloading and Large Send Offloading LSO cccseeeeeeeeeeeeeeeeeeeaes 63 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic ccecce 63 TEP Offloading TOE Jatsiin inn a o E EEEE 64 Receive Window Auto Tuning and Compound TOP 67 Interrupt CoaleSCing 0 nri enn ee ete 67 CPU Binding Consideration Sierrei sranani anniina E EEADERS AANA 68 Single TCP Connection Performance SettingS cceccee rererere 69 SCSI Driver Configuration sissisccsssscttsscscssetcsscescsecens EnnEL IE ssasesensesnesesanees 69 Configuring iSCSI Driver OOUMIIS lt i cacetenteedvettvectavsentuncentedtientberpeetenseesentinencs 69 Backing Up and Editing the Registry ccccccee cent eee esse sees eeatesaeeeeeeeeeeeneeanees 69 Interrupt Moderation Policy Settings iicisiiecscreiscrtescresiexwind extucewersnisesvevaataees 71 Creating Non Bootable Targets ccccccccececce reese tenes esas sean ee saeeesaenesaenesaaes 72 Emulex Drivers for Windows User
144. nd or to send pause frames Tx Enable P008011 01A Rev A gt G EMULEX 2 Configuration 42 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Supported Name Acceptable Values Operating Systems Definition Interrupt None Windows 2008 The network device uses interrupt moderation Moderation Static 90k Int sec Window 2008 R2 algorithms to reduce the total amount of CPU i cycles spent processing interrupts which increases salle 70k Int sec Windows 2012 efficiency for the system However interrupt Static 50k Int sec moderation increases the latency of each send Static 40k Int sec and receive It should only be disabled when short Static 30k Int sec latencies are more important than efficient CPU utilization Static 25k Int sec aA The None setting disables all delays to minimize stalle 20k Int sec latency Static 15k Int sec The static settings use a constant interrupt delay Static 10k Int sec to avoid any spikes in interrupt rate Static 5k Int sec The adaptive settings cause the driver to Adaptive 70k Int sec dynamically maintain a target interrupt rate If CPU usage is too high choose a higher adaptive AGSRIINE ORD INE SEG value to increase the interrupt delays and reduce Adaptive 40k Int sec the rate of interrupts Adaptive 30k Int sec default Adaptive 20k Int sec Adaptive 15k Int sec
145. nded with the specific status of Check Condition the ASC ASCQ information provided in bytes 0x12 and 0x13 will allow you to find out what status is being reported by the target and determine if there is an action that can be performed to return the device to functional status Nameserver Response Code 0x98 This code is useful in determining if the expected number of targets ina SAN configuration are being presented by the nameserver to the requesting adapter The number in byte 0x11 is the number of targets returned to the nameserver query made by the adapter if the number of targets does not match expectations examine the SAN configuration found in the switch tables and if that information shows targets or devices still missing check connections between the switch ports and those devices Context Allocation Failures There are a number of event codes for which the interpretation contains the phrase context allocation failure these types of events are referring to the internal memory constructs of the Emulex Storport Miniport driver and as such are intended for Emulex design engineer s information If a customer encounters such an event they should contact Emulex support for analysis and determination if that particular event may be an indicator of a failed adapter or of some problem with interaction between the adapter the Emulex Storport Miniport driver the host operating system and the host memory Note Context allocation
146. nerivcedeae oE R E EEEE ESEE EE 101 Error Codes ableSieverrideccdeiecriedatiniancdived evectsau E R 102 Viewing the FC FCoE Event L0G iccicicrrrocmotdueseeeniors enbrarwervigbintwecanesvanwiawntet 107 Event Log Interpretation rema erine Eia EEEE a E EEDE EUERE SEEEN EE 107 Additional Event Log Information ssssssssssssesrriirrertr tiiin iene 107 ASC ASCO nooiens e iei desu e SOES EIE 109 Additional Notes on Selected Error Codes eeceeeee eee ne nett tee e nett ene ea ene 110 Emulex Drivers for Windows User Manual P008011 01A Rev A 5 DE EMULEX Table of Contents 6 NIC TOE Error and Event LOGS ssssssssunnnnnnnnnsnunnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 111 Viewing the NIC TOE Error LOg sssssssssssssrrsrrrererrerrstsrrrrrrrrrerrrsrrrrrrerere 111 NIC TOE Event LOG s icctesnevisecareressrtcantacscteenemchencentsucsuseceteroseicecenniatees 111 ISCSI Error and Event LOrE aa 115 Viewing the iSCSI Error and Event Log on Windows Server 2008 cceeeeeee es 115 iSCSI Error Log on Windows Server 2008 cccccceccce eect ee eeeeeeaeeeeaeeeeaneeeenes 116 Viewing the iSCSI Error Log on Windows Server 2008 R2 and 2012 0cceee ees 120 Appendix B Configuring iSCSI through DHCP ssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 125 Dynamic Host Configuration Protocol DHCP Recommendations sceseeeseeeeae 125 Vendor Specific Option 43 cscceeccicesiieeskentsadeahe easieenhenesaeneaeers somtenasnsieeens
147. ng the link speed to auto detect Warning LOG_LINK_EVENT verbose None required Ipfc_mes1303 Link Up event tag x x link speed dG topology 0 Pt2Pt 1 AL d Description Severity Log Action Remarks Emulex Drivers for Windows User Manual A link up event was received It is also possible for multiple link events to be received together Error LOG_LINK_EVENT verbose If numerous link events are occurring check physical connections to the FC network Ipfc_mes1304 is recorded if Map Entries gt 0 and the corresponding mode and SEVERITY level is set P008011 01A Rev A gt EMULEX 3 Troubleshooting 91 Troubleshooting the FC FCoE Driver Ipfc_mes1305 Link down even tag x x Description Severity Log Action A link down event was received Error LOG_LINK_EVENT verbose If numerous link events are occurring check physical connections to the FC network Ipfc_mes1306 Link Down timeout Description Severity Log Action The link was down for greater than the configuration parameter HLinkTimeOut seconds All I O associated with the devices on this link will be failed Warning LOG_LINK_EVENT verbose Check adapter cable connection to SAN Tag Messages 1400 1401 Ipfc_mes1400 Tag out of range Contextindex x x MaxIndex x x ulpCommand x x Description Severity Log Action Firmware has generated an i
148. nged Information LOG_FCSP verbose No action needed informational P008011 01A Rev A 3 Troubleshooting Q4 SG EMULEX Troubleshooting the NIC TOE Drivers Troubleshooting the NIC TOE Drivers The following table provides troubleshooting information for the NIC TOE drivers Table 3 3 Troubleshooting the NIC TOE Drivers Problem Answer Solution Performance is not as expected The UCNA may be installed in a PCle slot other than an 8x PCle slot or a Gen2 slot Verify that the UCNA has been properly installed and that the system is properly set for 8x Gen2 PCle operation If TOE is enabled and performance is not as high as expected the operating system may not offload TOE connections For more information see Improving Performance with TCP Offload on page 71 There are frequent event log entries Unload and reload the driver to reset available target IDs Ensure for link changes or statistics that that the SAN configuration is correct prior to reloading the driver show more than expected CRC This clears the driver s consistent binding table and frees target errors IDs for new target nodes The driver fails to load and an There may not be enough memory installed in the system to event log entry states that the provide sufficient memory for all devices installed in the system driver failed to load due to memory Try installing more memory if possible constraints Unpredictable results occur when
149. ns on including drivers with your Windows PE images e Minimum 512 MB memory Note Check the Emulex website for required updates to the Windows operating system or the Emulex drivers Driver Installation Options There are two ways that you can install the Windows drivers the OnelInstall Installer OnelInstall package or AutoPilot Installer You must choose one of the options e Onelnstall contains all of the Emulex Windows drivers Emulex Storport Miniport and Network Driver Interface Specification NDIS Miniport drivers and the OneCommand Manager application utility in a single download package e AutoPilot Installer for Emulex Storport Miniport and NDIS Miniport drivers provides installation options from simple installations with a few mouse clicks to unattended installations that use predefined script files and text only installations Onelnstall Installer The Onelnstall Package is an executable file that self extracts and copies the following software onto your system e All compatible protocol drivers to manage communication and data transfer between applications and I O devices using Emulex adapters as agents There are four separate drivers for Emulex adapters o FC o FCoE o iSCSI o Ethernet e ElxPlus driver Supports the OneCommand Manager application persistent binding and LUN mapping and masking e OneCommand Manager application for the Emulex adapters Onelnstall is available for download from th
150. nvalid response Error LOG_LINK_EVENT verbose Review hardware configuration Contact Emulex Technical Support Ipfc_mes1401 Invalid tag Contextindex x x ulpCommand x x Description Severity Log Action Emulex Drivers for Windows User Manual Firmware has generated an invalid response Error LOG_LINK_EVENT verbose Review hardware configuration Contact Emulex Technical Support P008011 01A Rev A 3 Troubleshooting 92 DG EMULEX Troubleshooting the FC FCoE Driver NPIV Messages 1800 1899 Ipfc_mes1800 NPIV FDISC failure VPI x x Error x x Reason x x Description Virtual Port fails on a FDISC to the switch with the error and reason listed Severity Error Log LOG_NPIV verbose Action Check to ensure the switch supports NPIV Ipfc_mes1801 Memory allocation failure for NPIV port x x Description Fails to allocated the block of memory for the Virtual Port Severity Error Log LOG_NPIV verbose Action Check to ensure system has sufficient kernel memory Ipfc_mes1802 Exceeded the MAX NPIV port x x Description Exceeded the number of Virtual Port allows on the adapter Severity Error Log LOG_NPIV verbose Action Reduce the number of Virtual Ports Ipfc_mes1803 Virtual Port x x VPI x x successfully created Description Virtual Port ID is successfully created Severity Information Log LOG_NPIV verbose Action No action needed informational Ipfc_mes1804 Removin
151. o sections grouped according to related commands There are six main sections e AUTOPILOT ID Configuration Identification e AUTOPILOT CONFIG Software Configuration e STORPORT CONFIGURATION Configuration Prompts Vendor Specific Questions e STORPORT QFES QFE Checks e STORPORT PARAMS Setting Up FC Driver Parameters e SYSTEM PARAMS Setting Up System Parameters Each section begins with a heading The heading is required even if there are no settings in the section The only section not required is the Installation Prompts section which has the heading STORPORT CONFIGURATION That section cannot exist if AutoPilot Installer runs in silent mode You must delete or comment out that entire section for unattended installation Lines that begin with a semicolon are comments Some of the comments are sample settings To use the setting remove the semicolon Using the Windows Environment Variable ProgramFiles You can use the Windows ProgramFiles environment variable in the LocalDriverLocation and ReportLocation strings within the configuration file This allows you to specify strings in a driver independent manner allowing the same configuration file to be used on different systems where Windows may have been installed on different drives To use this option ProgramFiles must be the first component specified in the string The portion of the string that follows is appended to the contents of the ProgramFil
152. of the Custom property page the Emulex NIC reports the PCI Express link parameters and the maximum supported parameters For example installing a 8x device in a 4x PCI Express slot cuts the available PCI Express bandwidth in half The PCI Express MTU and Read Request size are also reported and these may be configurable in the system BIOS for the computer The performance of the main memory is the other major concern for networking throughput The ideal situation is using high speed memory with all memory channels populated per CPU typically 3 or 4 DIMMs per CPU socket For the ideal performance the same DIMM size should be used in each memory channel to allow perfect memory channel interleaving Features such as memory sparing or memory mirroring dramatically decrease the memory bandwidth of the system and cause drops TCP connection offload may lead to increased drops as a result of no memory If TCP connection offload is used enabling flow control may reduce the drops Alternatively disabling TCP connection offload may improve performance P008011 01A Rev A 2 Configuration 54 gt G EMULEX NIC TOE Driver Configuration Table 2 4 NIC TOE Driver Properties Statistics Continued Statistic Name Description CRC Errors The number of packets dropped as the result of CRC errors on the layer 2 Ethernet packet In products that expose multiple PCIE functions per Ethernet port this statistic is only incremented for the lowes
153. on 6 Reboot the system when prompted to do so After rebooting the Microsoft isCSI DSM claims all iSCSI discovered disks The MPIO GUI shows device id MSFT2005iSCSIBusType_0x9 under the MPIO Devices tab The Disk Manager does not show duplicate disks You can configure load balancing policies on the LUN from the Device Manager after you click on the disk and select the MPIO tab Logging into Targets for Multipath Support After you have successfully installed and enabled MPIO support on a Windows Server you must log in to the target This section describes the steps to log into iSCSI targets through the WMI GUI For information on using the iSCSISelect utility to log into an iSCSI target see the Emulex Boot Manual To log in to a target using WMI 1 Select the Enable multi path in the Log On to Target window This must be selected for every target to be logged in for MPIO Use the Advanced tab to select the specific UCNA port to use for login 2 After the target login is complete select the target and click on the Details or Properties button depending on the Windows operating system to see the multiple sessions connected Maximum Transmission Unit MTU for iSCSI Connections Because the Emulex OneConnect UCNA is a multi function adapter the MTU settings for iSCSI functions are different than the ones for NIC functions For iSCSI there is no explicit way to configure MTU from the OneCommand Manager application Instead thi
154. on policy parameter controls the rate of interrupts for the UCNA For more information see Interrupt Moderation Policy Settings on page 71 Iqd 128 1 Emulex Drivers for Windows User Manual 255 The LUN queue depth parameter configures the number of concurrent commands to a logical unit via Storport API StorPortSetDeviceQueueDepth The Iqd parameter also sets the maximum number of concurrent commands allowed per LUN P008011 01A Rev A gt EMULEX Table 2 7 iSCSI Driver Options Continued 2 Configuration iSCSI Driver Configuration 71 Parameter large_io 64 Default Value Minimum Value 64 Maximum Value 512 Interrupt Moderation Policy Settings The Interrupt Moderation policy settings control the rate of interrupts for UCNA hardware By default the driver implements an interrupt moderation scheme that is based on the I O load and the interrupt rate The default setting for im_policy tries to vary the interrupt rate between 3500 to 10000 interrupts per second In addition the iSCSI driver allows other configuration settings as shown in Table 2 8 Table 2 8 im_policy Settings Description Maximum transfer size in a single I O request in KB By default the iSCSI driver supports a maximum of 64 KB of data and 16 scatter gather entries in a single I O request This option enables support for 512 KB of data in a single I O request If an application issu
155. ondition 0x21 Info Target Reconnected for N A Session id N 0x22 Info Interrupt Redirection N A capability is enabled 0x23 Warning Interrupt Redirection Update the firmware to the latest version capability is not supported by this firmware Update your firmware 0x24 Info Interrupt Redirection N A capability is not supported by this hardware 0x26 Warning Logical link on the The iSCSI function may have been disabled in OneConnect Port is down the PXESelect application If you disabled it traffic is disallowed on this intentionally you can ignore this message function 0x27 Error Firmware returned invalid Reload the firmware data in its configuration iSCSI login and offload are disabled 0x28 Warning Error Recovery is not being An Unrecoverable Error UE has occurred but attempted Adapter is no longer functional Emulex Drivers for Windows User Manual UE recovery is not enabled A system reboot is required to make the adapter operational again P008011 01A Rev A SXC EMULEX Appendix B Configuring iSCSI through DHCP 125 Dynamic Host Configuration Protocol DHCP Recommendations Appendix B Configuring iSCSI through DHCP Dynamic Host Configuration Protocol DHCP Recommendations If you are using the DHCP server to obtain an IP address for the UCNA Emulex recommends that you set up a reservation A reservation assigns a specific IP address based on the MAC address of the UCNA If you do not reserve an IP Ad
156. onfiguration Parameters DiagEnable Running Diagnostics Note The DiagEnable parameter cannot be specified on the command line it must be specified within the configuration file Default True By default AutoPilot Installer runs its diagnostics after all driver installation tasks have been completed To disable this function set this parameter to false ForceDriverTypeChange Forcing a Driver Type Change Default False When installing a driver set this parameter to true to cause silent mode installations to update or install the Storport Miniport driver on each adapter in the system without regard for the currently installed driver type replacing any installation of the SCSIport Miniport or FC Port driver Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax 132 ForceDriverUpdate Forcing a Driver Version Update Default False By default if the same version of the driver is already installed an unattended installation proceeds with installing only the utilities To force a driver update even if the same version of the driver is installed set this parameter to true Note ForceDriverUpdate applies to unattended installations only in interactive installations this parameter is ignored Instead you are asked if the driver should be updated ForceRegUpdate Forcing an Update of an Existing Driver Para
157. ontext allocation 0x7C Menlo initialization error 0x7D Menlo initialization error 0x7E Menlo initialization error 0xA0 Failed to initialize adapter port OneConnect 0xA1 Failed to initialize adapter port LightPulse 0xCO Insufficient revision level for STORPORT SYS OxC1 Failed to allocate miniport un cached extension OxC2 Insufficient un cached extension space 0xC3 Port initialization failure OneConnect 0xC4 Port initialization failure LightPulse 0xC5 Utility mailbox command error 0xC6 SLI4 Pre initialization failure 0xD3 NPIV memory allocation failure OxFO Unresponsive adapter port SLI4 mode OxF4 ULP Unrecoverable Error low part SLI4 mode OxF5 ULP Unrecoverable Error high part SLI4 mode OxF6 ARM Unrecoverable Error SLI4 mode OxF7 READ_NV failed SLI4 mode OxF8 READ_NV failed SLI4 mode OxF9 READ_REV failed SLI4 mode OxFA READ_CONFIG failed SLI4 mode OxFB Failed to post header templates SLI4 mode OxFC Invalid Completion Queue Entry SLI4 mode Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX Appendix A Error and Event Log Information 104 FC FCoE Error and Event Logs Table A 1 Severe Errors Continued Bits 0 7 OxFD Interpretation Invalid Completion Queue Entry SLI4 mode OxFE Inva
158. or Service under the general tab click Change 2 Type your initiator name and click OK Logging into a Target Using the Microsoft Software Initiator If you install the Software Initiator you must select the UCNA initiator when logging into the target To do this 1 From the Targets tab select the target and click LogOn 2 Click Advanced Under the General Tab everything appears as default 3 Select the UCNA initiator as the local adapter select your source IP and click OK Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX 2 Configuration iSCSI Driver Configuration Windows Multipath I O Support This section describes the installation and login processes for multipath I O support on Windows Server operating systems Multipath Support on Windows Server 2008 2008 R2 and 2012 On Windows Server 2008 2008 R2 and 2012 MPIO must be installed from the Server Manager After installing the MPIO feature you must launch and configure the MPIO GUI to enable multipath support for iSCSI devices The following steps describe the installation process for setting up Microsoft iSCSI DSM and enabling multipath I O for all iSCSI devices irrespective of their vendor and device IDs You can use the MPIO GUI to configure DSMs other than Microsoft iSCSI DSM Also you can use the GUI to enable multipath support for a specific vendor ID and device ID For details on these topics refer to the Microsoft TechNet Library on
159. ow Older Versions of the Emulex Storport Miniport Driver To uninstall or update an earlier version of the Storport Miniport driver prior to version 1 20 you must remove the registry settings for the adjunct driver prior to manually installing a new driver To remove the adjunct driver registry settings 1 Browse to the Storport Miniport driver version 1 20 or later driver kit that you downloaded and extracted 2 Double click on the deladjct reg file A Registry Editor window appears to confirm that you want to execute deladjct reg 3 Click Yes The elxadjct key is removed from the registry Windows Server 2012 The Emulex Storport Miniport and PLUS ElxPlus drivers are uninstalled using the device manager Note On Windows 2012 after the message Warning you are about to uninstall this device from your system is displayed you must select the checkbox Delete the software for this device in order to uninstall the driver Emulex Storport Miniport Driver To uninstall the Emulex Storport Miniport driver in Windows Server 2012 1 Select Server Manager gt Dashboard gt Tools gt Computer Management gt Device Manager 2 Double click the adapter from which you want to remove the Storport Miniport driver A device specific console window is displayed Select the Driver tab 3 Click Uninstall and click OK to uninstall Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 29 gt G EMULEX
160. ow a performance degradation can occur due to driver throttling of its device queue QueueDepth supports more than 1000 outstanding commands per port Value 1 254 or 0x1 OxFE hex Default 32 0x20 QueueTarget QueueTarget controls I O depth limiting on a per Dynamic target or per LUN basis If set to 0 depth limitation is applied to individual LUNs If set to 1 depth limitation is applied across the entire target Value 0 1 or 0x0 0x1 hex Default 0 0x0 RmaDepth n RmaDepth sets the remote management buffer Reboot queue depth The greater the depth the more concurrent management controls can be handled by the local node Value 8 64 or 0x8 0x40 hex Default 16 0x10 Note The RmaDepth driver parameter pertains to the functionality of the OneCommand Manager application ScanDown n If set to 0 lowest AL_PA lowest physical disk Reboot FC Only ascending AL_PA order If set to 1 highest AL_PA lowest physical disk ascending SEL_ID order Value 0 1 Default 1 Note This option applies to private loop only in DID mode Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 37 DG EMULEX FC FCoE Driver Configuration Table 2 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol SLIMode n If set to 0 autoselect firmware use the latest Reboot LightPulse Only fi
161. ped by the receiving system or in a network switch Ideally reduce retransmits to 0 Processor gt Processor Time If CPU usage is high try to enable all available offloads such as TCP offload checksum offloads and use j umbo packets J umbo Packet The jumbo packet setting in the registry determines the maximum Ethernet packet size It includes the Ethernet frame header typically 14 bytes but excludes the trailing Cyclic Redundancy Check CRC The standard packet size is 1514 bytes plus a 4 byte trailing CRC Vendors use many terms that refer to this same quantity such as packet size frame size or Maximum Transmission Unit MTU The MTU is the Ethernet packet payload size This does not include the Ethernet frame header or the trailing CRC The standard MTU is 1500 bytes corresponding to a 1514 byte packet size plus a 4 byte trailing CRC Historically any 1514 byte frame is a standard packet while any frame larger than 1514 bytes is called a jumbo packet Windows Server attempts to standardize the terminology across vendors so the jumbo packet parameter refers to the byte size of the packet The Windows Server driver supports several jumbo packet values The larger packet size provides better throughput and CPU usage Typically all devices on the network including switches must be configured for the larger size The drawbacks of using jumbo packets are interoperability and increased memory usage on the server To s
162. perating systems typically use standard 1500 byte frames Most desktop systems do not support jumbo packets e Servers that need both high performance server to server communication and client access can be configured with jumbo frames with Path MTU Discovery enabled Path MTU Discovery is enabled by default in Windows Server and it allows TCP connections to negotiate the optimal packet size that avoids IP fragmentation Flow Control The UCNA supports IEEE 802 3x standard flow control which uses control packets to temporarily pause the transmission of packets between two endpoints These control messages are point to point they are not forwarded by switches or routers You must configure both endpoints for flow control The UCNA can either respond to flow control packets by temporarily pausing transmits or send flow control PAUSE packets when the transmitter is overwhelming the system s receive bandwidth For best performance flow control must be enabled on the switches as well as on UCNAs Receive and transmit flow control are on by default Flow control is not available if using FCoE on a converged network adapter In this situation priority pause is negotiated with the network switch and used only for the FCoE protocol packets The NIC function can also use priority pause if supported by the switch This requires tagging packets in the operating system with the correct priority value and enabling ETS in the driver properties Configu
163. pleted At a later time using an interactive installation Through an unattended installation AutoPilot Installer provides Note Command line functionality Initiates an installation from a command prompt or script Configuration settings can be specified in the command line Compatibility verification Verifies that the driver to be installed is compatible with the operating system and platform Driver installation and update Installs and updates drivers Multiple adapter installation capability Installs drivers on multiple adapters alleviating the need to manually install the same driver on all adapters in the system Driver diagnostics Determines whether the driver is operating properly Silent installation mode Suppresses all screen output necessary for unattended installation AutoPilot Installer does not allow you to install the driver if the minimum Windows service pack or Microsoft Storport driver update is not installed Starting Installers from a Command Prompt or Script When a driver kit installer or AutoPilot Installer is run from a command prompt or command script batch file the Windows command processor does not wait for the installer to run to completion As a result you cannot check the exit code of the installer before the next command is executed Emulex recommends that for command line invocation always use the start command with the wait option This causes the command processor to w
164. properly Check the UCNA and reinstall the firmware if required 0x0e Warning iSCSI error was detected on session A ExpCmdSn B MaxCmdsSn C The iSCSI driver received an invalid iSCSI Command Sequence Number update from the target The event log entry indicates the session handle MaxCmdSN and ExpCmdsSN e Verify that the iSCSI target is certified by Microsoft Check for errors reported at the target The Emulex iSCSI UCNA is only supported with certified targets e Check for software updates at the target vendor s website If applicable update the software e Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware OxOf Warning The iSCSI target on session id N failed to open the command window within configured timeout The iSCSI driver did not receive an iSCSI command window update for up to 25 seconds during I O operations The event log entry indicates the session handle on which the error occurred The iSCSI driver triggers a session recovery on the session and continues e Verify that the iSCSI target is certified by Microsoft Check for errors reported at the target The Emulex iSCSI UCNA is only supported with certified targets e Check for software updates at the target vendor s website If applicable update the software e Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware 0x10
165. r folder is not removed so you can still view installation history and the drivers that have been installed on the system You can delete the reports folder at any time if you want Emulex Drivers for Windows User Manual P008011 01A Rev A SG EMULEX 1 Installation 27 Removing Emulex Driver Kits and Drivers Windows Server 2012 To uninstall a driver kit on a Windows Server 2012 system 1 Select Start gt Control Panel 2 From the Control Panel select Programs gt Uninstall a Program 3 Select one of the following in the program list and click the Uninstall icon in the tool bar above the program list If you have User Access Control enabled click Continue when asked for permission e Emulex FC kit 2 xx xxx e Emulex FCoE kit 2 xx xxx e Emulex NIC 4xx xxx e Emulex iSCSI kit 4 xx xxx 4 Click Yes when prompted to remove the kit When the kit is removed from the system click OK To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files x86 folder on a 64 bit system 2 Navigate to Emulex AutoPilot Installer 3 Run one or more of the following batch files e uninstall fc_kit bat uninstall fc kit e uninstall_cna_kit bat uninstall fcoe kit e uninstall_iscsi_kit bat uninstall iscsi kit e uninstall_nic_kit bat uninstall nic kit 4 The proper driver kits are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installer folder is not
166. ransfer size is limited to 500 KB If set to 1 on a OneConnect adapter or an Emulex 16 Gb adapter the max transfer size is limited to 1012 KB If set to 2 the max transfer size is limited to 2036KB Use ConfigScale 2 if connecting to tape devices on a OneConnect or an Emulex 16 Gb port If set to 3 which is the best setting if you are running performance benchmarks in a non production environment the max transfer size is limited to 2036KB Values 0 1 2 and 3 Default 1 Activation Parameter Definitions Requirement Adapter Protocol ConfigScale ConfigScale sets the memory footprint profile in OneConnect and accord with the anticipated use case on a per Emulex 16 Gb port basis The default value of 1 is considered to adapters DiscoveryDelay n DiscoveryDelay controls whether the driver waits for n seconds to start port discovery after link up If set to 0 immediate discovery after link up If set to 1 or 2 the number of seconds to wait after link up before starting port discovery Value 0 2 seconds decimal Default 0 Emulex Drivers for Windows User Manual Dynamic P008011 01A Rev A 32 2 Configuration 33 DG EMULEX FC FCoE Driver Configuration Table 2 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol DriverTraceMask The DriverTraceMask parameter is only available Dynamic on operating
167. rations that support multiple PCI functions per port generally configure flow control from the switch or blade configuration application Since flow control is an Ethernet port property it must be the same for all PCI functions using the same port If multiple PCI functions are exposed for a single 10 Gb s Ethernet port such as ina blade configuration the flow control parameter must be set the same on all adapters for the port The results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10 Gb s port Examples Flow control greatly improves the following situations e The UCNA is installed in 4x PCI Express slot or an underpowered server system If the PCI Express bus does not provide 10 Gb s of throughput due to chipset limitations or the bus width the UCNA cannot maintain 10 Gb s of incoming receive data It starts dropping packets quickly In this situation it may be beneficial to enable receive flow control in the UCNA and enable flow control in the attached switch for all devices This helps to slow down the transmitters Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration gt lt 63 gt lt EMULEX NIC TOE Driver Configuration e The UCNA transmits to 1 Gb devices especially non TCP protocol If the UCNA transmits to a 10 Gb s switch with attached 1 Gb clients the UCNA may overwhelm the switch The switch is then forced to start dropping packet
168. rds must be specified by non DHCP means D is the default setting The following is an example of default initiator name and data digest settings 0 2 3261 000000000000000E ign 2009 4 com 12345 iscsi 192 168 67890 E228 e Target IP address 192 168 0 2 e Target TCP port 3261 e Target boot LUN 0x0E e Target iqn name iqn 2009 04 com 1234567890 e Initiator name Not specified Use the initiator name that is already configured or use the default name if no initiator name is already configured e Header digest Enabled e Data digest Not specified assume disabled e Authentication type One way CHAP Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix B Configuring iSCSI through DHCP 127 gt lt EMULEX Dynamic Host Configuration Protocol DHCP Recommendations The following is an example of default TCP port and mutual CHAP settings iscsi 192 168 0 2 000000000000000E ign 2009 4 com 1234567890 ge to sa e Target IP address 192 168 0 2 e Target TCP port Use default from RFC 3720 3260 e Target boot LUN 0x0E e Target iqn name iqn 2009 04 com 1234567890 e Initiator name Not specified Use the initiator name that is already configured or use the default name if no initiator name is already configured e Header digest Enabled e Data digest Disabled e Authentication type Mutual CHAP Emulex Drivers for Windows User Manual P008011 01A Rev A
169. re does not The firmware and the driver are not support TCP offload functionality compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers 0x0024 36 Error The device firmware does not The firmware and the driver are not support network functionality compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers 0x0023 35 Warning The Ethernet link is down due toa The Ethernet link is down due to the remote fault remote partner signaling a fault Check the peer device for errors 0x0022 34 Warning The Ethernet link is down due toa The Ethernet link is down due toa local fault link down event detected at the OneConnect driver 0x0021 33 Informational Network device is operating in Gen2 For best performance install the mode and installed in a 4x UCNA in an 8x Gen2 PCle slot Note PCI Express slot A 16x slot will not provide any additional performance 0x0020 32 Informational The network device is operating in For best performance install the Gen2 mode and installed in a 1x UCNA in an 8x Gen2 PCle slot Note PCI Express slot A 16x slot will not provide any additional performance 0x001f 31 Informational The network device is operating in For best performance install the Gen1 mode and installed in a 8x UCNA in an 8x Gen2 PCle slot Note PCI Express slot A 16x slot will not provide any additional performance 0x001e 30 Informational
170. recommended that you disable any low power processor states and low power settings for PCI Express e On certain AMD systems it is possible the intelppm sys driver isenabled and should not be To query this system driver s run state log in as administrator and at the command line type sc query intelppm If the results indicate that the intelppm driver is running you must disable it At the command line type sc config intelppm start disabled On all systems it may be necessary to set the power options to High Performance See the operating system documentation for details Monitoring TCP Offloads To monitor TCP offloads in a command window type netstat t This command indicates the offload state for each TCP connection of the system Windows Server 2008 and later versions allows TCP offloads in more scenarios than previous versions of Windows Server In particular TCP offloads may occur with the Windows firewall enabled Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX TCP Offload Failure 3 Troubleshooting 96 Troubleshooting the NIC TOE Drivers The following table lists common reasons why TCP offloads do not occur and their suggested fixes Table 3 4 Troubleshooting TCP Offload Failures Reasons for No TCP Offload Chimney offload is disabled on the system Solutions For Windows Server 2008 and Windows Server 2008 R2 To determine whether Chimney offload is enabled or disa
171. rget in question Ipfc_mes0730 Ipfc_mes0737 SCSI check condition SenseKey x x ASC x x ASCQ x x SrbStatus x x Description Severity Log Action See Also The issued FCP command resulted in a Check Condition Warning LOG_FCP verbose Review SCSI error code values Ipfc_mes0730 Ipfc_mes0747 Target reset complete PathId x x Targetld x x Did x x Description Severity Log Action Remark Emulex Drivers for Windows User Manual A target reset operation has completed Warning LOG_FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0713 P008011 01A Rev A gt EMULEX 3 Troubleshooting QQ Troubleshooting the FC FCoE Driver Ipfc_mes0748 Lun reset complete Pathlid x Targetld x x Lun x x Description Severity Log Action Remark A LUN reset operation has completed Warning LOG_FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0703 Ipfc_mes0749 Abort task set complete Did x x SCSIId x x Description Severity Log Action Remark A task management has completed Warning LOG_FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0701 Link Log Messages 1302 1306 Ipfc_mes1302 Invalid speed for this board d forced link speed to auto Description Severity Log Action The driver is re initializi
172. ript Example sssssssssssnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 139 Emulex Drivers for Windows User Manual P008011 01A Rev A SXC EMULEX List of Figures List of Figures Figure 1 1 AutoPilot Installer Warning Software First Installation ccccccccccccccccs 18 Figure 2 1 Partial View of Windows Device Manager cceceeceete eee eee eee en eee ees 49 Figure 2 2 NIC TOE Advanced Properties in Windows Server 2008 ccceeee eee eee 50 Figure 2 3 NIC TOE Statistics Properties in Windows Server 2008 cceeeee eee 51 Figure A 1 Event PropertieS cccccc cece cece e eee erent ee eee eee scenes rnnr EErEE EEEE EEEn EE EES 100 Fig re A 2 ISCSI EMOL aetec bh oncaentes cence erid peren EE EAEE Sau E EEEREN 116 Emulex Drivers for Windows User Manual P008011 01A Rev A gt G EMULEX List of Tables Table 2 1 Table 2 2 Table 2 3 Table 2 4 Table 2 5 Table 2 6 Table 2 7 Table 2 8 Table 2 9 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table A 1 Table A 2 Table A 3 Table A 4 Table A 5 Table A 6 Table A 7 Table A 8 Table A 9 Table A 10 Table A 11 Table A 12 Table A 13 Table A 14 Table B 1 Table C 1 Table D 1 Emulex Drivers for Windows User Manual storport Miniport Driver Parameters cccciccecccseccesscwesncecepeecbesevatcenaecseawcns 31 Recommended Settings for I O Coalescing eeeeeeeeee sees teen teeta 38 Windows Server 2008 2008 R2 and 20
173. rmware installed If set to 2 implies running the adapter firmware in SLI 2 mode If set to 3 implies running the adapter firmware in SLI 3 mode Value 0 2 and 3 Default 0 SrbTimeout SrbTimeout limits the SRB timeout value to 60 seconds when set to 1 or enabled This is a non displayed parameter where it has to be set manually into the registry This option alters the I O timeout behavior where an I O will be returned in a max timeout of 60 seconds on some long I O timeout If set to 1 enabled If set to 0 disabled Values 0 1 Default 0 Topology Topology values can be 0 to 3 Reset FC Only If set to 0 0x0 FC Arbitrated Loop FC AL If set to 1 0x1 PT PT fabric If set to 2 0x2 FC AL first then attempt PT PT If set to 3 0x3 PT PT fabric first then attempt FC AL Topology fail over requires v3 20 firmware or higher If firmware does not support topology fail over options 0 2 and 1 3 are analogous Value 0 3 Default 2 0x2 TraceBufSiz n TraceBufSiz sets the size in bytes for the internal Reboot driver trace buffer The internal driver trace buffer acts as an internal log of the driver s activity Value 250 000 2 000 000 or 0x3D090 0x1E8480 hex Default 250 000 0x3D090 Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration gt lt 38 gt lt EMULEX FC FCoE Driver Configuration Server Performance with FC Drivers
174. rt ID and timeout value Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0260 Stop node timer on NPortlid x x SCSIId x x Description Discontinuing timer for reconnected target with NPort ID and SCSI ID Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0262 Node timeout on NPortld x x SCSIId x x Description Disconnected NPort ID SCSI ID has failed to reconnect within timeout limit Severity Error Log LOG_ELS verbose Action Review system configuration Mailbox Log Messages 0310 0326 Ipfc_mes0310 Mailbox command timeout HBA unresponsive Description A Mailbox command was posted to the adapter and did not complete within 30 seconds sync 0 asynchronous mailbox command is issued 1 synchronous mailbox command is issued Severity Error Log LOG_MBOX verbose Action This error could indicate a software driver or firmware problem If no I O is going through the adapter reboot the system If these problems persist report these errors to Technical Support Ipfc_mes0326 Reset HBA HostStatus x x Description The adapter has been reset Severity Information Log LOG_MBOX verbose Action No action needed informational Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting 85 DG EMULEX Troubleshooting the FC FCoE Driver INIT Log Messages 0400 0463 Ipfc_mes0400 Initializing discovery
175. rt lived TCP connections do not show a performance improvement using TCP offload Windows Server provides control over the applications and TCP ports that are eligible for TCP offload using the netsh tool Refer to the Microsoft documentation for these netsh commands netsh interface tcp add chimneyapplication state disabled application lt path gt netsh interface tcp add chimneyport state disabled remoteport 23 localport Note The netsh commands require the Windows firewall to be running If the firewall is disabled all applications and ports added with the netsh commands may fail to connect TCP Offload Optimization Settings The UCNA supports an option for optimizing TCP connection offload characteristics for throughput or latency This option is available through the Advanced Property Page See Configuring NIC TOE Driver Options on page 40 for the TCP Offload Optimization settings The default option is Optimize Throughput which produces the best throughput characteristics for certain types of traffic flows This configuration setting has produced the best results on benchmarks such as Chariot ntttcp and iperf The other available option Optimize Latency improves the latency characteristics for the class of traffic flows not ideally suited for offloaded by sacrificing throughput These are applications that typically do not pre post receive buffers at a rate fast enough to keep up with the traffic flow causing the re
176. rted an error upgrading Server 2 if not errorlevel 2147483650 goto unsupported echo Configuration file missing goto server2ok unsupported if not errorlevel 2147483649 goto older echo Unsupported operating system detected older2 if not errorlevel 2001 goto none2 cho The driver found is the same or older than the existing driver goto server2ok none2 if not errorlevel 1248 goto noreport2 echo No adapter found goto server2ok snoreport if not errorlevel 110 goto nocfg2 echo Could not open installation report file goto server2ok nocfg2 if not errorlevel 87 goto badcfg2 echo Invalid configuration file parameters goto server2ok badcfg2 if not errorlevel 2 goto server2ok echo No appropriate driver found Emulex Drivers for Windows User Manual P008011 01A Rev A 140 Appendix D AutoPilot Installer Command Line and Configuration File Parameters 141 gt EMULEX Command Script Example server2ok Emulex Drivers for Windows User Manual P008011 01A Rev A
177. s because although it may receive a 10 Gb s stream the client can only sink a 1 Gb stream In this situation it may be beneficial to enable transmit flow control in the UCNA and enable flow control for the 10 Gb s switch port Note If multiple PCI functions are exposed for a single 10 Gb s Ethernet port such as in a blade configuration the flow control parameter must be set the same on all adapters for the port The results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10 Gb s port For information on modifying the Flow Control parameter see Configuring NIC TOE Driver Options on page 40 Checksum Offloading and Large Send Offloading LSO The UCNA supports IP TCP and UDP checksum offloading All these protocols are enabled by default You can disable offloading through the Windows Device Manager Advanced Properties Disabling checksum offloading is only useful for packet sniffing applications such as Ethereal or Microsoft Network Monitor on the local system where the UCNA is installed and monitored When packets are sniffed transmit packets may appear to have incorrect checksums because the hardware has not yet calculated them The UCNA supports transmit LSO which allows the TCP stack to send one large block of data and the hardware segments it into multiple TCP packets This is recommended for performance but it can be disabled for packet sniffing applications LSO sen
178. s value is auto negotiated by the firmware Before establishing a TCP connection for an iSCSI Login the iSCSI firmware issues an ICMP Echo with a large payload to the iSCSI target If Jumbo Frames has been enabled on all the switches leading to the target as well as on the target interface and if there is a successful ICMP Echo reply the iSCSI firmware uses Jumbo Frames for that connection The MTU used in this case is 8342 bytes If the large ping request is unsuccessful the firmware defaults to non jumbo mode and uses an MTU size of 1514 bytes The Max MTU value is displayed in the OneCommand Manager application for the iSCSI controller under the Port Information Tab on the Max MTU field The TCP MSS used for an active iSCSI connection is displayed in the OneCommand Manager application in the TargetSessions screen on the TCPMSS field iSCSI Error Handling The goal of iSCSI error handling is to be tolerant of link level and target level failures up to configured timeout values so that I O errors are not seen by the application or operating system The error handling is triggered under the following conditions Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 75 DG EMULEX iSCSI Driver Configuration e Loss of immediate link to the UCNA such as a cable disconnect or port failure The UCNA firmware detects the loss of link and notifies the driver When this happens the driver queues the I O requests in
179. se Action Check the fabric connection Ipfc_mes0101 FLOGI completes successfully NPortid x x RaTov x EdTov x x Description An ELS FLOGI command that was sent to the fabric succeeded Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0102 PLOGI completes to NPortld x x Description The adapter performed an N _port_login PLOGI into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0103 PRLI completes to NPortlid x x TypeMask x x Fcp2Recovery x x Description The adapter performed a process login PRLI into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Emulex Drivers for Windows User Manual P008011 01A Rev A 3 Troubleshooting 79 DG EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes0104 ADISC completes to NPortid x x Description The adapter performed a discover address ADISC into the remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0105 LOGO completes to NPortld x x Description The adapter performed a LOGO into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0112 ELS command x x received from NPortld x x Description Received the specific ELS command from a remote NPort Severity Information Log
180. ser Manual P008011 01A Rev A gt EMULEX Appendix D AutoPilot Installer Command Line and Configuration File Parameters 138 AutoPilot Installer Exit Codes AutoPilot Installer Exit Codes AutoPilot Installer sets an exit code to indicate whether an installation was successful or an error occurred These exit codes allow AutoPilot Installer to be used in scripts with error handling In unattended installations AutoPilot Installer sets the following exit codes Table D 1 Unattended Installation Error Codes Error Code Hex Description 0 0x00000000 No errors 2399141889 0x8F000001 Unsupported operating system detected 2399141890 Ox8F 000002 The AutoPilot Configuration file is not found 2399141891 0x8F000003 Disabled adapters detected in the system 2399141892 Ox8F 000004 The selected driver is 64 bit and this system is 32 bit 2399141893 0x8F000005 The selected driver is 32 bit and this system is 64 bit 2399141894 Ox8F 000006 Installation activity is pending AutoPilot Installer cannot run until it is resolved 2399141895 0x8F000007 GUI Mode only You cancelled execution because you did not wish to perform a software first install 2399141896 0x8F000008 No drivers found 2399141897 0x8F000009 One or more adapters failed diagnostics 2399141904 0x8F000010 GUI Mode only You chose to install drivers even though a recommended QFE or Service Pack was not
181. shows the target state as connected but no LUNs are seen from the disk manager Verify that the UCNA name used to connect to the target matches the UCNA name configured on the iSCSI target Multipath configuration shows duplicate LUNs on the disk manager Ensure that MPIO software is installed and the login options have selected the MPIO flag On Windows Server 2008 and Windows Server 2008 R2 Operating Systems the server role must be set up for Multipath See the Emulex Boot Manual for more information on MPIO Multipath configuration takes a long time to fail over or failover does not occur Ensure that link down timeout LDTO settings and extended timeout ETO settings have been configured for MPIO These values must be set to 0 For more information see Configuring LDTO and ETO on Windows Server on page 75 Sendtargets to an IET target fails because it violates the iSCSI specification If you still want to add an IET target you must add the target manually This issue affects Sendtargets only The following POST error message appears Initiator iSCSI Name mismatch Please use iSCSISelect to set a single name for all controllers Press lt Ctrl gt lt S gt to enter iSCSISelect Reboot required Emulex Drivers for Windows User Manual In the iSCSI BIOS the Emulex iSCSI initiator name may be different if more than one OneConnect UCNAs are in the system This message appears if the iSCSI init
182. sing the clock speed of the memory interface to the processor can be critical for achieving the best networking performance This interface may be the front side bus FSB Intel s QPI or AMD s HyperTransport Emulex Drivers for Windows User Manual P008011 01A Rev A gt EMULEX 2 Configuration NIC TOE Driver Configuration 60 Windows Server Network Driver Table 2 5 describes ways to use various OneConnect driver properties and Microsoft Windows properties to performance tune a system Table 2 5 Windows Server Performance Tuning Situations Situation There are a large number of short lived TCP connections such as web server or e mail server Answer Solution Enable RSS increase number of RSS queues and disable TCP offload There are large data transfers such astoa file server web server with file downloads or an FTP server Use TCP connection offload There are large data transfers such as toa backup server Enable jumbo packets and use TCP offload There is a small server struggling to keep up with larger servers on the network Disable RSS enable TCP offload enable jumbo packets and increase the interrupt moderation to allow fewer interrupts per second There is a general purpose server such as Active Directory server DHCP server or a DNS server Analyzing Performance Problems Use TCP offload and enable RSS You can use the Windows Performance Monitor perfmon to vi
183. st any CPU since the processing time for small packets is very high in the networking stack Using a teaming driver may also lead to this since it increases the CPU load during receive Increasing the number of Receive Buffers in the advanced property page may alleviate some of these drops in particular if the drops are the result of bursts of small receive packets on the network However if the CPU is the limit increasing the buffer resources does not help because the driver cannot post them fast enough Enabling RSS is another strategy to reduce drops since it allows the NIC driver to use additional CPU cores The number of RSS queues may be increased to increase the total number of posted buffers available to the adapter Enabling RSC can also reduce CPU consumption in the networking stack by combining multiple TCP packets into one larger packet For best performance the system BIOS should be set to Maximum Performance or manually disable C states The transitions to low power C states may cause a steady trickle of drops due to increased latencies from packet reception until the driver s interrupt processing code is invoked Receive Drops No Fragments CPU Limited Emulex Drivers for Windows User Manual The number of receive packets dropped because of a DMA bottleneck from the network adapter to host memory This may be caused by bottlenecks in either the PCI Express bus or main memory In the Status tab
184. stallation To add a Windows QFE check to the configuration file edit the STORPORT QFES section in the AutoPilot configuration file You may place this section anywhere within the file as long as it is not contained within another section This section contains a single line for each QFE that is to be checked Up to 10 lines are checked more than that may exist but they are ignored All parameters in each line must be specified These lines have the format Emulex Drivers for Windows User Manual P008011 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Configuration File 137 qfe qfe name path and file name file version applicable OS qfe name The name of the item being checked For example QFE 838896 The name should facilitate searching Microsoft s website for any required code updates path and file This string identifies the file to be checked and its location relative name to the Windows home folder In most cases the file to check is the Microsoft Storport driver for example system32 drivers storport sys This string is also used in dialogs and log file messages file version This is the minimum version that the file to be checked must have for the QFE to be considered installed It is specified as a text string using the same format as is used when displaying the files property sheet For example 5 2 1390 176 applicable OS This is
185. structions on how to do this Select Start gt Settings gt Control Panel gt Administrative Tools gt Computer Management Emulex Drivers for Windows User Manual P008011 01A Rev A 10 11 12 1 Installation 22 gt lt EMULEX Manually Installing or Updating the Emulex Protocol Drivers 3 Click Device Manager left pane 4 Click the plus sign next to the Emulex PLUS class right pane to show the ElxPlus driver entry Right click the ElxPlus driver entry and select Update Driver from the menu Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Click Next Select Install from a list or specific location Advanced and click Next Select Don t Search I will choose the driver to install Click Have Disk Direct the Device Wizard to the location of driver s distribution kit If you have installed the driver installer kit in the default folder the path is e C Program Files Emulex AutoPilot Installer Drivers Storport x86 for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport x64 for the x64 driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport IA64 for the Itanium driver version Click OK Select Emulex PLUS Click Next to install the driver Click Finish The ElxPlus driver update is finished Continue with manual installation of the Storport Miniport Driver Installing or Updating th
186. systems that support extended system event logging If set to 0 the parameter is disabled If set to 1 error events logging is enabled If set to 4 warning events logging is enabled If set to 8 informational events logging is enabled The values can be masked to generate multi levels of events logging Values 0 1 4 and 8 Default 0 EnableAckO n Set to 1 to force sequence rather than frame level Reset FC only acknowledgement for class 2 traffic over an exchange This applies to FCP data exchanges on IREAD and IWRITE commands Value 0 1 decimal Default 1 EnableAUTH EnableAUTH enables fabric authentication This Reboot parameter requires the authentication to be supported by the fabric Authentication is enabled when this value is set to 1 Value 0 1 Default 0 EnableFDMI n If set to 1 enables management server login on Reset fabric discovery This allows Fabric Device Management Interface FDMI to operate on switches that have FDMI capable firmware If set to 2 FDMI operates and uses the host name feature of FDMI Value 0 2 decimal Default 0 EnableNPIV n If set to 1 enables N_Port_ID virtualization Reboot NPIV Requires NPIV supported firmware for the adapter Value 0 1 Default 0 disabled Note To run the driver using NPIV or SLI 3 optimization the firmware must be version 2 72a0 or later If an earlier version is used the driver runs in SLI 2 mode and does not support NPIV Note NPIV is not availab
187. t PCI function per port since the packet cannot be further classified because of the error Receive IP Checksum Errors The number of receive packets with an incorrect IPv4 checksum These packets are provided to the TCP IP stack for disposal in the operating system Receive UDP Checksum Errors The number of receive packets with an incorrect UDP checksum These packets are provided to the TCP IP stack for disposal in the operating system Receive TCP Errors The number of receive packets with an incorrect TCP checksum These packets are provided to the TCP IP stack for disposal in the operating system Using OCCFG for Windows NIC TOE Driver Options The occfg exe program supports configuring parameters for the network functions on Emulex OneConnect adapters either through interactive mode with a set of menus or command line mode that is scriptable If you did a standard driver installation the occfg exe is located in the following directory Directory of C Program Files Emulex AutoPilot Installer NIC Drivers NDIS lt platform gt lt OS gt The following section describes how to use the occfg exe program to configure the Windows OneConnect device driver from the command line Displaying OCCFG Help To display help use the option by typing occfg on the command line The following text will be displayed OneConnect Network Config 0 0 9999 0 Copyright 2011 Emulex Usage occfg exe options Running wi
188. t rerien renerne 81 Mailbox Log Messages 0310 0326 cccccccececee eect eeeeeeeeeeeeeeeteeeeeseeeeeeeenesatens 84 INIT Log Messages 0400 0463 cc entered 85 FCP Log Messages 0701 0749 0 ccc cece ee eee nent need 87 Link Log Messages 1302 1306 ccc ect t eee etree teed 90 Tag Messages 1400 1401 ones 91 NPIV Messages 1800 1899 ccccccccce cece cece eee e eee tease eee eee esate sat esateeneeenenaeees 92 ELS Messages 1900 1999 s ssssssis skirtin ttnn titt EEEE EEEE EEEE EEEE EEEE EEEE EEEE EEEE 93 Troubleshooting the NIC TOE DriverS ssssssnsssssnnnnunnnnnnnnnnnnnnnnnnnnnannnnnnnnnnn 94 Monitoring TCP Otl0ads sicctens crm sndyseernietiesiciieieeeieaveriiesecinbyinesvemtvanesies 95 TCP Orthoad Failure civsscsutcr Scrcnapereedoan bed eeteiabery eae EDE bude EN AE aaite 96 Troubleshooting the iSCSI Driver ssssusussnsnnsnnsnunnunnnnnnnnnnnnnnnnnnnnnannnnnnnnnnn 97 Appendix A Error and Event Log Information cccceccssseeeesscceeeessserersssers LOO FC FCoE Error and Event LO 5 sssasicccivasweisransssmsnasciscscismscinasennaionsaeeemncoenramenan 100 Viewing the FC FCoE Error LOg ssssssessssssrrsrrrereresresrrrrrrrrerrrtrrsrrrrrrerere 100 Severity SCHEME isi cccse nce dh eedi ninna aa cee a a as beet daa dk bes ede aai 101 Related Driver Parameter LOQErrOr c cece cece e teen nnter rnnr nnr e netted 101 Format ofan Error LOG ENY rianietcteo
189. talled the driver installer kit to the default folder the path is e C Program Files Emulex AutoPilot Installer Drivers Storport x86 HBA for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA for the x64 driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport IA64 HBA for the Itanium driver version Click OK Select Emulex LightPulse LPX000 PCI Slot X Storport Miniport Driver your adapter model is displayed here Click Next Click Finish The driver installation is complete The driver should start automatically If the adapter is connected to a SAN or data storage device a blinking yellow light on the back of the adapter indicates a link up condition Installing or Updating the iSCSI Driver To update or install the iSCSI driver from the desktop OO SY Oe eS 9 10 Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click Device Manager Open the SCSI and RAID Controllers item Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All DC adapter models are displayed in Device Manager as two adapt
190. te Server Manager is set to open by default when booting Windows Server 2012 If not you can open it with the Service Manager icon at the bottom left of the screen Open the Network Adapters item Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Click Browse my computer for driver software Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All DC adapter models are displayed in the Device Manager as two adapters therefore you must update each adapter Click Let me pick from a list of device drivers on my computer Select the network adapter that matches your hardware and click Have Disk Direct the Device Wizard to the location of oemsetup inf Select the desired oemsetup inf file and click Open If you have installed the driver installer kit to the default folder the path is e C Program Files Emulex AutoPilot Installer Drivers NDIS x86 NIC Windows Version for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers NDIS x64 NIC Windows Version for the x64 driver version Or Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation 26 gt G EMULEX Removing Emulex Driver Kits and Drivers e C Program Files Emulex AutoPilot Installer Drivers NDIS IA64 NIC Windows Version for the Itanium dri
191. ternally up to a configured timeout period so that the operating system does not see I O errors This timeout period is known as link down timeout LDTO e Loss of connection to the target because of target or network disconnection at the target If the driver has I O requests pending with the target and the target becomes unavailable because the target is down has failed over or network issues are detected at the target the driver queues the I O request internally up to aconfigured timeout period This timeout period is known as extended timeout ETO If the configured threshold for LDTO and ETO is reached and the UCNA is still unable to connect to the target the driver fails all I O requests I O errors are seen by the application and operating system Note Following a link up switch ports can take a long time to initialize and go toa forwarding state Because of this add additional time to the ETO and LDTO settings to eliminate I O disruption or target unavailability If the switch port is connected to a single host then PortFast mode can be enabled on the switch port to eliminate delays in transitioning to a forwarding state Configuring LDTO and ETO on Windows Server LDTO and ETO values are configured via the Windows registry Table 2 9 lists the default values of LDTO and ETO on Windows Server and the limits within which they can be configured Note If the ETO is set to a number between 0 and 19 the driver assumes the val
192. th no arguments will display a menu to select the adapter and parameters to modify Using the command line arguments allow scripting this process Options str str Selects all adapters with any of the given strings in the connection or device name If omitted occfg prompts for an adapter from a list Emulex Drivers for Windows User Manual P008011 01A Rev A 2 Configuration 55 DG EMULEX NIC TOE Driver Configuration s name v name v Sets the parameter s value and reloads the devices g name name Gets parameter value F Skips reloading the driver when setting a parameter f Force reloading the driver I List available adapters and exit x Reset all parameters to the default value p Show all registry parameter values q Show all driver parameter values h Show help text for all parameters Show this help Examples Run interactively with menus occfg exe Set a parameter on all Emulex adapters occfg exe a Emulex s rss 1 Set multiple parameters on one adapter adapter occfg exe a Local Area Connection 23 s Flow 3 rss 0 Selecting an Adapter In batch mode the a parameter should be followed by a substring that is contained within the adapter name The name is a combination of the device manager name for example Emulex OneConnect OCe11102 and the network connection name for example Local Area Connection The later may be modified by using the Window s
193. the Microsoft website To configure the iSCSI drivers to fail over to an alternate path as quickly as possible edit the Driver Parameters for the iSCSIi service in the registry 1 Locate the key and set eto 0 ldto 0 HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters 2 Reboot the system for the registry changes to take effect 3 Log into the iSCSI target using WMI For more information see Logging into Targets for Multipath Support on page 74 4 Enable MPIO a Select Start gt Administrative Tools gt Server Manager b In the Server Manager tree click Features c In the Features area click Add Features d In the Add Features wizard on the Select Features page select the Multipath I O check box and click Next On the Confirm Installation Selections page click Install f When the installation is completed click Close on the Installation Results page g When prompted to restart the computer click Yes h Click Close 5 Discover all possible paths to all devices on the system a Open the MPIO control pane select Start gt Administrative Tools gt MPIO b On the User Account Control page click Continue The Properties dialog box is displayed c Select the Discover Multi Paths tab d Select Add support for iSCSI Devices and click Add Emulex Drivers for Windows User Manual P008011 01A Rev A 73 2 Configuration 74 gt G EMULEX iSCSI Driver Configurati
194. tion information and task results e Print Installation Report The Windows print dialog box is displayed to select options for printing the installation report 5 Click Finish to exit the AutoPilot Installer Text Only Driver Installation Text based installation mode is used automatically when the driver kit installer runs on a server with the Server Core installation option of Windows Server During text based installations AutoPilot Installer uses a command prompt window The driver kit installer notifies you when the driver is installed and also gives you a chance to stop the installation Whether it is launched from the command line or started programmatically Windows always starts AutoPilot Installer as a separate stand alone task This means that AutoPilot Installer has its own command prompt window and cannot access others Emulex Drivers for Windows User Manual P008011 01A Rev A 1 Installation gt lt EMULEX AutoPilot Installer Overview 19 Unattended Driver Installation An unattended driver installation sometimes referred to as a quiet or silent installation requires no user input This is useful for performing an installation remotely from a command script or when you want to make sure a custom configuration is not changed by a user during installation When in unattended installation mode AutoPilot Installer does the following e Reads the configuration file e Reads any options that may be specified on the co
195. ue to 20 seconds internally You will not see any modification to the registry Table 2 9 LDTO and ETO Information on Windows Server Value Default Minimum Maximum LDTO 20 sec 0 sec 3600 sec ETO 90 sec 0 sec 3600 sec To modify LDTO and ETO values edit the Driver Parameters for the iscsi service in the registry Locate the key HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters and edit the REG_SZ parameter to Idto 25 eto 50 This sets the default value of LDTO to 25 seconds and the default value of ETO to 50 seconds The settings are applied the next time the driver is loaded You must reboot the system boot drivers or disable the iSCSI driver and enable it again non boot drivers in Device Manager for the settings to take effect Emulex Drivers for Windows User Manual P008011 01A Rev A S lt 2 Configuration 76 EMULEX iSCSI Driver Configuration Error Handling Under MultiPath MPIO and Cluster Configurations In an MPIO or cluster configuration fault tolerant software is present on the system in addition to the iSCSI driver s default error handling scheme Depending on the type of failover configuration the iSCSI driver s error handling parameter needs to be configured appropriately If the iSCSI target is in Active Active failover mode the iSCSI driver must report I O errors as soon as they are detected This allows the failover software to trigger a path failover to a
196. ver version 10 Click Next 11 When the device driver finishes installing click Close The driver installation is complete The driver should start automatically Removing Emulex Driver Kits and Drivers Uninstalling Emulex Driver Kits Note When you uninstall the Emulex driver kit AutoPilot Installer is automatically uninstalled Windows Server 2008 To uninstall a driver kit on a Windows Server 2008 system 1 Open the Programs and Features control panel 2 Select one of the following in the program list and click the Uninstall icon in the tool bar above the program list If you have User Access Control enabled click Continue when asked for permission e Emulex FC kit 2 xx xxx e Emulex FCoE kit 2 xx xxx e Emulex NIC 4xx xxx e Emulex iSCSI kit 4 xx xxx 3 Click Yes when prompted to remove the kit Once the kit is removed from the system click OK To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files folder on an x86 system or the Program Files x86 folder on a 64 bit system 2 Navigate to Emulex AutoPilot Installer 3 Run one or more of the following batch files e uninstall fc_kit bat uninstall fc kit e uninstall_cna_kit bat uninstall fcoe kit e uninstall_iscsi_kit bat uninstall iscsi kit e uninstall_nic_kit bat uninstall nic kit 4 The proper driver kits are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installe
197. ws 2008 R2 Lookahead split is not supported for jumbo frames If Lookahead split is enabled with VMQs the NIC can directly DMA received packets to the virtual machine memory eliminating a packet copy from the host to VM Lookahead split requires Advanced Mode Support is enabled in the BIOS controller configuration P008011 01A Rev A gt G EMULEX 2 Configuration 48 NIC TOE Driver Configuration Table 2 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Supported Name Acceptable Values Operating Systems Definition VMQ Transmit Enabled default Note For 0Ce11102 If this option is enabled with VMQs separate Disabled UCNAs only transmit queues are created for each VM network Windows 2008 R2 interface Send and receive interrupts for a VM network interface are processed on the same Windows 2012 CPU s ETS Disabled default Note For OCe11102 If ETS is enabled the driver filters transmit Enabled Emulex Drivers for Windows User Manual UCNAs only ETS is not supported in conjunction with VMQ technology Windows 2008 Window 2008 R2 Windows 2012 packets based on the 802 1p priority tag into multiple separate transmit rings The network switch should be configured for ETS to group priorities into a priority group or traffic class Each priority group may be assigned an QoS bandwidth limit For example one network priority may to support priority f
198. x Info2 OxAC x amp x Description Severity Log Action The firmware has interrupted the host with a firmware trap error Error LOG_INIT verbose Review HBAnyware diagnostic dump information FCP Log Messages 0701 0749 Ipfc_mes0701 Issue Abort Task Set to PathId x x Targetid x x Lun x x Description Severity Log Action The driver has issued a task management command for the indicated SCSI device address Warning LOG_INIT verbose Review system configuration Ipfc_mes0703 Issue LUN reset to Pathld x x Targetid x x Lun x x Did x x Description Severity Log Action Emulex Drivers for Windows User Manual Storport is requesting a reset of the indicated LUN Warning LOG_INIT verbose Review system configuration Possible side effect of cluster operations P008011 01A Rev A gt EMULEX 3 Troubleshooting 88 Troubleshooting the FC FCoE Driver Ipfc_mes0713 Issued Target Reset to Pathld d Targetld d Did x x Description Severity Log Action See Also Storport detected that it needs to abort all I O to a specific target This results in login reset to the target in question Warning LOG_FCP verbose Review system configuration Possible side effect of cluster operations Ipfc_mes0714 Ipfc_mes0714 Issued Bus Reset for PathId d Description Severity Log Action See Also Storport is requesting the driver to reset all targets on this
199. y specify one parameter to modify but it may be only a substring on the full parameter name For example the following are all equivalent occfg a emulex s Flow Control 3 occfg a emulex s flow 3 occfg a emulex s control 3 Note that the parameter name is generally the text readable parameter description name but you may specify the exact registry key name as well Microsoft has defined many documented standard registry key names that start with a character The is not a wildcard it is part of the registry key name The following examples are equivalent occfg a emulex s Flow Control 3 occfg a emulex s FlowControl 3 Note Quotes are required if the parameter name contains a space character To modify a parameter without a driver reload use r This is useful to modify several parameters in sequence then force a reload of the driver at the end To force a driver reload use the f parameter The following is an example of such a sequence occfg a emulex r s rss 0 occfg a emulex r s interrupt moderation 0 occfg a emulex f Registry keys may be set to two special values e The delete value will cause the key to be entirely deleted and the driver will use the default value This is appropriate for keys that are optional such as the Network Address e The default value will set the key to the driver s default value If the key is optional the

windows manual elx

Contents

Download Pdf Manuals

Related Search

Related Contents