Home

Emulex Drivers for Windows User Manual

1. Bits 0 7 Interpretation OxFA READ_COMFIG failed SLI4 mode OxFB Failed to post header templates SLI4 mode OxFC Invalid Completion Queue Entry SLI4 mode OxFD Invalid Completion Queue Entry SLI4 mode OXxFE Invalid Completion Queue Entry SLI4 mode Malfunction Errors Table A 2 Malfunction Errors Bits 0 7 Interpretation 0x05 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 0x5A PRLI response error 0x5F CT command error 0x62 Name server response error 0x66 State Change Notification registration failure Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix A
2. Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 41 DG EMULEX FC FCoE Driver Configuration Table 3 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 firmware 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 1 0 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 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 driv
3. 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 malfunction 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 P009412 02A Rev A 3 Configuration 40 DG EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Ac
4. Emulex Drivers for Windows User Manual driver load ID and Device ID are not supported Check the UCNA configuration P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 139 Table A 14 iSCSI Error Log Entries on Windows 7 Windows Server 2008 R2 and Windows Server 2012 Message ID 0x18 Severity Error Message Memory could not be allocated failing driver load Recommended Resolution This failure occurred because of a failed memory allocation in the driver This failure may indicate a low memory condition 0x19 Warning WMI driver error code A 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 driv
5. Option Name Enhanced Transmission Selection Acceptable Values Disabled default Enabled Supported Operating Systems Note For OCe11102 UCNAs only ETS is not supported in conjunction with VMQ technology Windows 2008 Windows 2008 R2 Windows 2012 Definition If ETS is enabled the driver filters transmit 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 a QoS bandwidth limit For example one network priority may to support priority flow 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 configurations regarding bandwidth and priority flow control should be performed on the network switch The adapter will learn the configuration using the DCBx protocol Flow Control Disabled RX and TX Enabled default Rx Enable Tx Disable Tx Enable Rx Disable Emulex Drivers for Windows User Manual Windows 2008 Windows 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 c
6. AutoPilot Installer Command Line and Configuration File Parameters on page 145 Option 2 Run the Driver Kit Installer Separately 1 Follow steps 1 3 for Running a Software Installation Interactively on page 20 2 Clear the Run AutoPilot Installer check box on the Finish dialog box 3 Choose one of the following options 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 AutoPilot Installer The configuration file is typically located in c Program Files Emulex AutoPilot Installer lt driver type gt 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 147 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 displays 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 Emulex Drivers for Windows User Manual P009412 02A Rev A S lt EMULEX 2 Installa
7. Backing Up and Editing the Registry e N pr 10 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 Navigate to HKEY LOCAL MACHINE System CurrentControlSet Services be2iscsi Parameters Device Double click on DriverParameters to edit Enter the configuration parameter See Table 3 7 iSCSI Driver Options on page 85 for iSCSI configuration parameters For example eto 60 ldto 30 im_policy 3 Note A semicolon is required after every parameter Reboot the system 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 If the system boots but does not work properly restore from a previous restore point or import the saved reg file and reboot Table 3 7 iSCSI Driver Options Parameter ETO Default Value Minimum Value Maximum Value Description 90 seconds 0 seconds 3600 seconds 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 im_policy N oO D The Interrupt Moderation policy parameter controls the rate
8. ELS FCP Command Error Status Codes Internal firmware codes posted by the adapter firmware that explain why a particular ELS 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 P009412 02A 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_Po
9. Registry Maximum Number of RSS Queues 4 Driver Maximum Number of RSS Queues 8 Registry Network Address lt not set gt Driver Network Address lt not set gt Registry Packet Size 1514 1514 Driver Packet Size 1514 0x5ea 1514 Registry Preferred NUMA Node lt not set gt Driver Preferred NUMA Node lt not set gt Registry Receive Buffers 896 Driver Receive Buffers 1280 0x500 Registry Receive CPU lt not set gt Driver Receive CPU lt not set gt Registry Receive Side Scaling 1 Enabled Driver Receive Side Scaling 1 Enabled Registry Recv Segment Coalescing IPv4 1 Enabled Driver Recv Segment Coalescing IPv4 1 Enabled Emulex Drivers for Windows User Manual P009412 02A Rev A gt G EMULEX Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Recv Segment Coalescing IPv6 1 Recv Segment Coalescing IPv6 1 SR IOV 0 Disabled SR IOV 0 Disabled TCP Checksum Offload IPv4 3 Rx TCP Checksum Offload IPv4 3 Rx TCP Checksum Offload IPv6 3 Rx TCP Checksum Offload IPv6 3 Rx Transmit 1
10. cccceeceeeeeeateeateeeeeeeeeeeteeutenes 91 Error Handling Under MultiPath MPIO and Cluster Configurations 6068 91 4 Troubleshooting hivstursieriawiird ee ONAN Oe General Troubleshooting sssssssssssnnnnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 92 Troubleshooting the FC FCoE Driver ssssssssnsssnsnnununnnnnnnnnnnnnnnnnnnnnanunnnnnnnnn 92 Troubleshooting the Cisco Nexus Switch Configuration ccceeeeeee eee eee eae 92 Event Trace Messages voir cirniss ev isund tended anes suuan cna eedenddanunst ake emeretekusdeevetsauss 93 ELS Log Messages 0100 0130 c ccccccce cee eeeeeeee sees cesses sees satesateseneenneenees 93 Discovery Log Messages 0202 0262 ccccee cette eee netted 96 Mailbox Log Messages 0310 0326 cccccccececeee cess eset eee eeeeeeeeeeatesatesateeneeenega 99 INIT Log Messages 0400 0463 0 cece nnn e nes 100 FCP Log Messages 0701 0749 0 ec nner tes 102 Link Log Messages 1302 1306 0 c cee ener ed 105 Tag Messages 1400 1401 00 eee nes 106 NPIV Messages 1800 1899 cccccccece cee eee sees eeeeeeeeeeeeeeeee sate sateseteenerenenaes 107 ELS Messages 1900 1999 sic ccitivivissaiaiaa vad ebotebeedidaeaeenie E Da bade EAA 108 Troubleshooting the NIC TOE DriverS sssssssssssssnnnnnnnnnnnnnannnnnnnnnnnnnnnnnnnnnnn 109 Monitoring TCP Omloads civcssesatetiniprncieseieysteiieniyenei sce siantentys
11. SG EMULEX 3 Configuration 55 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Acceptable Values Wake on LAN Enabled default Disabled Notes For Windows Server 2012 inbox drivers Wake on LAN is disabled by default and not overwritten on driver updates Wake on LAN is disabled by default on 0Ce10102 series adapters Supported Operating Systems Windows 2008 Windows 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 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 74 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 Emulex Drivers for
12. Usage occfg exe options Running with no arguments will display a menu to select the adapter and parameters to modify Using the command line arguments allow scripting this process Options Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration Ld 62 gt lt EMULEX NIC TOE Driver Configuration a str str Selects all adapters with any of the given strings in the connection or device name If omitted occfg prompts for an adapter froma list s name v name v Sets the parameter s value and reloads the devices g name name Gets parameter value Skips reloading the driver when setting a parameter f Force reloading the driver gt L 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 ma
13. e Supply parameters on the command line See appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 145 for details Once you have finished this step you can run AutoPilot Installer at a later time using either of the following methods Note 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 e Run AutoPilot Installer from the command line Type c Program Files Emulex AutoPilot Installer lt driver type gt 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 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 t
14. e Through an unattended installation AutoPilot Installer provides e Command line functionality Initiates an installation from a command prompt or script Configuration settings can be specified in the command line e Compatibility verification Verifies that the driver to be installed is compatible with the operating system and platform e Driver installation and update Installs and updates drivers e Multiple adapter installation capability Installs drivers on multiple adapters alleviating the need to manually install the same driver on all adapters in the system e Driver diagnostics Determines whether the driver is operating properly e Silent installation mode Suppresses all screen output necessary for unattended installation Note AutoPilot Installer does not allow you to install the driver if the minimum Windows service pack or Microsoft Storport driver update is not installed Emulex Drivers for Windows User Manual P009412 02A Rev A 19 2 Installation gt lt EMULEX AutoPilot Installer Overview 20 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
15. start command with the wait option This causes the command processor to wait 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 145 Running a Software Installation Interactively There are two options when performing an installation interactively e Option 1 allows you to automatically run the AutoPilot Installer which completes a driver kit installation and AutoPilot installation with a few mouse clicks e 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 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 145 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 displayed with driver kit version i
16. Adapter is no enabled A system reboot is required to make longer functional the adapter operational again 0x2b Informati The storage device is Informational message that provides the slot onal operating in Gen lt xx gt mode capabilities where the iSCSI adapter is Emulex Drivers for Windows User Manual and installed in a lt yy gt x PCI Express slot installed P009412 02A Rev A SXC EMULEX Appendix B Configuring iSCSI through DHCP 141 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 Address 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 crea
17. Advanced Property Configuration Configuration Cass of Service 802 1p Enhanced Transmission Selection Network Address Packet Size VLAN Identifier 802 1q Wake On LAN E Performance 6 CPU Affinity Flow Control Interrupt Moderation Receive Buffers RSS zi Reset All to Defaut 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 3 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 3 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 3 3 on page 58 Emulex Drivers for Windows User Manual P009412 02A Rev A SG EMULEX 3 Configuration NIC TOE Driver Configuration 4 From the
18. 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 147 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 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 uestion uestion explanation answer0 answerl E AAJ E kei n w L E n wW 0 n AAJ 1 n 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 b
19. 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 Configurations 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 Ma
20. Once the Hyper V role is added you can enable SR IOV in the Hyper V Manager by e Creating the virtual switch e Creating each virtual NIC See Microsoft documentation for more information Note Make sure SR IOV is enabled on the server and on the Emulex adapter prior to configuring the Hyper V virtual switch The Windows 2012 Server treats SR IOV as an offload an active active team with virtual function and an emulated adapter That means each Emulex SR IOV adapter is accompanied by a fully functional emulated NIC The emulated NIC is named Microsoft Virtual Network Adapter and the TCP IP stack is only bound to this device Once the Emulex driver is loaded the Emulex SR IOV virtual function is used for all unicast receive and transmit traffic The emulated NIC handles multicast and broadcast traffic If SR IOV is disabled the Emulex adapter is removed from the virtual machine and all traffic automatically uses the emulated NIC This technology allows Live Migration of Virtual Machines when using SR IOV Note If multiple adapters are added to the virtual machine Emulex recommends using MAC addresses to map the Emulex Network adapter to the corresponding Microsoft Virtual Network adapters Verifying SR IOV When SR IOV is working it can be verified by opening the Device Manager within the virtual machine and examining the information about the transmit and receive packets that are using the SR IOV virtual function This i
21. Open the Network Adapters item find the Emulex OneConnect device and right click Select Properties from the context menu The OneConnect Properties dialog box opens See Figure 3 5 Click the Advanced tab The Advanced Property Configuration page opens Diver Oetats Everts Resouces Power Management General Advanced Satus Sasis Diagnostics FSSEMULEX vanced Property Cortiguation Wake On LAN B Pefomance E CPU Aliny Set to Defauk lt Beset Alto Defaut Single Root 10 Virtualization SR IOV enables the adapter to a allocate virtual PCI functions for each virtual machine in Hyper V Note that the virtual switch and virtual network adapter must have SRIOV enabled in the Hyper V Manager When using SRIOV the Emulex NIC driver must be installed lon each virtual function within the virtual machine SR IOV provides a direct hardware interface from the virtual machine to the networking adapter which reduces latency land improves performance Co core Figure 3 6 Emulex OneConnect NIC TOE Advanced Properties page 5 Select SR IOV from the list and select Enabled from the Value list Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 72 DG EMULEX NIC TOE Driver Configuration Note You must configure Hyper V to create an SR IOV enabled virtual machine See Microsoft Hyper V documentation for more information Hyper V The Hyper V role must be added using the Server Manager
22. SLI2 3 mode Ox0E Invalid adapter type LightPulse OxOF Invalid adapter type LightPulse 0x10 CONFIG_PORT failed reinitialization 0x12 READ_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 P009412 02A Rev A Invalid response tag SLI2 3 mode 118 Appendix A Error and Event Log Information 119 gt lt EMULEX FC FCoE Error and Event Logs Table A 1 Severe Errors Continued Bits 0 7 Interpretation 0x25 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 Ox2A Atte
23. The change takes effect while the system is running e Reset An adapter reset from the utility is required before the change takes effect e Reboot A reboot of the entire machine is required before the change takes effect In this case you are prompted to perform a reboot when you exit the utility Notes e If you are creating custom unattended installation scripts any driver parameter can be modified and included in the script e Ifthe Adapter Protocol column is blank the parameter is supported on both LightPulse and OneConnect adapters LightPulse only indicates that the parameters is supported only on LightPulse adapters FC only indicates that the parameters is supported on LightPulse and non LightPulse FC adapters e The Windows driver enumerates 1024 targets across all physical and virtual ports with 8G and 16G adapters However setting ConfigScale to 0 changes the support to 128 targets See ConfigScale in Table 3 1 Storport Miniport Driver Parameters on page 35 Emulex Drivers for Windows User Manual P009412 02A Rev A S lt 3 Configuration 35 EMULEX FC FCoE Driver Configuration Most parameters default to a setting that optimizes adapter performance Table 3 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 SC
24. Transmit 1 Transmit CPU Transmit CPU UDP Checksum UDP Checksum UDP Checksum UDP Checksum TCP Connection Offload TCP Connection Offload TCP Offload Optimization TCP Offload Optimization Enabled Enabled Transmit Buffers 256 Transmit Buffers 256 0x100 lt not set gt lt not set gt Offload IPv4 Offload IPv4 Offload IPv6 Offload IPv6 Vlanid lt not set gt Vlanid Virtual Machine Queues Virtual Machine Queues Wake On LAN Wake On LAN Emulex Drivers for Windows User Manual lt not set gt 1 1 Enabled 1 0 Disabled IPv4 0 0 3 Rx 3 Rx 3 Rx 3 Rx Enabled Enabled amp Tx amp Tx amp TX amp TX 3 Configuration NIC TOE Driver Configuration Enabled Enabled Enabled Enabled Enabled Enabled 0 Disabled IPv4 0 Disabled Optimize Throughput Optimize Throughput Enabled Enabled Enabled Enabled P009412 02A Rev A 66 3 Configuration 67 DG EMULEX NIC TOE Driver Configuration 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 p
25. decimal Default 0 EnableNPIV n If set to 1 enables NPIV Requires NPIV supported Reboot firmware for the adapter Value 0 1 Default 0 disabled Notes e Torun 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 e NPIV is not available on 1 Gb s and 2 Gb s adapters Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 38 DG EMULEX FC FCoE Driver Configuration Table 3 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
26. 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 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 Table 3 1 Storport Miniport Driver Parameters on page 35 for a listing of driver parameters defaults and valid values Setting Up System Parameters SYSTEM PARAMS To change the s
27. remote Did in bits 8 31 OxEB Authentication policy has been changed remote Did in bits 8 31 0OxED Same passed 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 P009412 02A Rev A Appendix A Error and Event Log Information 123 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
28. sec to dynamically maintain a target Adaptive 30k Int sec interrupt rate If CPU usage is too default high choose a higher adaptive value Adaptive 20k Int sec to increase the interrupt delays and Adaptive 15k Int sec reduce the rate of interrupts Adaptive 12k Int sec Adaptive 10k Int sec Adaptive 7k Int sec Adaptive 5k Int sec IP Checksum Disabled Windows 2008 This offloads the transmit and or Offload IPv4 RX and TX Enabled default RX Enabled TX Enabled Windows 2008 R2 Windows 2012 receive IPv4 checksum computation Offloading checksums increases system efficiency IP Checksum Offload IPv6 Disabled RX and TX Enabled default RX Enabled TX Enabled Windows 2008 Windows 2008 R2 Windows 2012 This offloads the transmit and or receive IPv6 checksum computation Offloading checksums increases system efficiency Large Send Offload v1 IPv4 Disabled Enabled default Emulex Drivers for Windows User Manual Windows 2008 Windows 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 Version 1 LSO supports only IPv4 P009412 02A Re
29. 2008 R2 Windows 2012 UDP offload checksum settings offload the transmit and or receive IPv4 UDP checksum computation Offloading checksums increases system efficiency UDP Checksum Offload IPv6 Disable RX and TX Enabled default RX Enabled TX Enabled Emulex Drivers for Windows User Manual Windows 2008 Windows 2008 R2 Windows 2012 User Datagram Protocol UDP offload checksum settings offload the transmit and or receive IPv6 UDP checksum computation Offloading checksums increases system efficiency P009412 02A Rev A SG EMULEX 3 Configuration 54 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Virtual Machine Queues Acceptable Values Enabled default Disabled Supported Operating Systems Note For OCe11102 and 16Gb UCNAs only VMQs require Windows Server 2008 R2 or later with Hyper V Definition VMQs 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 Virtual Machine Queu
30. 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 97 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
31. 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 serverilok echo No appropriate driver found serverlok remd server2 g autopilot ApInstall ConfigFileLocation g autopilot mysetup apinstall cfg if errorlevel 1 goto server2ok echo AutoPilot reported 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 echo 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 noreport 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 server2o0k Emulex Drivers for Windows User Manual P009412 02A Rev A 156
32. 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 Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax 7 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 Parameter 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 Defau
33. P009412 02A Rev A gt EMULEX 4 Troubleshooting 110 Troubleshooting the NIC TOE Drivers Table 4 3 Troubleshooting the NIC TOE Drivers Continued Problem When Wake on LAN is set through the advanced properties page the system does not wake when receiving a magic packet or a packet that would normally wake the system Answer Solution The system may not support Wake on LAN on the PCle slot in which the UCNA is installed Check the system documentation to determine whether the system is capable of Wake on LAN operation A system BIOS setting may not be correct for Wake on LAN to work as expected Check the system documentation to determine whether Wake on LAN must be enabled in the system BIOS Wake on LAN may not be supported by the chipset as reported by the firmware The driver reports the value that is reported by the firmware 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 When running Windows Server 2008 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 Apply the 979614 hotfix as des
34. 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 transfer 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 P009412 02A Rev A 3 Configuration 39 DG EMULEX FC FCoE Driver Configuration Table 3 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
35. Rev A gt EMULEX 4 Troubleshooting 103 Troubleshooting the FC FCoE Driver Ipfc_mes0703 Issue LUN reset to Pathld x x Targetid x x Lun x x Did x x Description Severity Log Action Storport is requesting a reset of the indicated LUN Warning LOG_INIT verbose Review system configuration Possible side effect of cluster operations Ipfc_mes0713 Issued Target Reset to Pathlid 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 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 Emulex Drivers for Windows User Manual FCP device provided less data than was requested Supplement Information LOG FCP verbose No action needed informational Ipfc_mes0730 P009412 02A Rev A gt EMULEX 4 Troubleshooting 104 Troubleshooting the FC FCoE Driver Ipfc_mes0729 FCP command error ulpStat
36. Selected Error Codes l enn 126 NIC TOE Error and Event LOGS ssssssssunnnnnnnnnsnunnunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 127 Viewing the NIC TOE Error LOg sssssssssssssrrsrrrererrerrrrsrrrrrrrrrrerrsrrrrrrerere 127 NIC TOE Event Log cccsteacnaceabarsieeuntaeaaieesandncistecmstgh scents te cteeessaesareeaaadas 127 iSCSI Error and Event LOg ssssssssssssnnnnnnnnnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 131 Viewing the iSCSI Error and Event Log on Windows Server 2008 ccecce 131 iSCSI Error Log on Windows Server 2008 oc 0cvcvccicswcceytgreeeasses ed e 133 Viewing the iSCSI Error Log on Windows 7 Windows Server 2008 R2 and Windows Server 2012 c ccsccciecs des cccdscvedacteiacssdacriesdsdiaesaiesssasdeaeeiveris 136 Appendix B Configuring iSCSI through DHCP ssssssssnnnnsnnnnnnnnnnnnnnnnnnnnnnnn 141 Dynamic Host Configuration Protocol DHCP Recommendations sceesseeeeeeeees 141 Vendor Specific Option Aa wcisesviceavsotcenrecwonrceybiawacrrsy tamebacteboinnodiansoamiereets 141 Format of Vendor Specific Option 49 icy occ nncet sees tears cheese denvels eax cance bee cxetes tex 141 Description of Mandatory and Optional Parameters cccceceeeeeeeee seer eene ees 142 EXOMDICS lt cincvidineidndercekobelans iueleneereereiwin dp rcendd eens deaverdnisepeerintiieaeeaes 142 Appendix C Port Speed Specifications sssssssssnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 144 Negotiating Speed on a Mezzanine Card ssssssssss
37. Settings for I O Coalescing eeeeeeeeee sees eee eeeeeeaes 42 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options 45 NIC TOE Driver Properties Statistics vis icciseeccswcicei ck caves lasekcaecd caves Gacexinenns 58 Windows Server Performance Tuning Situations cceeee eee e eee eee eee es 75 Statistics and Fine TUNING sccoctcerPiaveieienriwntinepriavenricbremiaee Seavert 75 iSCSI Driver ODUIOIIS six nich sie nenat ienien ED cesenees emee seen sewees naeesmmedeanstmnteican 85 IM OME Y SCEEINGS crise aa rake n E EEE Ea EAEE AE 87 LDTO and ETO Information on Windows Server cccceeeeeee eee eeeeeeeenenes 91 General TOUDleShOOUING sc cares icedecesdesdenvenrvsinueesmebesSeaxeantsleeveeasdaineees 92 Cisco Nexus Switch Situations 92 Troubleshooting the NIC TOE DriverS sssssesessesrrrrrrrrrererrrrrrrrrerere 109 Troubleshooting TCP Offload Failures cccccceccceeeeeeeeeeeee sees eenaenens 112 Cisco Nexus Switch Situations for SU Slas lt 42cccrcicacecwexacsvecctisniecarieasseses 113 Troubleshooting the iSCSI Driver ssssssssssrsrererrsrsrrrrrrerrererrrrrrrrrerere 113 Severe ENOT Simipis iieii irie EEEE NEEDE RAEE EENE EEEE EATE canes RNEER 118 Malfunction Errors s cscssecauerobiscanctaesevenntecvasscageiaokiseesteschviaastiaesisecs 120 COMIMANG EM OrS s cveverevou tetacesdiaweecinee Reine E EE Raa 121 Event IndicationS ssssssssrsrrrrrrrrstrrrrrrrrrrttt rtr rrrrrr
38. a task that is not present 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 properly Check the UCNA and reinstall the firmware if required 0x0e Warning iSCSI error was detected on session A ExpCmdSn B MaxCmdSn 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 ExpCmdSN 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 Emulex Drivers for Windows User Manual 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
39. all the hosts in a SAN e 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 also referred to as quiet mode and creates an extensive report file with installation status Note You can download complete driver and utilities documentation from the Emulex website Driver Kit Installer Overview The driver kit installer is an executable file that self extracts and copies the following software onto your system e lt A protocol specific driver that manages 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 that supports the OneCommand Manager application and NPIV vPort registry 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 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 20 for more information e Run AutoPilot Installer later on your system Se
40. 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 of 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 P009412 02A Rev A 3 Configuration 44 gt C EMULEX NIC TOE Driver Configuration NIC TOE Driver Configuration Notes e TOE is supported and enabled by default e TOE is not supported on 16Gb UCNAs Configuring NIC TOE Driver Options The Windows Server NIC TOE dr
41. area network Small Computer System Interface small form factor pluggable service level interface SCSI Request Block Single Root I O Virtualization Secure Shell network protocol Transmission Control Protocol TCP push flag task management function timed out TCP Offload Engine transmit Universal Converged Network Adapter User Datagram Protocol unrecoverable error Unified Extensible Firmware Interface BIOS Upper Layer Protocol Universal Multichannel virtual function virtual local area network virtual local area network id virtual machine virtual machine queue virtual private network virtual port Windows Automated Installation Kit P009412 02A Rev A gt G EMULEX WMI WWN WWNN WWPN XRI Window Management Instrumentation world wide name world wide node name world wide port name exchange resource indicator Emulex Drivers for Windows User Manual 1 Introduction Abbreviations P009412 02A Rev A 15 2 Installation SG EMULEX Driver Installation Options 16 2 Installation Driver Installation Options There are two ways that you can install the Windows drivers using the Onelnstall Installer Onelnstall package or the AutoPilot Installer You must choose one of these options e Onelnstall contains all the Emulex Windows drivers Emulex Storport Miniport and NDIS Miniport drivers and the OneCommand Manager application in a single download package e AutoPilot Installer for Em
42. 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 uses 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 Disable Priority Emulex Drivers for Windows User Manual P009412 02A Rev A SG EMULEX 3 Configuration 46 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued
43. 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 99 Troubleshooting the FC FCoE Driver Ipfc_mes0256 Start node timer on NPortld x x timeout value d Description Severity Log Action Starting timer for disconnected target with NPort ID and timeout value Information LOG _ELS verbose No action needed informational Ipfc_mes0260 Stop node timer on NPortlid x x SCSIId x x Description Severity Log Action Discontinuing timer for reconnected target with NPort ID and SCSI ID Information LOG ELS verbose No action needed informational Ipfc_mes0262 Node timeout on NPortld x x SCSIId x x Description Severity Log Action Disconnected NPort ID SCSI ID has failed to reconnect within timeout limit Error LOG ELS verbose Review system configuration Mailbox Log Messages 0310 0326 Ipfc_mes0310 Mailbox command timeout HBA unresponsive Description Severi
44. for RSS without manual configuration TCP Offloading TOE The UCNA and drivers support TCP offload which provides significant performance improvements The performance improvements are 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 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 signifi
45. is 32 bit and this system is 64 bit 2399141894 0x8F 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 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 Ox8F00000C 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 0x8F000050 Unattended software first installations are disallowed 2399141984 0x8F000060 You cancelled APInstall before any driver utility i
46. 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 passwords 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 iscsi 192 168 0 2 3261 000000000000000E ign 2009 4 com 12345 67890 E 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 disable
47. list of properties select the property parameter you want to view 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 3 3 NIC TOE Statistics Properties in Windows Server 2008 Table 3 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 receive
48. more spaces must separate the switch and each parameter setting The syntax of a parameter setting is parameter _name value 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 147 Settings specified in the APInstall command override those specified in the configuration file ConfigFileLocation path specifier NoSoftwareFirstInstalls TRUE FALSE SilentRebootEnable TRUE FALSE ForceDriverUpdate TRUE FALSE ForceDriverTypeChange TRUE FALSE SkipDriverInstall TRUE FALSE InstallWithoutQFE TRUE FALSE ForceRegUpdate TRUE FALSE LocalDriverLocation path specifier ReportLocation path specifier Path Specifiers Paths may be specified as e an explicit path ReportLocation C Program Files Emulex AutoPilot Installer Reports Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax is e arelative path LocalDriverLocation Drivers Storport Miniport assuming installation into C P
49. of interrupts for the UCNA For more information see Interrupt Moderation Policy Settings on page 87 Emulex Drivers for Windows User Manual P009412 02A Rev A SG EMULEX Table 3 7 iSCSI Driver Options Continued 3 Configuration 86 iSCSI Driver Configuration Parameter large_io Default Value 64 Minimum Value 64 Maximum Value 512 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 issues 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 LDTO 20 seconds 0 seconds 3600 seconds 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 LUNs are unavailable to the operating system Note LDTO values are configurable via the Windows registr
50. of Contents gt EMULEX Receive Window Auto Tuning and Compound TOP ccce 82 INterrUpt COaLESCING ndenann A ENEE aan faapeentanes REEERE 83 CPU Binding Considerations s2 cccgenestes sce tis cin erineda tae pd ead EEPE ERRAT anaes 83 Single TCP Connection Performance Settings cccccccceceeceeeeeeeeeeseeeeeeeeneeeneeaes 84 iSCSI Driver CONFGUEALION cists tcaxanaeiataananeaiadannmneedeniareidedeniernteresiometorseienneis 84 Configuring iSCSI Driver OptiOnS cccccecee eect ee eee ee eeeeeeeee esate esaetesaenesnans 84 Backing Up and Editing the Registry c cece cee eee eee tetera 85 Interrupt Moderation Policy Settings s c2siccscdeiprcennabecanceandiedneeerpicaranaceeaaiiaues 87 Creating Non Bootable Targets cccce cee o etcetera ene e nae 87 Using the Microsoft iSCSI Initiator Service cccecece cee eeee eee eset eeeeeeseeeeeeeenesaeens 87 Logging into a Target Using the Microsoft Software Initiator cccceeeeeeeeeeeees 88 Windows Multipath IO Support 2 c cccccsc lt cxedadxetecsencdseetavedaciebcatesccesheistdaasegaas 88 Multipath Support on Windows Server 2008 2008 R2 and 2012 ccceseeee seat ees 88 Logging into Targets for Multipath SUPport cccccecceece cece eset eeeeeeeeeeeeeneeaaees 89 Maximum Transmission Unit MTU for iSCSI Connections i 90 SCSI Error Handing eraser oreen RER AE EREE neal neuacesaneaees 90 Configuring LDTO and ETO on Windows SEPVel
51. 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 the session and continue 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 update from the target Following this error log entry the next three entries will indicate the session handle and the iSCSI parameters MaxCmdSN and ExpCmdsSN respectively Emulex Drivers for Windows User Manual 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 software updates at the Emulex website If applicable update the software P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 135 Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x12790006 Aconnection to the target was lost fo
52. that may be specified on the command 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 Verifies if appropriate that the selected driver is either 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 co installer FC and FCoE drivers only Emulex Drivers for Windows User Manual P009412 02A Rev A DE EMULEX 2 Installation 24 Text Only Driver Installation 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 elxdrv 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
53. 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 ProgramFiles 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 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 Emulex Drivers for Windows User Manual P009412 02A Rev A o Appendix D AutoPilot Installer Command Line and Configuration File Parameters 151 gt EMULEX AutoPilot Configuration File Software Configuration AUTOPILOT
54. the port driver error code of SP_INTERNAL_ADAPTER_ERROR which translates to an Event ID 11 entry in the system event log Emulex Drivers for Windows User Manual P009412 02A Rev A ys Appendix A Error and Event Log Information 132 gt lt EMULEX iSCSI Error and 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 E Computer management CL FATTE I e aten yew Window tep ale x e On ec hB e Ha System Toots aP Error MINOO 1A beses tone 1i KA SERVEREN n S Ei Event Viewer Qin MIDO 11I _ becewt fen 4 OA SERVEREN Aoplcation Giana 1 13 2009 Ih bedent Sonn 1 WA SERVEREN Seosty Warsita SRO I bedrnt tere 2 wa SERVEREN L Srem Error i320 R23 belat teen 4 OWA SERVEREN e Shared Folders aisee vss ns u KA SERVEREN 2 1 Loca ies ord Graes g Performance Logs and Alert 13 uja SER Evert KA SERVEREN BB Orice Manager E fag Storage s wA SERVEREN BA mamit Storage Q Dye Source be2incsi t N NA SERVEREN Ok Defragmenter Q Tipe SEA AM Cegar None XS SYSTEM SERVEREN i A Tye Ena Evert D 11 E N NA SERVEREN Ea Services and Applications Q Ra 7035 SYSTEM SERVEREN Q 73 NA SERVER
55. the server chipset beyond standard virtualization technologies including operating system control of PCI Express and interrupt remapping The server may have BIOS options to control SR IOV and typically these are disabled by default The following may need modification in your system BIOS during boot e Enable Virtualization such as Intel VT x or AMD V This is required for any virtual machine e Explicitly enable SR IOV in the system BIOS This may be called Intel VT d Virtualization Technology for Direct I O AMD Vi AMD I O Virtualization Technology or IOMMU Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration gt lt 69 gt lt EMULEX NIC TOE Driver Configuration Emulex PXESelect Configuration for SR lIOV The Emulex OCe11000 family of adapters requires enabling firmware support for SR IOV within the Emulex PXESelect BIOS See the Boot for NIC iSCSI and FCoE Protocols User Manual for more information To enable firmware support in the PXESelect BIOS 1 Press lt Ctrl P gt during the Emulex PXE Select splash screen as the server boots A screen appears showing global options 2 Set the following options to use SR IOV e Advanced mode Enable e Universal Multichannel UMC Disable 3 Save the settings and enable SR IOV for each PCI function The server reboots after this modification SR IOV Server Validation Use the following Microsoft PowerShell commands to determine if your s
56. 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 98 Troubleshooting the FC FCoE Driver Ipfc_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
57. 0 7 Interpretation 0x18 Port shutdown event LightPulse 0x19 Port in off line state LightPulse 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
58. 12 02A Rev A DE EMULEX 2 Installation 33 Removing Emulex Driver Kits and Drivers 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 ElxPlus Driver Note Uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled To uninstall the ElxPlus driver 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 P009412 02A Rev A 3 Configuration 34 DG EMULEX FC FCoE Driver Configuration 3 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 Table 3 1 Storport Miniport Driver Parameters 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
59. 2 seconds decimal Default 0 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 37 DG EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol DriverTraceMask The DriverTraceMask parameter is only available Dynamic on operating 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 FC only up to and parameter requires the authentication to be including 8 Gb 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 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
60. 32 3 CONTIUIALON scitesdiciaccincianiereannanedianetcnateratemntieeteniieeenaeiannee oo FC FCoE Driver Configuration ssssssssssrssssnnnnnnnnnnnnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnn 34 Configuring FC Driver Par ainiG vers 4ccciisees secret tavsim ve cteenvinseestenctusteapen ciaena snes 34 Server Performance with FC Drivers ccceeeece tees eres teat neat eee eeeeeeeenaeees 42 I O Coales g aan paces esse ne aa E pects ancy bnaned E RETEA cawerdsunise abso vaants 42 Performance Testing asrin inaen E EE sc aadeen ead EE ATAR TEER ATEREA 42 NIC TOE Driver Configuration sssssssnssnnnnnnnsnunnnnnnnnnnnnnnununnnnnnnnnnnnnnnnnnnnnnn 44 Configuring NIC TOE Driver Options ssssssssssssrrrrrrerererrrrrrrrrerrrrrrrrrrrrrrre 44 Configuring Windows Server NIC TOE Driver Parameters ccccccseeeseeeeaneeeaees 55 Modifying Advanced Properties ccc eee nen nett eed 55 Statistics Property Page nnn ey 57 Using OCCFG for Windows NIC TOE Driver Options cccccceeeeeeee sete seer eenee es 61 Displaying OCCEG Help sid cisaesidices eae teen iniae E A T EEEE EEE D 61 Selecting an Adapter 0 teed 62 Configuring Device Parameters cece cece cence eee eee ee eee tee nett eee 63 Viewing Device Parameters 0 ccc cece ee enter tetas 64 Resetting All Parameters vise iscsaschameeesdesscuneseiansesueademaned A DEE TAEA EET RAEE 64 Displaying All Parameters ccccecce cece eee e
61. 4 Manually Installing or Updating the Emulex Protocol DriversS csccccceeeseeeesseeeeaes 25 Installing the Emulex PLUS ElxPlus Driver for the First Time cacce 25 Updating the Emulex PLUS EIXPIUS DriVer cccccecee cece eee e eee e ee eee ee eae ee ene ees 26 Installing or Updating the FC FCoE Storport Miniport Driver cccceceeeeeeeeeeees 26 Installing or Updating the iSCSI Driver sssssssrsrreeresssrsrrrrrrerrrrsrrrrrrrrrrrrre 27 Installing or Updating the NIC Driver oc 120 sceer inked edeneemnbeanecadebacanecuiebauenekinerds 28 Windows Server 2008 wis ice cisscsasroitaianivd ines nieried Udlarcumdecdeneeiaa de rreneeunens vance 28 Windows Server 2012 ccecc cece cece cece cent eee e esate eee EEEE eee sae teat eseeeseneeatennneas 29 Removing Emulex Driver Kits and Drivers ccccscccscceescceeccceeesueeesueeesueeesueeeager 30 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 SXC EMULEX Table of Contents Uninstalling Emulex Driver RitSiicsieissiiucnbsatenidwooidiysictoruivexweianeeaiedaiaees 30 Windows Server 2008 ccccec eee ee eee i TE EE eet EE 30 Windows Server 2012 aiiin eeina aden idthebonddanteesdiervescnnie alas diaiaheedadatian 31 Uninstalling the Emulex Drivers scccesssriscsiessivina ventas yp taronrseeeraveors yeiaeedeatbnda 31 Windows Server 2008 nocniinc menait aniran nra oriei Ea AN edie en EIEEE 31 Windows Server 2012 neesiinaocnacriinsi oi i ienien ai i nr O NE a E e A A AER A
62. 412 02A Rev A gt G EMULEX 4 Troubleshooting 113 Troubleshooting the iSCSI Driver Troubleshooting the iSCSI Driver Troubleshooting the Cisco Nexus Switch Configuration Note The LACP cannot be used on the an iSCSI port Table 4 5 Cisco Nexus Switch Situations for iSCSI Problem Solution The system is showing an excessive number of Ensure that the LACP is not used on the I O timeouts as a result of the switch routing frames to the incorrect port iSCSI port iSCSI Driver Troubleshooting The following table provides troubleshooting information for the iSCSI driver Table 4 6 Troubleshooting the iSCSI Driver Problem Overall failure Answer Solution Use the iSCSlSelect 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 133 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 ne
63. 7 55 Warning This adapter may have a problem This adapter exposes a vulnerability recovering from corrupted use of to the VM that may allow the VM to SR IOV Assigning an SR IOV device crash the entire physical computer to a Virtual Machine could leave the This is no different than running a system vulnerable and lead to physical adapter SR IOV should only instability It is strongly be used when the VM has a trusted recommended that you assign server administrator SR IOV devices only to Virtual Machines that run trusted workloads or consider disabling the use of SR IOV 0x00036 54 Warning Incompatible optics Replace the incompatible SFP Replace with compatible optics for transceivers with compatible ones card to function for the card to function correctly 0x00035 53 Warning Optics of two types Remove one SFP transceiver or installed Remove one optic or install a matching pair of SFP install matching pair of optics transceivers Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix A Error and Event Log Information NIC TOE Error and Event Logs G EMULEX 128 Table A 12 NIC TOE Event Log Entries Continued Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x00034 52 Warning Optics faulted incorrectly Reseat the SFP transceiver If the installed not installed Reseat problem is not resolved replace it optics if issue not resolved r
64. 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 exe a TOE 3 pq OneConnect Network Config 4 6 94 0 Emulex OneConnect OCe11102 N X NIC TOE 3 Ethernet 2 Display all properties Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 65 DG EMULEX NIC TOE Driver Configuration Registry Class of Service 802 1p 1 Auto Priority Pause Driver Class of Service 802 1p 1 Auto Priority Pause Registry Enhanced Transmission Selection 0 Disabled Driver Enhanced Transmission Selection 0 Disabled Registry Flow Control 3 Rx amp Tx Enabled Driver Flow Control 3 Rx amp Tx Enabled Registry IPv4 Checksum Offload 3 Rx amp Tx Enabled Driver IPv4 Checksum Offload 3 Rx amp Tx Enabled Registry Interrupt Moderation 4 Adaptive 30k Int sec default Driver Interrupt Moderation 4 Adaptive 30k Int sec default Registry Large Send Offload V1 IPv4 1 Enabled Driver Large Send Offload V1 IPv4 1 Enabled Registry Large Send Offload V2 IPv4 1 Enabled Driver Large Send Offload V2 IPv4 1 Enabled Registry Large Send Offload V2 IPv6 1 Enabled Driver Large Send Offload V2 IPv6 1 Enabled
65. EMULEX wW M Emulex Drivers for Windows User Manual FC and FCoE version 2 74 014 001 NIC version 4 6 142 8 iSCSI version 4 6 130 0 P009412 02A Rev A Emulex Connects Servers Storage and People gt G EMULEX Copyright 20003 2013 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 produ
66. EN Q 7035 SYSTEM SERVEREN Q 73 NA SERVEREN Q 7035 NETWORK SER SERVEREM Q m NA SERVEREM Q a NyA SERVEREN Q a5 NA SERVEREN Q u Wa SERVEREN Q 15 WA SERVEREN x Wa SERVEREN Q 1 nA SERVEREN x WA SERVERIN WA SERVERIN 3 WA SLAVERI HO ONA SERVEREN G 1 WA SERVEREN WA SERVEREN WA SERVEREN 13 WA SERVEREN Bere ALSO 11 05 10 OCON teen 10016 NETWORKSER SERVEREN Qin ALIO 11 05 10 DEON Seon 10036 NETWORKSER SERVEREN Ginan ALO 81 05 08 AmtociamSve Neon 3 KA SERVEREN Giens trazo 11 05 04 DEON fone 10025 WA SERVEREN J J 2 Gana R 1 06 04 evertion Neon 0S NYA SERVEREN z E Fs 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 Emulex Drivers for Windows User Manual P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 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 indicate
67. Error and Event Log Information 121 gt lt EMULEX FC FCoE Error and Event Logs Table A 2 Malfunction Errors Continued Bits 0 7 Interpretation 0x6A Unrecognized ELS command received 0x6F Received PRLI from un typed source 0x73 Failed to pend PRLI for authentication 0x77 Failed to allocate Node object 0x7A REG_VPI failed 0xA3 Command context allocation failure OxAB SCSI command error OxAC Read check error 0xB0 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 0xA2 SCSI address assigned to discovered target 0xA4 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 P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information 122 FC FCoE Error and Event Logs Event Indicators Table A 4 Event Indications Bits
68. L FCoE FCP FDISC FDMI FLOGI FW Gen 2 or Gen2 GET_FT GUI HBA hex ICMP IEEE IET Int I O IOCTL iocb IOMMU IP IPL IP NAT IPSec IPv4 IPv6 iSCSI iSNS 1 Introduction 12 Abbreviations discovery node count direct memory access domain name server device specific module extended link service extended time out enhanced transmission selection file area network Fibre Channel Fibre Channel arbitrated loop Fibre Channel over Ethernet Fibre Channel Protocol Discover F_Port Service Params Fabric Device Management Interface fabric login firmware Generation 2 PCI Express get port identifiers graphical user interface host bus adapter hexidecimal Internet Control Message Protocol Institution of Electrical and Electronics Engineers iSCSI Enterprise Target interrupts Input Output Input Output control input output control block input output memory management unit internet protocol initial program load IP network address translation IP Security protocol Internet Protocol version 4 Internet Protocol version 6 internet Small Computer System Interface internet Storage Name Server Emulex Drivers for Windows User Manual P009412 02A Rev A gt EMULEX IQN KB LACP LAN LDTO LOGO LSO LS_RJT LUN MAC MPIO MSI MSS MTU N A NAS NAT NDIS NIC NTFS NUMA NPIV OCCFG OS PCI PCle or PCIE PDISC PE PHY PLOGI POST PRLI PRLO PT PT PXE QFE QoS Emulex Drivers for Wind
69. NA 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 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 Microsof
70. OR 0x04 BUSY 0x05 TIMEOUT 0x09 SELECTION TIMEOUT 0x0A COMMAND TIMEOUT 0x0B BUS RESET 0x0E DATA OVERUN 0x12 ASC ASCQ 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 P009412 02A Rev A Appendix A Error and Event Log Information f 126 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 infor
71. SI IDs according to the selected binding method Persistent bindings do not take effect with the driver in stand alone mode 0 automap is disabled The OneCommand Manager application persistently sets the SCSI address of a discovered FCP capable FC node target 1 automap by WWNN 2 automap by WWPN 3 automap by DID Value 0 3 Default 2 Class 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 P009412 02A Rev A 3 Configuration 36 DG EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol ConfigScale ConfigScale sets the memory footprint profile in Reboot OneConnect and accord with the anticipated use case on a per Emulex 16 G
72. SI targets On the iSCSI target system LUNs can be numbered sequentially they do not have to start at zero P009412 02A Rev A se Appendix A Error and Event Log Information 116 gt 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 a x Event Date Source elxstor Time amp 52 19PM Categoyr None Type Error EventID 11 User N A B gt Computer EMULEX D4C6ESBE 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 t
73. Save the reg file to a location off of the server as a precaution ae YN Navigate to HKLM Software Microsoft Windows NT CurrentVersion Virtualization Create a DWORD type entry named IovEnableOverride Set the value of IovEnableOverride to 1 Reboot the system S200 Nr OY 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 Verifying the Driver Version To verify the Emulex device driver meets the minimum requirements 1 Select Server Manager gt Dashboard gt Tools gt Computer Management 2 Click Device Manager The Device Manager opens File Action Media Clipboard View Help 3 9 O O ii I gt bs oo sips 2 T 1 File Action View Help oy lt gt m mR E OR 5 2 2 WIN QosPoDsiHEG p 7 Computer b aa Disk drives p A Display adapters 3 DVD CD ROM drives ta of Foy dk ie HEES ca Floppy drive controllers 53 Human Interface Devices ig IDE ATA ATAPI controllers lt Keyboards A Mice and other pointing devices E Monitors 4 I Network adapters E Emulex OneConnect OCe11102 1 NIC 6P Microsoft Hyper V Network Adapter iy Microsoft Hyper V Network Adapter 3 EP Microsoft Hyper V Network Adapter 4 EP Microsoft Kernel De
74. TOE Driver Configuration Using SR IOV with Emulex Devices Advisory OCe11100 series adapters may have a problem recovering from corrupted use of SR IOV Assigning an SR IOV device to a virtual machine could leave the system vulnerable and lead to instability It is strongly recommended that you assign SR IOV devices only to virtual machines that run trusted workloads or consider disabling the use of SR IOV This advisory is highlighting a use case where a rogue non Emulex digitally signed driver is installed by the system administrator in a virtual machine It is then possible for that rogue driver to crash an OCe11100 series networking adapter While there are many benefits to using SR IOV with virtualized workloads these benefits should be weighed against the potential risks in doing so As an example see the Microsoft TechNet Blog cited in the link below where the benefits and usage of the Windows Server 2012 Hyper V switch versus NIC SR IOV are noted http www emulex com downloads sr iov html Notes e SR IOV is supported only on OCe11000 series NIC adapters and 16 Gb UCNAs installed in Windows 2012 servers e SR IOV support requires the Emulex NIC driver for Windows 2012 SR IOV is supported inbox with Windows Server 2012 and in device drivers from Emulex with driver versions 4 2 390 6 and higher e The Windows Server 2012 inbox driver does not support 16Gb UCNAs Server BIOS Configuration SR IOV requires support in
75. 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 P009412 02A Rev A 3 Configuration 49 gt lt EMULEX NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Supported Option Name Acceptable Values Operating Systems Definition Network Address Valid MAC Address Windows 2008 This overrides the permanent MAC The default setting is None Windows 2008 R2 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 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 Windows 2012 valid Packet Size 1514 default Windows 2008 Configures packet size for 9014 Windows 2008 R2 OneConnect NIC only 8222 Windows 2012 This parameter determines the 4088 maximum packet size transmitted and received on the i
76. Windows User Manual P009412 02A Rev A 3 Configuration 56 gt lt EMULEX NIC TOE Driver Configuration The Windows Device Manager is displayed E Server Manager File Action View Help gt A m Bien ee ks Device Manager Actions am Emulex OneConnect OCe 11102 1 NIC TOE 10 K Emulex OneConnect OCe 11102 1 NIC TOE 9 E F Ports COM amp LPT amp Processors E lt Storage controllers lt gt Dell SAS 6 R Integrated Controller gt Emulex OneConnect OCe 11102 1 iSCSI Initiator gt Emulex OneConnect OCe 11102 1 iSCSI Initiator lt Microsoft iSCSI Initiator lt gt Microsoft MultiPath Bus Driver E System devices Universal Serial Bus controlers Figure 3 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 3 2 on page 57 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 P009412 02A Rev A 3 Configuration 57 DG EMULEX NIC TOE Driver Configuration Note Modifying properties causes the network driver to reload and some TCP connections may be temporarily dropped IT NIC TOE Pre x General Advanced Status Statistics Diagnostics SE EMULE X
77. a 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 Windows Server has not optimized the connection offload path Some applications that use numerous short 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 44 for the TCP Offload Optimization settings The default option is Optimize Throughput which produces the best throughput characteristics for certain t
78. 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 When software based iSCSI targets are logged into the UCNA Event ID 56 Driver SCSI 000000 Appears in the Windows event viewer This issue has been observed on Windows 2008 R2 under the following conditions e The iSCSI target is a software based target MSiSCSI IET StarWind that uses a local hard drive or a RAM disk for its backend LUN e Different UCNA ports are involved in the login A SAS controller is present on the system Emulex Drivers for Windows User Manual This occurs caused because of an issue with the data reported by the iSCSI target in the Product Identification field in response to the standard inquiry from the UCNA This field should be unique among different targets LUNs but software based targets report the same pre formatted data for all the LUNs across all targets When Windows encounters the same Product Identification field for different LUNs with the same Bus Target Lun field it records error in the event log No other effect has been found as a result of this behavior The workaround for this error is to use non overlapping LUN numbers for the various LUNs across the various iSC
79. age 62 The program prompts for an operation such as modifying or querying a parameter value Follow the prompt 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 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 can 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 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 68 DG EMULEX NIC
80. age when standard 1514 byte sized frames are in use Notes e If checksum offloads are disabled RSC should also be disabled RSC depends on checksum offloads for better performance Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled P009412 02A Rev A SG EMULEX 3 Configuration 51 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Acceptable Values Recv Segment Coalescing IPv6 2008 2008 R2 2012 Disabled default on Windows Enabled default on Windows Supported Operating Systems Windows 2008 Windows 2008 R2 Windows 2012 Definition RSC 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 Notes If checksum offloads are disabled RSC should also be disabled RSC depends on checksum offloads for better performance Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled SR IOV Disabled default Enabled Note For OCe11102 and 16Gb UCNAs only Windows 2012 SR IOV enables the adapter to allocate virtual PCI functions for each virtual machine in Hyper V Note that the virtual switch and virtual network adapter must have SR IOV enabled
81. ailure memory allocation in the driver Check low memory conditions 0x0005 5 Error Failed to register scatter gather This failure occurred due to a failed DMA 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 This may be a firmware driver failed mismatch or corrupt installation Check the firmware version reinstall the firmware and try again This may also indicate a hardware problem 0x0001 1 Informational The driver successfully loaded This message is informational and indicates successful loading of the device driver 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 Click the Start tab on the bottom of the screen Click Run Type eventvwr and click OK Click Windows Log Click System Click the be2iscsi error under System Events to show the details of the event ONO pe Da The iSCSI driver logs errors with
82. al 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 83 DG EMULEX NIC TOE Driver Configuration Interrupt Coalescing The Windows Server network 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 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 Increa
83. apter 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 6 Select the Driver tab 7 Click Update Driver The Update Driver wizard starts 8 Select No not this time Click Next on the Welcome to the Hardware Update Wizard window 9 Select Install from a list or specific location Advanced and click Next 10 Select Don t search I will choose the driver to install and click Next 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 11 Click Have Disk and direct the Device Wizard to the location of oemsetup inf 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 HBA for the 32 bit driver version Or e C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA for the x64 driver version 12 Click OK Select Emulex LightPulse LPX000 PCI Slot X Storport Miniport Driver your adapter model is displayed here 13 Click Next 14 Click Finish The driver installation has completed The driver should start automatically If
84. ation 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 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 internally up to a configured timeout period so that the operating system does not see I O errors This timeout period is known as 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 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 t
85. b port basis While the default value is 4 a value of adapters 1 is considered to be the typical use case The ConfigScale parameter supersedes the ExtTransferSize parameter for OneConnect adapters For OneConnect adapters For all values except 0 up to 1024 targets can be discovered and mapped When ConfigScale 0 only 128 targets can be discovered and mapped A value of 0 limits max XRIs to 512 Note Use ConfigScale 0 to minimize the driver s per port memory foot print When ConfigScale is set to e 0 the max transfer size is limited to 500 KB e 1 the max transfer size is limited to 1012 KB e 2 the max transfer size is limited to 2036KB o Use ConfigScale 2 if connecting to tape devices e 3 the max transfer size is limited to 2036KB which is the best setting if you are running performance benchmarks in a non production environment e 4 the max transfer size is limited to 512KB Emulex 16 Gb s adapters ConfigScale is always set at 4 The max transfer size is set according to the value of the ExtTransferSize parameter Values 0 1 2 3 and 4 Default 4 Note For Emulex 16Gb s adapters only the value of 4 is valid DiscoveryDelay n DiscoveryDelay controls whether the driver waits Dynamic 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
86. boots successfully but then gets stuck during the GUI portion of the installation right from the beginning HP N DL385G2 server 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 The system is showing an excessive number of I O timeouts as a result of the switch routing frames to the incorrect port Emulex Drivers for Windows User Manual Ensure that the LACP is not used on the FCoE port P009412 02A Rev A 4 Troubleshooting Q3 SG 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 FLOGI command that was sent to the fabric failed Severity Error Log LOG ELS verbose 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 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 perfo
87. bug Network Adapter pb F Ports COM amp LPT b Ea Print queues b E Processors b lt gt Storage controllers pE System devices lost 0 0z loss Figure 3 4 Device Manager for Windows Server 2012 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 71 gt lt EMULEX NIC TOE Driver Configuration Open the Network Adapters item find the Emulex OneConnect device and right click Select Properties from the context menu The OneConnect Properties dialog box opens showing the Driver page The Driver page contains the driver version number Genel Advanced Stamm Statutes Dever Doais Everts Resources Power Management Be Erde One Connect Ce 111024 NIC TOE lt Dever Provider Gader Onver Date 215 2012 Driver Verson 00 9999 4417 Dota Syner Emex Dyer Dotais To view detas about the cover es Update Dever To updato the ver softwear for thas device Ethe device fals aher updating the diver rol Dack to the previeuwsly installed dever Disables the selected device To uninstall the diver Advanced Figure 3 5 Emulex OneConnect NIC TOE Driver Properties page 4 Click Driver Details A window opens displaying the driver name Enabling SR IOV in the Emulex Device To enable SR IOV in the Emulex device 1 2 3 Select Server Manager gt Dashboard gt Tools gt Computer Management Click Device Manager The Device Manager opens See Figure 3 4 on page 70
88. cantly 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 the 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 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 81 DG EMULEX NIC TOE Driver Configuration During Nagling a single connection may have long pauses 200 ms between sending subsequent packets as the driver waits for more dat
89. cceseeeeeeeeeeeeeeeee es 149 SilentRebootEnable Enabling Silent Reboot ccccecceeceeeeeeeeeeetesateseneeneees 149 InstallWithoutQFE Enabling Installation if a QFE Check Fails ccccceeseeeeeeees 149 AutoPilot Configuration File ssssssssssunnnnnnnnnsnnnnunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 150 Using the Windows Environment Variable WProgramFiles ccc 150 Configuration Identification AUTOPILOT ID ccccccceseee eects sees eeaeenenes 150 Software Configuration AUTOPILOT CONFIG ccccccceeeeeeeeeeeeeeeeeeeaneennaes 151 Configuration Prompts Vendor Specific Questions STORPORT CONFIGURATION 151 QFE Checks Sl ORPORT QF ES evicarccicsctcesetase eerste ban WeawseantQeasraebigearees 152 Setting Up FC Driver Parameters STORPORT PARAMS c0ccceeeeeeneeeeaeeeeaes 153 Setting Up System Parameters SYSTEM PARAMS ccccecceeeeeeeeaeeeeeneeeenes 153 AutoPilot Installer Exit CodeS sssssssunnnnnnsnnnnnnnunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 154 AutoPilot Installer Installation Reports sssssssnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 155 Command Script ExaMple siccissicdsciedscdcscsevsdssisessssacsdsessesaesdversdsarsevennsedecees 155 Emulex Drivers for Windows User Manual P009412 02A Rev A SXC EMULEX List of Figures List of Figures Figure 2 1 AutoPilot Installer Warning Software First Installation cccseeeeeeeenees 22 Figure 3 1 Partial View of Windo
90. cket 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 set 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 55 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 Typical cases for using the MTU e Server interconnects are typically deployed using jumbo frames This is t
91. cribed on the Microsoft website When an NDIS driver is being installed manually on a Windows 2008 system the installer installs the first driver it finds even if it is not the latest version of the driver Emulex Drivers for Windows User Manual Windows 2008 picks up the first available driver it finds when an NDIS driver is being installed manually Thus an NDIS5 driver will be installed even if a Windows NDIS6 driver is available An event log message advises you to update to the latest driver for best performance P009412 02A Rev A gt EMULEX 4 Troubleshooting 111 Troubleshooting the NIC TOE Drivers Table 4 3 Troubleshooting the NIC TOE Drivers Continued Problem The system crashes or appears to hang In the case of a hang there could be a message indicating that the driver experienced a hardware malfunction Answer Solution There are several possible causes for this problem e Certain systems require an updated BIOS to properly manage the power states of newer Intel and AMD processors Check with your OEM for information regarding BIOS and firmware 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 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 shou
92. ct described in this manual at any time and without any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this manual Emulex disclaims any undertaking to give notice of such changes Emulex 3333 Susan Street Costa Mesa CA 92626 Emulex Drivers for Windows User Manual P009412 02A Rev A gt G EMULEX Table of Contents Table of Contents List Of FIQUIES a cisaisinnsa nmana ibe KES List OF Tabl6S viissicsassctcciariitatenssnenncensencndsstiens canines a iaa 1 Introduction sssssssnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnna L Driver Infor Matin caccscascesdcpssnssneaiwseaiansdanssnimaransiaqianieansswinniennaewiansanniemsnaen 10 COMPACIDUNICY os nevsecavernuvianteyeevewreceersiwer aa e AEE a iaa Vere 10 Operating System RequireMent so 0 c casciccvadeveces EEEE 10 ADDOVidtiOns issisisassasndadsdicasiisssriessneiaesaiecisarsiateaiasaieatanlataeisialesaeernctees 11 2 Installati n snaa aaa a aa a aaa a aana r AO Driver Installation QDI ONS sisiiacsictevswasiiacentsiasanadswesantinaswinas nanan aa 16 Onelnstall Installer cat tic totec tance eeesenenereeoaseetecmanedacunenpnet wack scence sete 16 Loading the Onelnstall Package ccccccecce cece eee e eats eee eeeeeeee eset eaeeeceteeeeeenesat
93. d e Authentication type One way CHAP Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix B Configuring iSCSI through DHCP 143 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 E D M 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 P009412 02A Rev A Appendix C Port Speed Specifications 144 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 sp
94. d by this adapter Transmit Packet Rate The rate of transmit packets 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 P009412 02A Rev A 58 gt EMULEX 3 Configuration 59 NIC TOE Driver Configuration Table 3 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 TOE TCP Offloads The
95. d 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 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 RCMD service was installed for example a script similar to the following would run remote execution remd serverl g emulex autopilot installer fc apinstall exe 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 if not errorlevel 2001 goto none echo The driver found is the same or older than the existing driver Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX Command Script Example goto serverlok none if not errorlevel 1248 goto noreport echo No Emulex adapter found goto serverlok noreport if not errorlevel 110 goto nocfg echo
96. dicating 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 0x31840001 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 LDTO If reestablished any sessions that previously the UCNA has connection to the existed are reestablished and the devices is target there will be event log entries available for I O 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 Emulex Drivers for Windows User Manual P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID 0x1180000A Message The logical link on the OneConnect Port is down traffic is disallowed on this function Description Recommended Reso
97. dows Server 2008 R2 and Windows Server 2012 x64 versions Enterprise and Server Core installation Windows 7 Ultimate Enterprise or Professional edition x64 only supported on only OneConnect OCe1110x Universal Converged Network Adapters UCNAs Windows Pre installation Environment PE 2 x 3 x or 4 x Note AutoPilot Installer is not supported for use with Windows PE See the Windows Automated Installation Kit WAIK documentation for instructions on including drivers with your Windows PE images Note Check the Emulex website for required updates to the Windows operating system or the Emulex drivers Abbreviations ACC accept ACK acknowledgement ADISC discover address AL_PA arbitrated loop physical address API application programming interface ARM Advanced RISC Machine ASC additional sense code ASCO additional sense code qualifier BIOS basic input output system CHAP Challenge Handshake Authentication Protocol CNA Converged Network Adapter CNT count CPU central processing unit CRC cyclic redundancy check CT command transport CTCP compound TCP DAS direct attached storage DCB Data Center Bridging DCBx Data Center Bridging Exchange Protocol DPC deferred procedure call DHCP Dynamic Host Configuration Protocol DID destination ID DIMM dual in line memory module DISC discover Emulex Drivers for Windows User Manual P009412 02A Rev A gt EMULEX DISC CNT DMA DNS DSM ELS ETO ETS FAN FC FC A
98. e A lot of small packets lead to this behavior on almost 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 th
99. e 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 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 offloading 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 P009
100. e Option 2 on page 21 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation gt lt EMULEX AutoPilot Installer Overview Note The name of the driver kit installer depends on the current version identifier 2 If you plan to create Windows 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 20 e For control of all interactive installation settings see Option 2 Run the AutoPilot Installer Separately on page 21 e For an unattended installation with AutoPilot Installer see Unattended Driver Installation on page 23 AutoPilot Installer Overview AutoPilot Installer runs after the driver kit and the OneCommand Manager application are installed AutoPilot Installer can be installed e Immediately after the driver kit installation has been completed e Ata later time using an interactive installation
101. e PCI Express bus or main memory In the Status tab 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 P009412 02A Rev A 3 Configuration 61 DG EMULEX NIC TOE Driver Configuration Table 3 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 po
102. e 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 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 0x0009 9 Error Failed to register interrupt service Thisis an NDIS error Verify that routine hardware resource conflicts do not exist 0x0008 8 Error Failed to get TCP offload handlers Thisis an NDIS error Verify the NDIS version is valid for the driver 0x0007 7 Warning A memory allocation failure This warning occurred due toa occurred during driver load failed memory allocation Check low Performance may be reduced memory conditions Use a smaller MTU or disable TCP offload to reduce driver memory requirements Emulex Drivers for Windows User Manual P009412 02A Rev A SXC EMULEX Appendix A Error and Event Log Information 131 iSCSI Error and Event Log Table A 12 NIC TOE Event Log Entries Continued Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x0006 6 Error Driver load failed due to memory This failure occurred due to a failed allocation f
103. e 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 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 gather list for an SRB an IO it failed to retrieve a scatter gather list from has failed the 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 initialization failed during 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
104. e 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 malfunction 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 P009412 02A Rev A 117 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
105. e 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 be a corresponding answer section with its corresponding driver parameters listed beneath it The answer uses the format answer 0 DriverParameter Paraml value Param2 value answer 1 DriverParameter Paraml value Param2 value answer n DriverParameter Paraml value Param2 value Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Configuration File Example of STORPORT CONFIGURATION section STORPORT CONFIGURATION The first section contains the driver parameters common to all configurations no matter what answers are given DriverParameter EmulexOption 0 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
106. ecifications 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 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 P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 145 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
107. eee eee tees eeeeeee eens UENDA 64 Using Interactive MOde ccccceeseeee eect cease eee cnet eee ttrt tE seen eeeat saat eceeeeeeeene eaten 67 Parameter Help dicpccsanenicenesshyiistadnetiniseadone pany ATERPE ERE TEER 67 Using SR IOV with Emulex Devices cceccee eee e eter eee ee et een et ee nen ne nenne neni ees 68 Server BIOS Configuration nent 68 Emulex PXESelect Configuration for SR IOV cccccece cee eeee eens eeeeeeeeeeeeeeeeeenesatens 69 SR IOV Server Validation sivccinetecesiaatewhsaoedd aiina iae OE EA E EAA iE 69 Verifying the Driver Version sssssssssrrrsssrrrrrrnst att en nee 70 Enabling SR IOV in the Emulex Device sssssssssssseerererrerrrerrrrrrrrrrrrrrrrrrrrrrrrrr 71 an A TTE E E E E E T T TTT T E E E 72 Venfying SR IOV wd eeni naa iogarlneiia nana leioain soesanuiey anaemia admatsandicintieiunta aan 72 Network Driver Performance TUNING cccceceee eect eeeeeeeeeeeeeeeeeeaeeeeaeeeenenenas 74 Optimizing Server Hardware and BIOS Configuration ccccecceeeeeeeeeeeeeeteeneeenes 74 Windows Server Network Driver 0 cece eee ete ens 75 Checksum Offloading and Large Send Offloading LSO cccsecceeeeeeeeeeeeeeeeeaes 78 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic c0ceeeees 78 TGP Off loading TOE wi siscctteadias sans ger dtus fas Enia AKENE Rag eeetanes 80 Emulex Drivers for Windows User Manual P009412 02A Rev A 4 Table
108. een the adapter the Emulex Storport Miniport driver the host operating system and the host memory Note Context allocation failures are rare Emulex Drivers for Windows User Manual P009412 02A 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 1 2 Click Run 3 Type eventvwr and click OK 4 Click Windows Log 5 Click System 6 127 NIC TOE Error and Event Logs Click the be2net error under System Events to show the event details NIC TOE Event Log 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 0x0003
109. 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 3 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 If the 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 85 DG EMULEX iSCSI Driver Configuration
110. egs 17 AutoPilot Installer ccactaiarsdaceuytesenaceteniasdasteg aise adesymiiedatagatiagaceeasetidattasans 17 Driver Kit Installer OVGIWiew sndecintcdsstasseticdsicasederaicaierenieneieenetsiaereeradeeeds 18 Installing the Driver Ribs ssercduceceedaseacedosputeaent oa bbsercnceaaheceeesceneieatencenensieancs 18 AutoPilot Installer Overview ssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 19 Starting Installers from a Command Prompt or Script cccceceeeeeeeee seer eee ees 20 Running a Software Installation Interactively cccccccee eee cece tesa eee eeeeeae eens 20 Option 1 Automatically Run the AutoPilot Installer ccccecceeececeeeeeeeeeeeeeeenes 20 Option 2 Run the AutoPilot Installer Separately cccccseeeeeeeeeseeeeeeeeeeeeneeaees 21 Hardware First Installation or Driver Update cccccccceceeee sees eeeeeeeaeeeenaeenas 21 Software First Installation c ccc eee eee eee ee eee eer eE EEE EE EE DEE EE EEE EES 22 Text Only Driver Installation ssssssssnsnnnnnnnnsnsnnnnnnnnnnnnnnnnnnnnnnnnnnanunnnnnnnnn 23 Unattended Driver InStallatiGn c sicceisecscstssiacecsstealbelooedetiedenstsdalseneergaaivenas 23 Option 1 Install the Driver Silently cc eee eee eee ee eee tne 24 Option 2 Run the Driver Kit Installer Separately cccccceeeeeeeeeeeeeseeeeeeeeeneeaes 24 Installation Failure ciceossessivesuesdbeuvecsengMteeenteahsonenionsheneesacacnlonenactansateeass 2
111. em prompt navigate to the Program Files folder on an x86 system or on a 64 bit system 2 Navigate to Emulex AutoPilot Installer 3 Run the following batch files e Uninstall_fc_kit bat e Uninstall_cna_kit bat e Uninstall_nic_kit bat e Uninstall_iscsi_kit bat The driver files are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installer 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation 31 gt G EMULEX 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 4 xx 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 Server Core System To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files folder 2 Navigate to Emulex AutoPilot Installe
112. emark A target reset operation has completed Warning LOG _FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0713 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 Emulex Drivers for Windows User Manual The driver is re initializing the link speed to auto detect Warning LOG _ LINK EVENT verbose None required P009412 02A Rev A gt EMULEX 4 Troubleshooting 106 Troubleshooting the FC FCoE Driver Ipfc_mes1303 Link Up event tag x x link speed dG topology 0 Pt2Pt 1 AL d Description Severity Log Action Remarks 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
113. eplace 0x00033 51 Warning SR IOV virtualization failed Check system BIOS settings or initialization Check system BIOS disable SR IOV for the adapter settings or disable SR IOV for the adapter 0x00032 50 Warning The Ethernet link is down due to Improve the cooling conditions for PHY over temperature condition the device Improve cooling for the device 0x00031 49 Warning RSS is limited to 4 queues Enable Enable Advanced Mode in the PXE Advanced Mode in the PXE BIOS to Select BIOS utility during boot to use use up to 16 queues This may up to 16 queues This may require a require a firmware update firmware update See the Downloads section of the Emulex website for compatible firmware 0x00030 48 Warning SR IOV is not enabled Update the Update the firmware enable SR IOV firmware enable SR IOV in the in the server BIOS and enable server BIOS and enable SR IOV and SR IOV and Advanced Mode in the Advanced Mode in the PXE BIOS PXE Select BIOS utility See the Downloads section of the Emulex website for compatible firmware 0x0002f 47 Warning VMQ offload is disabled Disable Disable SR IOV support in PXE BIOS SR IOV support in PXE BIOS to use _ to use VMQ VMQ 0x0002d 45 Error Error recovery failed The device 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 inf
114. er name must uniquely 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 Emulex Drivers for Windows User Manual P009412 02A Rev A f 3 Configuration 64 DG EMULEX NIC TOE Driver Con
115. er 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 P009412 02A Rev A gt G 3 Configuration 42 EMULEX FC FCoE Driver Configuration Server Performance with FC Drivers 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 3 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 h
116. er 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 Table 3 7 iSCSI Driver Options on page 85 for the correct range of values Oxl1d Warning A configuration parameter is invalid The iSCSI driver ignored a configuration entry because the entry was invalid Check the registry configuration for new driver parameter entries The invalid entry must be removed or corrected See Table 3 7 iSCSI Driver Options on page 85 for the correct range of values Oxle Error Emulex Drivers for Windows User Manual 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 P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 140 Table A 14 iSCSI Error Log Entries on Windows 7 Windows Server 2008 R2 and Windows Server 2012 Message ID Severity Message Recommended Resolution Ox1f Error Hardware initialization has The hardware initialization has failed This failed error code A error causes the driver load to fail The error code included in the event log ent
117. errupt 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 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 For example on a four processor server that interrupts all processors without RSS the DPC jumps 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 applicati
118. erver is capable of SR IOV These commands may be run prior to installing the Hyper V role e Get VmHost e Get NetAdapterSriov e Get VmNetworkAdapter e Get VmSwitch See Microsoft documentation for more information Note Early SR IOV capable chip sets had errors that may prevent SR IOV from operating in Windows 2012 The PowerShell command Get VmHost fl includes lovSupportReasons that indicates if the chipset suffers from this issue Enabling SR IOV on Unqualified Servers If Windows 2012 detects a problem with the system I O remapping hardware you may still be able to use SR IOV by explicitly enabling SR IOV in the registry using lovEnableOverride Note Emulex recommends this procedure for trusted virtual machines only Note Emulex recommends that you make a back up of your registry before you make any changes Caution Using registry editor can cause serious issues that may require you to reinstall the computer s operating system Emulex cannot guarantee that issues resulting from changes you make to the registry can be repaired Use the registry editor at your own risk Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 70 gt lt EMULEX NIC TOE Driver Configuration 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
119. es Lookahead Split Enabled default Disabled Note For OCe11102 UCNAs only Windows 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 Note Lookadhead split is not supported for jumbo frames Virtual Machine Queues Transmit Enabled default Disabled Note For OCe11102 and 16Gb UCNAs only Windows 2008 R2 Windows 2012 If this option is enabled with VMQs separate transmit queues are created for each VM network interface Send and receive interrupts for a VM network interface are processed on the same CPU s VLAN Identifier 802 1q Not Present default 1 to 4094 Emulex Drivers for Windows User Manual Windows 2008 Windows 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 should be used to configure VLANs on each virtual machine P009412 02A Rev A
120. evice Status shows This device cannot start Code 10 and an Event 11 error is logged in the Windows system event log for the iSCSI driver with 0x31840006 in the 5th DWORD There is no workaround for this issue When an iSCSI UCNA is used to log in to an iSCSI target and the LUN configuration on the target is changed neither the UCNA nor the WMI GUI see the updated LUN configuration Emulex Drivers for Windows User Manual If an iSCSI target provides an asynchronous event notification to the UCNA when its logical unit inventory has changed the iSCSI driver initiates a bus rescan and the LUNs are updated dynamically However if an iSCSI target does not provide an asynchronous event notification the LUN list is not updated dynamically Perform a manual rescan in Disk Management P009412 02A Rev A gt EMULEX 4 Troubleshooting 115 Troubleshooting the iSCSI Driver Table 4 6 Troubleshooting the iSCSI Driver Continued Problem A login to new target fails after Microsoft iSCSI Initiator Service is installed Answer Solution When Microsoft iSCSI software is installed the service chooses a default IQN name for the UCNA The Microsoft iSCSI service 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
121. ex 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 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 P009412 02A Rev A 3 Configuration 43 DG 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
122. f 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 Click OK Select Emulex PLUS Click Next and click Next again to install the driver Emulex Drivers for Windows User Manual P009412 02A Rev A 25 DE EMULEX 2 Installation 26 10 Manually Installing or Updating the Emulex Protocol Drivers Click Finish The initial ElxPlus driver installation has completed Continue with manual installation of the Storport Miniport Driver See Installing or Updating the FC FCoE Storport Miniport Driver on page 26 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 10 11 12 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 20 for instructions on how to do this Select Start gt Settings gt Control Panel gt Administrative Tools gt Computer Management Click Device Manager left pane Click the plus sign next to the Emulex PLUS class right pane to
123. figuration e The default value will set the key to the driver s default value If the key is optional the default value may be equivalent to deleting the key For example occfg a emulex s vlan delete occfg a emulex s rss default 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 occfg a emulex x Displaying
124. g 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 the Microsoft website In a multipath configuration the driver parameters LDTO and ETO can be configured to control the amount of time it takes for the failover operation to complete The default value of LDTO is 20 seconds and the default value of ETO is 90 seconds For information on modifying the timeout parameters in a failover configuration refer to Error Handling Under MultiPath MPIO and Cluster Configurations on page 91 If the ETO or LDTO value needs to be modified 1 Locate the registry key HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters 2 Set the desired value of ETO and LDTO for example ETO 120 and LDTO 60 3 Reboot the system for the registry changes to take effect Log into the iSCSI target using WMI For more information see Logging into Targets for Multipath Support on page 89 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 89 gt lt EMULEX iSCSI Driver Configuration 5 Enable MPIO a Select Start gt Administrative Tools gt Server Manager b In the Server Manager tree click Features c Inthe Features area cl
125. g the SR IOV direct hardware access aes Le Saus Statisses Diagnostics S GEMULEX Device Statistics Statistic Receive Throughput TCP Offload Transmit Rate VMQs Allocated Interrupt Rate 4 0 0 0 0 0 0 0 0 0 0 1 0 D Receive Drops No Memory DMA limits Rerrie Dens No Fema 2 aind gi Be Figure 3 7 Emulex OneConnect NIC Statistics Properties page Verifying SR IOV from the Host Hyper V Server 1 From the Device Manager open the Network Adapters item click the Microsoft Hyper V Network adapter and right click Select Properties from the context menu The Hyper V Network adapter Properties dialog box opens showing the Driver page Select the Statistics tab From the Statistics tab locate the Virtual Functions Allocated item Virtual Functions Allocated shows the count of currently enabled virtual functions Note The Microsoft Powershell command Get NetAdapterSriovVf lists each SR IOV virtual function See Microsoft documentation for more information Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration gt lt 74 gt lt EMULEX NIC TOE Driver Configuration 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 requ
126. gs expression For example the command line all on one line elxdrv 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 21 and Unattended Driver Installation on page 23 Emulex Drivers for Windows User Manual P009412 02A Rev A o Appendix D AutoPilot Installer Command Line and Configuration File Parameters 146 gt 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 elxdrv 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
127. he most efficient configuration for high bandwidth server to server communication such as Network Attached Storage iSCSI and database transactions Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 77 DG EMULEX NIC TOE Driver Configuration e Servers connected to client systems that run desktop operating 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
128. he 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 unhandled exceptions in the hardware or this error log entry the next 3 entries firmware indicate the error codes 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 is in 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
129. i 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration QQ DG EMULEX iSCSI Driver Configuration 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 this 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 Inform
130. ianuaiis 111 TCP Offload FSU icceceserdescsiesdizerenicapassenence dbeevenieaiaractacssmheieeseteasaueca 112 Troubleshooting the iSCSI Driver sssssssnnrnnnsnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 113 Troubleshooting the Cisco Nexus Switch Configuration cece ee eee eee es 113 iSCSI Driver Troubleshooting ci1s stave prainteecsaneensbeconeekesceeieciuaseaeesataaresceucteat 113 Emulex Drivers for Windows User Manual P009412 02A Rev A 5 DE EMULEX Table of Contents 6 Appendix A Error and Event Log Information sssssssssssnnnnssnnnnnnnnnnnnnnnna 116 FC FCoE Error and Event LOgS ssssssssunnnnnnnnnsnunnnnnnnnnnnnnnannnnnnnnnnnnnnnnnnnnnnn 116 Viewing the FC FCoE Error LOg ss ssssssssesrrrrrrereresrrrrrrrrrrrrrrerrrsrrrrrrerert 116 Severity Scheme sintesenn Een e eE E NaN E eE a EE EEE AEE ANNER 117 Related Driver Parameter LogErTOT ssssssssssssssserssrerrrrerrrrrrrrrrerrrrrrerrerrrrrrr 117 Format of an Error Log Entry recien erara E edtae barat caer 117 Error COdES TableS sicctcantewiedtiaelaavenieadelaeadtiaasd en n n A 118 Viewing the FC FCoE Event Logit ia tccseccinetedabieivpdcteprecapcadenteesciacdareaeazeaiay 123 Event Log Interpretation ccccececccce cece cece eset eee eeeeeeeeeeee sate saeesaeeeeneneeags 123 Additional Event Log Information cccccceeeeecee seats eeeeeeeeeeteeaeesnteeeeeeneeaees 123 ASC ASCO E E E T E A saneaeadeatssante TE 125 Additional Notes on
131. iator iSCSI Name mismatch Please use iSCSISelect to set a single name for all controllers Press lt CtrI gt lt S gt to enter iSCSISelect Reboot required Answer Solution 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 initiator 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 When an iscsicli logouttarget command is issued back to back ina 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 This behavior is not specific to the OneConnect UCNA On a system running Windows 2008 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 D
132. ically 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 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 InstallWithoutQFE Enabling Installation if a QFE Check Fails Default False AutoPilot Installer checks for Mic
133. ick Add Features d Inthe 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 m 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 6 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 7 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 mult
134. ill not provide any additional performance P009412 02A Rev A 129 gt G EMULEX Table A 12 NIC TOE Event Log Entries Continued Appendix A Error and Event Log Information 130 NIC TOE Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x001d 29 Informational The network device is operating in 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 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 hardwar
135. ime 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration QJ DG EMULEX iSCSI Driver Configuration Configuring LDTO and ETO on Windows Server LDTO and ETO values are configured via the Windows registry Table 3 9 lists the default values of LDTO and ETO on Windows Server and the limits within which they can be configured Note Ifthe ETO is set to a number between 0 and 19 the driver assumes the value to 20 seconds internally You will not see any modification to the registry Table 3 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 lIdto 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 dr
136. in the Hyper V Manager When using SR IOV the Emulex NIC driver must be installed on each virtual function within the virtual machine SR IOV provides a direct hardware interface from the virtual machine to the networking adapter which reduces latency and improves performance The Windows 2012 Server SR IOV architecture establishes each Emulex virtual NIC with a corresponding emulated NIC This allows the virtual machine to seamlessly failover to the emulated NIC if SR IOV is disabled It also allows Live Migration to another system regardless of the installed NIC hardware TCP Checksum Offload IPv4 Disable RX Enabled TX Enabled RX and TX Enabled default Windows 2008 Windows 2008 R2 Windows 2012 TCP Checksum Offload IPv4 offloads the transmit and or receive IPv4 TCP checksum computation Offloading checksums increases system efficiency TCP Checksum Offload IPv6 Disable RX Enabled TX Enabled Emulex Drivers for Windows User Manual RX and TX Enabled default Windows 2008 Windows 2008 R2 Windows 2012 TCP Checksum Offload IPv6 offloads the transmit and or receive IPv6 TCP checksum computation Offloading checksums increases system efficiency P009412 02A Rev A 3 Configuration 52 gt lt EMULEX NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Supported Option Name Acceptable Values Operati
137. indows 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 Click OK Select Emulex OneConnect OCmXXXXX iSCSI Initiator your adapter model is displayed here Click Next Click Finish The driver installation has completed The driver should start automatically Installing or Updating the NIC Driver Windows Server 2008 Gy 01 pe a 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 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 dual channel 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 be2nd6x inf If you have installed the driver installer kit in the default folder the path is Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation 29 gt lt EMULEX Manually Installing or Updating the Emulex Protocol Drivers e C Progra
138. installed To uninstall the ElxPlus driver 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 window 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 Emulex 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 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 Emulex Drivers for Windows User Manual P0094
139. ion Severity Log Action Virtual Port fails on a FDISC to the switch with the error and reason listed Error LOG _NPIV verbose Check to ensure the switch supports NPIV Ipfc_mes1801 Memory allocation failure for NPIV port x x Description Severity Log Action Fails to allocated the block of memory for the Virtual Port Error LOG _NPIV verbose Check to ensure system has sufficient kernel memory Ipfc_mes1802 Exceeded the MAX NPIV port x x Description Severity Log Action Exceeded the number of Virtual Port allows on the adapter Error LOG _NPIV verbose Reduce the number of Virtual Ports Ipfc_mes1803 Virtual Port x x VPI x x successfully created Description Severity Log Action Emulex Drivers for Windows User Manual Virtual Port ID is successfully created Information LOG _NPIV verbose No action needed informational P009412 02A Rev A gt EMULEX 4 Troubleshooting 108 Troubleshooting the FC FCoE Driver Ipfc_mes1804 Removing Virtual Port x x VPI x x Description Severity Log Action Removing Virtual Port ID Information LOG _NPIV verbose No action needed informational 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 Se
140. ires 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 PCle data transfers This may be an option in the server 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 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 detec
141. iver and enable it again non boot drivers in Device Manager for the settings to take effect 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 can be configured to modify the timing characteristics of a failover operation If the iSCSI target is in Active Active failover mode the iSCSI driver can be configured to report I O errors as soon as they are detected by setting the iSCSI driver s LDTO and ETO parameters to 0 This allows the failover software to trigger a path failover to an active path or active node as quickly as possible 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 92 General Troubleshooting 4 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
142. iver 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 55 You can also set configurable driver options using Microsoft PowerShell on Windows Server 2012 Refer to the documentation that accompanies the Windows Server 2012 operating system for more information on using PowerShell For more information on NIC TOE driver options see Network Driver Performance Tuning on page 74 Considerations for Using UMC and NIC TOE Note UMC is not supported on 16Gb UCNAs e 64 VLAN can be used with each UMC virtual channel e SR IOV must be disabled when using UMC For additional information on UMC refer to the Emulex Universal Multichannel Reference Guide Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 45 gt lt EMULEX NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Supported Option Name Acceptable Values Operating Systems Definition Class of Service Automatic Priority default Windows 2008 The following modes are supported 802 1p Filtered Priority Windows 2008 R2 for selecting 802 1p priority tags User Priority Windows 2012 e Automatic Priority The DCBX standard allows the network adapter to negotiate priority class usage with DCBX
143. ld 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 P009412 02A Rev A gt EMULEX TCP Offload Failure 4 Troubleshooting 112 Troubleshooting the NIC TOE Drivers The following table lists common reasons why TCP offloads do not occur and their suggested fixes Table 4 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 disabled 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 disabl
144. lt 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 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 Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax 1an ReportLocation Setting Up an Installation Report Title and Location The automat
145. lution The iSCSI function may have been disabled in the PXESelect application If you disabled it intentionally you can ignore this message Viewing the iSCSI Error Log on Windows 7 Windows Server 2008 R2 and Windows Server 2012 The iSCSI driver on the Windows 7 Windows Server 2008 R2 and Windows Server 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 informational 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 7 Windows Server 2008 R2 and Windows Server 2012 Message ID Severity Message Recommended Resolution 0x02 Info Driver loaded successfully N A 0x04 Error Firmware version does not The driver version that is running on the match with driver version 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 Check the links to the UCNA connection to UCNA 0x06 Info Port link is up N A 0x07 Error Link down timeout expired on The link on the UCNA is down for a period the port all targets are lost exceeding the 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 wa
146. m 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 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 completed 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 Note Server Manager is set to open by default when booting Windows Server 2012 If it does not open automatically you can open it with the Server 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 dual channel 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 ocnd63 inf Select the desired oemse
147. m pre installation tasks unattended installations or text only installations For these tasks use the AutoPilot Installer kits Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation 17 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 and x64 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 FC driver package elxdrvr fc lt version gt exe e FCoE driver package elxdrvr fcoe lt version gt exe e iSCSI driver package elxdrvr iscsi lt version gt exe e NIC driver package elxdrvr nic lt ve
148. mation along with the SCSI status are provided In the specific case of code 0x9B this code indicates that the device responded 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 betw
149. mpted 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 context allocation 0x7C Menlo initialization error 0x7D Menlo initialization error Ox7E Menlo initialization error OxA0 Failed to initialize adapter port OneConnect OxA1 Failed to initialize adapter port LightPulse 0xC0 Insufficient revision level for STORPORT SYS 0xC1 Failed to allocate miniport un cached extension 0xC2 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 0xE0 Unable to allocate exchange for unsolicited ELS command OxE1 Mis configured ports event on indicated port link and status Bits 31 24 Port ID Bits 23 16 Link ID Bits 15 8 Link status 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 Emulex Drivers for Windows User Manual P009412 02A Rev A gt EMULEX Appendix A Error and Event Log Information 120 FC FCoE Error and Event Logs Table A 1 Severe Errors Continued
150. n Emulex Drivers for Windows User Manual Adapter initialization failed when issuing INIT_LINK mailbox command Error LOG_INIT verbose This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support P009412 02A Rev A gt EMULEX 4 Troubleshooting 102 Troubleshooting the FC FCoE Driver Ipfc_mes0458 Bring Adapter online Description Severity Log Action The FC driver has received a request to bring the adapter online This may occur when running HBAnyware Warning LOG _INIT verbose None required 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 OxA8 x 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 Targetld x x Lun x x Description Severity Log Action Emulex Drivers for Windows User Manual The driver has issued a task management command for the indicated SCSI device address Warning LOG _INIT verbose Review system configuration P009412 02A
151. nes the number of Ethernet receive buffers allocated per receive queue This number may be adjusted by the driver as needed Receive CPU Not Present or a value from Windows 2008 Sets the logical CPU used for 0 through number of CPUs on windows 2008 R2 processing the non RSS receive the system 1 i packets By default the driver Optional There is no default WdawE Aa intelligently chooses a CPU in the setting system so this parameter should only be used for advanced performance tuning RSS packets are processed by the set of RSS CPUs provided by the Windows operating system Receive Side Disabled Windows 2008 Support for multiple RSS queues if Scaling Enabled default Windows 2008 R2 enabled Windows 2012 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 For additional PCI functions RSS does not appear in the Properties List Recv Segment Coalescing IPv4 Disabled default on Windows 2008 2008 R2 Enabled default on Windows 2012 Emulex Drivers for Windows User Manual Windows 2008 Windows 2008 R2 Windows 2012 RSC 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 us
152. nformation 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 21 e Software First Installation page 22 Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation gt lt EMULEX AutoPilot Installer Overview al Option 2 Run the AutoPilot Installer Separately To access these options run AutoPilot Installer after the driver kit installation has been completed 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 147 for details
153. ng Systems Definition TCP Connection Enabled Windows 2008 Note TCP Connection Offload is not Offload IPv4 Disabled default Windows 2008 R2 supported on 16Gb UCNAs Windows 2012 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 e NDIS 5 1 Intermediate Drivers TCP offload must be enabled in the Windows operating system with the shell command netsh int tcp set global chimney 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 Note Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled Emulex Drivers for Windows User Manual P009412 02A Rev A SG EMULEX 3 Configuration 53 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name TCP Offload Optimization Acceptable Values Optimize La
154. nstallation occurred 2399142000 0x8F000070 You cancelled APinstall after driver utility installation occurred Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SC EMULEX PP g 155 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 Report file contains details AutoPilot Installer Installation Reports During each installation AutoPilot Installer produces a report describing events that occurred during the installation This report has several sections Note 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 The second section provides an inventory of the Emulex adapters as they were before AutoPilot Installer performed any actions The third section lists the tasks that AutoPilot performs in the order they are done The fourth section records the results of each task When all driver installation tasks are completed an updated adapter inventory is recorded If you cancel AutoPilot Installer that fact is recorded along with when you cancelle
155. nterface 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 Preferred NUMA Not present or a value from Windows 2008 Most modern multi socket servers Node 0 65535 Windows 2008 R2 have separate memory controllers for Optional No default setting is w each CPU socket These systems have a 219 Windows 2012 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 Preferred 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 Emulex Drivers for Windows User Manual P009412 02A Rev A SG EMULEX 3 Configuration 50 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Receive Buffers Acceptable Values 64 16384 inclusive The default value is 896 Supported Operating Systems Windows 2008 Windows 2008 R2 Windows 2012 Definition This determi
156. nual P009412 02A Rev A 3 Configuration 78 DG 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 packets 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 44 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 incor
157. o exit the wizard each time it appears Emulex Drivers for Windows User Manual P009412 02A Rev A gt DE EMULEX 2 Installation 22 AutoPilot Installer Overview 2 Run AutoPilot Installer using one of the two options listed in Running a Software Installation Interactively on page 20 3 When the AutoPilot Installer Welcome page appears select an adapter in the list and click Next The installation continues Consider the following e Ifyou 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 is completed automatically 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 ada
158. o use the AUXSOURCE flag to retrieve this description see Help and Support for details The following information is part of the event Device RaidPortd Data Byes O Words 0000 Of 00 10 00 01 00 68 00 h a 0008 00 00 00 00 Ob 00 O04 cO A 0010 9b 00 29 00 00 00 00 00 Ge A be l OK l Cancel Figure A 1 Event Properties Emulex Drivers for Windows User Manual P009412 02A 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 Se
159. omputer system is sending or receiving IP fragments This is a serious performance problem See J umbo Packet on page 76 P009412 02A Rev A 3 Configuration 76 gt lt EMULEX NIC TOE Driver Configuration Table 3 6 Statistics and Fine Tuning Continued Situation Answer Solution TCPv4 gt Segments Retransmitted sec TCP retransmits indicate that packets are being dropped 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 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 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 pa
160. 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 P009412 02A Rev A 137 gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 138 Table A 14 iSCSI Error Log Entries on Windows 7 Windows Server 2008 R2 and Windows Server 2012 Message ID Severity Message Recommended Resolution 0x10 Warning Encountered an error The iSCSI driver detected an error while offloading an iSCSI offloading the iSCSI connection The connection error code N 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 0x11 Warning The IOCTL opcode A requires The iSCSI driver failed an IOCTL request more scatter gather elements because the number of scatter gather than allowed Transfer length elements required for the IOCTL buffer is B exceeded the UCNA firmwar
161. ons 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 44 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 80 DG EMULEX NIC TOE Driver Configuration For Windows Server 2008 R2 and Windows Server 2012 the operating system uses all available CPU cores
162. ontrol 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 and or to send pause frames Tx Enable P009412 02A Rev A SG EMULEX 3 Configuration 47 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Supported Option Name Acceptable Values Operating Systems Definition Interrupt None Windows 2008 The network device uses interrupt Moderation Static 90k Int sec Windows 2008 R2 moderation algorithms to reduce the l total amount of CPU cycles spent aut 70k Int sec Windows 2012 processing interrupts which increases Static 50k Int sec efficiency for the system However Static 40k Int sec interrupt moderation increases the latency of each send and receive It Static 30k Int sec uel should only be disabled when short Static 25k Int sec latencies are more important than Static 20k Int sec efficient CPU utilization Static 15k Int sec The None setting disables all delays Static 10k Int sec to minimize latency Static 5k Int sec The static settings use a constant Adaptive 70k Int sec interrupt delay to avoid any spikes in Ad EO int interrupt rate ap ADE INE SE The adaptive settings cause the driver Adaptive 40k Int
163. 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 _ 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 Emulex Drivers for Windows User Manual
164. ormational 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 P009412 02A Rev A gt G 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 firmware 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 firm
165. orrected Check the registry configuration for was invalid any new valid values added to the driver parameters For more information on valid driver values see Table 3 7 iSCSI Driver Options on page 85 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 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 Table 3 7 iSCSI Driver Options on page 85 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 bootup Emulex Drivers for Windows User Manual being present or currently running This failure may also indicate a hardware problem P009412 02A Rev A 133 gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 134 Table A 13 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x31640004 An internal API failed in t
166. ows User Manual 1 Introduction 13 Abbreviations iSCSI Qualified Name kilobyte or Knowledge Base Link Aggregation Control Protocol local area network link down time out N_Port Logout large send offload link service reject logical unit number media access control multipath input output message signaled interrupt maximum segment size maximum transmission unit not applicable network attached storage network address translation Network Driver Interface Specification network interface card or controller New Technology File System non uniform memory access N_Port ID virtualization OneConnect config operating system peripheral controller interface peripheral controller interface express discover N_Port service parameter pre installation environment physical layer Port login power on self test process login process logout point to point fabric topology Pre boot Execution Environment Quick Fix Engineering quality of service P009412 02A Rev A gt EMULEX RAID RCMD Recv ROM RPI RSC RSCN RSS Rx SACK SAN SCSI SFP SLI SRB SR IOV SSH TCP TCP PSH TMF TMO TOE Emulex Drivers for Windows User Manual 1 Introduction 14 Abbreviations redundant array of independent disks Remote Command Service received read only memory remote port indicator receive segment coalescing Register State Change Notify receive side scaling receive selective acknowledgement storage
167. physical connections to the FC network Ipfc_mes1304 is recorded if Map Entries gt 0 and the corresponding mode and SEVERITY level is set 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 Emulex Drivers for Windows User Manual Firmware has generated an invalid response Error LOG_LINK_EVENT verbose Review hardware configuration Contact Emulex Technical Support P009412 02A Rev A gt EMULEX 4 Troubleshooting 107 Troubleshooting the FC FCoE Driver Ipfc_mes1401 Invalid tag Contextindex x x ulpCommand x x Description Severity Log Action Firmware has generated an invalid response Error LOG _ LINK EVENT verbose Review hardware configuration Contact Emulex Technical Support NPIV Messages 1800 1899 Ipfc_mes1800 NPIV FDISC failure VPI x x Error x x Reason x x Descript
168. provides information regarding unusual situations General Troubleshooting Table 4 1 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 Windows PE offline or online utilities install a version of firmware that is compatible with the driver The firmware is corrupt or non responsive Using the OneCommand Manager application or one of the Windows PE 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 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 Note The LACP cannot be used on an FCoE port Table 4 2 Cisco Nexus Switch Situations Problem 1 Windows creates the NTFS partition ok but then reports that The hard disk containing the partition or free space you chose has a LUN greater than 0 Setup cannot continue Dell 1850 server Windows re
169. pter inventory configuration information and task results 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 20 The message Figure 1 1 appears AutoPilot Installer Warning N AutoPilot Installer cannot find any Emulex adapters in this system AutoPilot Installer can perform a driver pre installation allowing you to install your adapters later Click OK to pre install drivers or click Cancel to stop the installation Cancel Figure 2 1 AutoPilot Installer Warning Software First Installation Emulex Drivers for Windows User Manual P009412 02A Rev A DE EMULEX 2 Installation 23 Text Only Driver 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 o
170. r 3 Run the following batch files e Uninstall_fc_kit bat e Uninstall_cna_kit bat e Uninstall_nic_kit bat e Uninstall_iscsi_kit bat The driver files are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installer 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 Uninstalling the Emulex Drivers The Emulex Storport Miniport and Emulex 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 Delete the software for this device to uninstall the driver Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation _ 3 2 gt EMULEX Removing Emulex Driver Kits and Drivers 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 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 click OK to uninstall ElxPlus Driver Note Uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are un
171. r Check the connection to the target or the state a period exceeding the ETO The error of the target device If the target is made log entry immediately following this available any sessions that existed previously entry will indicate the session ID of are reestablished and the devices are available the target that lost the connection for 1 0 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 TMF that is The operating system version is not supported not supported and rejected this request The error log entry immediately following this entry will indicate the TMF function code that was rejected 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 in
172. r 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 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 AutoPilot installer is launched from the command line or run as a program 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 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 froma 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
173. rbose No action needed informational Ipfc_mes0406 Service Level Interface SLI 3 selected n Description Severity Log Action Emulex Drivers for Windows User Manual Service Level Interface level 3 is selected Information LOG _ELS verbose No action needed informational P009412 02A Rev A gt EMULEX 4 Troubleshooting 101 Troubleshooting the FC FCoE Driver Ipfc_mes0436 Adapter not ready hostStatus x x Description Severity Log Action The adapter failed during powerup diagnostics after it was reset Error LOG_INIT verbose This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Ipfc_mes0442 Adapter failed to init CONFIG_PORT mbxStatus x x Description Severity Log Action Adapter initialization failed when issuing CONFIG_PORT mailbox command Error LOG_INIT verbose 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 Severity Log Action Adapter initialization failed when issuing CFG_RING mailbox command Error LOG_INIT verbose 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 Severity Log Actio
174. rect 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 sends appear as giant packets in the packet sniffer because the hardware has not yet segmented them Note On Windows 2012 Recv Segment Coalescing is enabled by default You must disable Recv Segment Coalescing if you want to set the Checksum Offload setting to anything other than enabled For information on modifying the CheckSum Offload or Large Send Offload parameter see Configuring NIC TOE Driver Options on page 44 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 79 DG EMULEX NIC TOE Driver Configuration 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 int
175. rewall 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 To set firewall services to load on sc config MpsSvc start demand demand To stop firewall services Net stop MpsSvec To temporarily disable firewall services netsh advfirewall set all state off 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 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 direction
176. rmed a PRLI into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Emulex Drivers for Windows User Manual P009412 02A Rev A 4 Troubleshooting Q4 SG EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes0104 ADISC completes to NPortid x x Description The adapter performed an 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 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 905 Troubleshooting the FC FCoE Driver Ipfc_mes0115 Unknown ELS command
177. rogram 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 ProgramFiles 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 Configuration 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 ForceDriverUpdate
178. rosoft s 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 Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 15Q gt G EMULEX AutoPilot Configuration File AutoPilot Configuration File The AutoPilot configuration file is organized into 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
179. rotocols e Fibre Channel FC e FC over Ethernet FCoE e Ethernet NIC which includes the TCP Offload Engine TOE e Internet Small Computer System Interface iSCSI This document explains how to install the Windows drivers on your system and configure the drivers capabilities based on the supported networking protocols e FC and FCoE o Configuring the FC FCoE driver parameters o Improving server performance with FC FCoE drivers e Ethernet and TOE o Configuring NIC TOE driver options o SR IOV o Tuning network driver performance e iSCSI o Configuring iSCSI driver options o Creating non bootable targets o Configuring Multipath I O A NIC teaming package driver and manager are also available as a separate download The user manual OneCommand NIC Teaming and VLAN Manager User Manual is available for download as well See the Emulex website for more information 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 on an x 86 or x64 server with a minimum of 512 megabytes MB of memory e Windows Server 2008 x86 or x64 versions Enterprise and Server Core installation Emulex Drivers for Windows User Manual P009412 02A Rev A 1 Introduction 11 gt G EMULEX Abbreviations Win
180. rrrrtrrsrrrrrrerere 122 ELS FCP Command Error Status Codes ccccceceeeeceeeeeeseeneeneneeeenaees 123 CT Command Response Code ccssiscetisnteneisaereeasnersiteeediaenveseerinbs 123 FC CT Reject Reason Codes cc c ipo cvcatretanencaers eteecaleete sen cere seeeeeseeecees 124 ELS Command 00S cccsces cc cctae cess cicertaperenesesseaseolemanerscessaaresnaiend 124 SCSI Sa CUS CONG Gj anewsscicanmisidanwsayedenesiew nelcannnDinaaeiaacnennderieawneania 124 Local Reject Status Codes acceca 125 SRB Status COJE Skrape mie oa aR Eaa 125 NIC TOE Event Log Entries 2ccvicsiitawotirisboivecriwst taredetsbiarooiarneaonetsbs 127 iSCSI Error Log Entries on Windows Server 2008 ccccecceeeeeeeeeeee eens 133 iSCSI Error Log Entries on Windows 7 Windows Server 2008 R2 and Windows Server 2012 sssssssrrssrrrsssssrsrrrrrrrrrrrsrrrrrrrrrerrrerrrrrrrerrre 136 Data String Parameters for Option 43 ccccccceeceee eect ee eeeeeeeeteeeneeeenes 142 Negotiated Speed Specification per Adapter Port Connection s es 144 Unattended Installation Error Cod S ccccccecseeeeseeeeeeesaeeesnetesnaeeeas 154 P009412 02A Rev A List of Tables Q XC EMULEX 1 Introduction 10 Driver Information 1 Introduction Driver Information This product supports the Emulex OneConnect family of universal converged network adapters UCNAs and the Emulex LightPulse family of host bus adapters HBAs The Windows drivers support the following p
181. rsion 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 P009412 02A Rev A 2 Installation gt lt EMULEX Driver Kit Installer Overview 18 e Network installation You can place the driver kit installers on a shared network drive and install them across your 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
182. rt this statistic is only incremented for the lowest 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
183. rt Service Params FDISC 0x51 Discover Address ADISC 0x52 Register State Change Notify RSCN 0x61 SCSI Status Codes The 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 P009412 02A Rev A 124 sc Appendix A Error and Event Log Information 125 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 ERR
184. ry 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 0x20 Warning Initial memory allocation The driver failed to allocate its complete failed driver is running with memory requirement and attempts to load reduced capabilities with reduced capabilities The total number of targets available is reduced This message indicates a low memory condition 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 Error Device is not supported on The iSCSI adapter family is not supported on Windows 7 Operating System the Windows 7 client operating systems failing driver load 0x25 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 A UE has occurred but UE recovery is not attempted
185. s 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 A connection to the target was lost for a Emulex Drivers for Windows User Manual to connect within the configured timeout period exceeding the ETO The error log entry includes the session ID of the target that 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 P009412 02A Rev A 136 gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log Table A 14 iSCSI Error Log Entries on Windows 7 Windows Server 2008 R2 and Windows Server 2012 Message ID 0x09 Severity Error Message Task Management request N was unhandled Recommended Resolution 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 Ox0a Error Task Management Function abort was received on
186. s 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 0x348d0007 The iSCSI 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 c
187. s the final verification that SR IOV is working correctly SR IOV can also be verified from the host Hyper V server Note Because current versions of Windows 2012 require that SR IOV be enabled in different locations prior to creating the virtual switch if SR IOV is not working delete the virtual switch and create it again The SR IOV option is always available during switch creation Verifying SR IOV from the Virtual Machine To verify the SR IOV from within the virtual machine 1 From within the virtual machine select Server Manager gt Dashboard gt Tools gt Computer Management 2 Click Device Manager The Device Driver opens See Figure 3 4 on page 70 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 73 gt lt EMULEX NIC TOE Driver Configuration Open the Network Adapters item click the Emulex OneConnect device and right click Select Properties from the context menu The OneConnect Properties dialog box opens showing the Driver page See Figure 3 5 on page 71 Note The Emulex adapter may initially appear as a Network Adapter before the driver is loaded Select the Statistics tab Information about the transmit and receive packets that are using the SR IOV virtual function are displayed specifically the number of Transmit Bytes and Receive Bytes that are transmitted directly to hardware from the virtual function If this number is greater than zero the device is successfully usin
188. 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 and 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 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 the FC FCoE Storport Miniport Driver To update or install the FC FCoE Storport Miniport driver from the desktop 1 ae YN 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 Emulex Drivers for Windows User Manual P009412 02A Rev A DE EMULEX 2 Installation 27 Manually Installing or Updating the Emulex Protocol Drivers Note The driver affects only the selected ad
189. sing 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 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 tha
190. snnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 144 Appendix D AutoPilot Installer Command Line and Configuration File Parameters sci cicsinriniscannniovnnminiiceemieneeniniaicuamameaamaam 145 AParg Driver Kit Parameter and Appending to the APinstall exe File ccec0e 145 AutoPilot Installer Sy ntancaccatasccnasticestenesieiadcisedewmiieamaermisemceresiaenoxernicnnns 146 Path SUCCINCT hes tettscnarsnusceestceniioes sion bycotest os pean ec nccas becaenscasieecenteaaleeee 146 Configuration File Location ssssssssrsrrerrerrerrsrsrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 147 Software Configuration ParameterS cccccsccecseeeeeeeeeeseesessenseneeseneesanes 147 DiagEnable Running Diagnostics ssssssrssrrsrssrrsrrrrrrrrrnrrnrrrnrrnrernrerrrrrne 147 ForceDriverTypeChange Forcing a Driver Type Change sssssssessseserrrrerrerrrerre 147 ForceDriverUpdate Forcing a Driver Version Update sssssssssssssrerrrrrrrerrerrerere 147 Emulex Drivers for Windows User Manual P009412 02A Rev A DE EMULEX Table of Contents 7 ForceRegUpdate Forcing an Update of an Existing Driver Parameter Value 148 LocalDriverLocation Specifying Location to Search for Drivers scceseeeeeeeeees 148 NoSoftwareFirstInstalls Prohibiting Software First Installations eccer 148 ReportLocation Setting Up an Installation Report Title and Location 0085 149 SilentInstallEnable Enabling Unattended Installation c
191. t 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 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 Emulex Drivers for Windows User Manual P009412 02A Rev A f 3 Configuration 84 DG EMULEX iSCSI Driver 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 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
192. t iSCSI Initiator Service you need to select only the Initiator Service check box and not the Software Initiator check box Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 88 DG EMULEX iSCSI Driver Configuration 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 Initiator 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 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 enablin
193. tency Optimize Throughput default Supported Operating Systems Windows 2008 Windows 2008 R2 Windows 2012 Definition 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 Windows 2008 Windows 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 Transmit CPU Not Present or a value from 0 through number of CPUs 1 Optional There is no default setting Windows 2008 Windows 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 UDP Checksum Offload IPv4 Disabled RX and TX Enabled default RX Enabled TX Enabled Windows 2008 Windows
194. 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 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 D NE a ega T Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation 28 gt lt EMULEX Manually Installing or Updating the Emulex Protocol Drivers 10 11 12 13 14 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 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 Click Have Disk and direct the Device Wizard to the location of be2iscsi inf 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 iSCSI W
195. 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 23 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 elxdrv 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 parameter 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 elxdrv 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 q 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 APar
196. ting 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 142 All options are case sensitive Emulex Drivers for Windows User Manual P009412 02A Rev A gt G EMULEX Appendix B Configuring iSCSI through DHCP 142 Dynamic Host Configuration 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 TargetT CPPort 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
197. tion Manually Installing or Updating the Emulex Protocol Drivers Note You can run AutoPilot Installer again from the Start menu Programs gt 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 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 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 20 for instructions Select Start gt Settings gt Control Panel gt Add Hardware The Add Hardware Wizard window appears Click Next Select Yes I 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 and direct the Device Wizard to the location o
198. tivation 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 low 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
199. 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 END STORPORT CONFIGURATION QFE Checks STORPORT QFES This section specifies an additional QFE check also known as KB Knowledge Base updates during installation 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 qfe qfe name path and file name file version applicable OS n 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 Emulex Drivers for Windows User Manual P009412 02A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Configuration File oe path and file This string identifies the file to be checked and its location relative
200. total number of TCP connections that have been offloaded 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 P009412 02A Rev A gt EMULEX 3 Configuration NIC TOE Driver Configuration Table 3 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 rat
201. ts 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 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 Increasing 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 P009412 02A Rev A gt EMULEX 3 Configuration NIC TOE Driver Configuration 75 Windows Server Network Driver Table 3 5 describes ways to use various OneConnect driver properties and Microsoft Windows properties to performance tune a system Table 3 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 ser
202. tup inf file and click Open If you have installed the driver installer kit in 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 10 Click Next Emulex Drivers for Windows User Manual P009412 02A Rev A 2 Installation 30 gt G EMULEX Removing Emulex Driver Kits and Drivers 11 When the device driver finishes installing click Close The driver installation has completed 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 After the kit is removed from the system click OK Server Core System To uninstall a driver kit on a Server Core system 1 From the syst
203. twork 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 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 LDTO settings and 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 91 Sendtargets to an IET target fails because it violates the iSCSI specification Emulex Drivers for Windows User Manual If you still want to add an IET target you must add the target manually This issue affects Sendtargets only P009412 02A Rev A gt EMULEX 4 Troubleshooting 114 Troubleshooting the iSCSI Driver Table 4 6 Troubleshooting the iSCSI Driver Continued Problem The following POST error message appears Init
204. ty Log Action Emulex Drivers for Windows User Manual 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 Error LOG MBOX ve rbose 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 P009412 02A Rev A gt EMULEX 4 Troubleshooting 100 Troubleshooting the FC FCoE Driver Ipfc_mes0326 Reset HBA HostStatus x x Description Severity Log Action The adapter has been reset Information LOG MBOX verbose No action needed informational INIT Log Messages 0400 0463 Ipfc_mes0400 Initializing discovery module OptionFlags x x Description Severity Log Action Driver discovery process is being initialized with internal flags as shown Information LOG_ELS verbose No action needed informational Ipfc_mes0401 Initializing SLI module Deviceld x x NumMSI d Description Severity Log Action PCI function with device id and MSI count as shown is being initialized for service level interface Information LOG ELS verbose No action needed informational Ipfc_mes0405 Service Level Interface SLI 2 selected n Description Severity Log Action Service Level Interface level 2 is selected Information LOG_ELS ve
205. ulex 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 Note If you are installing this driver as an update to the WS2012 driver some parameter defaults are different from the inbox driver Emulex recommends that after you install the Emulex driver you select reset to default on the Device Manager property page This returns all adapter and driver settings to the default values listed in this manual 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 NIC e ElxPlus driver that supports the OneCommand Manager application and NPIV vPort registry for the FC FCoE driver e OneCommand Manager application for the Emulex adapters Note The Enterprise kit for the OneCommand Manager application does not operate locally on Windows Server Core You must install the OneCommand Manager Core Kit command line interface only to the Windows Server Core Onelnstall is available for download from the Emulex website The limitation of the single package is that you cannot perfor
206. us x x ulpWord 4 x x XRI x x ulpWord 7 x x Description Severity Log Action Remarks 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 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 Description Severity Log Action See Also The issued FCP command returned a Read Check Error Warning LOG _FCP verbose Check the state of the target 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 Emulex Drivers for Windows User Manual The issued FCP command resulted in a Check Condition Warning LOG FCP verbose Review SCSI error code values Ipfc_mes0730 P009412 02A Rev A gt EMULEX 4 Troubleshooting 1Q5 Troubleshooting the FC FCoE Driver Ipfc_mes0747 Target reset complete PathId x x Targetld x x Did x x Description Severity Log Action R
207. v A SG EMULEX 3 Configuration 48 NIC TOE Driver Configuration Table 3 3 Windows Server 2008 2008 R2 and 2012 NIC TOE Driver Options Continued Option Name Large Send Offload v2 IPv4 Acceptable Values Disable Enable default Supported Operating Systems Windows 2008 Windows 2008 R2 Windows 2012 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 Version2 LSO supports larger offload sizes Large Send Offload v2 IPv6 Disabled Enabled default Windows 2008 Windows 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 Maximum Number of RSS Queues 4 16 8 default Emulex Drivers for Windows User Manual Note For 0Ce11102 and 16Gb UCNAs only Windows 2008 R2 Windows 2012
208. verity 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 Y d d Description Severity Log Action Emulex Drivers for Windows User Manual Authentication is done Information LOG _FCSP verbose No action needed informational P009412 02A Rev A 4 Troubleshooting 109 DG EMULEX Troubleshooting the NIC TOE Drivers Ipfc_mes1905 Authentication policy change for local x 08x x 08x remote x 08x 08x Description Authentication policy has been changed Severity Information Log LOG FCSP verbose Action No action needed informational Troubleshooting the NIC TOE Drivers The following table provides troubleshooting information for the NIC TOE drivers Table 4 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
209. vers 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 view 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 3 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 3 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 c
210. ware 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 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 w
211. ws Device Manager ccccccceeeeeeeeeeeeeeaeeeeneeenaes 56 Figure 3 2 NIC TOE Advanced Properties in Windows Server 2008 0cceeee eee eee 57 Figure 3 3 NIC TOE Statistics Properties in Windows Server 2008 cceeeee eee ees 58 Figure 3 4 Device Manager for Windows Server 2012 cccceccceeeeeeeeeeeeeeneeeenaneenas 70 Figure 3 5 Emulex OneConnect NIC TOE Driver Properties page cecseeeseeeeeeeenees 71 Figure 3 6 Emulex OneConnect NIC TOE Advanced Properties page ceeeeeeea ee 71 Figure 3 7 Emulex OneConnect NIC Statistics Properties page c ccc eeeeee eee e eee ea ee 73 Figure A 1 Event Properties ccxccstptiacadeceridenn deeds trta rnrn rrr t tarnrn rnrn EEEE EREEREER rE rrn 116 Figure A 2 iSCSI Error ctciteacixedesececaced cade rrr rrrrrtt tntan rrr rrr r tann PE EEEEEEEEEE PERIE EEE EEne 132 Emulex Drivers for Windows User Manual P009412 02A Rev A gt G EMULEX List of Tables Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 5 Table 4 6 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 cccccccecccseccesscwedneecepeecbecevatcensecsanwens 35 Recommended
212. 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 failure Error LOG _ELS verbose Check remote NPORT for potential problem P009412 02A Rev A sc 4 Troubleshooting 96 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
213. y Iqd 128 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 lqd parameter also sets the maximum number of concurrent commands allowed per LUN P009412 02A Rev A 3 Configuration 87 gt lt EMULEX iSCSI Driver Configuration 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 3 8 Table 3 8 im_policy Settings 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 UC
214. y be modified by using the Window s 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 63 gt lt EMULEX NIC TOE Driver Configuration 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 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 paramet
215. ypes 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 received 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 Emulex Drivers for Windows User Manual P009412 02A Rev A 3 Configuration 2 gt lt EMULEX NIC TOE Driver Configuration 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 Fi
216. ystem 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 User Manual P009412 02A Rev A gt EMULEX Appendix D AutoPilot Installer Command Line and Configuration File Parameters 154 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

Emulex Drivers for Windows User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents