Home

Emulex Drivers for Windows

1. Q u NYA SERVEREN g 15 NYA SERVEREN HO NA SERVEREN 1 NA SERVEREN nA SEVERE 0000 Of 00 10 oO 01 wa 0009 0 00 00 OO Ob O4 lt 0 Saami 10010 O5 00 80 11 00 00 09 oi 1 WA SERVEREN DOO WA SERVEREN WA SERVEREN 13 WA SERVEREN Dire tao 11 06 10 OCOM Neon 10016 NETWORKSER SERVEREN Qie traoo 11 06 10 DEON tone 10016 NETWORKSER SERVEREN Dintemaen 1 19 2000 11 05 08 AabociagSive Neon 3 WA SERVEREN Gina 1 13 2009 11 06 04 DCOM teen 10025 NYA SERVEREN j 2 Dovtemsen irzo 1 06 04 everti fone 6005 YA SERVEREN zl Figure 6 iSCSI Error Because the UCNAs are dual PCl function adapters the Device RaidPort lt n gt value changes depending on the device that observed the error Viewing the iSCSI Error Log on Windows 2003 and 2008 The following is a brief description of the error log codes generated by the iSCSI driver for Windows Server 2003 and 2008 It includes the error code the message displayed and the meaning of the message and the recommended resolution Table 29 iSCSI Error Log Entries on Windows Server 2003 and 2008 Message ID Message Description Recommended Resolution 0x348d0008 The iSCSI driver failed a WMI IOCTL request This failure indicates that an operation from the port driver because the request was attempted from the Microsoft WMI application failed by the ARM firmware
2. lpfc_mes0401 0401 Initializing SLI module Deviceld x x NumMSI d DESCRIPTION PCI function with device id and MSI count as shown is being initialized for service level interface SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0405 Service Level Interface SLI 2 selected n DESCRIPTION Service Level Interface level 2 is selected SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0406 0406 Service Level Interface SLI 3 selected n DESCRIPTION Service Level Interface level 3 is selected SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0436 Adapter not ready hostStatus x x DESCRIPTION The adapter failed during powerup diagnostics after it was reset SEVERITY Error LOG LOG_INIT verbose ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support lpfc_mes0442 0442 Adapter failed to init CONFIG_PORT mbxStatus x x DESCRIPTION Adapter initialization failed when issuing CONFIG_PORT mailbox command SEVERITY Error LOG LOG_INIT verbose ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support lpfc_mes0446 0446 Adapter failed to init CONFIG_RING mbxStatus x x DESCRIPTION Adapter initialization failed when issuing CFG_RING mail
3. qfe name path and file name file version applicable OS qfe name The name of the item being checked For example QFE 838896 The name should facilitate searching Microsoft s website for any required code updates path and file name This string identifies the file to be checked and its location relative 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 1 76 applicable OS This is used to determine if the QFE applies to the operating system platform present The acceptable values are Win2003 and Win2008 For example STORPORT OFES qfe QFE 83896 system32 drivers storport sys 5 2 1390 176 Win2003 Emulex Drivers for Windows User Manual Page 16 gt G EMULEX 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 Th
4. Check the manufacturer s documentation and BIOS parameters for details about optimizing memory bandwidth Typically all the dual in line memory module DIMM slots must be populated to make use of all the memory channels As a general rule more DIMMs provide better performance by allowing a higher degree of memory access interleaving to occur Some servers may allow memory mirroring where the total memory is divided in half and each location is stored twice This allows fault recovery if one memory location detects an error but it greatly reduces the perceived memory bandwidth of the system Nearly any desktop or low end server has enough memory bandwidth for the UCNA to support 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 All processor memory accesses use the front side bus FSB 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 Windows Server Network Driver Table 7 describes ways to use various OneConnect driver properties and Microsoft Windows properties to performance tune a system Table 7 Windows Server Performance Tuning Situations Situation Answer Solution There are a large number of short li
5. Dell 1850 server 2 Windows reboots successfully but then gets stuck during the GUI portion of the installation right from the beginning HP DL385G2 server containing the partition or free space you Set up the FCoE switch ports as follows no priority flow control mode on untagged cos 0 flowcontrol receive on flowcontrol send on spanning tree port type edge Emulex Drivers for Windows User Manual Page 75 gt G EMULEX Event Tracing Windows Server 2003 SP1 and later only Trace messages are part of the Emulex Ipfc log messages Storage Event Tracing supports two types of events e FFInit 0x00000001 events that occurred at HwFindAdapter and Hwinitialize e FFlo 0x00000002 events that occurred during I O Storage Event Tracing supports four levels of events e DbgLviErr 0x00000001 error level e DbGLvlWrn 0x00000002 warning level e DbgLvilnfo 0x00000004 Information level e DbgLvilnfo Ox00000008 excessive information level Note To view trace messages you must enable Event Tracing in the operating system See your Microsoft operating system documentation for more information Table 14 Event Tracing Summary Table a From To ioii Verbose Description ELS 0100 0130 0199 ELS events Discovery 0202 0262 0299 Link discovery events Mailbox 0310 0326 0399 Mailbox events INIT 0400 0463 0499 Initialization events FCP 0701 0749 0799 FCP traffic history event
6. IPv4 RX and TX Enabled Disabled RX and TX Enabled RX Enabled TX Enabled User Datagram Protocol UDP offload checksum settings offload the transmit and or receive IPv4 UDP checksum computation Offloading checksums increases system efficiency VLAN Identifier Not Present Not Present If selected the adapter adds a 1 to 4095 VLAN tag to all transmitted packets Wake on LAN Disabled Disabled Enabling Wake on LAN allows Enabled 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 Emulex Drivers for Windows User Manual Page 34 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Option Name Default Value Acceptable Values Definition Class of Automatic Priority Automatic Priority The following modes are Service Filtered Priority supported for selecting 802 1p 802 1p User Priority priority tags Disable Priority Automatic Priority The DCBX standard allows the network adapter to negotiate priority class usage with DCBX aware endpoints such as switches or network cards If the peer indicates that priority pause is supported for a non zero priority the NIC automatically inserts the default priority in all transmitted packets This is the defau
7. 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 that both the DPC and application run on the same processor different processors or different cores of a dual core processor that share a common memory cache Even when the best affinity relationship is determined it is impossible to enforce this relationship because RSS or TCP offloading choose the DPC processor The driver uses multiple parallel DPCs that are explicitly assigned to particular
8. 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 2003 SP2 and later Registry Key RSS Default Value 1 Enable Valid Values 0 Disable 1 Enable Emulex Drivers for Windows User Manual Page 47 Configuring iSCSI Driver Options Table 5 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 gt G EMULEX 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 Table 4 iSCSI Driver Options Parameter Default Value Minimum Value Maximum Value Description LDTO 20 seconds 0 seconds 3600 seconds Link down timeout LDTO in seconds This parameter determines the amount of time the universal converged network adapter UCNA driver waits for the controller s physical link to be available before reporting that the logical unit numbers LUNs are unavailable to the operating system Note
9. 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 Viewing the iSCSI Error Log on Windows 2003 and 2008 on page 107 and look for specific event codes to confirm Unable to create a memory dump file on a system booted over iSCSI Unable to log in to target from WMI 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 e Ensure that the IP address on the UCNA is valid and the network connection has been set up to reach the target e If login is attempted after discovering the target ensure that the correct UCNA port has been selected for the login The iSCSI WMI GUI 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
10. This error is resulted in an error Check the operation being immediately followed by another error code attempted for user or configuration errors entry indicating the WMI request code in error 0x348d0007 The iSCSI driver failed a WMI IOCTL request This failure indicates that an operation from the port driver This error is immediately attempted from the Microsoft WMI application followed by another error code entry resulted in an error Check the operation being indicating the WMI request code in error attempted for user or configuration errors Emulex Drivers for Windows User Manual Page 107 gt G EMULEX Table 29 iSCSI Error Log Entries on Windows Server 2003 and 2008 Continued Message ID Message Description Recommended Resolution 0x33900002 The iSCSI driver failed an I O request This failure occurred due to a failed memory because it failed to retrieve a scatter gather allocation in the operating system Check low 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 one or This failure may indicate a low memory more PCI Base Address Registers and failed condition or a hardware error to load 0x3184000b The iSCS
11. below 4 Enable MPIO a Select Start gt Administrative Tools gt Server Manager b Inthe Server Manager tree click Features c Inthe Features area click Add Features d Inthe Add Features wizard on the Select Features page select the Multipath I O check box and click Next e On the Confirm Installation Selections page click Install f When the installation is completed click Close on the Installation Results page g When prompted to restart the computer click Yes h Click Close Emulex Drivers for Windows User Manual Page 51 gt G EMULEX 5 Discover all possible paths to all devices on the system a Open the MPIO control pane select Start gt Administrative Tools gt MPIO b On the User Account Control page click Continue The Properties dialog box is displayed c Select the Discover Multi Paths tab d Select Add support for iSCSI Devices and click Add 6 Reboot the system when prompted to do so After rebooting the Microsoft iSCSI DSM claims all iSCSI discovered disks The MPIO GUI shows device id MSFT2005iSCSIBusType_0x9 under the MPIO Devices tab The Disk Manager does not show duplicate disks You can configure load balancing policies on the LUN from the Device Manager after you click on the disk and select the MPIO tab Logging into Targets for Multipath Support After you have successfully installed and enabled MPIO support on a Windows Server you must log in to the target This section descri
12. hex Default 32 0x20 Dynamic Emulex Drivers for Windows User Manual Page 72 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol QueueTarget n QueueTarget controls I O depth limiting on a per 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 Dynamic RmaDepth n RmabDepth sets the remote management buffer 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 Reboot ScanDown n If set to 0 lowest AL_PA lowest physical disk 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 Reboot FC Only SLIMode n If set to 0 autoselect firmware use the latest 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 Reboot LightPu
13. 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 will choose the driver to install Click Have Disk Direct the Device Wizard to the location of driver s distribution kit If you have installed the driver installer kit in the default folder the path is C Program Files Emulex AutoPilot Installer Drivers Storport x86 for the 32 bit driver version or C Program Files Emulex AutoPilot Installer Drivers Storport x64 for the x64 driver version or C Program Files Emulex AutoPilot Installer Drivers Storport lA64 for the Itanium driver version Click OK Select Emulex PLUS Click Next to install the driver Click Finish The ElxPlus driver update is finished Continue with manual installation of the Storport Miniport Driver ling or Updating the FC Storport Miniport Driver To update or install the FC Storport Miniport driver from the desktop 1 Or ee IN OND Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click Device Manager Open the SCSI and RAID Controllers item Double click the desired Emulex adapter Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All dual channel adapter models are displayed in Device Manager as two adapters ther
14. state Offloads are disabled for specific ports or applications To view any TCP ports or applications that may be configured to disable TCP offload at the command line type netsh interface tcp show chimneyports netsh interface tcp show chimneyapplications A third party firewall is running The Windows firewall does not affect TCP offload but third party firewalls may prevent TCP offloads Uninstall third party firewall software to allow TCP offloads In the network properties some intermediate drivers prevent offloading Go to Network Connections gt Properties and clear check boxes for unused drivers In particular Network Load Balancing and some third party drivers prevent offloads IPSec is enabled Disable IPSec IP Network Address Translation NAT is enabled The driver supports an Advanced Property to disable TCP offloading The TCP connection uses using IPv6 Disable IP NAT Make sure TCP offloading is enabled The driver supports offloading TCP connections only with IPv4 Emulex Drivers for Windows User Manual Page 60 gt G EMULEX Windows Networking and TOE Note Although TOE is supported it is turned off by default If certain Windows Server 2003 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 co
15. with reduced capabilities Total number of targets available will be reduced 0x14831000 There was an Unrecoverable Error detected This may be due to hardware errors or due to by the iSCSI driver Following this error log unhandled exceptions in the hardware or entry the next 3 entries indicate the error firmware codes 0x138e0103 The iSCSI driver failed an IOCTL request This error may indicate an incorrect because the number of scatter gather elements required for the IOCTL buffer exceeded the firmware limit Following this error log entry the next entry will indicate the IOCTL opcode and the payload length requested configuration option for the iSCSI driver It may also indicate a low memory condition Emulex Drivers for Windows User Manual Page 108 gt G EMULEX Table 29 iSCSI Error Log Entries on Windows Server 2003 and 2008 Continued Message ID Message Description Recommended Resolution 0x138d0101 The iSCSI driver detected an error offloading This may indicate a target is in error or may the iSCSI connection The operation will be point to transient network connectivity issues It retried again Following this error log entry may also indicate a firmware error the next entry will indicate the session handle and the firmware error code 0x12990013 The iscsi driver did not receive an iSCSI e Verify that the iSCSI target is certified by command window update within 25 s
16. 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 applications that receive data but perform no other processing For other applications RSS allows the application to scale other processing tasks across all CPUs thereby improving overall performance RSS offers the most benefit for applications that create numerous short lived connections These applications are typically CPU limited instead of network bandwidth limited Emulex Drivers for Windows User Manual Page 58 gt G EMULEX For information on modifying the RSS Q
17. G EMULEX 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 28 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 28 NIC TOE Event Log Entries support network functionality Message ID Hexadecimal Severity Message Recommended Resolution Decimal 0x0002e 46 Error Device is not supported on Windows 7 Operating System 0x0002d 45 Error Error recovery failed The device See the Downloads section of the is no longer operational Update Emulex website for compatible all drivers and firmware firmware and drivers 0x0002c 44 Warning Error recovery is disabled on the This message is informational system The device is no longer operational 0x0002b 43 Informational The driver successfully recovered This message is informational from an error 0x0002a 42 Warning Legacy driver loaded Move to the NDIS 6 20 driver for Windows 2008 R2 for best performance 0x0029 41 Warning Legacy driver loaded Move to the NDIS 6 x driver for Windows 2008 for best performance 0x0028 40 Warning The firmwa
18. Installer after driver kit installation is complete This allows you to change the configuration options supplied to AutoPilot Installer see below 1 Perform steps 1 through 3 for Option 1 2 Clear the Run AutoPilot Installer check box on the Finish page 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 12 for details e Supply parameters on the command line See AutoPilot Installer Command Line and Configuration File Parameters on page 10 for details Once you have finished this step you can run AutoPilot Installer at a later time using either of the following methods If you are supplying options via the command line you must run AutoPilot Installer from the command line e Select Programs gt Emulex gt AutoPilot Installer in the Start menu e Run AutoPilot Installer from the command line Type C Program Files Emulex AutoPilot Installer APInstall exe Note The location of APInstaller exe may differ on your system depending on your system s Program Files location You may also specify a different location when you install the driver package Hardware First Installation or Driver Update The driver kit installer must be downloaded from the Emulex website and installed Note Updating the NIC protocol driver may temporarily disrupt opera
19. Offload to be enabled This warning applies only to Windows Server 2003 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 Emulex Drivers for Windows User Manual that the firmware flash image is not corrupted Contact Emulex Technical Support Page 104 Table 28 NIC TOE Event Log Entries Continued gt G EMULEX Message ID Hexadecimal Severity Message Recommended Resolution Decimal 0x0015 21 Error Firmware version does not match The firmware version and driver driver version must match This is a warning message but it is recommended that you reinstall matching versions of the firmware and driver 0x0015 21 Warning Firmware version does not match The firmware version and driver driver version must match This is a warning message but it is recommended that you reinstall matching versions of the firmware and driver 0x0014 20 Error Failed to read registry The registry is corrupted Reinstall configuration the driver and or operating system 0x0013 19 Error Resource conflict The operating system failed to allocate resources for the device Check low memory conditions and operating system hardware resource conflicts 0x0012 18 Error Failed to enable bus mastering V
20. PLOGI accepted 0x56 LOGO accepted 0x59 PRLI accepted 0x63 Fabric name server response 0x6B ELS RSCN processed 0x71 LOGO received from fabric 0x79 FDISC accepted OxA2 SCSI address assigned to discovered target OxA4 Report LUNs error initial I O to discovered target OxA5 Local error indication on FCP command OxA8 Data overrun OxA9 FCP command error OxAA SCSI check condition 0OxAD Local reject indication on FCP command OxAE Error on SCSI pass through command OxAF Error on Menlo CT command Table 20 Event Indications Bits 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 0xE0 Authenticated successfully remote Did in bits 8 31 0xE1 Failed to authenticate remote Did in bits 8 31 0xE2 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 D
21. Run AutoPilot Installer on page 6 e For control of all interactive installation settings see Option 2 Run AutoPilot Installer Separately on page 7 e Foran unattended installation with AutoPilot Installer see Performing an Unattended Driver Installation on page 9 Text Only Driver Installation Text based installation mode is used automatically when the driver kit installer runs on a server with the Server Core installation option of Windows Server During text based installations AutoPilot Installer uses a command prompt window The driver kit installer notifies you when the driver is installed and also gives you a chance to stop the installation Whether it is launched from the command line or started programmatically Windows always starts AutoPilot Installer as a separate stand alone task This means that AutoPilot Installer has its own command prompt window and cannot access others Emulex Drivers for Windows User Manual Page 5 gt G EMULEX AutoPilot Installer Overview AutoPilot Installer runs after the driver kit and the OneCommand Manager application are installed AutoPilot Installer can be run by e Continuing the installation process after the driver kit installation is completed e Interactive installation at a later time e Unattended installation AutoPilot Installer provides Command line functionality Initiates an installation from a command prompt or script Configuration settings can be speci
22. SCSIId x x DESCRIPTION Discontinuing timer for reconnected target with NPort ID and SCSI ID SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0262 0262 Node timeout on NPortld x x SCSIId x x DESCRIPTION Disconnected NPort ID SCSI ID has failed to reconnect within timeout limit SEVERITY Error LOG LOG_ELS verbose ACTION Review system configuration Mailbox Log Messages 0310 0326 lpfc_mes0310 0310 Mailbox command timeout HBA unresponsive DESCRIPTION A Mailbox command was posted to the adapter and did not complete within 30 seconds sync 0 asynchronous mailbox command is issued 1 synchronous mailbox command is issued SEVERITY Error LOG LOG_MBOX verbose ACTION This error could indicate a software driver or firmware problem If no I O is going through the adapter reboot the system If these problems persist report these errors to Technical Support lpfc_mes0326 0326 Reset HBA HostStatus x x DESCRIPTION The adapter has been reset SEVERITY Information LOG LOG_MBOxX verbose ACTION No action needed informational Emulex Drivers for Windows User Manual Page 80 gt G EMULEX INIT Log Messages 0400 0463 lpfc_mes0400 0400 Initializing discovery module OptionFlags x x DESCRIPTION Driver discovery process is being initialized with internal flags as shown SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational
23. 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 Page 57 gt G EMULEX Checksum Offloading and Large Send Offloading LSO The UCNA supports IP TCP and UDP checksum offloading All these protocols are enabled by default You can disable offloading through the Windows Device Manager Advanced Properties Disabling checksum offloading is only useful for packet sniffing applications such as Ethereal or Microsoft Network Monitor on the local system where the UCNA is installed and monitored When packets are sniffed transmit packets may appear to have incorrect checksums because the hardware has not yet calculated them The UCNA supports transmit LSO which allows the TCP stack to send one large block of data and the hardware segments it into multiple TCP packets This is recommended for performance b
24. 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 For best performance the network applications should try to use memory and CPU affinity from the same NUMA node This level of tuning is primarily noticeable when multiple adapters are running Transmit CPU Optional not set Not present or a value from 0 through number of CPUs 1 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 The valid values are 0 to number of CPUs 1 TCP Checksum RX and TX Disabled Disable TCP Checksum Offload IPv4 Offload IPv4 RX and TX Enabled offloads the transmit and or RX Enabled receive IPv4 TCP checksum TX Enabled computation Offloading checksums increases system efficiency TCP Checksum RX and TX Enabled Disable TCP Checksum Offload IPv6 Offload IPv6 RX and TX Enabled offloads the transmit and or RX Enabled receive IPv6 TCP checksum TX Enabled computation Offloading checksums increases system efficiency Emulex Drivers for Windows User Manual Page 41 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition TCP Disabl
25. a network share Removable media are not searched Example LocalDriverLocation d drivers new Storport Note On x64 and 32 bit systems the path specified by LocalDriverLocation must contain at least one instance of an FC FCoE iSCSI and NIC driver AutoPilot Installer automatically selects the most recent revisions that it finds For IA64 systems only FC and FCoE drivers are supported so no iSCSI or NIC drivers are included for installation NoSoftwareFirstInstalls Prohibiting Software First Installations Default False When this parameter is set to true AutoPilot Installer prevents unattended installations from performing software first installations This way you can execute an automated installation on multiple machines in your network but only machines with Emulex adapters actually have Emulex drivers updated or installed If this parameter is omitted from the configuration file or explicitly set to true the page is not displayed AutoPilot Installer uses configuration file parameters to determine the appropriate management mode ReportLocation Setting Up an Installation Report Title and Location The automatically generated file name for this report is report_mm dd yy txt where mm is the month number dd is the day and yy indicates the year You can change only the installation report folder the file name is auto generated In the following example x could be any available drive R
26. 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 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 For information on modifying the Flow Control parameter see Configuring NIC TOE Driver Options on page 29 TCP Offload Optimization Settings The UCNA supports an option for optimizing TCP offload characteristics for throughput or latency This option is available through the Advanced Property Page See Configuring NIC TOE Driver Options on page 29 for the TCP Offload Optimization settings The default option is Optimize Throughput which produces the best throughput characteristics for certain types of traffic flows This configuration setting has produced the best results on benchmarks such as Chariot ntttcp and iperf The other available option Optimize Latency improves the latency characteristics for the class of traffic flows not ideally suited for offloaded by sacrificing throughput
27. command for the indicated SCSI device address SEVERITY Warning LOG LOG_INIT verbose ACTION Review system configuration lIpfc_mes0703 0703 Issue LUN reset to Pathld x x Targetld x x Lun x x Did x x DESCRIPTION Storport is requesting a reset of the indicated LUN SEVERITY Warning LOG LOG_INIT verbose ACTION Review system configuration Possible side effect of cluster operations Emulex Drivers for Windows User Manual Page 82 gt E EMULEX lpfc_mes0713 0713 Issued Target Reset to Pathld d Targetld d Did x x DESCRIPTION Storport detected that it needs to abort all I O to a specific target This results in login reset to the target in question SEVERITY Warning LOG LOG_FCP verbose ACTION Review system configuration Possible side effect of cluster operations SEE ALSO Ipfc_mes0714 lIpfc_mes0714 0714 Issued Bus Reset for Pathld d DESCRIPTION Storport is requesting the driver to reset all targets on this adapter SEVERITY Warning LOG LOG_FCP verbose ACTION Review system configuration Possible side effect of cluster operations SEE ALSO Ipfc_mes0713 lpfc_mes0716 0716 FCP Read Underrun expected d residual d DESCRIPTION FCP device provided less data than was requested SEVERITY Supplement Information LOG LOG_FCP verbose ACTION No action needed informational SEE ALSO Ipfc_mes0730 lpfc_mes0729 0729 FCP command error ulpStatus x x ulpWord 4 x x XRI x x ulpWor
28. driver installation to proceed even if a check for QFEs fails set this parameter to true AutoPilot Configuration File The AutoPilot configuration file is organized into sections grouped according to related commands There are six main sections Each section begins with a heading The heading is required even if there are no settings in the section The only section not required is the Installation Prompts section which has the heading STORPORT CONFIGURATION That section cannot exist if AutoPilot Installer runs in silent mode You must delete or comment out that entire section for unattended installation Lines that begin with a semicolon are comments Some of the comments are sample settings To use the setting remove the semicolon Using the Windows Environment Variable ProgramFiles You can use the Windows ProgramFiles environment variable in the LocalDriverLocation and ReportLocation strings within the configuration file This allows you to specify strings in a driver independent manner allowing the same configuration file to be used on different systems where Windows may have been installed on different drives To use this option ProgramFiles must be the first component specified in the string The portion of the string that follows is appended to the contents of the ProgramFiles environment variable For example ReportLocation ProgramFiles my company reports Note The contents of the ProgramFiles environm
29. driver is issuing a nameserver request to the fabric Also recorded if a GID_FT is sent SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational SEE ALSO Ipfc_mes0239 or Ipfc_mes0240 lpfc_mes0238 0238 NameServer response DID count d DESCRIPTION Received a response from fabric name server with N DIDs SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational Emulex Drivers for Windows User Manual Page 79 gt E EMULEX lpfc_mes0239 0239 NameServer Response next DID value x x DESCRIPTION The driver received a nameserver response And this message is recorded for each DID included in the response data SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational SEE ALSO Ipfc_mes0236 lpfc_mes0240 0240 NameServer Response Error CmdRsp x x ReasonCode x x Expla nation x x DESCRIPTION The driver received a nameserver response containing a status error SEVERITY Error LOG LOG_DISCOVERY verbose ACTION Check Fabric configuration The driver recovers from this and continues with device discovery SEE ALSO Ipfc_mes0236 lpfc_mes0256 0256 Start node timer on NPortld x x timeout value d DESCRIPTION Starting timer for disconnected target with NPort ID and timeout value SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0260 0260 Stop node timer on NPortld x x
30. 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 0x4E World Wide Port Name mismatch on ADISC 0x4F World Wide Node Name mismatch on ADISC 0x50 ADISC response failure 0x55 LOGO response failure 0x57 PRLI to non existent node Ox5A PRLI response error Ox5F CT command error 0x62 Name server response error 0x66 State Change Notification registration failure Ox6A Unrecognized ELS command received Ox6F Received PRLI from un typed source 0x73 Failed to pend PRLI for authentication 0x77 Failed to allocate Node object 0x7A REG_VPI failed 0xA3 Command context allocation failure OxAB SCSI command error Emulex Drivers for Windows User Manual Page 95 gt G EMULEX Table 18 Malfunction Errors Continued Bits 0 7 Interpretation OxAC Read check error OxBO Node timeout device removal signaled to Storport Table 19 Command Errors Bits 0 7 Interpretation 0x43 Fabric login succeeded 0x46 ELS command failed 0x47 Exhausted retries on ELS command 0x4A
31. gt G EMULEX Emulex Drivers for Windows FC and FCoE version 2 70 NIC version 4 1 iSCSI version 4 1 User Manual Emulex Connects P007628 01C Rev A Servers Storage and People gt G EMULEX Copyright 2003 2012 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this manual as is without any warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product described in th
32. initialize adapter port LightPulse 0xCO Insufficient revision level for STORPORT SYS OxC1 Failed to allocate miniport un cached extension 0xC2 Insufficient un cached extension space 0xC3 Port initialization failure OneConnect Emulex Drivers for Windows User Manual Page 94 Table 17 Severe Errors Continued gt G EMULEX Bits 0 7 Interpretation 0xC4 Port initialization failure LightPulse 0xC5 Utility mailbox command error 0xC6 SLI4 Pre initialization failure 0xD3 NPIV memory allocation failure OxFO Unresponsive adapter port SLI4 mode OxF4 ULP Unrecoverable Error low part SLI4 mode OxF5 ULP Unrecoverable Error high part SLI4 mode OxF6 ARM Unrecoverable Error SLI4 mode OxF7 READ_NV failed SLI4 mode OxF8 READ_NV failed SLI4 mode OxF9 READ_REV failed SLI4 mode OxFA READ_CONFIG failed SLI4 mode OxFB Failed to post header templates SLI4 mode OxFC Invalid Completion Queue Entry SLI4 mode OxFD Invalid Completion Queue Entry SLI4 mode OxFE Invalid Completion Queue Entry SLI4 mode Table 18 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
33. installation proceeds with installing only the utilities To force a driver update even if the same version of the driver is installed set this parameter to true Note ForceDriverUpdate applies to unattended installations only in interactive installations this parameter is ignored Instead you are asked if the driver should be updated Emulex Drivers for Windows User Manual Page 12 gt G EMULEX 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 Default Drivers The default Drivers folder is located in the same folder as AutoPilot Installer You can specify a local location that is to be searched for drivers during unattended installations The location may be a local hard drive or
34. 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 1 O NOOR WD 10 11 Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click Device Manager Open the SCSI and RAID Controllers item Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All DC adapter models are displayed in Device Manager as two 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 Direct the Device Wizard to the location of oemsetup inf If you have installed the driver installer kit to the default folder the path is C Program Files Emulex AutoPilot Installer Drivers Storport x86 iSCSI Windows Version for the 32 bit driver version or Emulex Drivers for Windows User Manual Page 22 12 13 14 gt G EMULEX e C Program Files Emulex AutoPilot Installer Drivers Storport x6
35. netsh interface tcp set global congestionprovider none Emulex Drivers for Windows User Manual Page 62 gt G EMULEX 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 Increasing interrupt coalescing may improve total bandwidth for applications that transfer large data buffers Additionally servers running numerous parallel TCP connections may benefit from higher interrupt coalescing Some applications run slower with interrupt coalescing enabled such as applications that depend on the completion of the current network transfer before they post additional work
36. not detected on the system 2399141836 0x8F000030 ee was not invoked from an account with Administrator level 2391419952 0x8F000040 AutoPilot Installer has detected unsupported adapters on the system 2399141968 0x8F000050 Unattended software first installations are disallowed 2399141984 0Ox8F000060 You cancelled APInstall before any driver utility installation occurred 2399142000 0x8F000070 You cancelled APInstall after driver utility installation occurred 9399142032 0x8F000090 sora a aa an error while parsing the command line Report file 2399142048 0x8FO000A0 NIC or iSCSI adapters are installed but are not supported on IA64 systems AutoPilot Installer Installation Reports During each installation AutoPilot Installer produces a report describing events that occurred during the installation This report has several sections e The first section provides basic information including the time and date of the installation the name of the machine that the installation was performed on the version number of AutoPilot Installer and the identification of the configuration file that was used e The second section provides an inventory of the Emulex adapters as they were before AutoPilot Installer performed any actions e The third section lists the tasks that AutoPilot performs in the order they are done The fourth section records the results of each task When all driver installation tasks are completed an updated adapter inv
37. of the boot device By default LUN 0 is assumed to be the boot LUN It is an eight byte number which should be specified as a hexadecimal number consisting of 16 digits with an appropriate number of zeroes padded to the left if required Optional lt TargetName gt A valid iSCSI name of up to 223 characters Mandatory lt InitiatorName gt A valid iSCSI iqn name of up to 223 characters If it is not provided the default initiator name generated by the UCNA based on its MAC address is used Optional lt HeaderDigest gt Either E the header digest is enabled or D the header digest is disabled Optional lt DataDigest gt Either E the data digest is enabled or D the data digest is disabled Optional lt AuthenticationType gt D authentication is disabled E one way CHAP is 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 Optional Examples The following is an example of default initiator name and data digest settings iscsi 192 168 0 2 3261 000000000000000 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 in
38. 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 appears disabled for additional PCI functions in blade server configurations RSS requires Windows 2003 SP2 and later TCP Checksum Offload IPv4 RX and TX Disabled Disabled RX and TX Enabled RX Enabled TX Enabled TCP Checksum Offload IPv4 offloads the transmit and or receive IPv4 TCP checksum computation Offloading checksums increases system efficiency Emulex Drivers for Windows User Manual Page 32 gt G EMULEX Table 2 Windows Server 2003 Driver Options Continued Option Name Default Value Acceptable Values Definition TCP Disabled Enabled If TCP offload is enabled the Connection Disabled device offloads the entire TCP Offload IPv4 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 Windows Firewall Service Server 2003 e Network Load Balancing IPSEC e Network Address Translation NDIS 5 1 Intermediate Drivers TCP offload must be enabled in the Windows operating system with t
39. 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 Use Cases Typical cases for using the MTU e Server interconnects are typically deployed using jumbo frames This is the most efficient configuration for high bandwidth server to server communication such as Network Attached Storage iSCSI and database transactions e Servers connected to client systems that run desktop 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 pau
40. 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 the Performing an Unattended Driver Installation on page 9 for more information The AParg Driver Kit Parameter and Appending to the APInstall exe File If you specify a value for the APargs driver kit parameter this value is appended to the APInstall exe command line For example if you execute this installer file as lxdrv fc fcoe lt version gt exe q APargs SilentRebootEnable True then after installing the AutoPilot Installer the driver kit automatically executes it as APInstall exe silent SilentRebootEnable True To specify more than one 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 lxdrv fc fcoe lt version gt exe APargs SilentRebootEnable True localDriverLocation d drivers new Storport results in the AutoPilot Installer being run as APInstall exe SilentRebootEnable True localDriverLocation d drivers new Storport Emulex Drivers for Windows User Manual Page 10 gt G EMULEX Parameter values that contain spaces such as path names must be enclosed in quotes To add such a setting to APargs you must insert ba
41. table provides information such as the allowable range of values and factory defaults Parameters can be entered in decimal or hexadecimal format Note If you are creating custom unattended installation scripts any driver parameter can be modified and included in the script Note If the Adapter Protocol is blank it indicates that the parameter is supported on both LightPulse as well as OneConnect adapters LightPulse only indicates parameters supported only on LightPulse and not on OneConnect adapters FC only indicates parameters supported on non LightPulse FC adapters Most parameters default to a setting that optimizes adapter performance Table 11 Storport Miniport Driver Parameters Activation Adapter Parameter Definitions Requirement Protocol AutoMap n AutoMap controls the way targets are assigned Reboot SCSI IDs Discovered targets are assigned persistent SCSI IDs according to the selected binding method Persistent bindings do not take effect with the driver in stand alone mode If set to 0 automap is disabled The OneCommand Manager application persistently sets the SCSI address of a discovered FCP capable FC node target If set to 1 automap by WWNN If set to 2 automap by WWPN If set to 3 automap by DID Value 0 3 Default 2 Class 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
42. the software Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware 0x10 Warning Encountered an error offloading an iSCSI connection error code N The iSCSI driver detected an error while offloading the iSCSI connection The operation is retried up to five times The session handle and the UCNA firmware error code are included in the event log message This may indicate a target is in error or it may point to transient network connectivity issues It may also indicate a UCNA firmware error 0x11 Warning The IOCTL opcode A requires more scatter gather elements than allowed Transfer length is B The iSCSI driver failed an IOCTL request because the number of scatter gather elements required for the IOCTL buffer exceeded the UCNA firmware limit The IOCTL opcode and the payload length requested are included in the event log entry This error may indicate an incorrect configuration option for the iSCSI driver It may also indicate a low memory condition Emulex Drivers for Windows User Manual Page 112 gt G EMULEX Table 30 iSCSI Error Log Entries on Windows Server 2008 R2 Continued Message ID Severity Message Recommended Resolution 0x12 Error Unrecoverable error An unrecoverable error was detected by the detected UE Low A UE iSCSI driver High B FW Line C This may be caused by har
43. unexpected manner The Troubleshooting section contains reference tables on event codes and error messages and provides information regarding unusual situations General Troubleshooting Table 12 General Troubleshooting Problem Answer Solution The operating system fails to install or does not successfully install the driver Windows Device Manager shows a code 10 or code 39 with a yellow or red exclamation point on the device Verify that the operating system is supported by the driver The firmware image does not match the installed device drivers or the firmware is corrupt Using the OneCommand Manager application or one of the WinPE offline or online utilities install a version of firmware that is compatible with the driver The firmware is corrupt or non responsive Using the OneCommand Manager application or one of the WinPE offline or online utilities install a version of firmware that is compatible with the driver The Emulex iSCSI BIOS banner is not displayed during system POST 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 Table 13 Cisco Nexus Switch Situations Problem Solution 1 Windows creates the NTFS partition ok but then reports that The hard disk chose has a LUN greater than 0 Setup cannot continue
44. you need to select only the Initiator Service check box and not the Software Initiator check box The Microsoft iSCSI Initiator Service sets its own initiator name Once you have installed it you must replace this with your chosen initiator name To do this 1 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 2003 On Windows Server 2003 operating systems Microsoft provides multipath support for iSCSI devices via the Microsoft iSCSI Software Initiator This software includes the Microsoft Multipath I O MPIO components and Microsoft iSCSI Device Specific Module DSM To enable multipath support you must download Microsoft iSCSI Software Initiator and install the relevant components as described in this section If you are installing a third party DSM instead of Microsoft iSCSI DSM the installation steps may vary See the ve
45. you want to make sure a custom configuration is not changed by a user during installation There are two ways to perform an unattended installation These correspond to the options for running the software installation interactively Option 1 Install the driver silently Run the driver kit installer from a command prompt or script Specify the q quiet command line option For example lxdrv fc fcoe lt version gt exe q Note The name of the driver kit installer depends on the current version identifier For other command line options see AutoPilot Installer Command Line and Configuration File Parameters on page 10 Option 2 Run the driver kit installer separately Follow steps 1 3 for Running a Software Installation Interactively on page 6 Clear the Run AutoPilot Installer check box on the Finish page 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 the AutoPilot Installer The configuration file is typically located in C Program Files Emulex AutoPilot Installer APInstall cfg Uncomment the line that sets SilentInstallEnable to True There are other settings in the same section of the configuration file related to unattended installations that you may also want to edit See Software Configuration Parameters on page 12 for more i
46. 105 0105 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 0112 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 lpfc_mes0114 and lpfc_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 0114 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 lpfc_mes0115 0115 Unknown ELS command x x received from NPortld x x n DESCRIPTION Received an unsupported ELS command from a remote NPORT SEVERITY Error LOG LOG_ELS verbose ACTION Check remote NPORT for potential problem SEE ALSO Ipfc_mes0112 Emulex Drivers for Windows User Manual Page 77 gt E EMULEX lpfc_mes0128 0128 Accepted ELS command OpCode x x DESCRIPTION Accepted an ELS command from a remote NPORT SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0129 0129 Rejected ELS command OpCode x x DESCRIPTION Rejected E
47. 2 3 mode 0x0C INIT_LINK failed SLI2 3 mode 0x0D READ_REV failed SLI2 3 mode Ox0E Invalid adapter type LightPulse OxOF Invalid adapter type LightPulse 0x10 CONFIG_PORT failed reinitialization 0x12 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 0x1C Firmware trap info1 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 Invalid response tag SLI2 3 mode 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 Attempted ADISC to non existent node 0x2B Failure on iocb context allocation 0x2C Unable to initiate nport unbinding operation 0x2D Unable to initiate nport binding operation 0x30 Failure on mailbox context allocation 0x7C Menlo initialization error 0x7D Menlo initialization error Ox7E Menlo initialization error OxA0 Failed to initialize adapter port OneConnect OxA1 Failed to
48. 2399141891 0x8F000003 Disabled adapters detected in the system 2399141892 0x8F000004 The selected driver is 64 bit and this system is 32 bit 2399141893 0x8F000005 The selected driver is 32 bit and this system is 64 bit 2399141894 0x8F000006 Installation activity is pending AutoPilot Installer cannot run until it is resolved GUI Mode only You cancelled execution because you did not wish to perform 2399141895 Dx F000007 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 0x8F00000C A silent reboot was attempted but according to the operating system a reboot is not possible 2399141901 0x8F00000D GUI Mode only A driver package download was cancelled 2399141902 0x8F00000E Non Enterprise No adapters were found in the system Emulex Drivers for Windows User Manual Page 17 gt G EMULEX Table 1 Unattended Installation Error Codes Continued Error Code Hex Description 2399141903 0x8F00000F A required QFE or Service Pack was
49. 4 iSCSI Windows Version for the x64 driver version or C Program Files Emulex AutoPilot Installer Drivers Storport lA64 iSCSI Windows Version for the Itanium driver version Click OK Select Emulex OneConnect OCMXXXXxX iSCSI Initiator your adapter model is displayed here Click Next Click Finish The driver installation is complete The driver should start automatically Installing or Updating the NIC Driver Note Although TOE is supported it is turned off by default Windows 2003 To update or install the NIC driver from the desktop 1 NOOR WD 10 11 Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click 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 Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All DC adapter models are displayed in the 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 Direct the Device Wizard to the location of oemsetup inf If you have installed t
50. 8 18000 lt I Os lt 26000 1 16 1 Os gt 26000 1 24 Emulex Drivers for Windows User Manual Page 52 gt G EMULEX 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 Ox3F hex The default is 0 and disables I O Coalescing CoalesceRspCnt The CoalesceRspCnt parameter controls the maximum number of responses to batch before an interrupt generates If CoalesceRspCnt expires an interrupt generates for all responses collected up to that point With CoalesceRspCnt set to less than 2 response coalescing 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 or 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 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 throttlin
51. 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 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 efficient application such as ntttcp Emulex Drivers for Windows User Manual Page 63 gt G EMULEX 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 Error Handling The goal of iSCSI error handling is to be tolerant
52. Default 3 Emulex Drivers for Windows User Manual Page 66 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol CoalesceMsCnt n CoalesceMsCn specifies wait time in milliseconds 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 Ox3F hex Default 0 0x0 Reset LightPulse Only CoalesceRspCnt n CoalesceRspCn specifies the number of response entries that trigger an Interrupt response Value 0 255 decimal or 0x1 OxFF hex Default 8 0x8 Reset LightPulse Only Emulex Drivers for Windows User Manual Page 67 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Te Activation Adapter Parameter Definitions Requirement Protocol ConfigScale ConfigScale sets the memory footprint profile in OneConnect and accord with the anticipated use case on a per port basis The default value of 1 is considered to be the typical use case The ConfigScale parameter supersedes the ExtTransferSize parameter for OneConnect adapters and Emulex 16 Gb adapters For all values except 0 up to 1024 targets can be discovered and mapped If set to 0
53. Emulex Drivers for Windows User Manual Page 3 gt G EMULEX e Windows PE 2 x or 3 x e Minimum 512 MB memory Note Check the Emulex website for required updates to the Windows operating system or the Microsoft Storport driver Compatibility Only OneConnect OCe11100 adapters are supported on Windows 7 x64 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 Changing Driver Types If you currently use a SCSlport Miniport or FC Port driver the driver is replaced when you install the Emulex Storport Miniport FC driver The FC driver is installed for all adapters on the server You lose your customized driver parameters persistent bindings logical unit number LUN masking and LUN mapping The default parameters set with AutoPilot Installer are usually the best options However you may want to note your current settings before you install the Emulex FC driver After the installation you can then update your customized driver parameters Note This update process can leave files associated with old driver kits on your system After running AutoPilot Installer and restarting your system you may be required to uninstall old driver or utility program entries Follow the procedures in Uninstalling Emulex Driver Kits on page 25 Ensure you delete only previous driver versions Oneln
54. Emulex drivers do not support the Emulex 16 Gb adapters e Windows Server 2008 running on an x86 x64 or Itanium 64 bit server e Server Core installation option of Windows Server 2008 running on an x86 or x64 server e Windows Server 2008 R2 running on an x64 or Itanium 64 bit server e Windows Server 2008 R2 SP1 e Windows 7 Ultimate Enterprise or Professional edition x64 only not supported on Fibre Channel HBAs e Windows Pre installation Environment PE 2 x or 3 x e Minimum 512 MB memory Note Check the Emulex website for required updates to the Windows operating system or the Emulex drivers 1 Itanium support is for FC driver only 2 AutoPilot Installer is not supported for use with Windows PE See the Windows Automated Installation Kit WAIK documenta tion for instructions on including drivers with your Windows PE images Emulex Drivers for Windows User Manual Page 2 gt S EMULEX Compatibility Only OneConnect OCe11000 adapters are supported on Windows 7 x64 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 iSCSI Driver Prerequisites One of the following operating systems must be installed e Windows 2003 R2 SP2 e Windows Server 2003 SP2 running on an x86 or x64 server Note For Windows Server 2003 SP2 and Windows Server R2 SP2 the KB932755 u
55. Error driver parameter determines the minimum severity level to enable entry of a logged error into the system If set to 0 all errors regardless of severity are logged If set to 1 severe malfunction and command level errors are logged If set to 2 both severe and malfunction errors are logged If set to 3 only severe errors are logged Note See the Configuration Section for instructions on how to set driver parameters 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 Date date entry was logged Source elxstor Time time entry was logged Category none Type error Event id 0 User N A Computer name of computer Emulex Drivers for Windows User Manual Page 93 Error Codes Tables Table 17 Severe Errors gt G EMULEX Bits 0 7 Interpretation 0x00 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 SLI
56. I driver ignored a configuration The invalid entry must be removed or entry because the entry was invalid corrected Check the registry configuration for any new valid values added to the driver parameters For more information on valid driver values see Driver Parameters for Windows on page 66 0x31840009 The iSCSI driver failed to load a The range specified for a configuration configuration value specified in the registry parameter is too large or too small and must be because the value was out of range The corrected Check the registry configuration for driver will use the default value for this any new valid values added to the driver configuration parameter instead parameters For more information on valid driver values see Driver Parameters for Windows on page 66 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 being present or currently running This failure may also indicate a hardware problem 0x31640004 An internal API failed in the iSCSI driver This failure may indicate a low memory during initialization condition 0x3164000D The driver failed to allocate its complete This message indicates a low memory memory requirement and will attempt to load condition
57. LDTO values are configurable via the Windows registry ETO 90 seconds 0 seconds 3600 seconds Extended timeout ETO in seconds This parameter determines the amount of time the UCNA driver waits for the target to be available after it has lost connection to the target during an I O operation Note ETO values are configurable via the Windows registry im_policy The Interrupt Moderation policy parameter controls the rate of interrupts for the UCNA For more information see Interrupt Moderation Policy Settings below Iqd 128 255 The LUN queue depth parameter configures the number of concurrent commands to a logical unit via Storport API StorPortSetDeviceQueueDepth The Iqd parameter also sets the maximum number of concurrent commands allowed per LUN Emulex Drivers for Windows User Manual Page 48 gt G EMULEX Table 4 iSCSI Driver Options Continued Continued Parameter Default Value Minimum Value Maximum Value Description large_io 64 64 512 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 S
58. LS command from a remote NPORT SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0130 0130 ELS command error ulpStatus x x ulpWord 4 x x DESCRIPTION ELS command failure SEVERITY Error LOG LOG_ELS verbose ACTION Check remote NPORT for potential problem Discovery Log Messages 0202 0262 lpfc_mes0202 0202 Start Discovery Link Down Timeout x x initial PLOGICount d DESCRIPTION Device discovery rediscovery after FLOGI FAN or RSCN has started TMO is the current value of the soft link time It is used for link discovery against the LinkDownTime set in parameters DISC CNT is number of nodes being discovered for link discovery RSCN CNT is number of nodes being discovered for RSCN discovery There will be value in either DISC CNT or RSCN CNT depending on which discovery is being performed SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational lpfc_mes0204 0204 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 lpfc_mes0214 0214 RSCN received Word count d DESCRIPTION Received RSCN from fabric SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational lpfc_mes0215 0215 RSCN processed DID x x DESCRIPTION Processed RSC
59. N from fabric SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational Emulex Drivers for Windows User Manual Page 78 gt E EMULEX lpfc_mes0225 0225 Device Discovery completes DESCRIPTION This indicates successful completion of device re discovery after a link up SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational lpfc_mes0229 0229 Assign SCSIId x x to WWN word 0 x x WWN word 1 x x NPortld X X DESCRIPTION The driver assigned a SCSI ID to a discovered mapped FCP target BindType 0 DID 1 WWNN 2 WWPN SEVERITY Information LOG LOG_DISCOVERY verbose ACTION No action needed informational lpfc_mes0230 0230 Cannot assign SCSIId to WWN word 0 x x WWN word 1 x x NPortld X X DESCRIPTION SCSI ID assignment failed for discovered target SEVERITY Warning LOG LOG_ELS verbose ACTION Review system configuration Ipfc_mes0232 0232 Continue discovery at sequence number d PLOGIs remaining d DESCRIPTION NPort discovery sequence continuation SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0235 0235 New RSCN being deferred due to RSCN in process DESCRIPTION An RSCN was received while processing a previous RSCN SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0236 0236 Issuing command to name server type x x DESCRIPTION The
60. RK See also Message 0713 0748 Lun reset complete Pathld x x Targetld x x Lun x x DESCRIPTION A LUN reset operation has completed SEVERITY Warning LOG LOG_FCP verbose ACTION Review system configuration Possible side effect of cluster operations REMARK See also Message 0703 0749 Abort task set complete Did x x SCSIId x x DESCRIPTION A task management has completed SEVERITY Warning LOG LOG_FCP verbose ACTION Review system configuration Possible side effect of cluster operations REMARK See also Message 0701 Link Log Messages 1302 1306 Ipfc_mes1302 1302 Invalid speed for this board d forced link speed to auto DESCRIPTION The driver is re initializing the link speed to auto detect SEVERITY Warning LOG LOG_LINK_EVENT verbose ACTION None required lpfc_mes1303 1303 Link Up event tag x x link speed dG topology 0 Pt2Pt 1 AL d DESCRIPTION A link up event was received It is also possible for multiple link events to be received together SEVERITY Error LOG LOG_LINK_EVENT verbose ACTION If numerous link events are occurring check physical connections to the FC network REMARKS Ipfc_mes1304 is recorded if Map Entries gt 0 and the corresponding mode and SEVERITY level is set Emulex Drivers for Windows User Manual Page 84 gt G EMULEX lofc__mes1305 1305 Link down even tag x x DESCRIPTION A link down event was received SEVERITY Error LOG LOG_LINK_EVEN
61. Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic 58 TCP OfflOAGING cceeeeceeeeeeeeeeccaeeeeeeeeeeeeeaaaeeeeeeeeeeeccaaeeeeeeeeeseecenaaeeeeeees 59 Windows Networking and TOE ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetaaaeeeeenees 61 Receive Window Auto Tuning and Compound TOP ccccceeeeeeeeeeeeeeees 62 INterruipt COAlSSCING sesssssesesexeecssceeseneeneyenesessussbsenehepessxeuevaststeeneseaawasbeees eee 63 CPU Binding Considerations cccceeeeeeeeeeeeeeeeceeeeeeeeeeeeeetaaeeeeeeeeeenees 63 Single TCP Connection Performance Settings cccseeeeeeeeeeeeeesteees 63 iSCSI Error Handling cco Aten eaten eee eae Atala 64 Configuring LDTO and ETO on Windows Servet u ccceecceseceeeeeeeeeeeeeeseeeeeees 64 Error Handling Under MultiPath MPIO and Cluster Configurations 65 Driver Parameters for WiNdOWS 0h tii i i nin i ii iii iiiiiiieeeeeaaaaaa 66 Troubleshooting lt ccccccccctesecceteeteeetedeee aden dees 75 General Troubleshooting cccceecceeeeeeeeeeeeeeaeeeeeeeeeccaaaeeeeeeeeeseecaaeeeeeeeeeeeseaaees 75 Troubleshooting the FC FCOE Driver ccccceeceeeeeeeeeeeeeeeeceeeeeeeeeeeeeenaeeeeeeeeeteee 75 Troubleshooting the Cisco Nexus Switch Configuration eseese 75 Event Tracing Windows Server 2003 SP1 and later only cceeeeeeeees 76 Event Trace MESSAGES ceccceeeeeeeceeeeeeeeeeeeeeeeeeeeeeeeeee
62. SCSI driver s default error handling scheme Depending on the type of failover configuration the iSCSI driver s error handling parameter needs to be configured appropriately If the iSCSI target is in Active Active failover mode the iSCSI driver must report I O errors as soon as they are detected This allows the failover software to trigger a path failover to an active path or active node as quickly as possible This configuration requires that the iSCSI driver s LDTO and ETO parameters be set to 0 If the iSCSI target is in Active Standby failover mode then the iSCSI driver must wait for the target side failover operation to complete before reporting device unavailability to the operating system For such configurations the driver s ETO must be set to the amount of time the iSCSI target needs to complete its failover operation Emulex Drivers for Windows User Manual Page 65 gt G EMULEX Driver Parameters for Windows The parameters listed in Table 11 are applicable to the Storport Miniport driver versions 2 70 xxx or later Activation Requirements A parameter has one of the following activation requirements e Dynamic The change takes effect while the system is running e Reset Requires an adapter reset from the utility before the change takes effect e Reboot Requires a reboot of the entire machine before the change takes effect In this case you are prompted to perform a reboot when you exit the utility The Driver Parameter
63. T verbose ACTION If numerous link events are occurring check physical connections to the FC network Ipfc_mes1306 1306 Link Down timeout DESCRIPTION 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 SEVERITY Warning LOG LOG_LINK_EVENT verbose ACTION Check adapter cable connection to SAN Tag Messages 1400 1401 lpfc_mes1400 1400 Tag out of range ContextIndex x x MaxIndex x x ulpCommand x x DESCRIPTION Firmware has generated an invalid response SEVERITY Error LOG LOG_LINK_EVENT verbose ACTION Review hardware configuration Contact Emulex Technical Support lpfc_mes1401 1401 Invalid tag ContextIndex x x ulpCommand x x DESCRIPTION Firmware has generated an invalid response SEVERITY Error LOG LOG_LINK_EVENT verbose ACTION Review hardware configuration Contact Emulex Technical Support NPIV Messages 1800 1899 lpfe_mes1800 1800 NPIV FDISC failure VPI x x Error x x Reason x x DESCRIPTION Virtual Port fails on a FDISC to the switch with the error and reason listed SEVERITY Error LOG LOG_NPIV verbose ACTION Check to ensure the switch supports NPIV lpfc_mes1801 1801 Memory allocation failure for NPIV port x x DESCRIPTION Fails to allocated the block of memory for the Virtual Port SEVERITY Error LOG LOG_NPIV verbose ACTION Check to ensure system has sufficient kernel memor
64. The following describes the format of option 43 and includes guidelines for creating the data string iscsi lt TargetIP gt lt TargetTCPPort gt lt LUN gt lt TargetName gt lt InitiatorName gt lt Heade rDigest gt lt DataDigest gt lt AuthenticationType gt e Strings shown in quotes are part of the syntax and is therefore mandatory e 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 e Ifan optional field is skipped a colon must be used as a placeholder to indicate the default value for that field e When specified the value of each parameter should be enclosed in double quotes See Examples on page 117 All options are case sensitive Description of Mandatory and Optional Parameters Table 31 describes the parameters used in the data string for option 43 Table 31 Data String Parameters for Option 43 Parameter Description Field Type lt TargetIP gt A valid IPv4 address in dotted decimal Mandatory notation lt TargetT CPPort gt A decimal number ranging from 1 to Optional 65535 inclusive The default TCP port is 3260 Emulex Drivers for Windows User Manual Page 116 Table 31 Data String Parameters for Option 43 Continued gt G EMULEX Parameter Description Field Type lt LUN gt A hexadecimal representation of the LUN
65. ULPOCUGCHION cece cenectauawentteatene eeaaaanaktettieeeeaassnakeertie eaueaanakcertcecenaaa nae ce teecenaneahaneateneeane 1 AutoPilot Installer ssccosiiccdiaiiiacdiasdiaabiat dies E AARETE ENERE AAAA AE AEAEE AAAA AAA EAA AA AANRADER ESEA 1 Onelnstall Installer cceccceeeeeee eee eeeecceee eee ee eeeccaaaeeeeeeeeeeeccaaaeeeeeeeesseessnaeeeeeees 2 Important Considerations cccccccceeeeeeeeeecneeeeeeeeeeeecccaeeeeeeeeeeeeccaaeeeeeeeeetesseaeeeeeees 2 Minimum Software RequireMent ccccccecceeeeeeeeeeeeeeeccneeaaeeeeeeeeeseeednaeeeeetnee 2 Windows Driver Information ccccccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteeeegs 2 FC and FGOE Driv SF assesses aacvanaxanacanacagensaazenas cuadacasecasasasteasadasteasanauasenspansas 2 Prerequisite S ucne iceeacecstersen ieee tercacn ten mer teceeecenn cere tcrasescr rn cere cece etn 2 COM Dati IY oaan neee E E E 3 SOSI Driva enaa i i ii 3 Prerequisite Scornen ea a a a aaa aaa a aaa aa aAa Sa 3 COPANO e E E E TEEI EEEIEE RER 3 NDIS Miniport Ethernet NIC Driver esessssseseesssessserrrrsssssrrrrnrrsssssrrrsssssrrens 3 Prerequisites cccceceeeeeeeeeeeeeeeeeeeeeeaaaeeeeeeeeeeeeeaaaeaeeeeeeeeesaaaaeeeeeeeeeeseaaaaees 3 CONAD serseri e at acanatetadanieadaeagieatadaniaatadaeitatataeitatatacaeataeataes 4 Changing Driver Typ S ceecee EEEE 4 Onelnstall Package OvervieW sssssssseeiesssssssrrrrrssssstrrrnnnnsssstrrnnnnnnsssnnnnnnnnnssennnn
66. 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 valid Note There is no boundary checking for this field It is the administrator s responsibility to set this field correctly Packet Size 1514 1514 9014 Configuration packet size for OneConnect NIC only Limit normal sized frames and one value for jumbo packet This parameter determines the maximum packet size transmitted and received on the interface A 1514 byte frame size is standard while larger packets are called jumbo frames Using a higher frame size is generally more efficient but it uses more system memory A larger frame size also requires support on the network switch Emulex Drivers for Windows User Manual Page 39 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition RSS Enabled Disabled Support for up to 4 RSS queues if Enabled enabled Receive Side Scaling RSS scales receive processing over multiple CPUs in parallel This scaling typically improves application performance however it tends to increase CPU usage on low end machines RSS is only supported on two primary adapters per device It app
67. a long time to fail over or failover does not occur Ensure that link down timeout LDTO settings and extended timeout ETO settings have been configured for MPIO These values must be set to 0 For more information see Configuring LDTO and ETO on Windows Server on page 64 Sendtargets to an IET target fails because it violates the iSCSI specification If you still want to add an IET target you must add the target manually This issue affects Sendtargets only The following POST error message appears Initiator iSCSI Name mismatch Please use iSCS ISelect to set a single name for all controllers Press lt Cirl gt lt S gt to enter iSCS ISelect Reboot required 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 Emulex Drivers for Windows User Manual Page 89 gt G EMULEX Table 16 Troubleshooting the iSCSI Driver Continued Problem Answer Solution When an iscsicli logouttarget command is issued back to back in a script event 12 errors from the PlugPlayManager a
68. aeeeeeees 93 Related Driver Parameter LOQError cccccccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeness 93 Format of an Error Log Entry cccccceccceeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteneas 93 Error Codes Tables reanimarea aaa aa aAa Aa aE 94 Viewing the FC FCoE Event Log cc cccceeeeeeeeeceneeeeeeeeeseseaeeeeeeeeeeeeeenaaees 97 Event Log Mterpretation saana ERRERA ERRERA ERRERA ERRERA ARARE 97 Additional Event Log Information ssssssssssssrrrrrrnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 97 NIC Erro EVEN OOS ironinen eaa EEE EEES 101 Viewing the NIC TOE Error LOg eeeeeeesseeeeeseesesserirrrrssssrrrrnnnsssssrnnnnenssne 101 Viewing the NIC TOE Event Log sssesseessssesssssssssrrrrrsssssrirrrssssssrrnnnnsnssnt 103 ISCSI Error Event LOG ccccccccccecccccceeeeee eee eeeeccneeeeeeeeeeeecccaaeeeeeeeeeeeeccceeeeeeeenenees 106 Viewing the iSCSI Error Event Log on Windows 2003 Window 2008 106 Viewing the iSCSI Error Log on Windows 2003 and 2008 ceeeeeee 107 Viewing the iSCSI Error Logs on Windows 2008 R2 eeeeeeeetteeettees 110 Appendix B Configuring iSCSI through DHCP cccesecceeeeeeeeeeceeeeeeeeeeeeeeetesneeeees 116 Dynamic Host Configuration Protocol DHCP Recommendations 0 06 116 Vendor Specific Option 43 eee ceeecceceeeeeeeecceeeeeeeeeeeeeecaeeeeeeeeesesecceeeeeeeessaaaes 116 Emulex Drivers for Windows User Manual Page v Format of V
69. ager 2 Right click the network adapter for which you wish to modify advanced properties 3 Click Properties then click the Advanced tab ST gt 4 From the list of properties click on 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 Note Modifying properties this way causes the network driver to reload and some Transmission Control Protocol TCP connections may be temporarily dropped Emulex Drivers for Windows User Manual Page 28 gt G EMULEX Class of Service 802 1p Enhanced Trensmission Selection Network Address Packet Size VLAN Identifier 802 1q 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 e en Figure 3 NIC TOE Advanced Properties in Windows Server 2003 and Windows Server 2008 Configuring NIC TOE Driver Options The Windows Server NIC TOE drivers support 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 27 No more than one VLAN can be used with each universal multichannel UMC virtual channel Note You cannot run Link Aggregation C
70. all icon in the tool bar above the program list If you have User Access Control enabled click Continue when asked for permission 3 Click Yes The application is removed from the system Click OK To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files folder on an x86 system or the Program Files x86 folder on a 64 bit system 2 Navigate to Emulex AutoPilot Installer 3 Run uninstall_elx_core_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 if you want Uninstalling the Emulex Drivers The Emulex Storport Miniport and PLUS ElxPlus drivers are uninstalled using the Device Manager Note On Windows 2008 after the message Warning you are about to uninstall this device from your system is displayed You must select the checkbox Delete the software for this device in order to uninstall the driver To uninstall the Emulex Storport Miniport driver 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 Dr
71. ance Tuning Network driver performance tuning improves performance of the network and TCP Offload driver for the Windows Server operating system The OneConnect UCNA is an x8 Generation 2 Gen 2 or Gen2 PCI Express device and requires substantial memory bandwidth in a system to support 10 Gb s data streams Note When a performance test is run it is recommended that the system description be transmitted as part of the Link Layer Discovery Protocol LLDP You can modify LLDP settings on the DCB tab of the OneCommand Manager application see the OneCommand Manager Application User Manual or you can use the SetDCBParam command of the OneCommand Manager CLI application hbacmd to enable Link Layer Discovery Protocol LLDP parameters see the OneCommand Manager Command Line Interface User Manual Improving Performance with PCI Express Bandwidth 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 PCle packet payload size provides the best efficiency for PCle data transfers Improving Performance with TCP Offload TCP offload helps memory bandwidth significantly by eliminating the data copy of receive packets This higher memory bandwidth leads to better network performance Most computers offer multiple distinct memory channels or memory interleaves which may not be enabled by default
72. ance with FC Drivers cccecceeeeeeeeeeeeenneeeaaeeeeeeeeeeesecaeeeeeeesenaaees 52 VO COAlSSCING 0 ee eeeeeeeeeccneeeee eee eeeeeecaeeeee eee eeeaeeeeeeeeeeeeeeeecccaaeeeeeeeeegeeenaeeeeninee 52 CoalesceMS Cntissneasiitsiinicranisiisne hehe nana Aandannaieed 53 CoaleSCeRSpCnnt cccccccccceeeececccceeeeeeeeeneeeeeeeeeeteeecaeeeeeeeeeeeeeeeeeniaeeeeeeneed 53 PEMOlMANCS TOSUN E E EERE EREE 53 TU 10T Bl 0 iA ee 53 COaleSCOMSCittiesasccetcesctesessissseeacisntteenaceeeredededeteead a A R a 53 CoaleSCeRSpCnnt siiip ia a a aa aaa aaa a ea 53 Network Driver Performance TUNING ccccccecceececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 54 Improving Performance with PCI Express Bandwidth cceseeeeeeeeeeeees 54 Improving Performance with TCP Offload cceceeceeeceeeeeeeeeeeeeeeeetneeeeeeeeeetees 54 Windows Server Network Drivel ccscccceeeeeeeeeecneeeeeeeeeeeeeccnaeeeeeeeeeeeeseaaaes 54 Analyzing Performance Problems cccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeenees 55 JUNIO PACK OU acca ca KE LERRET EEEE ceca ceca cw eaten 56 Fow Contool ccc o5 costes certs cee cece ctctct et ca ct ceca ceas cect cnc cece reauetet cnc cece ree eeectce 56 TCP Offload Optimization Settings ccccsccceeeeeeeeeeeeneeeeeeeeeeeeesnneeeeeees 57 Checksum Offloading and Large Send Offloading LSO eeee 58 Emulex Drivers for Windows User Manual Page iv gt G EMULEX
73. bes the steps to log into iSCSI targets through the WMI GUI For information on using the iSCSISelect utility to log into an iSCSI target see the Emulex Boot Manual To log in to a target using WMI 1 Select the Enable multi path in the Log On to Target window This must be selected for every target to be logged in for MPIO Use the Advanced tab to select the specific UCNA port to use for login 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 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 6 Recommended Settings for I O Coalescing VOS pet second Can acti Cae aca I Os lt 10000 0 8 10000 lt I Os lt 18000 1
74. box command SEVERITY LOG LOG_INIT verbose ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support Emulex Drivers for Windows User Manual Page 81 gt E EMULEX lpfc_mes0454 0454 Adapter failed to init INIT_LINK mbxStatus x x DESCRIPTION Adapter initialization failed when issuing INIT_LINK mailbox command SEVERITY Error LOG LOG_INIT verbose ACTION This error could indicate a hardware or firmware problem If problems persist report these errors to Technical Support lpfc_mes0458 0458 Bring Adapter online DESCRIPTION The FC driver has received a request to bring the adapter online This may occur when running HBAnyware SEVERITY Warning LOG LOG_INIT verbose ACTION None required lpfc_mes0460 0460 Bring Adapter offline DESCRIPTION The FC driver has received a request to bring the adapter offline This may occur when running HBAnyware SEVERITY Warning LOG LOG_INIT verbose ACTION None required lpfc_mes0463 0463 Adapter firmware error hostStatus x x Info1 0xA8 x x Info2 OxAC X X DESCRIPTION The firmware has interrupted the host with a firmware trap error SEVERITY Error LOG LOG_INIT verbose ACTION Review HBAnyware diagnostic dump information FCP Log Messages 0701 0749 lpfc_mes0701 0701 Issue Abort Task Set to Pathld x x Targetld x x Lun x x DESCRIPTION The driver has issued a task management
75. cation of oemsetup inf If you have installed the driver installer kit to the default folder the path is C Program Files Emulex AutoPilot Installer Drivers NDIS x86 NIC Windows Version for the 32 bit driver version or C Program Files Emulex AutoPilot Installer Drivers NDIS x64 NIC Windows Version for the x64 driver version or C Program Files Emulex AutoPilot Installer Drivers NDIS IA64 NIC Windows Version for the Itanium driver version Click OK The Windows Security dialog box opens Click Install When the device driver finishes installing click Close The driver installation is complete The driver should start automatically Emulex Drivers for Windows User Manual Page 24 gt G EMULEX Uninstallation Uninstalling Emulex Driver Kits Note When you uninstall the Emulex driver kit AutoPilot Installer is automatically uninstalled To uninstall a driver kit on a Windows Server 2003 system Open the Add or Remove Programs control panel 2 Select Emulex FC FCoE NIC iSCSI Driver kit 2 xx xxx in the program list and click Remove Where Emulex FC FCoE NIC iSCSI Driver kit 2 xx xxx is the complete name and version of the driver 3 Click Yes The application is removed from the system Click OK To uninstall a driver kit on a Windows Server 2008 system 1 Open the Programs and Features control panel 2 Select Emulex FC FCoE NIC iSCSI Driver kit 2 xx xxx in the program list and click the Uninst
76. cceptable Values Definition Receive 896 64 through 16384 inclusive This determines the number of Buffers Ethernet receive buffers allocated per receive queue If RSS is enabled 4 or more receive queues are used Otherwise a single queue is enabled Decreasing this value will reduce the required system memory but performance may decrease Each buffer is the size of the Packet Size parameter IP Checksum RX and TX Enabled Disabled This offloads the transmit and or Offload IPv4 RX and TX Enabled receive IPv4 checksum RX Enabled computation TX Enabled Offloading checksums increases system efficiency IP Checksum RX and TX Enabled Disabled This offloads the transmit and or Offload IPv6 RX and TX Enabled receive IPv6 checksum RX Enabled computation TX Enabled Offloading checksums increases system efficiency Large Send Enable Disabled Large Send Offload allows the Offload LSO Enabled NIC hardware to segment large v1 IPv4 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 Emulex Drivers for Windows User Manual Page 37 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options C
77. ccfg 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 Emulex Drivers for Windows User Manual Page 43 gt G EMULEX Options 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 from a list s name v name v Sets the parameter s value and reloads the devices g name name Gets parameter value xr Skips reloading the driver when setting a parameter f Force reloading the driver 1 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 7 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 e g Emulex OneConnect OCe11102 and the network connection name e g Local Area Connection The later may be modified by using the Window s Network Connections applet ncpa cpl The most
78. checksum settings offload Offload IPv6 RX Enabled the transmit and or receive IPv6 TX Enabled UDP checksum computation Offloading checksums increases system efficiency Emulex Drivers for Windows User Manual Page 42 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition VLAN Identifier Not Present Not Present If selected the adapter adds a 1 to 4095 VLAN tag to all transmitted packets Wake on LAN Disabled Disabled Enabling Wake on LAN allows Enabled 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 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 The following section describes how to use the occfg program to configure the Windows OneConnect device driver from the command line Displaying OCCFG Help To display help use the option by typing occfg on the command line The following text will be displayed OneConnect Network Config 0 0 9999 0 Copyright 2011 Emulex Usage o
79. ckslashes before the quotes around the value and then add quotes around the entire APargs expression For example the command line all on one line lxdrv fc fcoe lt version gt exe APargs ReportLocation C Documents and Settings Adminis trator My Documents reports results in AutoPilot Installer being run as APInstall exe ReportLocation C Documents and Settings Administrator My Docu ments 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 AutoPilot Installer Separately on page 7 and Performing an Unattended Driver Installation on page 9 You can specify a non default directory for the driver kit by specifying an installation folder on the command line For example lxdrv fc fcoe lt version gt exe install C Emulex This option can be used in conjunction with the APArgs directive AutoPilot Installer Syntax The syntax used to run AutoPilot Installer silently from a command line or script is APInstall silent parameter setting parameter setting The silent switch and parameter settings can occur in any order One or more spaces must separate the switch and each parameter setting The syntax of a paramet
80. containing QUESTIONS marks the start of the subsection and the end of it is marked by a line containing ENDQUESTIONS Within the question subsection there can be as many questions as needed Each question uses the format question question explanation answer0O answer1 answer2 answern Where question contains the text of the question to be asked explanation contains brief text to help explain the question The explanation appears below the question in a smaller font If there is no explanatory text empty quotes must be used in its place answerO contains the 1st answer to be displayed in the drop down list answer contains the 2nd answer to be displayed in the drop down list 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 Page 15 gt G EMULEX Example of STORPORT CONFIGURATION section STORPORT CONFIGURATION The first section contains the driver parameters common to all configurations no matter what answers are
81. crementing 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 If this is greater than 0 the computer system is sending or receiving IP fragments This is a serious performance problem See Jumbo Packet below 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 jumbo packets Emulex Drivers for Windows User Manual Page 55 gt G EMULEX Jumbo Packet The jumbo packet setting in the registry determines the maximum Ethernet packet size It includes the Ethernet frame header typically 14 bytes but excludes the trailing Cyclic Redundancy Check CRC The standard packet size is 1514 bytes plus a 4 byte trailing CRC Vendors use many terms that refer to this same quantity such as packet size frame size or Maximum Transmission Unit MTU The MTU is the Ethernet packet payload size This d
82. d 7 x x DESCRIPTION The specified device failed an I O FCP command SEVERITY Warning LOG LOG_FCP verbose ACTION Check the state of the target in question REMARKS Ipfc_mes0730 is also recorded if it is a FCP Rsp error lpfc_mes0730 0730 FCP response error Flags x x SCSI status x x Residual d DESCRIPTION The FCP command failed with a response error SEVERITY Warning LOG LOG_FCP verbose ACTION Check the state of the target in question remark lIpfc_mes0716 lpfc_mes0734 lofc_mes0736 or lpfc_mes0737 is also recorded for more details if the corresponding SEVERITY level is set SEE ALSO Ipfc_mes0729 lpfc_mes0734 0734 Read Check fcp_parm x x Residual x x DESCRIPTION The issued FCP command returned a Read Check Error SEVERITY Warning LOG LOG_FCP verbose ACTION Check the state of the target in question SEE ALSO Ipfc_mes0730 Emulex Drivers for Windows User Manual Page 83 gt E EMULEX lofc__mes0737 0737 SCSI check condition SenseKey x x ASC x x ASCQ x x SrbStatus X X DESCRIPTION The issued FCP command resulted in a Check Condition SEVERITY Warning LOG LOG_FCP verbose ACTION Review SCSI error code values SEE ALSO Ipfc_mes0730 0747 Target reset complete Pathld x x Targetld x x Did x x DESCRIPTION A target reset operation has completed SEVERITY Warning LOG LOG_FCP verbose ACTION Review system configuration Possible side effect of cluster operations REMA
83. ditions 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 Event Log Viewing the iSCSI Error Event Log on Windows 2003 Window 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 oe ONS Click System 6 Click the be2iscsi error under System Events to show the details of the event The iSCSI driver logs errors with the port driver error code of SP_LINTERNAL_ADAPTER_ERROR which translates to an Event ID 11 entry in the system event log The following is an example of the iSCSI driver error code 0x11800003 viewed with the Event Viewer application The window sh
84. dware errors or by unhandled exceptions in the hardware or firmware 0x13 Error Hardware initialization The iSCSI driver detected a failure in the failed 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 gather list for an SRB an IO because it failed to retrieve a scatter gather has failed list from 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 Driver loading failed because the PCI failing driver load Vendor ID and Device ID are not supported Check the UCNA configuration 0x18 Error Memory could not be This failure occurred because of a failed allocated failing driver load 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 Emulex Drivers for Windows User Manual
85. e Emulex PLUS ElxPlus driver supports the OneCommand Manager application persistent binding and LUN mapping and masking The ElxPlus driver must be installed before you install the Emulex protocol drivers Removing the Adjunct Driver Registry Key The ElxPlus driver replaces the adjunct driver that was used with Storport Miniport 1 11a3 or earlier If it is currently installed the adjunct driver registry key must be removed using the deladjct reg file before you install the ElxPlus driver Installing the Emulex PLUS ElxPlus Driver for the First Time To install the ElxPlus driver from the desktop Note Only one instance of the ElxPlus driver should be installed even if you have multiple adapter ports installed in your system 1 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 6 for instructions 2 Select Start gt Settings gt Control Panel gt Add Hardware The Add Hardware Wizard window appears Click Next 3 Select Yes have already connected the hardware and click Next 4 Select Add a new hardware device and click Next 5 Select Install the hardware that I manually select from a list Advanced and click Next 6 Select Show All Devices and click Next 7 Click Have Disk Direct the Device Wizard to the location of elxplus inf If you have installed the driver installer kit in the default folder and C is your Windows system drive the
86. e 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 Emulex Drivers for Windows User Manual Page 49 gt G EMULEX In a configuration that involves a large number of iSCSI targets more than 32 or 64 and higher values of queue depth the default setting may prove to be too aggressive In such a case you may need to change the im_policy parameter setting to 3 or 4 Although this increases latency of an I O request the lower interrupt rate may allow the system to be functional under a high load Creating Non Bootable Targets To set up non bootable targets proceed with the driver and operating system installation then download and use the Microsoft iSCSI Initiator Service to configure and manage the adapter Using the Microsoft iSCSI Initiator Service You can use the Microsoft iSCSI Initiator Service to configure and manage the UCNA The Microsoft Initiator Service is available as a free download from www microsoft com See the documentation that accompanies it for detailed information Note When you install the Microsoft Initiator Service
87. ears disabled for additional PCI functions in blade server configurations RSS requires Windows 2003 SP2 and later TCP Offload Optimize Throughput Optimize Latency This parameter only applies to Optimization Optimize Throughput 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 256 64 through 256 inclusive Transmit Buffers sets the number Buffers 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 Emulex Drivers for Windows User Manual Page 40 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition Preferred NUMA Node Optional not set Not present or a value from 0 through 65535 Most modern multi socket servers have separate memory controllers for each CPU socket These systems have non uniform memory access NUMA latencies for
88. econds Microsoft Check for errors reported at the during I O operations Following this error log target The Emulex iSCSI UCNA is only entry the next entry will indicate the session supported with certified targets handle where this error occurred The iSCSI paani for ea p e Ba driver will trigger a session recovery on the he We Dele appa epee me session and continue Check for software updates at the Emulex website If applicable update the software 0x127b0012 The iSCSI driver received an invalid iSCSI e Verify that the iSCSI target is certified by Command Sequence Number update from Microsoft Check for errors reported at the the target Following this error log entry the target The Emulex iSCSI UCNA is only next three entries will indicate the session supported with certified targets handle and the iSCSI parameters e Check for software updates at the target MaxCmdSN and ExpCmdSN respectively sii website If applicable update the e Check for software updates at the Emulex website If applicable update the software 0x12790006 A connection to the target was lost for a Check the connection to the target or the state period exceeding the Extended Timeout of the target device If the target is made ETO The error log entry immediately available any sessions that existed previously following this entry will indicate the session are reestablished and the devices are available ID of the target that lost the connection for I O There wil
89. ed default for Disabled If TCP offload is enabled the Connection Windows 2008 Enabled device offloads the entire TCP Offload IPv4 Enabled default for protocol including ACK Windows 2008 R2 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 IPSEC 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 TCP Enabled Disabled Enable disable for TCP Connection Enabled Connection Offload Offload IPv6 UDP RX and TX Enabled Disabled User Datagram Protocol UDP Checksum RX and TX Enabled offload checksum settings offload Offload IPv4 RX Enabled the transmit and or receive IPv4 TX Enabled UDP checksum computation Offloading checksums increases system efficiency UDP RX and TX Enabled Disable User Datagram Protocol UDP Checksum RX and TX Enabled offload
90. eeeeeeeeeeeeeeeeeeeeeeteeeeteteas 76 ELS Log Messages 0100 0130 cc ccceceeeeeeeeeeeeeeeeeeeeeeeeetcaeeeeeeeeeeaaaes 76 Discovery Log Messages 0202 0262 ceceeecccecceeteeeeeeeeeeeeeeeeeeeeeeeteess 78 Mailbox Log Messages 0310 0326 oo ce eeeeeteeeeteeetttttetttaaaaaeeeeeees 80 INIT Log Messages 0400 04638 eeessseseeeeeeeeeeenceeeeeeeeeeeeeeeeeeeeeeetees 81 FCP Log Messages 0701 0749 ecccccceceeeceeccteeeeeeeeeeeeeecteeeeeeeeeteennaaes 82 Link Log Messages 1302 1306 cc eeeeeeeeeeeeeeeetttttttttettttteaaaaaeaaaaaea 84 Tag Messages 1400 1401 eeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteeeenes 85 NPIV Messages 1800 1899 cccccceeeeeeeeeeeeeeeeeeeeeeeeeeaaaaeeeeeeeeeesaaaaaees 85 ELS Messages 1900 1999 ceeecccceeeeeeeeeeeeeeeceeeeeeeeeeeeeeecaaeeeeeeseeaaaes 86 Troubleshooting the NIC and TCP Offload Drivers ecceeeeeeeeeeeeteeeeeeeeeeeees 87 Troubleshooting the iSCSI Driver cc cccceeeeeeeeeeeeeeeeeeeeeeeeecaeeeeeeeeeesecsnneeeeeees 89 Appendix A Error Event Log Information cccccccccccceeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneteeeeetenegs 92 FC FCoE Error Event LOQS cccccceceeeeecceeeeeeeeeeeeeccaeeeeeeeeeseecaaeeeeeeeeeteeesaeeeeeees 92 Viewing the FC FCoE Error Log 2 ceeeeeeeeeeeeeeencaeeeeeeeeeeeeceaaeeeeeeeeeeeeenaaaes 92 Severity SCHEME ccccccececeeeeeccneeeeeeeeeeeeenaaeeeeeeeeeseeeaaeeeeeeeeeseenen
91. eeeeeeeeteeeeeees 20 Installing the Emulex PLUS ElxPlus Driver for the First Time 20 Updating the Emulex PLUS EIxPlus Driver cecccceceseeeeeeeeeeeeeenaees 21 Installing or Updating the FC Storport Miniport Driver 21 Installing or Updating the iSCSI Driver ccccecccecseeeeeeeeeeeeeeeeeeneeeeees 22 Installing or Updating the NIC Driver ccccccceeceeeeeeeeeneeeeeeeeeeeeeeeeneeeeees 23 OTT ats te FE 1 Cs meceae decades terete eee ee elect ee ee eee rere cece eee ee 25 Uninstalling Emulex Driver KitS cc ccceesesecseeeeeeeeeeeeeceeeaaaaeaaaaaaaaaaaaaaaaaaaeeeeeees 25 Uninstalling the Emulex Drivers cccccccccccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 25 Driver Configuration cceccceeeeeeeeeeeeeeeecceee seer ee eeeecaaaeeeeeeeeeeeeecaaaeeeeeeeeteeecdiaeeeeeeeeeenee 27 FC FCoE Driver Configuration cccccccccccceceeeeeeececneeeeeeeeeeeeeeeeeeccaeeeeeeeeeteeneeeeeees 27 Windows Server NIC TOE Driver Parameters cccccceceeeeeeeeeeeeeeeetneeeeeeeeeetees 27 Modifying Advanced Properties cccceeeceeeeeeeeeeeeeeeeeaaeaaeaaaaaaaaaaaaaaaaaaaeeeeeees 27 Configuring NIC TOE Driver Options eececceeceeeeeeeeeeeecneeeeeeeeeeeeesnaeeeeeees 29 Using OCCFG for Windows NIC TOE Driver OptionS cccceceeeseeeeeeees 43 Displaying OCCFG Help sicions anaa aa aaa aata 43 Selecting an Adapter cccccecececeeeeeee
92. eeeeeeeneeeeeeeeeeeeceaaeeeeeeeeeetecenaeeeeeees 44 Configuring Device Parameters cceeeceeeeeeeeeeeeeeeeceeeeeeeeeeeeeetnaeeeeeetees 44 Viewing Device Parameters 0 0 00 aan 45 Resetting All Parameters cccccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeess 46 Displaying All Parameters ccccccccecececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeetenegs 46 Using Interactive Mod ccicscstncstncstnennnenhnesecucecudedeshnestneshnennnethnesnnassananee ceenes 47 Pala Meret el Pia caoecpctcncaccencteacmetnadtnenemenenanetenctetenencnentenannanedensnentnentnarcscadted 47 Configuring iSCSI Driver Options 20 0 0 cccccececeee cette ee ee eeeeccaeeeeeeeeeeeeecaaeeeeeeeetteee 48 Interrupt Moderation Policy SettingS ccccecceeeeeeeeeeeeeeeeeeeeeeeeeecceeeeeeeeeeteee 49 Creating Non Bootable Targets cccecccceeeececeeeaeeeeeeeeeeeeceaneeeeeeeeeteeseaaaes 50 Using the Microsoft iSCSI Initiator Service cccceceeeeseeeeeteetsetttteeeeeeee 50 Logging into a Target Using the Microsoft Software Initiator 0 50 Windows Multipath I O Support cccccccceeeeeeeeeeeeeecneeeeeeeeeeeeeccaaeeeeeeseeeaaaes 50 Multipath Support on Windows Server 2008 ccccccccccccceceeeeeaasnteeeeeees 50 Multipath Support on Windows Server 2008 or 2008 R2 sssssseeeeees 51 Logging into Targets for Multipath SUPPOMt cceeeeeeeeeeceeeeeeeeeetaees 52 Server Perform
93. efore each adapter must be updated Select the Driver tab Click Update Driver The Update Driver wizard starts Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Select Install from a list or specific location Advanced and click Next Emulex Drivers for Windows User Manual Page 21 10 11 12 13 14 gt G EMULEX Select Don t search I will choose the driver to install and click Next Note Using the OEMSETUP IMF file to update Emulex s FC Storport Miniport driver overwrites customized driver settings If you are updating a previous installation write down the settings Following installation use the OneCommand Manager application to restore the previous settings Click Have Disk Direct the Device Wizard to the location of oemsetup inf If you have installed the driver installer kit to the default folder the path is C Program Files Emulex AutoPilot Installer Drivers Storport x86 HBA for the 32 bit driver version or C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA for the x64 driver version C Program Files Emulex AutoPilot Installer Drivers Storport l A64 HBA for the Itanium driver version Click OK Select Emulex LightPulse LPX000 PCI Slot X Storport Miniport Driver your adapter model is displayed here Click Next Click Finish The driver installation is complete The driver should start automatically If the adapter
94. endor Specific Option 43 eeccceeeeeeeeeeeeeeecneeeeeeeeeeseenneeees 116 Description of Mandatory and Optional Parameters ceceeeeeeees 116 EXAM PICS issictstessreiiisiensashsisnstsbandiahensanneiectavtatabsnsbinanennteastanstanghacstanantdeenss 117 Appendix C Port Speed Specifications 00 0 cece eeeeneeeeeeeneeeeeenaeeeeeeseeeneaas 119 Negotiating Speed on a Mezzanine Card ccccccccceceeecececeeeeeeeeeeeeeeteeeeeeeeeenaaees 119 Emulex Drivers for Windows User Manual Page vi gt G EMULEX Installation Introduction AutoPilot Installer AutoPilot Installer for Emulex Storport Miniport and Network Driver Interface Specification 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 AutoPilot Installer is included with Emulex drivers and utilities in Windows executable files kit installers that you can download from the Emulex website There are three types of driver kits e Fibre Channel FC driver package elxdrvr fc lt version gt exe Fibre Channel over Ethernet FCoE driver package elxdrvr fcoe lt version gt exe e Internet Small Computer System Interface iSCSI driver package elxdrvr iscsi lt version gt exe e Network Interface Card NIC driver package elxdrvr nic lt version gt exe Each driver kit contains x86 x64 and IA64 Fibre Channe
95. ent variable is not terminated with a slash so you must provide one in the string Windows environment variables are not case sensitive Emulex Drivers for Windows User Manual Page 14 gt G EMULEX Configuration Identification AUTOPILOT ID This section appears at the beginning of every AutoPilot configuration file and contains revision and label information The revision entry identifies the file s version number and the date on which it was produced The label entry is used to identify the configuration that the file supports This section may appear only once in the APInstall cfg file Software Configuration AUTOPILOT CONFIG This section can contain settings that control and configure AutoPilot Installer and the OneCommand Manager application operation This section can appear only once in the AutoPilot configuration file See Software Configuration Parameters on page 12 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
96. entially 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 Max Segment Size MSS the driver like most TCP stacks uses a Nagling algorithm Nagling reduces the number of TCP packets on the network by combining small application sends into one larger TCP packet Nagling typically reduces the performance of a single connection to allow greater overall performance for a large group of connections During Nagling a single connection may have long pauses 200 ms between sending subsequent packets as the driver waits for more data from the application to append to the packet An application can disable Nagling using the TCP_NO_DELAY parameter TCP offload does not improve the performance for connections that Nagle because the performance is intentionally limited by the Nagling algorithm Telnet and SSH consoles are examples of connections that typically use Nagling 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 offl
97. entication is done SEVERITY Information LOG LOG_FCSP verbose ACTION No action needed informational gt E EMULEX 1905 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 Emulex Drivers for Windows User Manual Page 86 gt G EMULEX Troubleshooting the NIC and TCP Offload Drivers The following table provides troubleshooting information for the NIC and TCP offload drivers Table 15 Troubleshooting the NIC and TCP Offload Drivers Problem Answer Solution Performance is not as expected The UCNA may be installed in a PCle slot other than an 8x PCle slot or a Gen2 slot Verify that the UCNA has been properly installed and that the system is properly set for 8x Gen2 PCle operation If TOE is enabled and performance is not as high as expected the operating system may not offload TOE connections For more information see Improving Performance with TCP Offload on page 54 There are frequent event log entries for link changes or statistics that show more than expected CRC errors Unload and reload the driver to reset available target IDs Ensure that the SAN configuration is correct prior to reloading the driver This clears the driver s consistent binding table and frees target IDs for new target nodes The driver fails to load and an e
98. entory is recorded Note If you cancel AutoPilot Installer that fact is recorded along with when you cancelled the installation The contents of any error dialogs that are displayed are also recorded Command Script Example Modify the configuration file to script the installation of a system s driver The following example command script batch file assumes that you have made mandatory changes to the AutoPilot configuration file as well as any desired optional changes If your systems were set up with a service that supports remote execution then you can create a command script to remotely update drivers for all of the systems on the storage net If Microsoft s Remote Command Service RCMD service was installed for example a script similar to the following would run remote execution remd serverl g autopilot x86_full_kit apinstall if errorlevel 1 goto serverlok echo AutoPilot reported an error upgrading Server 1 if not errorlevel 2147483650 goto unsupported echo Configuration file missing goto serverlok unsupported if not errorlevel 2147483649 goto older echo Unsupported operating system detected older if not errorlevel 2001 goto none cho The driver found is the same or older than the existing driver goto serverlok none Emulex Drivers for Windows User Manual Page 18 w mM EMULEX if not errorlevel 1248 goto noreport echo No Emulex adapter found goto serverlok snoreport if not error
99. eportLocation x autopilot reports installs Emulex Drivers for Windows User Manual Page 13 gt G EMULEX 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 SilentIinstallEnable 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 Microsoft s Quick Fix Engineering updates QFEs also known as KB Knowledge Base updates based on the checks you have specified in the STORPORT QFES section By default the installation terminates if the QFE check fails To enable a
100. er setting is parameter_name Jvalue Double quotes are required only around values that contain spaces Spaces may separate parameters equal signs and values Parameter names and values are not case sensitive The APInstall command may contain the settings listed below Each setting except ConfigFileLocation may also be specified in the AutoPilot Configuration file For descriptions of each parameter see Software Configuration Parameters on page 12 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 Emulex Drivers for Windows User Manual Page 11 gt G EMULEX Path Specifiers Paths may be specified as e an explicit path ReportLocation C Program Files Emulex AutoPilot Installer Reports a relative path LocalDriverLocation Drivers Storport Miniport assuming installation into C Program Files Emulex AutoPilot Installer this path would logi cally become C Program Files Emulex AutoPilot Installer Driver
101. erify 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 device incorrect hardware device Verify that the correct driver is installed 0x0010 16 Warning The network driver was reset This may indicate a system hang or hardware problem Verify other system devices are working properly 0x0009 Error Failed to register interrupt service This is an NDIS error Verify that routine hardware resource conflicts do not exist 0x0008 8 Error Failed to get TCP offload This is an NDIS error Verify the handlers NDIS version is valid for the driver 0x0007 7 Warning A memory allocation failure This warning occurred due to a occurred during driver load failed memory allocation Check Performance may be reduced low memory conditions Use a smaller MTU or disable TCP offload to reduce driver memory requirements 0x0006 6 Error Driver load failed due to memory This failure occurred due to a allocation failure failed memory allocation in the driver Check low memory conditions Emulex Drivers for Windows User Manual Page 105 gt G EMULEX Table 28 NIC TOE Event Log Entries Continued Message ID Hexadecimal Severity Message Recommended Resolution Decimal 0x0005 5 Error Failed to register scatter gather This failure occurred due to a DMA failed memory allocation in the operating system Check low memory con
102. ers Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol LimTransferSize Limits maximum transfer size when non zero to selectable values Values 0 Port Default 1 64Kb 2 128 Kb 3 256Kb Reboot LinkSpeed n LinkSpeed has significance only if the adapter 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 Reset FC Only LinkTimeOut n LinkTimeOut applies to a private loop only A 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 OxFE hex Default 30 0x1E Dynamic Emulex Drivers for Windows User Manual Page 71 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol LogErrors n LogErrors determine the minimum severity level 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 inte
103. ese types of events are referring to the internal memory constructs of the Emulex Storport Miniport driver and as such are intended for Emulex design engineer s information If a customer encounters such an event they should contact Emulex support for analysis and determination if that particular event may be an indicator of a failed adapter or of some problem with interaction between the adapter the Emulex Storport Miniport driver the host operating system and the host memory Note Context allocation failures are rare NIC Error 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 Click Run Type eventvwr and click OK Click Windows Log oe a Click System 6 Click the be2net error under System Events to show the event details The following is an example of a Windows Server 2003 error be2ndis6x you would see in the system event log Emulex Drivers for Windows User Manual Page 101 gt G EMULEX asasi TELE LT SERVEREN SERVEREN SEESESESESSE SESS ELE ee ji i W S GSRSER EET SE Foes s Figure 5 Windows Server 2003 NIC Errors Emulex Drivers for Windows User Manual Page 102 Viewing the NIC TOE Event Log gt
104. fied 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 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 Thus you cannot check the exit code of the installer before the next command is executed Emulex recommends that for command line invocation always use the start command with the wait option This causes the command processor to wait for the installer to finish before it continues Running a Software Installation Interactively There are two options when performing an installation interactively These options assume you have already downloaded the driver kit installer from the Emulex website Option 1 Automatically Run AutoPilot Installer Use this option unless you have specific configuration needs This option allows you to com
105. g disables all delays to minimize latency The Minimal Static uses a constant interrupt delay to avoid any spikes in interrupt rate The adaptive settings cause the driver to dynamically maintain a target interrupt rate If CPU usage is too high choose a higher adaptive value to increase the interrupt delays and reduce the rate of interrupts Emulex Drivers for Windows User Manual Page 30 Table 2 Windows Server 2003 Driver Options Continued gt G EMULEX Option Name Default Value Acceptable Values Definition IP Checksum Offload IPv4 RX and TX Enabled Disabled RX and TX Enabled RX Enabled TX Enabled This offloads the transmit and or receive IPv4 checksum computation Offloading checksums increases system efficiency Large Send Offload LSO v1 IPv4 Enabled Disabled Enabled 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 Network Address None Valid MAC Address This overrides the permanent MAC address for the interface The MAC address should follow this format XX XX XX XX XX XX where X
106. g its device queue CoalesceMsCnt CoalesceMsCnt defaults to zero If you are using a performance evaluation tool such as IOMETER and if you expect the I O activity to be greater than 8000 I Os per second set CoalesceMsCnt to 1 and reinitialized with an adapter reset or system reboot CoalesceRspCnt CoalesceRspCnt defaults to 8 For all other values up to the maximum of 63 the adapter does not interrupt the host with a completion until either CoalesceMsCnt milliseconds has elapsed or CoalesceRspCnt responses are pending The value 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 Performance Testing Examples Test Scenario One 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 Recommendation set CoalesceMsCnt to 0 or leave the default value Test Scenario Two You execute IOMETER with an I O depth of 48 I Os per device in a small scale configuration 16 devices Recommendation set QueueDepth to be greater than 48 e g 64 Emulex Drivers for Windows User Manual Page 53 gt G EMULEX Network Driver Perform
107. 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 Describ the topology of your storage network Note Select Arbitrated Loop when directly connected to the array no fibre switch Select Point to Point when connected to a SAN fibre switch Arbitrated Loop Point to Point ANSWER 0 DriverParameter Topology 2 ANSWER 1 DriverParameter Topology 3 ENDQUESTIONS END STORPORT CONFIGURATION QFE Checks STORPORT QFES This section specifies an additional Quick Fix Engineering QFE check also known as KB Knowledge Base updates during 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
108. hang In the case of a hang there could be a message indicating that the driver experienced a hardware malfunction There are several possible causes for this problem 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 is enabled and should not be To query this system driver s run state log in as administrator and at the command line type sc query intelppm If the results indicate that the intelppm driver is running you must disable it At the command line type sc config intelppm start disabled On all systems it may be necessary to set the power options to High Performance See the operating system documentation for details Emulex Drivers for Windows User Manual Page 88 gt G EMULEX Troubleshooting the iSCSI Driver The following table provides troubleshooting information for the iSCSI driver Table 16 Troubleshooting the iSCSI Driver Problem Answer Solution Overall failure Use the iSCSISelect utility to clear the Adapter Configuration
109. he driver installer kit to the default folder the path is C Program Files Emulex AutoPilot Installer Drivers NDIS x86 NIC Windows Version for the 32 bit driver version or C Program Files Emulex AutoPilot Installer Drivers NDIS x64 NIC Windows Version for the x64 driver version or C Program Files Emulex AutoPilot Installer Drivers NDIS IA64 NIC Windows Version for the Itanium driver version Emulex Drivers for Windows User Manual Page 23 12 13 14 gt G EMULEX Click OK Select Emulex OneConnect OCeXXXXX NIC TOE your adapter model is displayed here Click Next Click Finish The driver installation is complete The driver should start automatically Windows 2008 AE ee Or Ne 10 11 12 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 DC adapter models are displayed in the Device Manager as two adapters therefore you must update each adapter Click Let me pick from a list of device drivers on my computer and click Next Select the network adapter that matches your hardware and click Have Disk Direct the Device Wizard to the lo
110. he shell command netsh int ip set 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 TCP offload requires Windows 2003 SP2 View the Statistics property page to ensure that TCP connection offload is working Emulex Drivers for Windows User Manual Page 33 Table 2 Windows Server 2003 Driver Options Continued gt G EMULEX Option Name Default Value Acceptable Values Definition TCP Offload Optimization Optimize Throughput Optimize Latency Optimize Throughput 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 256 64 through 256 inclusive 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 UDP Checksum Offload
111. id in bits 8 31 OxE5 LS_RuT other than Logical Busy received for Authentication transaction remote Did in bits 8 31 OxE6 LS _RuT 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 Emulex Drivers for Windows User Manual Page 96 gt G EMULEX Table 20 Event Indications Continued Bits 0 7 Interpretation 0x18 Port shutdown event LightPulse OxEA Authentication spurious traffic remote Did in bits 8 31 OxEB Authentication policy has been changed remote Did in bits 8 31 OxED 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 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 ty
112. ilure in the This failure indicates that the hardware has not hardware during initialization This error may been initialized or is malfunctioning This may be followed by error codes 0x31840001 or also indicate that the firmware is not running 0x31880001 indicating that the iSCSI driver correctly failed to load 0x11800005 Both Port 0 and Port 1 links were down fora Check the links to the UCNA If the link is period exceeding the Link Down Timeout reestablished any sessions that previously LDTO If the UCNA has connection to the existed are reestablished and the devices is target there will be event log entries from the available for I O disk subsystem indicating that the drives were lost If any I Os were in progress the system may see 1 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 Vendor ID Check the configuration on the UCNA and Device ID are not supported 0x1180000A The logical link on the OneConnect Port is The iSCSI function may have been disabled in down traffic is disallowed on this function the PXESelect application If you disabled it intentionally you can ignore this message Viewing the iSCSI Error Logs on Windows 2008 R2 The iSCSI driver on the Windows 2008 R2 operating system supports the new event logging mechanism introduced by Storport Custom event messages are logged for a variety of events w
113. 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 valid Emulex Drivers for Windows User Manual Page 31 Table 2 Windows Server 2003 Driver Options Continued gt G EMULEX Option Name Default Value Acceptable Values Definition Packet Size 1514 1514 9014 Configure packet size for OneConnect NIC only Limit normal sized frames and one value for jumbo packet This parameter determines the maximum packet size transmitted and received on the interface A 1514 byte frame size is standard while larger packets are called jumbo frames Using a higher frame size is generally more efficient but it uses more system memory A larger frame size also requires support on the network switch Receive Buffers 896 64 through 16384 inclusive This determines the number of Ethernet receive buffers allocated per receive queue If RSS is enabled 4 or more receive queues are used Otherwise a single queue is enabled Decreasing this value will reduce the required system memory but performance may decrease Each buffer is the size of the Packet Size parameter RSS Enabled Disabled Enabled Support for up to 4 RSS queues if enabled Receive Side Scaling RSS scales receive processing
114. is 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 DH CHAP Notice License Copyright c 1998 2006 The OpenSSL Project All rights reserved This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit http www openssl org SSLeay License Copyright C 1995 1998 Eric Young eay cryptsoft com All rights reserved This product includes cryptographic software written by Eric Young eay cryptsoft com This product includes software written by Tim Hudson tjh cryptsoft com Windows DH CHAP Notice Derived from the RSA Data Security Inc MD5 Message Digest Algorithm Copyright C 1991 2 RSA Data Security Inc Created 1991 All rights reserved US patent notice is given for one or more of the following 6226680 6247060 6334153 6389479 6393487 6427171 6427173 6434620 6591302 6658480 6697868 6751665 6757746 6941386 6965941 6687758 7042898 7133940 7124205 7089326 6938092 6996070 Emulex 3333 Susan Street Costa Mesa CA 92626 Emulex Drivers for Windows User Manual Page ii MVS Cea TNO NN 5 ce ee acs crn nea necro cs nena eco en nen ets mee es cea ee eee ee 1 W
115. is 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 Storport Miniport Driver Parameters on page 66 for a listing of driver parameters defaults and valid values Setting Up System Parameters SYSTEM PARAMS To change the system parameters create a SYSTEM PARAMS section in the APInstall cfg file Create this section under the Optional Configuration File Changes heading in the AUTOPILOT CONFIG section For example you can adjust the operating system s global disk timeout The timeout is stored in the registry under the key HKML CurrentControlSet Services disk and is specified with the following string TimeOutValue 0x3C where the number is the timeout value in seconds 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 1 Unattended Installation Error Codes Error Code Hex Description 0 0x00000000 No errors 2399141889 0x8F000001 Unsupported operating system detected 2399141890 0x8F000002 The AutoPilot Configuration file is not found
116. ith 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 30 iSCSI Error Log Entries on Windows Server 2008 R2 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 Emulex Drivers for Windows User Manual Page 110 gt G EMULEX Table 30 iSCSI Error Log Entries on Windows Server 2008 R2 Continued Message ID Severity Message Recommended Resolution 0x07 Error Link down timeout expired on the port all targets are lost The link on the UCNA is down for a period exceeding the link down timeout LDTO value If the UCNA has a connection to the target event log entries from the disk subsystem indicate that the drives were lost If any I O was in progress the system may see I O errors or failures Check the links to the UCNA If the link is reestablished any sessions that previously existed are reestablished and the devices are available for I O 0x08 Error Target
117. itiator name is already configured e Header digest Enabled e Data digest Not specified assume disabled e Authentication type One way CHAP Emulex Drivers for Windows User Manual E i1gn 2009 4 com 1234567890 E E Page 117 gt G EMULEX The following is an example of default TCP port and mutual CHAP settings iscsi 192 168 0 2 000000000000000E iqn 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 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 Page 118 gt G EMULEX 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 32 lists negotiated speed specifications per an adapter s port connecti
118. iver Windows Server NIC TOE Driver Parameters The Windows Server NIC TOE drivers support driver options through the Advanced Property page in Windows Device Manager Note Although TOE is supported it is turned off by default 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 54 To modify the advanced properties 1 Enter the Windows Device Manager by e Clicking Start gt Control Panel gt System and click the Device Manager hyperlink or e Clicking Start gt Run then type devmgmt msc and click OK Emulex Drivers for Windows User Manual Page 27 gt G EMULEX The Windows Device Manager is displayed E Server Manager File Action View Hep Cm IDE ATA ATAPI controllers B Keyboards O Mice and other pointing devices mA Monitors AP Network adapters Ti Emulex OneConnect OCe 11102 I NIC TOE 10 amp Emulex OneConnect OCe11102 I NIC TOE 9 F Ports COM amp LPT Sj Dp Processors E lt Storage controllers lt gt Dell SAS 6 R Integrated Controller lt gt Emulex OneConnect OCe 11102 1 iSCSI Initiator lt Emulex OneConnect OCe 11102 1 iSCSI Initiator lt gt Microsoft iSCSI Initiator lt gt Microsoft Multi Path Bus Oriver gE System devices W Universal Serial Bus controlers Figure 2 Partial View of Windows Device Man
119. iver tab 4 Click Uninstall and click OK to uninstall Emulex Drivers for Windows User Manual Page 25 gt G EMULEX To uninstall the ElxPlus driver uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled 1 Run the Device Manager steps 1 and 2 above 2 Click the plus sign next to the Emulex PLUS driver class 3 Right click the Emulex driver and click Uninstall 4 Click OK in the Confirm Device Removal window 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 Emulex Drivers for Windows User Manual Page 26 gt G EMULEX Driver 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 the OneCommand Manager Application User Manual for information on using this utility to configure the dr
120. ivers for Windows User Manual Page 111 gt G EMULEX Table 30 iSCSI Error Log Entries on Windows Server 2008 R2 Continued Message ID Severity Message Recommended Resolution 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 Check for software updates at the target vendor s website If applicable update the software e Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware OxOf Warning The iSCSI target on session id N failed to open the command window within configured timeout The iSCSI driver did not receive an iSCSI command window update for up to 25 seconds during I O operations The event log entry indicates the session handle on which the error occurred The iSCSI driver triggers a session recovery on the session and continues e Verify that the iSCSI target is certified by Microsoft Check for errors reported at the target The Emulex iSCSI UCNA is only supported with certified targets Check for software updates at the target vendor s website If applicable update
121. l FC drivers and installs the correct files on a per system basis Run one of the driver kit installers to extract the software needed for the driver installation 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 Text Only installation Text based installation mode is used automatically when AutoPilot Installer is run on a Server Core system Network installation You can place the driver kit installers on a shared network drive and install them across your local area network LAN Network based installation is often used in conjunction with unattended installation and scripting This allows you to configure and install the same driver version on all the hosts in a storage area network SAN Unattended installation You can run the driver kit installers and AutoPilot installer with no user interaction from a command line or script Unattended installation works for both hardware first and software first installations and all driver kit
122. l be event log entries from the disk subsystem indicating that the drives were lost If any I Os were in progress the system may see I O errors or failures 0x11990007 The iSCSI driver received a Task The operating system version is not supported Management Function TMF that is not supported and rejected this 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 present target Check network connectivity to the target with the driver 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 mismatched This failure indicates that the driver version that version of the firmware running on the board This error may be followed by error codes 0x31840001 or 0x31880001 indicating that the iSCSI driver failed to load Emulex Drivers for Windows User Manual is running on the system does not match the version of the firmware on the board Correct this by running the installer from the desired version Page 109 gt G EMULEX Table 29 iSCSI Error Log Entries on Windows Server 2003 and 2008 Continued Message ID Message Description Recommended Resolution 0x11840001 The iSCSI driver detected a fa
123. ld 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 iSCSI targets On the iSCSI target system LUNs can be numbered sequentially they do not have to start at zero Emulex Drivers for Windows User Manual Page 91 gt G EMULEX Appendix A Error Event Log Information FC FCoE Error 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 on My Computer Manage and Event Viewer in Computer Management The Event Viewer window is displayed Double click any event with the source name ELXSTOR 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 4 byte 0010 9b byte 0011 00 byte 0012 29 and byte 0013 00 Event Properties Event Date Ure Sowce elxstor Time amp 52 19PM Categoy None ps Type Eror Event ID 11 _ User NZA Computer EMULEX D4C6E58E Description The de
124. le column Duplicate disks for multiple logins to the target should not appear if you run Disk Manager To run Disk Manager click Start gt Run and run diskmgmt msc You can configure load balancing policies on the LUN from the Device Manager after you click on the disk and select the MPIO tab Multipath Support on Windows Server 2008 or 2008 R2 On Windows Server 2008 or 2008 R2 MPIO must be installed from the Server Manager After installing the MPIO function you must launch and configure the MPIO GUI to enable multipath support for iSCSI devices The following steps describe the installation process for setting up Microsoft iSCSI DSM and enabling multipath I O for all iSCSI devices irrespective of their vendor and device IDs You can use the MPIO GUI to configure DSMs other than Microsoft iSCSI DSM Also you can use the GUI to enable multipath support for a specific vendor ID and device ID For details on these topics refer to the Microsoft TechNet Library on the Microsoft website 1 To configure the iSCSI drivers to fail over to an alternate path as quickly as possible edit the Driver Parameters for the iSCSli service in the registry Locate the key HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters and set eto 0 Ildto 0 2 Reboot the system for the registry changes to take effect 3 Log into the iSCSI target using WMI For more information see Logging into Targets for Multipath Support
125. level 110 goto nocfg echo Could not open installation report file goto serverlok nocfg if not errorlevel 87 goto badcfg echo Invalid configuration file parameters goto serverlok badcfg if not errorlevel 2 goto serverlok echo No appropriate driver found serverlok remd server2 g autopilot ApInstall ConfigFileLocation g autopilot mysetup apin stall 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 cho The driver found is the same or older than the existing driver goto server2ok none2 if not errorlevel 1248 goto noreport2 echo No adapter found goto server2ok snoreport if not errorlevel 110 goto nocfg2 echo Could not open installation report file goto server2ok nocfg2 if not errorlevel 87 goto badcfg2 echo Invalid configuration file parameters goto server2ok badcfg2 if not errorlevel 2 goto server2ok echo No appropriate driver found server2ok Emulex Drivers for Windows User Manual Page 19 gt G EMULEX Manual Installation and Updating Procedures Manually Installing or Updating the Emulex Protocol Drivers Overview You can install or update the Emulex protocol drivers and utilities manually without using AutoPilot Installer Th
126. lex 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 Emulex Drivers for Windows User Manual Page 45 gt E EMULEX 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 T 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 All Parameters To display the current value of all parameters use either p o
127. lse Only Emulex Drivers for Windows User Manual Page 73 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX internal driver trace buffer The internal driver trace buffer acts as an internal log of the driver s activity Value 250 000 2 000 000 or 0x3D090 0x1E8480 hex Default 250 000 0x3D090 Parameter Definitions Activation Adapter Requirement Protocol SrbTimeout SrbTimeout limits the SRB timeout value to 60 seconds when set to 1 or enabled This is a non displayed parameter where it has to be set manually into the registry This option alters the I O timeout behavior where an I O will be returned in a max timeout of 60 seconds on some long I O timeout If set to 1 enabled If set to 0 disabled Values 0 1 Default 0 Topology n Topology values can be 0 to 3 Reset FC Only If set to 0 0x0 FC Arbitrated Loop FC AL If set to 1 0x1 PT PT fabric If set to 2 0x2 FC AL first then attempt PT PT If set to 3 0x3 PT PT fabric first then attempt FC AL Topology fail over requires v3 20 firmware or higher If firmware does not support topology fail over options 0 2 and 1 3 are analogous Value 0 3 Default 2 0x2 TraceBufSiz n TraceBufSiz sets the size in bytes for the Reboot Emulex Drivers for Windows User Manual Page 74 Troubleshooting gt G EMULEX There are several circumstances in which your system may operate in an
128. lt 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 iSCS Select will be overridden and the new IQN name will be in effect Although this will not affect existing boot sessions and persistent sessions new target logins could fail because the new IQN name does not match the incoming IQN name configured on the target After the Microsoft iSCSI Initiator Service is installed the initiator name must be renamed to the previous name configured from the WMI GUI 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 e A SAS controller is present on the system 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 fie
129. lt 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 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 User Priority This mode allows any user specified priority value and should be limited to cases where storage functions are not used e Disable Priority The adapter always transmits either untagged packets or VLAN ID 802 1q tagged packets with a priority value 802 1p of zero Emulex Drivers for Windows User Manual Page 35 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition Flow Control RX and TX Enabled Disabled RX and TX Enabled Rx Enable Tx Disable Tx Enable Rx Disable Flow control is almost always advantageous to avoid packet drops on the network The switch or network peer must als
130. n 4 Loading the Onelnstall Package cccccceeeeeeecceeeeeeeeeeeeeeccaeeeeeeeeeesesenneeeeeess 4 Driver Kit Installer Overview ccccccceeeeececneeeeeeeeeeeeecaaeeeeeeeeeeeeecaaeeeeeeeeesecccaeeeeeees 5 Installing the Driver Kit 2 0 ccceeeee eee ee eee eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeas 5 Text Only Driver Installation ccccecceseeceeeeeeeeecceeeeeeeeeeeeecaaaeeeeeeeeseeeeneaeeeeeees 5 AutoPilot Installer OVe rvVieW ccceeeeeeeeeeeeee cece eeceee settee eeeeecaaaeeeeeeeeteeeeaaaaaaeeeeetnee 6 Starting Installers from a Command Prompt or Script ceeeeeeeeeeeeeeeeeees 6 Running a Software Installation Interactively c ccceeeeeeeeeeeeeeetneeeeeeeeenaees 6 Hardware First Installation or Driver Update ccccceeeccceeeeeeeeeeeaaaaaaaaaeeeeeeeees 7 Software First Installation ccccecccceccseeeeeeeeeeeeecneeeeeeeeeeseeecaaeeeeeeeeeeeseneeeeeeees 8 Diagnostics If the Installation Fails 2 2 eee ee cece eee eeeeeeeeeeeeeeeeeeeeeeeeeeeeees 9 Performing an Unattended Driver Installation 0 0 0 0 eee 9 AutoPilot Installer Process in Unattended Installation Mode 10 AutoPilot Installer Command Line and Configuration File Parameters 10 The AParg Driver Kit Parameter and Appending to the APInstall exe File 10 AutoPilot Installer Syntax cccceceeeeeeeeeeeeeceeeeeeeeeeeeaaaaaeeeeeeeeeeeeecaaeeeeeeseenaaaes 11 Path SPECIET S aa e ttre e
131. 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 1 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 2 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 emu
132. ndor s iSCSI DSM documentation for installation details The following steps describe the installation process for setting up multipath support using Microsoft iSCSI Software Initiator 1 To configure the iSCSI drivers to fail over to an alternate path as quickly as possible edit the Driver Parameters for the iSCSI service in the registry Locate the key HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters and set eto 0 ldto 0 Emulex Drivers for Windows User Manual Page 50 gt G EMULEX Reboot the system for the registry changes to take effect Download the latest version of Microsoft iSCSI Software Initiator from the Microsoft website Download the 32 bit or 64 bit version of this software depending on the Windows 2003 Server version 4 Install the Microsoft iSCSI Software Initiator During installation you must select the Microsoft iSCSI Initiator check box 5 When the installation is finished reboot the system if you are prompted to do so 6 Open the Device Manager and confirm that Multi Path Support is present under the SCSI and RAID controllers The MPIO software installation is now complete 7 Log into the iSCSI target using the Windows Management Instrumentation WMI For more information see Logging into Targets for Multipath Support on page 52 After the login is complete the devices LUN that are available with the target show Multi Path Support under the MPIO Capab
133. nformation After editing the file you can run the AutoPilot Installer from the Start menu a command prompt or a script Emulex Drivers for Windows User Manual Page 9 gt G EMULEX AutoPilot Installer Process in Unattended Installation Mode When in unattended installation mode AutoPilot Installer does the following e Reads the configuration file e Reads any options that may be specified on the 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 f appropriate verifies that the selected driver is a different type than the currently installed driver or a more recent version of the currently installed driver Copies the driver parameters from the configuration file into the registry for the driver s coinstaller FC and FCoE drivers only e Installs or updates the driver e Rediscovers adapters and records the updated adapter inventory in the report file e Records the final results and closes the report file AutoPilot Installer Command Line and Configuration File Parameters You can pass command line parameters to the AutoPilot Installer yet still have it run automatically by the driver kit if you
134. ng the installation process In this case answer each question and click Next on each window to continue 4 Click Next The installation automatically completes A dialog box is displayed if Windows requires a reboot Once the installation is successful a Finish page appears 5 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory configuration information and task results 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 beginning on page 6 The following message appears S AutoPilot Installer Warning a xj AutoPilot Installer cannot find any Emulex Fibre Channel HBAs in this system AutoPilot Installer can perform a driver pre installation allowing you to install your HBAs later Click OK to pre instal drivers or click Cancel t
135. ng wrong with the connection of that device to the SAN cables switches or switch ports status of the target device itself SCSI Command Error 0x9A and SCSI Check Condition code 0x9B Code 0x9A indicates that the SCSI command to a particular device was responded to with an error condition the target and LUN information along with the SCSI status are provided In the specific case of code 0x9B this code indicates that the device 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 in a 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 Emulex Drivers for Windows User Manual Page 100 gt G EMULEX Context Allocation Failures There are a number of event codes for which the interpretation contains the phrase context allocation failure th
136. nnections to be offloaded by the Windows Server 2003 Windows Server 2008 and Windows Server 2008 R2 network stack By default Windows Firewall Services are enabled at operating system installation time and they must be explicitly disabled in order to use TOE Firewall services can be disabled through the Service Control panel or the following commands at the command line prompt e To set firewall services to load on demand manual sc config MpsSvc start demand e To stop firewall services Net stop MpsSvc e 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 TCP Offload Performance 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 hardwa
137. o have flow control enabled The IEEE 802 3x Ethernet specification defines a control frame between peers that can request a pause in packet transmissions This allows one system to request a temporary halt of all incoming traffic when receive buffer space is exhausted The network device may be configured to respond to pause frames Rx Enable and or to send pause frames Tx Enable Interrupt Moderation Default Adaptive Aggressive Adaptive Default Adaptive Minimal Adaptive Minimal Static None The network device uses interrupt moderation algorithms to reduce the total amount of CPU cycles spent processing interrupts which increases efficiency for the system However interrupt moderation increases the latency of each send and receive It should only be disabled when short latencies are more important than efficient CPU utilization The None setting disables all delays to minimize latency The Minimal Static uses a constant interrupt delay to avoid any spikes in interrupt rate The adaptive settings cause the driver to dynamically maintain a target interrupt rate If CPU usage is too high choose a higher adaptive value to increase the interrupt delays and reduce the rate of interrupts Emulex Drivers for Windows User Manual Page 36 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value A
138. o stop the installation Figure 1 AutoPilot Installer Warning Software First Installation 2 Click OK A Welcome page appears 3 Click Next The installation automatically progresses Once the installation is completed successfully a Finish Page appears 4 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory 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 Emulex Drivers for Windows User Manual Page 8 gt G EMULEX Diagnostics If the Installation Fails If the installation fails the Diagnostics window opens showing that the adapter failed If the adapter fails 1 Select the adapter to view the reason for the failure The reason and suggested corrective action are displayed 2 Perform the suggested corrective action and run AutoPilot Installer again Note You can run AutoPilot Installer again from the Start menu Programs gt Emulex gt AutoPilot Installer or you can run APInstall exe from a command prompt Performing an Unattended Driver Installation An unattended driver installation sometimes referred to as a quiet or silent installation requires no user input This is useful for performing an installation remotely from a command script or when
139. oad 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 Windows TCP Parameters Emulex does not recommend modifying the TCP registry parameters such as TcpAckFrequency provided by Microsoft The default parameters are suitable for a wide variety of situations with or without using TCP offloading Receive Window Auto Tuning and Compound TCP Windows Server adds several features to the host TCP stack such as receive window auto tuning and Compound TCP CTCP These features affect only non offloaded TCP traffic Performance of some 10 Gb s stress applications may suffer with these features enabled In particular Emulex has seen some bi directional data stream test performance degradation when receive window auto tuning is enabled This is due to increased receive performance that adversely affects the same TCP connection s transmit performance To disable these features type these commands at the command line netsh interface tcp set global autotuning disabled
140. oes not include the Ethernet frame header or the trailing CRC The standard MTU is 1500 bytes corresponding to a 1514 byte packet size plus a 4 byte trailing CRC Historically any 1514 byte frame is a standard packet while any frame larger than 1514 bytes is called a jumbo packet Windows Server attempts to standardize the terminology across vendors so the jumbo packet parameter refers to the byte size of the packet The Windows Server driver supports 1514 byte 4088 byte and 9014 byte 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 27 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
141. 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 link down timeout LDTO e Loss of connection to the target because of target or network disconnection at the target If the driver has I O requests pending with the target and the target becomes unavailable because the target is down has failed over or network issues are detected at the target the driver queues the I O request internally up to a configured timeout period This timeout period is known as extended timeout ETO If the configured threshold for LDTO and ETO is reached and the UCNA is still unable to connect to the target the driver fails all I O requests I O errors are seen by the application and operating system Note Following a link up switch ports can take a long time to initialize and go toa forwarding state Because of this add additional time to the ETO and LDTO settings to eliminate I O disruption or target unavailability If the switch port is connected to a single host then P
142. on Table 32 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 Page 119
143. onal Network device is operating in For best performance install the Gen2 mode and installed in a 4x UCNA in an 8x Gen2 PCle slot PCI Express slot Note 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 PCI Express slot Note 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 PCI Express slot Note A 16x slot will not provide any additional performance 0x001e 30 Informational The network device is operating in For best performance install the Gen1 mode and installed in a 4x UCNA in an 8x Gen1 PCle slot PCI Express slot Note A 16x slot will not provide any additional performance 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 PCI Express slot Note 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 0x000d 13 Warning Windows 2003 Service Pack 2 is Windows Server 2003 Service required for RSS and TCP Pack 2 or higher is required for connection offload Receive Side Scaling and TCP
144. onding 0x18 LINK DOWN Queued cmds returned at link down 0x51A OUT OF ORDER DATA Possible bad cable or noise 0x1D SRB Status SCSI Request Block status provided by the driver to the operating system based upon response from SCSI device in the SAN Table 27 SRB Status Codes Explanation Code ERROR 0x04 BUSY 0x05 TIMEOUT 0x09 SELECTION TIMEOUT 0x0A Emulex Drivers for Windows User Manual Page 99 gt G EMULEX Table 27 SRB Status Codes Continued Explanation Code 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 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 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 somethi
145. only 128 targets can be discovered and mapped On a OneConnect adapter or an Emulex 16 Gb adapter a value of 0 limits max XRIs to 512 Use ConfigScale 0 to minimize the driver s per port memory foot print on any adapter model If set to 0 on a OneConnect adapter or an Emulex 16 Gb adapter the max transfer size is limited to 500 KB If set to 1 on a OneConnect adapter or an Emulex 16 Gb adapter the max transfer size is limited to 1012 KB If set to 2 the max transfer size is limited to 2036KB Use ConfigScale 2 if connecting to tape devices on a OneConnect or an Emulex 16 Gb port If set to 3 which is the best setting if you are running performance benchmarks in a non production environment the max transfer size is limited to 2036KB Values 0 1 2 and 3 Default 1 Emulex 16 Gb adapters Emulex Drivers for Windows User Manual Page 68 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol DiscoveryDelay n DiscoveryDelay controls whether the driver waits for n seconds to start port discovery after link up If set to 0 immediate discovery after link up If set to 1 or 2 the number of seconds to wait after link up before starting port discovery Value 0 2 seconds decimal Default 0 Dynamic DriverTraceMask The DriverTraceMask parameter is only available on operating systems
146. ontinued Option Name Default Value Acceptable Values Definition Large Send Offload LSO v2 IPv4 Enable Disable Enable 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 for IPv4 supports larger offload sizes Large Send Offload LSO v2 IPv6 Enabled Disabled Enabled Emulex Drivers for Windows User Manual 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 Page 38 gt G EMULEX Table 3 Windows Server 2008 and Windows Server 2008 R2 Driver Options Continued Option Name Default Value Acceptable Values Definition Network Address None Valid MAC Address This overrides the permanent MAC address for the interface The MAC address should follow this format XX
147. ontrol Protocol LACP when UMC is enabled Emulex Drivers for Windows User Manual Page 29 gt G EMULEX For more information on the options see Network Driver Performance Tuning on page 54 Table 2 Windows Server 2003 Driver Options Option Name Default Value Acceptable Values Definition Flow Control RX and TX Enabled Disabled RX and TX Enabled Rx Enable Tx Disabled Tx Enable Rx Disabled Flow control is almost always advantageous to avoid packet drops on the network The switch or network peer must also have flow control enabled The IEEE 802 3x Ethernet specification defines a control frame between peers that can request a pause in packet transmissions This allows one system to request a temporary halt of all incoming traffic when receive buffer space is exhausted The network device may be configured to respond to pause frames Rx Enable and or to send pause frames Tx Enable Interrupt Moderation Default Adaptive Aggressive Adaptive Default Adaptive Minimal Adaptive Minimal Static None The network device uses interrupt moderation algorithms to reduce the total amount of CPU cycles spent processing interrupts which increases efficiency for the system However interrupt moderation increases the latency of each send and receive It should only be disabled when short latencies are more important than efficient CPU utilization The None settin
148. ortFast mode can be enabled on the switch port to eliminate delays in transitioning to a forwarding state Configuring LDTO and ETO on Windows Server LDTO and ETO values are configured via the Windows registry Table 10 lists the default values of LDTO and ETO on Windows Server and the limits within which they can be configured Note If the ETO is set to a number between 0 and 19 the driver assumes the value to 20 seconds internally You will not see any modification to the registry Table 10 LDTO and ETO Information on Windows Server Value Default Minimum Maximum LDTO 20 sec 0 sec 3600 sec ETO 90 sec 0 sec 3600 sec To modify LDTO and ETO values edit the Driver Parameters for the iscsi service in the registry Locate the key HKLM System CurrentControlSet Services be2iscsi Parameters Device DriverParameters and edit the REG_SZ parameter to Idto 25 eto 50 This sets the default value of LDTO to 25 seconds and the default value of ETO to 50 seconds The settings are applied the next time the driver is loaded You must reboot the system boot drivers or disable the iSCSI driver and enable it again non boot drivers in Device Manager for the settings to take effect Emulex Drivers for Windows User Manual Page 64 gt G EMULEX 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 i
149. ows the driver generated error code in the fifth DWORD offset 0x10 of the word dump Note To improve the visibility of the error code in the Data field of the Event Properties window select the Words option Emulex Drivers for Windows User Manual Page 106 wW mM SG EMULEX zizjx Zj e edon yew Window tep 16 x e i O p ghB e E Computer Mansgemert Local on ati ergata E ig Syster Toots R Error mere IAI bedd teoa 1i KA SERVEREN SHES Event Viewer Qio LL30 11 30 23 bedent Neon WA SERVEREN 1 Application Girrens 1 19 2000 11 9 23 bedret teen 1 KWA SERVEREN Soosky Bweerieg MLIO 11 923 bedret None E KWA SERVEREN U Sytem Qie t1320 11 98 23 bedent toon K A SERVEREN EJ Shared Folsers ee rte topes speje ii WA TNE TOELEM h e Proverties o i Performance Logs and Alert 4 Evert WA SERVEREM Pag HO A SERVEREN 5 Pamevaide Storage 4 Dye fouce becsi t N NA SERVEREM Ork Defragmenter J Tam AM Categor None 7035 SYSTEM SERVEREN Deck Management Type Ene Event 0 11 E 7 NA SERVEREN 0 Ba Services and Appbcations lt User NA amp 70350 SYSTEM SERVEREN lt Computer SERVERENPTSIW 73 NA SERVEREN g 735 SYSTEM SERVEREN J Desorption 7 NA SERVEREN 2 The diver detected a corisolet esai on Deice R acPext 7035 NETWORK SER SERVEREM 5 For mace information see Help and Support Center at piad panaia g 4295 NIA SERVEREN
150. path is CAProgram Files Emulex AutoPilot Installer Drivers Storport x86 HBA for the 32 bit driver version or C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA for the x64 driver version or C Program Files Emulex AutoPilot Installer Drivers Storport A64 HBA for the Itanium driver version 8 Click OK 9 Select Emulex PLUS Click Next and click Next again to install the driver 10 Click Finish The initial ElxPlus driver installation is complete Continue with manual installation of the Storport Miniport Driver See Installing or Updating the FC Storport Miniport Driver on page 21 for this procedure Emulex Drivers for Windows User Manual Page 20 gt G EMULEX Updating the Emulex PLUS ElxPlus Driver To update an existing ElxPlus driver from the desktop Note Only one instance of the ElxPlus driver should be installed even if you have multiple adapter ports installed in your system 10 11 12 Instal Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 6 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 show the ElxPlus driver entry Right click the ElxPlus driver entry and select Update Driver from the menu Select No
151. pdate to the Microsoft Storport driver is required The KB932755 update must be applied before the Emulex Storport Miniport driver can be installed Note For Windows 2003 servers Emulex drivers do not support the Emulex 16 Gb adapters e Windows Server 2008 running on an x86 or x64 server e Server Core installation option of Windows Server 2008 running on an x86 or x64 server e Windows Server 2008 R2 running on an x64 server e Windows Server 2008 R2 SP1 Windows PE 2 x or 3 x Minimum 512 MB memory Note Check the Emulex website for required updates to the Windows operating system or the Emulex drivers 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 NDIS Miniport Ethernet NIC Driver Note Although TCP Offload Engine TOE is supported it is only enabled for certain adapters on Windows Server 2008 R2 Prerequisites One of the following operating systems must be installed e Windows 2003 R2 SP2 e Windows Server 2003 SP2 running on an x86 or x64 serverWindows Server 2008 running on an x86 or x64 server e Server Core installation option of Windows Server 2008 running on an x86 or x64 server e Windows Server 2008 R2 running on an x64 server e Windows Server 2008 R2 SP1 e Windows 7 Ultimate Enterprise or Professional edition x64 only
152. pe Note For troubleshooting SAN connectivity or device discovery issues set the LogErrors to 1 e The Emulex event code is found in byte 0010 and supplementary data is in byte offsets 0011 through 0013 Additional Event Log Information The following tables are not comprehensive but do include those codes which through Emulex s experiences in our support and testing environments we feel are most likely to show up in SAN environments where problems occur ELS FCP Command Error Status Codes Internal firmware codes posted by the adapter firmware that explain why a particular ELS or FCP command failed at the FC level Table 21 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 Emulex Drivers for Windows User Manual Page 97 CT Command Response Codes Codes that indicate the response to a FC Common Transport protocol command Table 22 CT Command Response Codes gt G EMULEX Explanation Code FC Common Transport Reject 0x8001 FC Common Transport Accept 0x8002 FC CT Reject Reason Codes Codes that indicate the reason a CT command was rejected Table 23 FC CT Reject Reason Codes Explanation Code Invalid command code 0x01 Invalid version level 0x02 Logical busy 0x05 P
153. plete a driver kit installation and AutoPilot installation with a few mouse clicks 1 Double click the driver kit installer or run it from a command line See AutoPilot Installer Command Line and Configuration File Parameters on page 10 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 information and Emulex contact information 2 Click Next to proceed to the Installation Options page For each installation option the default installation location for that option is displayed Browse to a different location if desired 3 Click Install to continue the installation The Progress dialog box is displayed After all tasks are completed a Finish page is displayed The Start AutoPilot Installer box is automatically selected 4 Click Finish AutoPilot Installer runs automatically and completes one of the following installations Emulex Drivers for Windows User Manual Page 6 gt G EMULEX e Hardware First Installation or Driver and Utility Update see page 7 e Software First Installation see page 8 Option 2 Run AutoPilot Installer Separately This option is recommended when e Changing installation settings for a limited number of systems e Familiarizing yourself with AutoPilot Installer configuration options To access these options run AutoPilot
154. put Registry Transmit Buffers 256 Registry Transmit CPU lt not set gt Registry VLAN Identifier 802 1q lt not set gt Registry Wake On LAN 0 Disabled Using Interactive Mode The occfg exe program also supports the interactive mode with a set of menus To start this utility in interactive mode run occfg exe from a command console and do the following 1 A list of adapters will display 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 2 The program will prompt for an operation such as modifying or querying a parameter value Follow the prompt 3 The program will provide a list of available registry parameters to modify or query Type either the number of the corresponding option or a substring in the parameter name The substring must uniquely identify the parameter or occfg will display all potential options 4 To apply the parameters select the menu item to exit and reload the drivers Pressing control c at any point may leave modifications in the registry but the driver does not use the new parameters until it 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
155. r q command line options This shows the registry value or driver value of the parameter or both when using pq together For example occfg a emulex p Emulex OneConnect OCel11102 I NIC TOE 2 Local Area Connection 2 Display all properties Registry Class of Service 802 1p 1 Auto Priority Pause Registry Flow Control 3 Tx Enable Rx Enable Registry IPv4 IP Checksum Offload 3 Tx Enable Rx Enable 1 Enable Registry IPv4 Large Send Offload vl Registry IPv4 Large Send Offload v2 1 Enable Registry IPv4 TCP Checksum Offload 3 Registry IPv4 TCP Connection Offload 0 Disable Registry IPv4 UDP Checksum Offload 3 Registry IPv6 Large Send Offload v2 1 Registry IPv6 TCP Checksum Offload 3 Tx Registry IPv6 UDP Checksum Offload 3 Tx T LX inable Rx Enable T LX nable Rx Enable eI nable inable Rx Enable I x nable Rx Enable Registry Interrupt Moderation 4 3 Adaptive Default Registry Network Address lt not set gt Registry Packet Size 9014 9014 Registry Preferred NUMA Node lt not set gt Registry RSS 1 Enable Registry Receive Buffers 896 Emulex Drivers for Windows User Manual Page 46 gt G EMULEX Registry Receive CPU lt not set gt Registry TCP Offload Optimization 0 Optimize Through
156. re reducing PCI Express bus usage and interrupts e TCP timers including delayed ACK push retransmit and keep alive are implemented in hardware This reduces host CPU usage e Retransmits are handled entirely in hardware e Packetizing data including segmenting checksums and CRC is supported The network driver can receive send and receive buffers that are larger than 1 MB for maximum efficiency e The driver provides efficient parallel processing of multiple connections TCP on multiple CPU systems The UCNA receive path is zero copy for applications that prepost receive buffers or that issue a socket read before the data arrives Ideal applications use Microsoft s Winsock2 Asynchronous Sockets API which allows posting multiple receive buffers with asynchronous completions and posting multiple send operations with asynchronous completions Applications that do not prepost receive buffers may incur the penalty of the data copy and the performance improvement is significantly less noticeable Emulex Drivers for Windows User Manual Page 61 gt G EMULEX 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 pot
157. re for the adapter Value 0 1 Default 0 disabled Note To run the driver using NPIV or SLI 3 optimization the firmware must be version 2 72a0 or later If an earlier version is used the driver runs in SLI 2 mode and does not support NPIV Note NPIV is not available on 1Gb s and 2 Gb s adapters Reboot ExtTransferSize FrameSizeMSB n ExtTransferSize is an initialization time parameter that affects the maximum SGL that the driver can handle which determines the maximum I O size that a port will support If set to 0 the maximum transfer size is 512KB If set to 1 the maximum transfer size is 1MB If set to 2 the maximum transfer size is 2MB Value 0 2 Default 0 disabled FrameSizeMSB controls the upper byte of receive 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 Reset LightPulse Only InitTimeout n Determines the number of time out seconds 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 0xF Reboot Emulex Drivers for Windows User Manual Page 70 Table 11 Storport Miniport Driver Paramet
158. re is outdated and The firmware and the driver are does not support TOE offloads for not compatible versions See the this 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 support RSS functionality for this not 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 support TCP offload functionality not compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers 0x0024 36 Error The device firmware does not The firmware and the driver are not compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers Emulex Drivers for Windows User Manual Page 103 Table 28 NIC TOE Event Log Entries Continued gt G EMULEX Message ID Hexadecimal Severity Message Recommended Resolution Decimal 0x0023 35 Warning The Ethernet link is down due toa The Ethernet link is down due to remote fault the 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 to a local fault link down event detected at the OneConnect driver 0x0021 33 Informati
159. re 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 P rod_00 amp Rev_3 64 5 amp 17659873 amp 2 amp 020 000 disappeared from the system without first being prepared for removal This behavior is not specific to the OneConnect UCNA On a system running Windows 2003 the system appears to hang during shutdown The Windows Storport driver incorrectly issued a Start Stop Unit SCSI command during shutdown Some targets may reject the command and the Storport driver retries this command repeatedly Apply the 932755 hotfix as described on the Microsoft website On a system running Windows 2003 NonPaged pool and NonPaged Page Table Entry PTE usage increases under the following conditions A large number of LUNs are connected to the iSCSI controller e An application issues I Os to these LUNs and the IO size is 128KB or larger Queue depth per LUN is 32 or larger After a period of time these resources will be completely depleted and the system becomes unresponsive Event ID 26 Delayed write errors Event ID 333 An I O operation initiated by the Registry failed and Event ID 2019 The server was unable to allocate from the system nonpaged pool are seen in the system s event log Because no hotfix is available to resolve this issue the application s queue depth must be configured for a maximum of 32 if thi
160. 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 Page 113 gt G EMULEX Table 30 iSCSI Error Log Entries on Windows Server 2008 R2 Continued Message ID Severity Message Recommended Resolution 0x1a 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 0x1b Warning A configuration parameter is The iSCSI driver failed to load a out of range configuration value specified in the registry because the value was out of range The driver uses the default value for this configuration parameter The range specified for a configuration parameter is either too large or too small and it must be corrected Check the registry configuration for new driver parameter entries See Driver Parameters for Windows on page 66 for the correct range of values 0x1d Warning A configuration parameter is The iSCSI driver ignored a configuration invalid entry because the entry was invalid Check the registry configuration for new driver parameter entries The invalid entry mus
161. rivers for Emulex adapters FC and FCoE iSCSI and Ethernet e ElxPlus driver Supports the OneCommand Manager application persistent binding and LUN mapping and masking If you are creating Windows PE disk images and or performing boot from SAN installation you must select the Unpack All Drivers option instead of running AutoPilot Installer See step 2 of Installing the Driver Kit in the following procedure After the driver kit is installed you have two options e Automatically run AutoPilot Installer immediately This is the default option See Option 1 on page 6 for more information e Explicitly run AutoPilot Installer later on your system See Option 2 on page 7 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 Download the driver kit installer from the Emulex website to your system Note The name of the driver kit installer depends on the current version identifier 2 If you plan to create Windows Pre installation Environment PE disk images and 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
162. rotocol error 0x07 ELS Command Codes FC protocol codes that describe what particular Extended Link Services command was sent Table 24 ELS Command Codes Explanation Code Link Service Reject LS_RJT 0x01 Accept ACC 0x02 N_Port Login PLOGI 0x03 Fabric Login FLOGI 0x04 N_Port Logout LOGO 0x05 Process Login PRLI 0x20 Process Logout PRLO 0x21 Discover F_Port Service Params FDISC 0x51 Discover Address ADISC 0x52 Register State Change Notify RSCN 0x61 Emulex Drivers for Windows User Manual Page 98 SCSI Status The SCSI status returned from a SCSI device which receives a SCSI command Table 25 SCSI Status Codes gt G EMULEX Explanation Code GOOD 0x00 CHECK CONDITION 0x02 BUSY 0x08 RESERVATION CONFLICT 0x18 QUEUE FULL 0x28 Local Reject Status Codes supplied by the Emulex adapter firmware which indicate why a command was failed by the adapter Table 26 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 OxOF NO RESOURCES Port out of exchanges or logins 0x11 LOOP OPEN FAILURE FC_AL port not resp
163. rvention 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 Dynamic NodeTimeout n The node timer starts when a node i e 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 Dynamic QueueDepth n QueueDepth requests per LUN target see 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 I 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 Value 1 254 or 0x1 OxFE
164. s Link 1300 1306 1399 Link events Tag 1400 1401 1499 NPIV 1800 1804 1800 N_Port_ID virtualization events Event Trace Messages ELS Log Messages 0100 0130 lpfc_mes0100 0100 FLOGI failure ulpStatus x x ulpWord 4 x x DESCRIPTION An ELS fabric login FLOGI command that was sent to the fabric failed SEVERITY Error LOG LOG_ELS verbose ACTION Check the fabric connection SEE ALSO Ipfc_mes0110 lpfc_mes0101 0101 FLOGI completes successfully NPortld x x RaTov x 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 Emulex Drivers for Windows User Manual Page 76 gt lt EMULEX lpfc_mes0102 0102 PLOGI completes to NPortld x x DESCRIPTION The adapter performed an N _port_login PLOGI into a remote NPort SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0103 0103 PRLI completes to NPortld x x TypeMask x x Fcp2Recovery x x DESCRIPTION The adapter performed a process login PRLI into a remote NPort SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0104 0104 ADISC completes to NPortld x x DESCRIPTION The adapter performed a discover address ADISC into a remote NPort SEVERITY Information LOG LOG_ELS verbose ACTION No action needed informational lpfc_mes0
165. s An unattended installation operates in silent mode sometimes referred to as quiet mode and creates an extensive report file with installation status Emulex Drivers for Windows User Manual Page 1 gt G EMULEX Onelnstall Installer In addition to individual driver and utility downloads a single download package Onelnstall contains all of the Emulex Windows drivers Emulex Storport Miniport and Network Driver Interface Specification NDIS Miniport drivers and the OneCommand Manager application Onelnstall is available for download from the Emulex website The limitation to the single package is that you cannot perform pre installation tasks unattended installations or text only installations For these tasks use the AutoPilot Installer kits Important Considerations Minimum Software Requirements AutoPilot Installer does not allow you to install the driver if the minimum Windows service pack or Microsoft Storport driver update is not installed Windows Driver Information FC and FCoE Driver Prerequisites e One of the following operating systems must be installed e Windows 2003 R2 SP2 1 e Windows Server 2003 SP2 running on an x86 x64 or Itanium server Note For Windows Server 2003 SP2 and Windows Server R2 SP2 the KB932755 update to the Microsoft Storport driver is required The KB932755 update must be applied before the Emulex Storport Miniport driver can be installed Note For Windows 2003 servers
166. s Storport Miniport e with the ProgramFiles environment variable LocalDriverLocation SProgramFiles Emulex AutoPilot Installer Driver Configuration File Location The optional setting ConfigFileLocation contains the path to the configuration file that should be used If this parameter is not specified AutoPilot Installer uses the file named APInstall cfg in the same folder as APInstall exe The format is the same as that of the other path settings Example APInstall silent SkipDriverInstall True configFileLocation MyConfiguration cfg Software 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 SCSlport Miniport or FC Port driver ForceDriverUpdate Forcing a Driver Version Update Default False By default if the same version of the driver is already installed an unattended
167. s 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 a NIC driver is being installed on a Windows Server 2003 64 bit system that has more than 32 processors the operating system may restart unexpectedly following a Stop 0x000000D1 message Apply the 945778 hotfix as described on the Microsoft website Emulex Drivers for Windows User Manual Page 87 gt G EMULEX Table 15 Troubleshooting the NIC and TCP Offload Drivers Continued Problem Answer Solution 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 described 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 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 The system crashes or appears to
168. s problem is seen On a system running Windows 2003 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 Device 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 Page 90 gt G EMULEX Table 16 Troubleshooting the iSCSI Driver Continued Problem Answer Solution A login to new target fails after Microsoft iSCSI Initiator Service is installed When Microsoft iSCSI software is installed the service chooses a defau
169. scription for E vent ID 11 in Source elxstor cannot be found The local computer may not have the necessary registry information or message DLL files to display messages from a remote Computer You may be able to use the AUXSOURCE flag to retrieve this description see Help and Support for details The follovang information is part of the event Device RaidPortd Data Bytes O Words GOO0 82 00 70 00 01 00766700 2 232 h A 0008 00 00 00 OO Ob 00 O04 c0 0010 9b 00 29 00 00 00 00 00 e E E v Figure 4 Event Properties Emulex Drivers for Windows User Manual Page 92 gt G EMULEX 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 A severe error code indicates that the driver firmware or adapter is behaving abnormally and your intervention is required to correct the problem A malfunction error code indicates that there is a problem with the system but your intervention is not required A command 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 Log
170. sing 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 Emulex Drivers for Windows User Manual Page 56 gt G EMULEX Flow control has limited usefulness at 10 Gb s network speeds because it only allows the receiver to completely turn off the incoming flow of packets it cannot just slow down the rate Current 10 Gb s devices tend to cause a dip in performance because the exceedingly fast pipeline of packets will drain before the flow control can resume sending The ideal situation is a continuous pipeline of packets flowing between the endpoints not a start and stop flow Flow Control 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 pack ets 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 transmit ters 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
171. stall Package Overview 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 FC FCoE iSCSI and Ethernet e ElxPlus driver Supports the OneCommand Manager application persistent binding and LUN mapping and masking e OneCommand Manager application for the Emulex adapters Loading the Onelnstall Package Navigate to the location of the Onelnstall package that you downloaded to your hard drive Double click on 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 Oi 0 Nisa A progress screen appears while the Onelnstall installer loads the selected drivers and applications 6 When the drivers and application software are loaded an Installation completed screen appears Click Finish Emulex Drivers for Windows User Manual Page 4 gt G EMULEX Driver Kit Installer Overview The driver kit installer is an executable file that self extracts and copies the following software onto your system e FC protocol drivers Manage communication and data transfer between applications and I O devices using Emulex adapters as agents There are three separate d
172. t be removed or corrected See Driver Parameters for Windows on page 66 for the correct range of values 0x1e Error Failed to map Base Address The iSCSI driver was unable to load Register failing driver 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 0x1f 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 entry identifies the specific point of failure This failure indicates that the hardware has not been initialized or is malfunctioning This may also indicate that the firmware is not running correctly Emulex Drivers for Windows User Manual Page 114 gt G EMULEX Table 30 iSCSI Error Log Entries on Windows Server 2008 R2 Continued Message ID Severity Message Recommended Resolution 0x20 Warning Initial memory allocation The driver failed to allocate its complete failed driver is running with memory requirement and attempts to load 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
173. 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 Dynamic EnableAckO n Set to 1 to force sequence rather than frame level 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 Reset FC only EnableAUTH EnableAUTH enables fabric authentication This parameter requires the authentication to be supported by the fabric Authentication is enabled when this value is set to 1 Value 0 1 Default 0 Reboot EnableFDMl n If set to 1 enables management server login on fabric discovery This allows Fabric Device Management Interface FDMI to operate on switches that have FDMI capable firmware If set to 2 FDMI operates and uses the host name feature of FDMI Value 0 2 decimal Default 0 Reset Emulex Drivers for Windows User Manual Page 69 Table 11 Storport Miniport Driver Parameters Continued gt G EMULEX Parameter Definitions Activation Requirement Adapter Protocol EnableNPIV n If set to 1 enables N_Port_ID virtualization NPIV Requires NPIV supported firmwa
174. thereal or Microsoft Network Monitor do not see TCP offloaded packets Windows Server 2008 allows TCP offloads in more scenarios than Windows Server 2003 In particular TCP offloads may occur with the Windows firewall enabled Emulex Drivers for Windows User Manual Page 59 gt G EMULEX The following table lists common reasons why TCP offloads do not occur and their suggested fixes Table 9 Troubleshooting TCP Offload Failures Reasons for No TCP Offload Solutions Chimney offload is disabled on the system For Windows Server 2008 and Windws 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 disable Chimney offload at the command line type netsh interface tcp set global chimney disabled For Windows Server 2003 1 Verify that Windows Server 2003 Service Pack 2 is installed 2 To determine whether TCP chimney is enabled or disabled on the command line type reg query HKLM SYSTEM CurrentControlSet Services Tcpip Parameters v EnableTCPChimney 3 To enable TCP chimney offload type netsh in ip set chimney enabled For Windows Server 2003 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
175. tion of any NIC teams configured on the system Note To update the Emulex protocol drivers begin the procedure at step 2 To perform a hardware first installation 1 Install a new Emulex adapter and power on the system If the Windows Found New Hardware wizard is displayed click Cancel to exit AutoPilot Installer performs this function Note If there are multiple adapters in the system the Windows Found New Hardware wizard appears multiple times Click Cancel to exit the wizard each time it appears 2 Run AutoPilot Installer using one of the two options listed in Running a Software Installation Interactively beginning on page 6 3 When the AutoPilot Installer Welcome page appears select an adapter in the list and click Next The installation continues Consider the following Emulex Drivers for Windows User Manual Page 7 gt E EMULEX e Ifyou are replacing a SCSlport Miniport or FC Port driver an Available Drivers list is displayed Click OK in this window e Ifyou 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 Ifyou 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 continui
176. torport 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 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 5 Table 5 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 UCNA system configuration the number of iSCSI targets to be connected the I O load and th
177. tree eee ee ect eee eee 12 Configuration File Location cccccecceceeceeeeeeeeeeeeeeeteeeeeeeeeeeeeeeeecaeeeeeeneed 12 Software Configuration Parameters ccccceceeeseeeeeeccneeeeeeeeeeeeecaneeeeeees 12 AutoPilot Configuration File ccccccececcecccceeeeeeeeeeeeeeecceeeeeeeeeeeeeccaeeeeeeeeeeneed 14 Configuration Identification AUTOPILOT ID eccceeeeeeeeeeeeeeeeteeeeeeeees 15 Software Configuration AUTOPILOT CONFIG eessen 15 Configuration Prompts Vendor Specific Questions STORPORT CONFIGURATION cccceeeeeeeeeeeeeeeeeeeeeeeeeeetaeeeeeeeeeeteea 15 QFE Checks STORPORT QFES 2 ccceeeeeeeeeeceneeeeeeeeeeeeeeeeenceeeeeeteea 16 Setting Up FC Driver Parameters STORPORT PARAMS ceeeee 17 Setting Up System Parameters SYSTEM PARAMS sssssssseeeeeeeeee 17 AutoPilot Installer Exit Codes cccccceececcceeee eee e rete eeecceeeeeeeeeeteeccaeeeeeeeeenteed 17 AutoPilot Installer Installation Reports eres 18 Command Script Example cccccccccceeeeeeeceeeeeeeeeeeeeecccaaeeeeeeeeeeeessaaeeeeeees 18 Manual Installation and Updating Procedures ccceeceeeeeeeeeeeeeeeeeeeteteteeeeeeeeees 20 Manually Installing or Updating the Emulex Protocol Drivers 0008 20 Emulex Drivers for Windows User Manual Page iii Ovie W atanan cece ater ng vr ee ect es v ace ep E 20 Removing the Adjunct Driver Registry Key eeeeeeeeeeeeeee
178. typical scenario involves setting parameters the same for all ports of a network adapter This is accomplished by specifying a emulex Often it is convenient to rename the connections to have a common name to easily operate on a group For example naming the network connections dot1 dot2 dot3 allows operating on all adapters using the substring dot or on any individual adapter by specifying the exact name such as dot1 Configuring Device Parameters OneConnect Config is used to query and modify registry parameters for Emulex network devices The registry keys are stored at HKLM System CurrentControlSet Control Class 4D36E972 E325 11CE BFC1 08002bE10318 where is the device instance number Emulex Drivers for Windows User Manual Page 44 gt G EMULEX The occfg program allows you to modify registry keys on a set of network devices Once modified the driver must be restarted to apply these parameters In batch mode occfg will automatically restart the driver when changing a parameter and in interactive mode there is a menu item to select to restart the driver In batch mode the commands to modify parameters will look like the following examples occfg a emulex s rss 0 occfg a emulex s Interrupt Moderation 4 Flow Control 3 The parameter name must uniquely specify one parameter to modify but it may be only a substring on the full parameter
179. ueues parameter see Configuring NIC TOE Driver Options on page 29 Note Microsoft currently does not schedule RSS processing on all hyperthreaded CPUs For example only CPU 1 and 3 have RSS queues on a dual core hyperthreaded CPU In contrast a quad core CPU has RSS queues on all four cores The current Microsoft RSS model requires four consecutive CPUs for RSS queues so a hyperthreaded system never uses all four RSS queues Enabling Windows to Use Up to Eight Processors Windows Server 2003 and Server 2008 by default use only four processors 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 2003 set the registry keyword MaxNumRssCpus a DWORD type to 8 at the location HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip Parameters 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 Do not set the registry keyword to a value greater than the number of processors in the system or 16 whichever is smaller TCP Offloading TCP offload is supported by Windows Server To monitor TCP offloads in a command window type netstat t This command indicates the offload state for each TCP connection of the system Note Packet sniffing applications such as E
180. ut 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 For information on modifying the CheckSum Offload or Large Send Offload parameter see Configuring NIC TOE Driver Options on page 29 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic The UCNA can process TCP receive packets on four processors in parallel per port or PCI function for a total of eight processors in parallel This is ideal for applications that are CPU limited Typically these applications have numerous client TCP connections that may be short lived Web servers and database servers are prime examples RSS typically increases the number of transactions per second for these applications Understanding RSS To better understand RSS it helps to understand the interrupt mechanism used in the network driver Without RSS a network driver receives an interrupt when a network packet arrives This interrupt may occur on any CPU or it may be limited to a set of CPUs for a given device depending on the server architecture The network driver launches one deferred procedure call DPC that runs on the same CPU as the interrupt Only one DPC ever runs at a time In contrast with RSS enabled the network driver launches up to four parallel DPCs on four different CPUs For example on a four processor server that interrupts all processors without RSS the
181. ved Enable RSS disable TCP offload TCP connections such as web server or e mail server Emulex Drivers for Windows User Manual Page 54 gt G EMULEX Table 7 Windows Server Performance Tuning Situations Continued Situation Answer Solution There are large data transfers such as to a file server web server with file downloads or an FTP server Use TCP offload There are large data transfers such as to a backup server Enable jumbo packets use TCP offload There is a small server struggling to keep up with larger servers on the network Disable RSS enable TCP offload enable jumbo packets There is a general purpose server such as Active Directory server DHCP server or a DNS server Use TCP offload enable RSS Analyzing Performance Problems 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 8 lists a few statistics to use for troubleshooting performance problems For network performance all the counters from the table are useful Network Interface TCPv4 IPv4 and Processor Table 8 Statistics and Fine Tuning Situation Answer Solution Network Interface gt Packets Received Errors If this is in
182. vent log entry states that the driver failed to load due to memory constraints There may not be enough memory installed in the system to provide sufficient memory for all devices installed in the system Try installing more memory if possible Unpredictable results occur when flow control setting differs among PCI functions If multiple PCI functions are exposed for a single 10 Gb s Ethernet port such as in blade configurations the flow control 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 unplug the system may hang or produce a bugcheck if a PCle hot unplug or replace is attempted When Wake on LAN is set through the advanced properties page the system does not wake when receiving a magic packet or a packet that would normally wake the system Hot unplug is not supported in this release 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 The system may not go to a lower power state because another software component device or driver i
183. version capability is not supported by this firmware Update your firmware 0x24 Info Interrupt Redirection N A capability is not supported by this hardware 0x26 Warning Logical link on the The iSCSI function may have been disabled OneConnect Port is down in the PXESelect application If you traffic is disallowed on this disabled it intentionally you can ignore this function message 0x27 Error Firmware returned invalid Reload the firmware data in its configuration iSCSI login and offload are disabled Emulex Drivers for Windows User Manual Page 115 gt G EMULEX 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
184. with session id N failed to connect within the configured timeout A connection to the target was lost for a period exceeding the Extended Timeout ETO The error log entry includes the session ID of the target 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 0x09 Error Task Management request N was unhandled 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 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 Emulex Dr
185. y Ipfc_mes1802 1802 Exceeded the MAX NPIV port x x DESCRIPTION Exceeded the number of Virtual Port allows on the adapter SEVERITY Error LOG LOG_NPIV verbose ACTION Reduce the number of Virtual Ports Emulex Drivers for Windows User Manual Page 85 Ipfc_mes1803 1803 Virtual Port x x VPI x x successfully created DESCRIPTION Virtual Port ID is successfully created SEVERITY Information LOG LOG_NPIV verbose ACTION No action needed informational Ipfc_mes1804 1804 Removing Virtual Port x x VPI x x DESCRIPTION Removing Virtual Port ID SEVERITY Information LOG LOG_NPIV verbose ACTION No action needed informational ELS Messages 1900 1999 1900 x x sends ELS_AUTH_CMD x x with TID x x DESCRIPTION An ELS_ AUTH_CMD is sent SEVERITY Information LOG LOG_FCSP verbose ACTION No action needed informational 1901 x x sends ELS AUTH REJECT x x x x to x x DESCRIPTION An ELS AUTH_REJECT is sent SEVERITY Information LOG LOG_FCSP verbose ACTION No action needed informational 1902 Receives x x from x x in state x x DESCRIPTION Receives an ELS AUTH CMD SEVERITY Information LOG LOG_FCSP verbose ACTION No action needed informational 1903 Receives ELS_AUTH_RUJT x x x x DESCRIPTION Receives an ELS AUTH REJECT SEVERITY Information LOG LOG_FCSP verbose ACTION No action needed informational 1904 Authentication ends for x x with status x x d d DESCRIPTION Auth

Emulex Drivers for Windows

Contents

Download Pdf Manuals

Related Search

Related Contents