Home

Emulex® Drivers Version 10.4 for Windows

1. Bits 0 7 Interpretation 0x23 Returned to safe temperature SLI2 3 mode 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 0x42 Re simulate FCF after exhausted retries on FLOGI 0x51 ABTS timeout on path and target Bits 8 15 path id Bits 16 23 target id 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 0x2E Failed to allocate resources for Express Lane 0x30 Failure on mailbox context allocation 0x7C Menlo initialization error 0x7D Menlo initialization error 0x7E Menlo initialization error 0xA0 Failed to initialize adapter port OneConnect OxAl Failed to initialize adapter port SLI2 3 mode 0xCO Insufficient revision level for STORPORT SYS 0xC1 Failed to allocate miniport un cached extension 0xC2 Insufficient un cached extension space 0xC3 Port initialization failure OneConnect 0xC4 Port initialization failure SLI2 3 mode 0xC5 Utility mailbox command error 0xC6 SLI4 Pre initialization failure 0xD3 NPIV memory allocation failure OxEO Unable to allocate exchange for unsolicited ELS command OxE1 Misconfigured ports event on indicated po
2. 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 SLI4 mode OxF2 Port in off line state SLI4 mode OxF3 Port in on line state SLI4 mode Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix A Error and Event Log Information 151 gt lt EMULEX FC FCoE Error and Event Logs Viewing the FC FCoE Event Log This section provides information on the FC FCoE event logs Event Log Interpretation e All events logged by Emulex Storport Miniport are in Event ID 11 with source elxfc elxcna 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 and the optional setting of 1 logs events of SEVERE MALFUNCTION and COMMAND type Note For troubleshooting SAN connectivity or device discovery issues set the LogErrors to 1 e The Emulex event code is found in byte 0010 and supplementary data is in byte offsets 0011 through 0013 Additional Event Log Information The following tables are not comprehensive but do include the codes that are most likely to show up in SAN environments where issues occur ELS FCP Command Error Status Codes
3. Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Transmit Buffer Transmit Buffer Transmit CPU Transmit CPU Transmit Side S Transmit Side S UDP Checksum Of UDP Checksum Of UDP Checksum Of UDP Checksum Of VLAN Identifier VLAN Identifier Virtual Machine Virtual Machine Wake On LAN Wake On LAN 1 0 Using Interactive Mode 3 Configuration 75 NIC Driver Configuration TCP Checksum Offload IPv4 3 Rx amp Tx Enabled TCP Checksum Offload IPv4 3 Rx amp Tx Enabled TCP Checksum Offload IPv6 3 Rx amp Tx Enabled TCP Checksum Offload IPv6 3 Rx amp Tx Enabled Transmit 1 Enabled Transmit 1 Enabled s 256 256 s 256 0x100 256 lt not set gt lt not set gt caling 1 Enabled caling 0 Disabled fload IPv4 3 Rx amp Tx Enabled fload IPv4 3 Rx amp Tx Enabled fload IPv6 3 Rx amp Tx Enabled fload IPv6 3 Rx amp Tx Enabled 802 1q 102 802 1q 102 0x66 Queues 1 Enabled Queues 1 Enabled Enabled Disabled The occfg exe program also supports the interactive mode with a set of menus To start this utility in interactive mode 1 Run occfg exe from a command console A list of adapters displays on which to operate 2 Type either a number of the list or a substring from any part of the
4. Where e question contains the text of the question to be asked e explanation contains brief text to help explain the question The explanation appears below the question in a smaller font If there is no explanatory text empty quotes must be used in its place e answer0 contains the 1st answer to be displayed in the drop down list e answerl contains the 2nd answer to be displayed in the drop down list e answern contains the nth answer to be displayed in the drop down list For each question there can be as many answers as needed For each answer there must 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 P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Configuration File 1535 Example of STORPORT CONFIGURATION section STORPORT CONFIGURATION The first section contains the driver parameters common to all configurations no matter what answers are given DriverParameter EmulexOption 0 QUESTIONS question What is your link speed Note select Auto detect if you are unsure about the answer 4GB 2GB
5. Action Emulex Drivers for Windows User Manual Disconnected NPort ID SCSI ID has failed to reconnect within timeout limit Error LOG_ELS verbose Review system configuration P011041 01A Rev A gt EMULEX 4 Troubleshooting 127 Troubleshooting the FC FCoE Driver Mailbox Log Messages 0310 0326 Ipfc_mes0310 Mailbox command timeout HBA unresponsive Description Severity Log Action A Mailbox command was posted to the adapter and did not complete within 30 seconds sync 0 asynchronous mailbox command is issued 1 synchronous mailbox command is issued Error LOG MBOX verbose This error could indicate a software driver or firmware issue If no I O is going through the adapter reboot the system If these issues persist report these errors to Emulex technical support Ipfc_mes0326 Reset HBA HostStatus x x Description Severity Log Action The adapter has been reset Information LOG MBOX verbose No action needed informational INIT Log Messages 0400 0463 Ipfc_mes0400 Initializing discovery module OptionFlags x x Description Severity Log Action Driver discovery process is being initialized with internal flags as shown Information LOG _ELS verbose No action needed informational Ipfc_mes0401 Initializing SLI module Deviceld x x NumMSI d Description Severity Log Action Emulex Drivers for Windows User Manual PCI function with device id and
6. SERVEREN Divtemanen 1 13 2009 11 06 08 AnleciagSve Nene 3 WA SERVEREN Dirtermanen 1 13 2000 1 06 04 DEON ene 10025 A SERVEREN j JP Divteemascn 1713 2009 81 05 04 evertion fone 6005 KA SERVEREN zl E Ee Figure A 2 iSCSI Error Because the adapters are dual PCI function adapters the Device RaidPort lt n gt value changes depending on the device that observed the error Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 162 iSCSI Error Log on Windows Server 2008 Table A 14 lists brief descriptions of the error log codes generated by the iSCSI driver for Windows Server 2008 It includes the error code the message displayed and the meaning of the message with the recommended resolution Table A 14 iSCSI Error Log Entries on Windows Server 2008 Message ID Message Description Recommended Resolution 0x348d0008 The iSCSI driver failed a WMI IOCTL This failure indicates that an operation request from the port driver because attempted from the Microsoft WMI application the request was failed by the ARM resulted in an error Check the operation being firmware This error is immediately attempted for user or configuration errors followed by another error code entry indicating the WMI request code in error 0x348d0007 The iSCSI driver failed a WMI IOCTL This failure indicates that an
7. 3 Configuration gt G EMULEX NIC Driver Configuration 109 Windows Server has not optimized the connection offload path Some applications that use numerous short lived TCP connections do not show a performance improvement using TCP offload Windows Server provides control over the applications and TCP ports that are eligible for TCP offload using the netsh tool Refer to the Microsoft documentation for these netsh commands netsh interface tcp add chimneyapplication state disabled application lt path gt netsh interface tcp add chimneyport state disabled remoteport 23 localport Note The netsh commands require the Windows firewall to be running If the firewall is disabled all applications and ports added with the netsh commands may fail to connect TCP Offload Optimization Settings The adapter supports an option for optimizing TCP connection offload characteristics for throughput or latency This option is available through the Advanced Property Page See Configuring NIC Driver Options on page 45 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 offloading by
8. 69 gt EMULEX 3 Configuration 70 NIC Driver Configuration Running with no arguments will display a menu to select the adapter and parameters to modify Using the command line arguments allow scripting this process Options a str str s name v name v g name name r T filename L filename M module trace 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 Sets the parameter s value and reloads the devices Gets parameter value Skips reloading the driver when setting a parameter Force reloading the driver Force disabling the driver Force enabling the driver List available adapters and exit Saves tinylog to a binary file Loads a binary file and replays tinylog Reset all parameters to the default values Show all registry parameter values Show all driver parameter values Show help text for all parameters Show this help Continously downloads ARM log into a file level module trace arguments set a specific trace level on listed level modules Default argument is all error Refer to ARM firmware for list of modules and debug trace levels This is a special command argument 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 Conn
9. cceceeteete eter teeter nee 79 Figure 3 5 Emulex NIC Driver Properties Page ccceeee eee eee e neces eeee teas eee eae 80 Figure 3 6 Emulex NIC Advanced Properties Page ccceeee eee eee eect eee e eee e teeta eens 81 Figure 3 7 Emulex NIC Statistics Properties page ccc ee cece eee eee eet eaten nae 83 Figure 3 8 Advanced Property Configuration ROCE Enabled cccceeeee eee ee eae 91 Figure 3 9 Get NetAdapterRDMA RoCE Enabled ccceccete cette renee eee etnies 91 Figure 3 10 Get NetOffloadGlobal ROCE Enabled ccecee cece eee e eee eee eee ee eee e ne ens 92 Figure 3 11 Active NetworkDirect Connections and Listeners ceecese cette eee eee nee 92 Figure 3 12 SMB Share Two RDMA Connections Per RDMA Enabled Network WEST ACE cc co ceterenacniicannesmenba ning E NEE EEEE EAEE EEEE EIEE 93 Figure 3 13 Get NetAdapterStatistics ccce ccc eee nent nee nas 93 Figure 3 14 Two SMB Direct Connections Per Interface cceceeeeee eee e eee eee a 94 Figure 3 15 SMB Multichannel Constraint ccccccccee cee e eee e eee ee eeeeeeeeeeeaeeenaneeenaes 95 Figure 3 16 Resource Counts on a 1 Port 10GbE or 40GbE OCe14000 Series Adapten menoon e EE N E E A 96 Figure 3 17 Resource Counts on a 2 Port 10GbE OCe14000 Series Adapter ccccccccccas 96 Figure 3 18 Resource Counts on a 4 Port 10GbE OCe14000 Series Adapter ccccccccccas 96 Figure A 1 Event Properties sssssssesrrrrrrrrrr r
10. e peat Beets d Ta Statistics i EMULEX Device Statistics Transmit Throughput Thi RSS Receive Packets Transmit Flow Control Pause Requests Receive Flow Control Pause Requests TCP Offloads Currently Established TCP Offload Receive Rate VMQs Allocated Interrupt Rate Receive Drops No Memory DMA limited packets sec packets sec packets packets packets packets packets connections connections packets packets bits sec bits sec queues int sec Figure 3 7 Emulex NIC Statistics Properties page Verifying SR IOV from the Host Hyper V Server 3 Configuration 83 NIC Driver Configuration 1 From the Device Manager open the Network Adapters item select the Microsoft Hyper V Network adapter and right click Select Properties from the context menu The Hyper V Network adapter Properties dialog box opens showing the Driver page 2 Select the Statistics tab 3 From the Statistics tab locate the Virtual Functions Allocated item Virtual Functions Allocated shows the count of currently enabled virtual functions Note The Microsoft Powershell command Get NetAdapterSriovVf lists each SR IOV virtual function See the Microsoft documentation for more information Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 84 gt lt EMULEX NIC Driver Configuration Configuring NVGRE for the OCe14000 series Adapters Network virtualization using NVGRE
11. e RDMA Check the output of Get NetAdapterRdma RdmaAdapterInfo for RdmaAdapterInfo If RdmaAdapterInfo is empty any reported fields in Get NetAdapterRdma fl are based on registry values If RdmaAdapterInfo is not null the driver is reporting RDMA capabilities Get NetAdapterRdma fields are based on what the driver reports Considerations for Using UMC and NIC Note UMC is not supported on LPe16202 adapters e 64 VLAN IDs can be used with each UMC virtual channel e SR IOV must be disabled if UMC is enabled For additional information on UMC refer to the Emulex Universal Multi Channel Reference Guide which is available for download from the Emulex website ARI Considerations Note RoCE is not supported with ARI Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 63 DG EMULEX NIC Driver Configuration The PCIe standard limits an adapter to a maximum of eight physical functions This means that a 2 port adapter can only have four functions per port and a 4 port adapter can only have two functions per port The following requirements must be met to fully support ARI and expose more than eight functions on an adapter ARI must be available on the system to support up to 16 functions on an adapter If these conditions are not met although you can configure all 16 functions only eight functions will be present and discovered by the OneCommand Manager application after a reboot Only OCe14000
12. im_policy 3 Conservative A lower interrupt rate than moderate im_policy 4 Very conservative The lowest interrupt rate The default setting can work for most configurations however there are instances when the setting may need to be altered The im_policy parameter setting must be based on the adapter system configuration the number of iSCSI targets to be connected the I O load and the throughput and latency offered by these iSCSI targets On systems that are capable of sustaining a higher interrupt rate and on which the number of connected targets is low eight or fewer setting the im_policy to 1 results in lower latency and higher values of IOPs However this aggressive interrupt rate can also result in system stalls and freezes especially if queue depth values are high and I O requests are small In a configuration that involves a large number of iSCSI targets more than 32 or 64 and higher values of queue depth the default setting may prove to be too aggressive In such a case you may need to change the im_policy parameter setting to 3 or 4 Although this increases latency of an I O request the lower interrupt rate can 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 Initi
13. A DE EMULEX 2 Installation 30 Noe 10 11 12 Manually Installing or Updating the Emulex Protocol Drivers Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Click Browse my computer for driver software Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All dual channel adapter models are displayed in the Device Manager as two adapters therefore you must update each adapter Click Let me pick from a list of device drivers on my computer and click Next Select the network adapter that matches your hardware and click Have Disk Direct the Device Wizard to the location of be2nd6x inf If you have installed the driver installer kit in the default folder the path is C Program Files Emulex AutoPilot Installer NIC Drivers NDIS x64 Win2008 Click OK The Windows Security dialog box opens Click Install After the device driver finishes installing click Close The driver installation is completed The driver will start automatically Windows Server 2012 1 NAOT PF SN Select Server Manager gt Dashboard gt Tools gt Computer Management gt Device Manager Note Server Manager is set to open by default when booting Windows Server 2012 If it does not open automatically you can open it with the Server Manager icon at the bottom left of the screen Open the Ne
14. Ensure that the IP address on the adapter 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 adapter port has been selected for the login The iSCSI WMI GUI shows the target state as connected but LUNs are not seen from the disk manager Verify that the adapter name used to connect to the target matches the adapter name configured on the iSCSI target Multipath configuration shows duplicate LUNs on the disk manager Ensure that the 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 for NIC iSCSI FCoE and RoCE Protocols User Manual for more information on MPIO Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 141 Troubleshooting the iSCSI Driver Table 4 6 Troubleshooting the iSCSI Driver Continued Issue Multipath configuration takes a long time to fail over or failover does not occur Answer Solution Ensure that LDTO settings and ETO settings have been configured for MPIO These values must be set to 0 For more information see Configuring LDTO and ETO on the Windows Server on page 118 Sendtargets to a IET fails because it violates the iSCSI specification If you still want to add a
15. ForceRegUpdate Forcing an Update of an Existing Driver Parameter Value 181 LocalDriverLocation Specifying Location to Search for Drivers 0scceseeeeeeeeeees 181 NoSoftwareFirstInstalls Prohibiting Software First Installations cecen 181 ReportLocation Setting Up an Installation Report Title and Location 0085 181 SilentInstallEnable Enabling Unattended Installation ccceseeeeeeeeeeeeeeenees 182 SilentRebootEnable Enabling Silent Reboot ccccccceeceeeee sees seeeeeteeeeeeneees 182 InstallWithoutQFE Enabling Installation if a QFE Check Fails s e 182 AutoPilot Configuration File ssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 183 Using the Windows Environment Variable WProgramFiles nccc 183 Configuration Identification AUTOPILOT ID cccccccceceeee sees eens eeaeeeaes 183 Software Configuration AUTOPILOT CONFIG c cccccesceseseeeeneeeeneeeenuees 184 Configuration Prompts Vendor Specific Questions STORPORT CONFIGURATION 184 QFE Checks STORPORT OFES cccrusecciss coottasericedieiirec ark ea Doe 185 Setting Up FC Driver Parameters STORPORT PARAMS ccccceeeeeeeeeeuneeeaes 186 Setting Up System Parameters SYSTEM PARAMS ccccecceeeeeeeeaeeeeeeeeeeaes 186 AutoPilot Installer Exit CodeS ssssssssunnnnnnnnnnnnnnunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 187 AutoPilot Installer Installation Reports s sssssssssnn
16. Get NetAdapterRdea ifdesc Emulex Microsoft Corporation All rights reserved F Format List Property MaxQuevePairCount Get NetAdapterRdma ifdesc Emulex Format List Property MaxQueuePairCount Figure 3 18 Resource Counts on a 4 Port 10GbE OCe14000 Series Adapter SMB Direct does not take these adapter reported limits into consideration when creating SMB Direct connections because the driver may still get a request to create more queue pairs or memory regions than are supported Note OCe14000 series adapters will fail to create a memory region or queue pair if it exceeds the limits of what is supported The per port maximum active connections and the maximum passive connections cannot exceed the MaxQueuePairCount See Table 3 5 SMB Direct Active Connections Client Mode Per Port for OCe14000 Series Adapters on page 96 for more information For Windows Server 2012 and Windows Server 2012 R2 all existing ROMA connections between the particular client server pair on which the failure occurred are torn down and recreated After a certain number of unsuccessful retries SMB traffic falls back to TCP IP Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q7 DG EMULEX NIC Driver Configuration The following event warning message is placed in the Windows System Log under the source be2net indicating the adapter is running out of resources The Adapter ran out of resources
17. Option 2 Run the Driver Kit Installer Separately 1 Follow steps 1 3 for Running a Software Installation Interactively on page 22 Clear the Run AutoPilot Installer check box on the Finish dialog box Choose one of the following options 2 3 Run the AutoPilot Installer from a command prompt or script with the silent option APInstall exe silent Edit the AutoPilot Installer configuration file before running AutoPilot Installer The configuration file is typically located in C Program Files Emulex AutoPilot Installer lt driver type gt APInstall cfg Uncomment the line that sets SilentInstallEnable to True You may also want to edit other settings in the same section of the configuration file related to unattended installations See Software Configuration Parameters on page 180 for more information After editing the file you can run the AutoPilot Installer from the Start menu a command prompt or a script Installation Failure If the installation fails the Diagnostics window is displayed with the adapter that 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 Man
18. To improve network and CPU performance for heavy network loads under these conditions you may have to make an appropriate NUMA CPU selection For example in Windows Server 2012 R2 you can use the Task Manager to adjust the Set Affinity property to bind the application to a specific NUMA node for maximum network performance and CPU efficiency Checksum Offloading and Large Send Offloading LSO The adapter 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 adapter 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 adapter supports transmit LSO which allows the TCP stack to send one large block of data and the hardware segments it into multiple TCP packets This is recommended for performance but it can be disabled for packet sniffing applications LSO sends appear as giant packets in the packet sniffer because the hardware has not yet segmented them Note On Windows Server 2012 Recv Segment Coalescing is enabled by default You must disable Recv Segment Coalescing if you want to set the Checksum Offload setting to anything other than enabled Fo
19. Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition The following modes are supported for selecting 802 1p priority tags e Automatic Priority The DCBX standard allows the network adapter to negotiate priority class usage with DCBX aware endpoints such as switches or network cards If the peer indicates that priority pause is supported for a non zero priority the NIC automatically inserts the default priority in all transmitted packets This is the default mode allowing priority pause to operate for both storage and network traffic If the peer indicates a zero default priority such as when the peer does not support priority pause the device uses the Non Storage Priority mode discussed below e Filtered Priority This mode coerces the user priorities in each packet to avoid sending packets on the network function that may disrupt the 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 must be limited to cases where storage functions are not used Disable Priority The adapter always transmits either untagged packets or VLAN ID 802 1q tagged packets with a priority
20. Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Acceptable Values TCP Enabled Connection Disabled default Offload IPv4 Emulex Drivers for Windows User Manual Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Note TCP Connection Offload is not supported on 16GFC adapters If TCP offload is enabled the device offloads the entire TCP protocol including acknowledgement processing retransmits and timers Applications that prepost receive buffers before the data arrives may avoid data copies in the receive path which substantially increases the system efficiency and data rates Windows does not offload TCP connections if any of the following are enabled e Network Load Balancing e IPSEC e Network Address Translation e NDIS 5 1 Intermediate Drivers TCP offload must be enabled in the Windows operating system with the shell command netsh int tcp set global chimney enabled This parameter appears disabled if the firmware installed on your device does not support TCP connection offload Upgrading the firmware may resolve this issue View the Statistics property page to ensure that TCP connection offload is working Note Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled P011041 01A Rev A gt G EMULEX 3 Configu
21. 1GB Auto detect ANSWER 0 DriverParameter LinkSpeed 4 4 GB ANSWER 1 DriverParameter LinkSpeed 2 2 GB ANSWER 2 DriverParameter LinkSpeed 1 1 GB ANSWER 3 DriverParameter LinkSpeed 0 Auto detect question Describe the topology of your storage network Note Select Arbitrated Loop when directly connected to the array no fibre switch Select Point to Point when connected to a SAN fibre switch Arbitrated Loop Point to Point ANSWER 0 DriverParameter Topology 2 ANSWER 1 DriverParameter Topology 3 ENDQUESTIONS END STORPORT CONFIGURATION QFE Checks STORPORT QFES This section specifies an additional QFE check also known as KB updates during installation To add a Windows QFE check to the configuration file edit the STORPORT QFES section in the AutoPilot configuration file You can 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 can exist but they are ignored All parameters in each line must be specified These lines have the format qfe qfe name path and file name file version applicable OS n qfe name The name of the item being checked For example QFE 2846340 The name should facilitate searching Microsoft s website for any required code updates Emulex Drivers for
22. An ELS_AUTH_CMD is sent Severity Information Log LOG FCSP verbose Action No action needed informational Ipfc_mes1901 x x sends ELS AUTH_REJ ECT 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 Ipfc_mes1902 Receives 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 Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 136 Troubleshooting the FC FCoE Driver Ipfc_mes1903 Receives ELS AUTH_RJ T x x x x Description Severity Log Action Receives an ELS_AUTH_REJECT Information LOG _FCSP verbose No action needed informational Ipfc_mes1904 Authentication ends for x x with status x x d d Description Severity Log Action Authentication is done Information LOG _FCSP verbose No action needed informational Ipfc_mes1905 Authentication policy change for local x 08x x 08x remote x 08x 08x Description Severity Log Action Emulex Drivers for Windows User Manual Authentication policy has been changed Information LOG_FCSP verbose No action needed informational P011041 01A Rev A 4 Troubleshooting 137 Troubleshooting the NIC Drivers gt G EMULEX Troubleshooting the NIC Drivers Table 4 3 provides troubleshooting information for the NIC drivers T
23. Configuration eea Details Events Power Management Advanced Status Statistics Diagnostics SG EMULE X Advanced Property Configuration Value Wake On LAN E Performance CPU Affinity Flow Control Interrupt Moderation Num RSS Queues Receive Buffers Receive Side Scaling TCP Offload Optimization Transmit Buffers Set to Default Virtual Machine Queues Protocol Offloads Reset All to Default Single Root IO Virtualization SR IOV enables the adapter tola allocate virtual PCI functions for each virtual machine in E Hyper V Note that the virtual switch and virtual network _ adapter must have SRIOV enabled in the Hyper V Manager When using SRIOV the Emulex NIC driver must be installed L on each virtual function within the virtual machine SR IOV provides a direct hardware interface from the virtual machine to the networking adapter which reduces latency v and improves performance Figure 3 6 Emulex NIC Advanced Properties Page 5 Select SR IOV from the list and select Enabled from the Value list Note You must configure Hyper V to create an SR IOV enabled virtual machine See the Microsoft Hyper V documentation for more information Hyper V The Hyper V role must be added using the Server Manager After the Hyper V role is added you can enable SR IOV in the Hyper V Manager by e Creating the virtual switch e Creating each virtual NIC See the Microsoft documentation for
24. Hosts Configuration To create a VM 1 Use a 10 GB disk image size and 1 GB RAM 2 Install Windows Serer 2012 RTM 3 Turn off automatic administrator login by using control userpasswords2 4 Turn off the Windows Firewall 5 Create a vswitch for NVGRE for example vport0 6 Create a vswitch for non NVGRE normal traffic 7 Expose a NIC interface into the VM for each of the vSwitches Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX 3 Configuration 85 NIC Driver Configuration e Make sure Enable virtual machine queue is selected under Network Adapter gt Hardware Acceleration of the VMs e Record the MAC addresses located under the Network Adapter gt Advanced Features These will be used in the add remove policy scripts 8 Rename the Network Connection name being used for NVGRE to WNVNIC for example Control Panel gt Network and Internet gt Network Connections rename Ethernet 3 to WNVNIC 9 Set up an NVGRE script Setting up a NVGRE Script The following sample script is required for network virtualization Example of a Script Adding the NVGRE Tunnel Between Two Hosts Add the locator records for Blue subnet Get NetVirtualizationLookupRecord where VirtualSubnetID eq 5001 Remove NetVirtualizationLookupRecord New NetVirtualizationLookupRecord VirtualSubnetID 5001 ProviderAddress 192 x x x MACAddress 060600000005 New NetVirtualizationLookupR
25. IET you must add the target manually This issue affects Sendtargets only The following POST error message appears Initiator iSCSI Name mismatch Please use iSCSISelect to set a single name for all controllers Press lt Ctril gt lt S gt to enter iSCSISelect Reboot required In the iSCSI BIOS the Emulex iSCSI initiator name may be different if more than one OneConnect adapters are in the system This message appears if the iSCSI initiator name is different on multiple controllers Enter the iSCSISelect utility and save a new initiator name on the first iSCSISelect utility 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 for NIC iSCSI FCoE and RoCE Protocols User Manual for more information If an iscsicli logouttarget command is issued back to back in a script event 12 errors from the PlugPlayManager are seen in the Windows Event Viewer The error message is similar to this string The device SE ISCSI 00 SCSI Disk Device SCSI Disk amp Ven_ SE_ISCSI amp Prod_00 amp Rev_3 64 5 amp 17659873 amp 2 amp 020000 disappeared from the system without first being prepared for removal This behavior is not specific to the OneConnect adapter On a system running Windows Server 2008 or Windows Server 2008 R2 the iSCSI driver fails to load after many iterations of enable disable from Device Manager Becaus
26. MSI count as shown is being initialized for service level interface Information LOG _ELS verbose No action needed informational P011041 01A Rev A gt EMULEX 4 Troubleshooting 128 Troubleshooting the FC FCoE Driver Ipfc_mes0405 Service Level Interface SLI 2 selected n Description Severity Log Action Service Level Interface level 2 is selected Information LOG _ELS verbose No action needed informational Ipfc_mes0406 Service Level Interface SLI 3 selected n Description Severity Log Action Service Level Interface level 3 is selected Information LOG_ELS verbose No action needed informational Ipfc_mes0436 Adapter not ready hostStatus x x Description Severity Log Action The adapter failed during powerup diagnostics after it was reset Error LOG_INIT verbose This error could indicate a hardware or firmware issue If issues persist report these errors to Emulex technical support Ipfc_mes0442 Adapter failed to init CONFIG_PORT mbxStatus x x Description Severity Log Action Adapter initialization failed when issuing CONFIG_PORT mailbox command Error LOG _INIT verbose This error could indicate a hardware or firmware issue If issues persist report these errors to Emulex technical support Ipfc_mes0446 Adapter failed to init CONFIG_RING mbxStatus x x Description Severity Log Action Emulex Drivers for Windows User Manual Ad
27. Manager After installing the MPIO feature you must launch and configure the MPIO GUI to enable multipath support for iSCSI devices The following steps describe the installation process for setting up Microsoft iSCSI DSM and enabling multipath I O for all iSCSI devices irrespective of their vendor and device IDs You can use the MPIO GUI to configure DSMs other than Microsoft iSCSI DSM Also you can use the GUI to enable multipath support for a specific vendor ID and device ID For more information refer to the Microsoft TechNet Library on the Microsoft website In a multipath configuration the driver parameters LDTO and ETO can be configured to control the amount of time it takes for the failover operation to complete The default value of LDTO is 20 seconds and the default value of ETO is 90 seconds For information on modifying the timeout parameters in a failover configuration refer to Error Handling Under MultiPath MPIO and Cluster Configurations on page 118 If the ETO or LDTO value needs to be modified 1 Select the Emulex OneConnect iSCSI adapter in the Windows Device Manager under Storage Controllers 2 Right click and select Properties The Device Manager Property page opens 3 Select the Advanced tab and set the desired value of ETO and LDTO for example ETO 120 and LDTO 60 4 Reboot the system for the changes to take effect Emulex Drivers for Windows User Manual P011041 01A Rev A SXG EMULEX 3 Configuratio
28. Target boot LUN 0x0E e Target iqn name iqn 2009 04 com 1234567890 e Initiator name not specified use the initiator name that is already configured or use the default name if no initiator name is already configured e Header digest Enabled e Data digest not specified assume disabled e Authentication type one way CHAP Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix B Configuring iSCSI through DHCP 176 gt lt EMULEX Dynamic Host Configuration Protocol DHCP Recommendations The following is an example of default TCP port and mutual CHAP settings iscsi 192 168 0 2 000000000000000E ign 2009 4 com 1234567890 E D M e Target IP address 192 168 0 2 e Target TCP port Use default from RFC 3720 3260 e Target boot LUN 0x0E e Target iqn name iqn 2009 04 com 1234567890 e Initiator name not specified use the initiator name that is already configured or use the default name if no initiator name is already configured e Header digest Enabled e Data digest Disabled e Authentication type Mutual CHAP Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix C Port Speed Specifications 177 gt EMULEX Negotiating Speed on a Mezzanine Card Appendix C Port Speed Specifications An adapter can support only one Ethernet port speed at a time and the preference is always for 10 Gbps The type of module used copper or optical does not make a difference As soon as
29. and advanced property windows are all closed The Control Panel renames the NDI Params registry keys and causes the policy scripts to be inoperative Cleaning Up Outdated Network Adapter Data To clean up outdated network adapter data 1 2 i w SO a OF Start a win32 console window command prompt From the command prompt type Set devmgr_show_nonpresent_devices 1 Start devmgmt msc In the device manager console go to the view menu and select Show hidden devices Open the network devices tree view Uninstall all Emulex entries Rescan for hardware changes Uninstall Emulex devices until they are not recognized Install the new driver Configuring RoCE for the OCe14000 Series Adapters Notes e Both Windows SMB Direct and Windows NetworkDirect which are included as part of the Windows operating system are required for RoCE e RoCE is not supported if UMC is enabled e RoCE configurations are not supported with SR IOV e Windows Server 2012 or Windows Server 2012 R2 is required to use the RoCE features on RoCE capable adapters Enabling the RoCE Profile on the Client Side The RoCE profile can be enabled by using one of the following e PXESelect BIOS See the Boot for NIC iSCSI FCoE and RoCE Protocols User Manual for details on the PXESelect BIOS utility e OneCommand Manager GUI See the OneCommand Manager Application Version User Manual for information about enabling the RoCE profile using the On
30. at the target the driver queues the I O request internally up to aconfigured timeout period This timeout period is known as ETO If the configured threshold for LDTO and ETO is reached and the adapter is still unable to connect to the target the driver fails all I O requests I O errors are seen by the application and operating system Note Following a link up switch ports can take a long time to initialize and go toa forwarding state Because of this add additional time to the ETO and LDTO settings to eliminate I O disruption or target unavailability If the switch port is connected to a single host then PortFast mode can be enabled on the switch port to eliminate delays in transitioning to a forwarding state Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 118 gt EMULEX iSCSI Driver Configuration Configuring LDTO and ETO on the Windows Server LDTO and ETO values are configured using the Advanced tab of the Device Manager Property page Table 3 12 lists the default values of LDTO and ETO on the Windows Server and the configuration limits Note Ifthe ETO is set to a number between 0 and 19 the driver assumes the value of 20 seconds internally The registry is not modified Table 3 12 LDTO and ETO Information on the 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
31. available for I O Emulex Drivers for Windows User Manual P011041 01A Rev A 165 SG EMULEX Appendix A Error and Event Log Information 166 iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID 0x08 Severity Error Message Target with session id N failed to connect within the configured timeout Recommended Resolution A connection to the target was lost for a period exceeding the ETO The error log entry includes the session ID of the target that lost the connection Event log entries from the disk subsystem indicate that the drives were lost If any I O was in progress the system may see I O errors or failures Check the connection to the target or the state of the target device If the target is made available any sessions that previously existed are re established 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 0x0a 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
32. 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 hexadecimal Default 30 0x1E QueueDepth n QueueDepth requests per LUN target see Dynamic QueueTarget parameter If you expect the number of outstanding I Os per device to exceed 32 then you must increase to a value greater than the number of expected 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 QueueDepth supports more than 1000 outstanding commands per port Value 1 254 or 0x1 OxFE hexadecimal Default 32 0x20 QueueTarget QueueTarget controls I O depth limiting on a per Dynamic target or per LUN basis If set to 0 depth limitation is applied to individual LUNs If set to 1 depth limitation is applied across the entire target Value 0 1 or 0x0 0x1 hexadecimal Default 0 0x0 RmaDepth n RmaDepth sets the remote management buffer Reboot queue depth The greater the depth the more concurrent management controls can be handled by the local node Value 8 64 or 0x8 0x40 hexadecimal Default 16 0x10 Note The RmaDepth driver parameter pertains to the functionality of the OneCommand Manager application Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Table 3 1 Storport Miniport D
33. by the OneConnect internally due to a bad firmware If this message is unexpected check unsolicited PDU unsolicited your iSCSI configuration PDUs are PDUs with ITT Oxffffffff Ox3c Warning Connection was invalidated This condition is detected by the OneConnect internally due to a bad WRB firmware If this message is unexpected check index your iSCSI configuration 0x3d Warning Command was invalidated This condition is detected by the OneConnect internally the received firmware If this message is unexpected check command had residual your iSCSI configuration overrun bytes 0x3e Warning Command was invalidated This condition is detected by the OneConnect internally the received firmware If this message is unexpected check command had residual your iSCSI configuration underrun bytes Ox3f Warning Command was invalidated This condition is detected by the OneConnect internally a received PDU had firmware If this message is unexpected check an invalid StatusSN your iSCSI configuration 0x40 Warning Command was invalidated This condition is detected by the OneConnect internally a received R2T had firmware If this message is unexpected check invalid field s your iSCSI configuration 0x41 Warning Command was invalidated This condition is detected by the OneConnect internally the received PDU had an invalid LUN Emulex Drivers for Windows User Manual firmware If this message is unexpected check your iSC
34. created for each VM network Transmit adapters only interface Send and receive Emulex Drivers for Windows User Manual Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 interrupts for a VM network interface are processed on the same CPUs Separate transmit queues increase system overall CPU utilization but offer greater system scalability P011041 01A Rev A gt G EMULEX 3 Configuration NIC Driver Configuration 61 Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition VLAN Not Present default Windows Server 2008 If selected the adapter adds a Identifier 1 to 4094 Windows Server 2008 R2 VLAN tag to all transmitted 802 1q i packets and only receives packets Windows SEVEN 20 lA with the matching VLAN tag Windows Server 2012 R2 Notes e This property must not be used if the Emulex Teaming Driver is enabled In that case VLAN configuration must be performed in the Teaming Driver application e This property must not be used with Hyper V In that case the Microsoft Hyper V Manager must be used to configure VLANs on each virtual machine Wake on LAN Enabled default Windows Server 2008 Enabling Wake on LAN allows the Disabled Windows Server 2008 R2 r to wake ura computer if a magic packet is pas ane indans Server 2012
35. detected at the driver 0x0021 33 Informational Network device is operating in Gen2 For best performance install the mode and installed in a 4x PCle slot adapter in an 8x Gen2 PCle slot Note A 16x slot does 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 adapter in an 8x Genz2 PCle slot PCle slot Note A 16x slot does not provide any additional performance 0x001f 31 Informational The network device is operating in For best performance install the Genl mode and installed in a 8x adapter in an 8x Gen2 PCle slot PCle slot Note A 16x slot does not provide any additional performance Emulex Drivers for Windows User Manual P011041 01A Rev A 158 gt EMULEX Table A 13 NIC Event Log Entries Continued Appendix A Error and Event Log Information NIC Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x001e 30 Informational The network device is operating in For best performance install the Gen1 mode and installed in a 4x adapter in an 8x Genl PCle slot PCle slot Note A 16x slot does 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 adapter in an 8x Genl PCle slot PCle slot Note A 16x
36. 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 the Finish dialog box is displayed The Start AutoPilot Installer box is automatically selected 4 Click Finish AutoPilot Installer runs automatically and completes one of the following installations e Hardware First Installation or Driver and Utility Update page 23 e Software First Installation page 24 Option 2 Run the AutoPilot Installer Separately To access these options run AutoPilot Installer after the driver kit loading has been completed This allows you to change the configuration options supplied to the AutoPilot Installer see below 1 Perform steps 1 through 3 for Option 1 Automatically Run the AutoPilot Installer 2 Clear the Run AutoPilot Installer check box on the Finish dialog box 3 Click Finish The driver kit installer exits After the driver kit loading is complete change the configuration in one of two ways e Change the configuration file See Software Configuration Parameters on page 180 for details Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation gt G EMULEX A
37. driver 188 Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX Command Script Example goto serverlok none if not errorlevel 1248 goto noreport echo No Emulex adapter found goto serverlok noreport if not errorlevel 110 goto nocfg echo Could not open installation report file goto serverlok nocfg if not errorlevel 87 goto badcfg echo Invalid configuration file parameters goto serverlok badcfg if not errorlevel 2 goto serverilok echo No appropriate driver found serverlok remd server2 g autopilot ApInstall ConfigFileLocation g autopilot mysetup apinstall cfg if errorlevel 1 goto server2ok echo AutoPilot reported an error upgrading Server 2 if not errorlevel 2147483650 goto unsupported echo Configuration file missing goto server2ok unsupported if not errorlevel 2147483649 goto older echo Unsupported operating system detected older2 if not errorlevel 2001 goto none2 echo The driver found is the same or older than the existing driver goto server2ok none2 if not errorlevel 1248 goto noreport2 echo No adapter found goto server2ok noreport if not errorlevel 110 goto nocfg2 echo Could not open installation report file goto server2ok nocfg2 if not errorlevel 87 goto badcfg2 echo Invalid configuration file parameters goto server2ok badcfg2 if not errorlevel 2 goto server2ok echo No appropriate driver found server2ok Emulex Drivers for Windows User Manual P0110
38. driver sets double the amount for discovery to complete Value 5 30 seconds or 0x5 0x1E hexadecimal Default 15 seconds OxF Reboot LimTransferSize Limits the maximum transfer size to selectable values if this parameter is non zero Values 0 Port Default 1 64Kb 2 128Kb 3 256Kb Emulex Drivers for Windows User Manual Reboot P011041 01A Rev A 3 Configuration 4Q gt lt EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol LinkSpeed n LinkSpeed has significance only if the adapter Reset FC Only supports speeds other than 1 Gbps Value Auto select 1 Gbps 2 Gbps 4 Gbps 8 Gbps Default Auto select Notes e Setting this option incorrectly can cause the adapter to fail to initialize e If you configure the link speed in a BIOS utility the link speed may be overwritten by the Windows operating system according to its own configuration settings To avoid this issue configure the link speed in both the operating system driver and the Boot BIOS or UEFI driver LinkTimeOut n LinkTimeOut applies to a private loop only A Dynamic timer is started on all mapped targets using the link timeout value If the timer expires before discovery is resolved commands issued to timed out devices returns a SELECTIION_TIMEOUT The Storport driver is notified of a bus change event which l
39. ee es 10 0 1 0 24 0 0 0 0 Onlink route for Blue subnet Remove the locator records for Blue subnet Get NetVirtualizationLookupRecord where VirtualSubnetID eq 5001 Remove NetVirtualizationLookupRecord Remove the customer route records for Blue subnet Get NetVirtualizationCustomerRoute where VirtualSubnetID eq 5001 Remove NetVirtualizationCustomerRoute EFE HEHEHE PE PEHE HEHE PE FE HH HEFE HE HE HHH FE HE HE E HH HERE FE HE E TE FE PE HE HH HE FE HE E TE HE FE HE HE TE HE E HE H HE H E RR RRR RRR RR ERRE H EARTH HH HERE HH HERE Red Virtual Network Information Rout ingDomainID 11111111 2222 3333 4444 000000006001 VirtualSubnetID 6001 Both RDID and VSID are defined by administrators MUST be unique in the datacenter Customer Addresses VM Name Host VSID CA PA MAC DefaultGw ee aa e a E Redl Host1 6001 10 0 0 5 192 x x x 08 08 00 00 00 05 10 0 0 1 Red2 Host2 6001 10 0 0 7 192 x x x 08 08 00 00 00 07 10 0 0 1 Customer Routes DestPrefix NextHopGW Note fhe Ste pio oe a a Be ea ee E E eS Se ee ee eee 10 0 0 0 24 0 0 0 0 Onlink route for Red subnet Remove the locator records for Red subnet Get NetVirtualizationLookupRecord where VirtualSubnetID eq 6001 Remove NetVirtualizationLookupRecord Remove the customer route records for Red subnet Get NetVirtualizationCustomerRoute where VirtualSubnetID eq 6001 Remove NetVirtualizationCus
40. eq 6001 Remove NetVirtualizationLookupRecord Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 86 NIC Driver Configuration gt EMULEX New NetVirtualizationLookupRecord VirtualSubnetID 6001 CustomerAddress 10 0 0 5 ProviderAddress 192 x x x MACAddress 080800000005 Rule TranslationMethodEncap New NetVirtualizationLookupRecord VirtualSubnetID 6001 CustomerAddress 10 0 0 7 ProviderAddress 192 x x x MACAddress 080800000007 Rule TranslationMethodEncap Add the customer route records for Red subnet Get NetVirtualizationCustomerRoute where VirtualSubnetID eq 6001 Remove NetVirtualizationCustomerRoute New NetVirtualizationCustomerRoute RoutingDomainID 11111111 2222 3333 4444 000000006001 VirtualSubnetID 6001 DestinationPrefix 10 0 0 0 24 NextHop 0 0 0 0 Metric 255 2 Configure the Host Provider Addresses and Routes required for this setup Host PA Address amp Route information required by the VM policy Host Hostname PA s VM VirtualSubnetID gt Set on the VMNetworkAdapter on eash host Se me E E i a a a a i ee i i EE ee a es a a ea cen ee ee Hostl example hostl 192 x x x Bluel 5001 Red1 6001 Host2 example host2 192 x x x Blue2 5001 Red2 6001 2 1 Hostl a Configure Provider Address and Route Get the interface assign the PA and the default route Get NetVirtualizationProviderAddress
41. 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 P011041 01A Rev A se Appendix A Error and Event Log Information 143 gt lt EMULEX FC FCoE Error and Event Logs Appendix A Error and Event Log Information FC FCoE Error and Event Logs Viewing the FC FCoE Error Log The system event log is a standard feature of Windows Server software All events logged by the Emulex Storport Miniport will be Event ID 11 with source elxfc elxcna To view the error log 1 Open the Event Viewer window by doing one of the following e Click Start gt Programs gt Administrative Tools gt Event Viewer e Right click My Computer Manage and Event Viewer in Computer Management The Event Viewer window is displayed 2 Double click any event with the source name ELXFC ELXCNA 3 Examine the entry at offset 0x10 and Event ID 11 The Emulex event code is found in byte 0010 and supplementary data is in the byte offsets 0011 through 0013 For example in Figure A 1 byte 0010 9b byte 0011 00 byte 0012 29 and byte 0013 00 Event Properties 2 x Event Date WAAT Source elxstor Time amp 52 19PM Categoyr None Type Error EventID 11 s User N A Bs Computer EMULE
42. gt G EMULEX Emulex Drivers Version 10 4 for Windows User Manual P011041 01A Rev A Connect Monitor Manage gt EMULEX Copyright 2003 2015 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 Emulex BladeEngine Emulex InSpeed Emulex LightPulse Emulex OneCommand Emulex OneConnect and SLI are registered trademarks and Emulex Advanced 8 Emulex Connect Emulex CrossLink Emulex Engine Emulex Edge Emulex ExpressLane Emulex GreenState Network Xceleration Emulex OneCore Emulex Pilot Emulex SURF Emulex Universal Multi Channel Emulex vEngine Emulex Virtual Fabric Emulex Virtual Network Exceleration Emulex vPath Emulex vScale AutoPilot AutoPilot Installer and BlockGuard are trademarks of Emulex All other brands 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 incl
43. in dotted decimal notation Mandatory lt TargetTCPPort gt A decimal number ranging from 1 to 65535 inclusive Optional The default TCP port is 3260 lt LUN gt A hexadecimal representation of the LUN of the boot Optional device By default LUN 0 is assumed to be the boot LUN It isan eight byte number that should be specified as a hexadecimal number consisting of 16 digits with an appropriate number of zeroes padded to the left if required lt TargetName gt A valid iSCSI name of up to 223 characters Mandatory lt initiatorName gt A valid iSCSI iqn name of up to 223 characters If it is Optional not provided the default initiator name generated by the adapter based on its MAC address is used lt HeaderDigest gt Either E the header digest is enabled or D the header Optional digest is disabled lt DataDigest gt Either E the data digest is enabled or D the data Optional digest is disabled lt AuthenticationType gt D authentication is disabled E one way CHAP is Optional Examples enabled the user name and secret must be specified by non DHCP means or M mutual CHAP is enabled the user name and passwords must be specified by non DHCP means D is the default setting The following is an example of default initiator name and data digest settings iscsi 192 168 0 2 3261 000000000000000E ign 2009 4 com 12345 67890 E E e Target IP address 192 168 0 2 e Target TCP port 3261 e
44. iscsi service 1 Select the Emulex OneConnect iSCSI adapter in the Windows Device Manager under Storage Controllers 2 Right click and select Properties The Device Manager Property page opens 3 Select the Advanced tab and make the following changes e LDTO 25 e ETO 50 4 Reboot the system for the changes to take effect 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 Error Handling Under MultiPath MPIO and Cluster Configurations In an MPIO or cluster configuration fault tolerant software is present on the system in addition to the iSCSI driver s default error handling scheme Depending on the type of failover configuration the iSCSI driver s error handling parameter can be configured to modify the timing characteristics of a failover operation If the iSCSI target is in Active Active failover mode the iSCSI driver can be configured to report I O errors as soon as they are detected by setting the iSCSI driver s LDTO and ETO parameters to 0 This allows the failover software to trigger a path failover to an active path or active node as quickly as possible If the iSCSI target is in Active Standby failover mode then the iSCSI driver must wait for the target side failover
45. only once in the APInstall cfg file Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 184 gt EMULEX AutoPilot Configuration 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 180 for information about settings that can 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 can exist in the AutoPilot configuration file The first items in this section are the driver parameters to be used regardless of how the questions are answered This is followed by a subsection that contains questions these may be vendor specific questions A line containing QUESTIONS marks the start of the subsection and the end of it is marked by a line containing TENDQUESTIONS Within the question subsection there can be as many questions as needed Each question uses the format uestion uestion explanation answer0 answerl E AAJ E kei n w L E n wW 0 n AAJ 1 n answer2 answern
46. operation request from the port driver This attempted from the Microsoft WMI application error is immediately followed by resulted in an error Check the operation being another error code entry indicating attempted for user or configuration errors the WMI request code in error 0x33900002 The iSCSI driver failed an I O request This failure occurred due to a failed memory because it failed to retrieve a scatter allocation in the operating system Check low gather list from the Storport driver memory conditions 0x31880001 The iSCSI driver failed to load because This failure may be due to the firmware not initialization failed during a power being present or currently running This failure management bootup may also indicate a hardware issue 0x3184000c The iSCSI driver was unable to map This failure may indicate a low memory one or more PCI Base Address condition or a hardware error Registers and failed to load 0x3184000b The iSCSI driver ignored a The invalid entry must be removed or configuration entry because the entry corrected Check the registry configuration for was invalid any new valid values added to the driver parameters For more information on valid driver values see Table 3 10 iSCSI Driver Options on page 113 0x31840009 The iSCSI driver failed to load a The range specified for a configuration configuration value specified in the parameter is too large or too small and must be registry because the value was out of corre
47. profile profile selected select the RoCE 2 profile 0x3C 60 Warning The adapter ran out of Reduce the connection count to a resources while creating the supported value requested number of SMB Direct connections Reduce the connection count to a supported value 0x3B 59 Warning RoCE is not enabled Update Update the firmware and ensure that the firmware and ensure that the RoCE 2 profile is selected in the the RoCE 2 profile is OneCommand Manager application the selected OneCommand Manager CLI or the PXESelect utility Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX NIC Event Log Appendix A Error and Event Log Information 156 NIC Error and Event Logs Windows Device Manager generates error log codes if any errors occur during the installation of the NIC driver Each log contains a Message ID Severity and Symbolic Link The Message ID is unique and tracks the error message if not displayed Table A 13 shows the list of error codes the severity of the error the message displayed the meaning of the error and recommended resolutions When reporting an issue with the adapter to Emulex check the event log and report any of these entries that are displayed Table A 13 NIC Event Log Entries Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x80000039 Warning Firmware does not support GRE Issue configuring NVRE hardware encapsulation Encapsu
48. rops on the network The switc Windows Server 2012 or network peer must also have Rx Enable Tx Disable windows Server 2012 R2 flow control enabled Tx Enable Rx Disable 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 if receive buffer space is exhausted The network device can be configured to respond to pause frames Rx Enable and also to send pause frames Tx Enable IP Checksum _ Disabled Windows Server 2008 This offloads the transmit and the Offload IPv4 RX and TX Enabled Windows Server 2008 R2 eae i checksum default Windows Server 2012 eae a r RX Enabled Windows Server 2012 R2 a A Miereaes TX Enabled Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX 3 Configuration 48 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Large Send Offload v1 IPv4 Acceptable Values Disabled Enabled default Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets lt Packet Size that can be transmitted This
49. sacrificing throughput These are applications that typically do not pre post receive buffers at a rate fast enough to keep up with the traffic flow causing the received data to be buffered until the application has pre posted a receive buffer Some applications intentionally are written this way to peek at incoming data to determine how large of a receive buffer to post The timings of such a usage semantic in some cases depending on factors such as CPU Memory performance line rates the sizes of the receive buffers and system loading at the time will result in no observable performance improvement Emulex recommends that you leave this parameter set to the default of Optimize Throughput Windows Networking and TOE If certain Windows Server 2008 and Windows Server 2008 R2 networking features are enabled TOE does not operate as expected and connections are not offloaded Installing or activating firewall applications causes no connections to be offloaded by the Windows Server 2008 and Windows Server 2008 R2 network stack By default Windows Firewall Services are enabled at operating system installation time and they must be explicitly disabled in order to use TOE Firewall services can be disabled Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 110 gt EMULEX NIC Driver Configuration through the Service Control panel or the following commands at the command line prompt To set firewall ser
50. sane UNEE EAEEE EREE URETA 26 Manually Installing or Updating the Emulex Protocol Drivers ccccccseeesseeesseeenaes 26 Installing the Emulex PLUS ElxPlus Driver for the First Time ccce 27 Updating the Emulex PLUS EIXPIUS Driver ssssssssssrrrrrersresrrsrrrerrerererrrrrne 27 Installing or Updating the FC FCoE Storport Miniport Driver cccceeeeeeeeeee eee 28 Installing or Updating the iSCSI Driver cccccccce cece eee eeeeeeeeeeeeeaeeeeaeeeenee eens 29 Installing or Updating the NIC Driver cccccccecese eects sense sense eeaeeeeneenenaeeeas 29 Windows Server 2008 ae nie a Ea AAEE EAA ERDRE AERE sar TEE EERTE 29 Windows S rver 2012 iiedcsciwd Gadineaure EEEE EN STE ETE EENS 30 Removing Emulex Driver Kits and DriverS ssssussssnsnnssnsnnnnnnnnnnnnnnnnnnnnnnnnnnnn 31 Uninstalling Emulex Driver KItS ssssssssssrrrrrerrrrsrsrrrrrrrrrresrrsrrrrrrerrrerrrrrr 31 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 SXC EMULEX Table of Contents Windows Server 2008 wic ci s c8niscevader sis Sadsde noted Tei i i a a e Ee E 31 Windows Server 2012 0csc cernar niani aE Aa EEE EEE AET REEE iE 32 Uninstalling the Emulex Drivers cccccececce eee eee eee eee sete neater enter ete 32 Windows Server 2008 wi ccssccvriasenniaceredavnieantaddaietiaasaws anid nannaladtvaateabaneussanees 32 Windows Server 2012 eisie anaiei o sags deeaekataseagesss saa taetear aa bassendscaaseacuadaneea 33 3 Conf
51. segmentation increases transmit efficiency for TCP applications that send large buffers During segmentation the hardware computes the IPv4 and TCP checksums for each individual packet The Windows Version 1 LSO supports only IPv4 Large Send Offload v2 IPv4 Disabled Enabled default Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets lt Packet Size that can 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 2 LSO supports larger offload sizes Large Send Offload v2 IPv6 Disabled Enabled default Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Large Send Offload allows the NIC hardware to segment large TCP packets up to 64kB into smaller packets less than the MTU that can 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 Server 2008 and later Maximum Number of RSS Processors Min 0 Max The number of CPU
52. several jambo 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 63 The path MTU is the maximum MTU that can be used before IP fragmentation occurs taking into account the MTU for the endpoints and all routers between the endpoints To verify the path MTU ping a remote target with an increasing payload size Eventually the IP packet length exceeds the path MTU and the packet fragments This can be seen by using a packet sniffing application such as Ethereal Wireshark or Microsoft Network Monitor IP fragmentation degrades performance dramatically because all fragments must be received and reassembled before delivering the network packet to the upper layer protocol In many cases IP fragmentation can lead to a 10x performance degradation The MTU parameter must be modified on all systems to avoid IP fragmentation for optimal network throughput Typical cases for using the MTU e Server interconnects are typically deployed using jumbo frames This is the most efficient configuration for high band
53. the APArgs directive AutoPilot Installer Syntax The syntax used to run AutoPilot Installer silently from a command line or script is APInstall silent parameter setting parameter setting The silent switch and parameter settings can occur in any order One or more spaces must separate the switch and each parameter setting The syntax of a parameter setting is parameter name value Double quotes are required only around values that contain spaces Spaces can separate parameters equal signs and values Parameter names and values are not case sensitive The APInstall command can contain the settings listed below Each setting except ConfigFileLocation can also be specified in the AutoPilot Configuration file For descriptions of each parameter see Software Configuration Parameters on page 180 Settings specified in the APInstall command override those specified in the configuration file ConfigFileLocation path specifier NoSoftwareFirstInstalls TRUE FALSE SilentRebootEnable TRUE FALSE ForceDriverUpdate TRUE FALSE ForceDriverTypeChange TRUE FALSE SkipDriverInstall TRUE FALSE InstallWithoutQFE TRUE FALSE ForceRegUpdate TRUE FALSE LocalDriverLocation path specifier ReportLocation path specifier Path Specifiers Paths can be specified as e an explicit path ReportLocation C Program Files Emulex AutoPilot Installer Reports e
54. the appropriate bandwidth to PG 1 for example 90 3 Create PG 2 or something different from above which is priority group 1 and assign NIC traffic to it 4 Assign remaining bandwidth to PG 2 5 Enable priority flow control on all ports participating in the cluster and at a global level in the switch Note Some switches have global and port level settings for flow control and bandwidth allocation Make sure the PFC flow control setting is performed on all the ports that participate in the cluster 6 Configure a valid VLAN with an ID other than 0 or 1 7 Ensure that Jumbo Frames is enabled or at minimum set the MTU gt 4200 Emulex Drivers for Windows User Manual P011041 01A Rev A sc Appendix E RoCE Switch Support 19 gt C EMULEX DCBX Enabled Switch Connection PFC Mode 8 Specify each switch port service policy rather than using the system QoS Notes e Some switches have jumbo frame size support disabled on the port and global level by default e Some switches show the priority for FCoE on the switch itself Use a policy with zero bandwidth for the FCoE priority Host Client Configuration For all host and clients participating in the network 1 Create a VLAN using the VLAN ID you configured in step 6 above 2 Assign an appropriate IP address to the VLAN interface Note Ensure that all the traffic is flowing through the VLAN interface DCBX Disabled Switch Connection Generic Pause Mode 1 Host C
55. the computer system is sending or receiving IP fragments This is a serious performance issue See J umbo Packet on page 103 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 or checksum offloads and use jumbo packets J umbo Packet The jumbo packet setting in the registry determines the maximum Ethernet packet size It includes the Ethernet frame header typically 14 bytes but excludes the trailing CRC The standard packet size is 1514 bytes plus a 4 byte trailing CRC Vendors use many terms that refer to this same quantity such as packet size frame size or MTU The MTU is the Ethernet packet payload size This does not include the Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX 3 Configuration 104 NIC Driver Configuration 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
56. 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 Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 21 gt lt EMULEX AutoPilot Installer Note Silent installation mode Suppresses all screen output necessary for unattended installation AutoPilot Installer does not allow you to install the driver if the minimum Windows service pack or Microsoft Storport driver update is not installed You can install a driver by any of the following methods Note Note These methods are not mutually exclusive Hardware first installation At least one Emulex adapter must be installed before you can install the Emulex drivers and utilities 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 After you install the adapters Utility only installation If the drivers in the driver kit share the same version with those already installed on the system you can rein
57. the scope of this document and is not included The adapter offers this Vendor ID to the DHCP server to retrieve data in the format described in this section Format of Vendor Specific Option 43 The following describes the format of option 43 and includes guidelines for creating the data string iscsi lt TargetIP gt lt TargetTCPPort gt lt LUN gt lt TargetName gt lt InitiatorName gt lt HeaderDigest gt lt DataDigest gt lt AuthenticationType gt 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 can be skipped e If an optional field is skipped a colon must be used as a placeholder to indicate the default value for that field e If specified the value of each parameter should be enclosed in double quotes See Examples on page 175 e All options are case sensitive Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Appendix B Configuring iSCSI through DHCP 175 Dynamic Host Configuration Protocol DHCP Recommendations Description of Mandatory and Optional Parameters Table B 1 describes the parameters used in the data string for option 43 Table B 1 Data String Parameters for Option 43 Parameter Description Field Type lt TargetIP gt A valid IPv4 address
58. to limit an SMB connection to specific network interfaces For example if you have a 1GbE interface meant for a management path and one or more 10GbE interfaces meant for the RDMA traffic you can restrict the RDMA traffic to the faster 10GbE interfaces by setting SMB multichannel constraints You can specify SMB multichannel constraints on the SMB client by doing the following e Use only certain RDMA network interface s to access a particular server e Ensure that only ConnectionCountPerRdmaNetworkInterface connections are created per RDMA network interface to a given server Figure 3 15 on page 95 shows that an SMB multichannel constraint has been added to specify that only InterfaceIndex 25 must be used to connect to the server bench29client1 Two SMB Direct connections are established on the ROMA Network Interface with IfIndex 25 None are established on the other OCe14000 series adapter ports for example the RDMA Network Interface with IfIndex 26 20 2 0 110 Note On Windows Server 2012 depending on the path used to open the previous SMB sessions to the SMB server you may notice multiple instances of ConnectionCountPerRdmaNetworkInterface connections being created while establishing a single SMB session to the server Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q5 gt EMULEX NIC Driver Configuration Are you sure you want to perform this action Performing operati
59. where _ ProviderAddress eq 192 x x x Remove NetVirtualizationProviderAddress Siface Get NetAdapter SWNVNIC New NetVirtualizationProviderAddress InterfaceIndex Siface InterfaceIndex ProviderAddress 192 x x x PrefixLength 24 b Set VirtualSubnetID on the VM network port Get VMNetworkAdapter Bluel where MacAddress eq 060600000005 Set VMNetworkAdapter VirtualSubnetID 5001 Get VMNetworkAdapter Redi where MacAddress eq 080800000005 Set VMNetworkAdapter VirtualSubnetID 6001 Example of a Script Removing the NVGRE Tunnel Between Two Hosts FEFEFE HEHE HEHEHE HEHEHE FE HH HE HE FE HE HHH HE HE HE HE HH FE HE E HE HE FE HE HE TE FE FE HE HH HE FE HE HE HE HE FE HE HE TE HE FE HE HE TE HE FE HE E E HE E HE RH H HHR H HHRHH HHHH HEEE EHEHEH E HEE H HH EE HH HHHH HH Blue Virtual Network Information Rout ingDomainID 11111111 2222 3333 4444 000000005001 VirtualSubnetID 5001 Both RDID and VSID are defined by administrators MUST be unique in the datacenter Customer Addresses VM Name Host VSID CA PA MAC DefaultGw Bluel Hostl 5001 10 0 0 5 192 x x x 06 06 00 00 00 05 10 0 0 1 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 87 gt EMULEX NIC Driver Configuration Blue2 Host2 5001 10 0 0 7 192 x x x 06 06 00 00 00 07 10 0 0 1 Customer Routes DestPrefix NextHopGW Note a ty ty ki a Na a a a a a a a i a a a a a a a el ee
60. 00 series adapters support a maximum of 24 virtual functions per port o OCel4000 series adapters support a maximum of o 2 port 10 Gb 31 virtual functions physical function o 4 port 10 Gb 31 virtual functions physical function o l port 40 Gb 63 virtual functions physical function Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX 3 Configuration 57 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition TCP Checksum Disabled Windows Server 2008 TCP Checksum Offload IPv4 Offload IPv4 py and TX Enabled Windows Server 2008 R2 offloads the transmit or receive default IPv4 TCP checksum computation RX Enabled Windows EENE Offloading checksums increases able Windows Server 2012 R2 system efficiency TX Enabled TCP Checksum Disabled Windows Server 2008 TCP Checksum Offload IPv6 Offload IPv6 RX and TX Enabled Windows Server 2008 R2 Offloads the transmit or receive default IPv6 TCP checksum computation RX Enabled Windows An Offloading checksums increases nable Windows Server 2012 R2 system efficiency TX Enabled Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX 3 Configuration 58 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2
61. 0005 Both Port 0 and Port 1 links were down Check the links to the adapter If the link is for a period exceeding the LDTO If re established any sessions that previously the adapter has a connection to the _ existed are re established and the devices are target there will be event log entries available for I O from the disk subsystem indicating that the drives were lost If any I Os were in progress the system may see I O errors or failures 0x11800003 Both Port 0 and Port 1 links are down Check the links to the adapter 0x31840005 Driver load failed because the PCI Check the configuration on the adapter Vendor ID and Device ID are not supported Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix A Error and Event Log Information gt lt EMULEX iSCSI Error and Event Log Table A 14 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x1180000A The logical link on the OneConnect The iSCSI function may have been disabled in Port is down traffic is disallowed on the PXESelect utility If you disabled it this function intentionally you can ignore this message Viewing the iSCSI Error Log on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Window Server 2012 R2 The iSCSI driver on the Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 o
62. 01A Rev A 3 Configuration 101 DG EMULEX NIC Driver Configuration NPar Partition Support Flexible bandwidth allocation with no changes required for the operating system or BIOS The switch is independent changes to the external switch are not required NIC teaming is supported The following items are supported on a per partition basis Statistics LSO LRO RSS TSO and MTU Support for NetQueues NPar Considerations Note NPar can use virtual adapters using VLAN tagging per partition NPar can use RSS queuing support per partition DCBX is supported while in NPar mode If iSCSI or FCoE functions are not enabled they are available as NIC functions Only one iSCSI function is allowed per physical port Only one FCoE function is allowed per physical port The second to fourth functions on a particular port are available for storage protocols if desired allowing you to configure up to two storage functions If NParEP is disabled a total of eight functions are available evenly distributed across the ports on the adapter For example a 2 port adapter can have four functions per port and a 4 port adapter can have two functions per port A system reboot is required if any of the NPar function mode settings are modified A reboot is not required for bandwidth and MTU settings modifications Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX 3 Configuration 102 NIC Driver Configuration Network
63. 1 01A Rev A gt G EMULEX 3 Configuration NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name RSS Profile Acceptable Values Closest processor default Closest processor static NUMA scaling NUMA scaling static Conservative scaling Supported Operating Systems Windows Server 2012 Definition The RSS Profile setting determines the RSS load balancing profile implemented by Microsoft for this network adapter The Closest Processor settings tend to localize the RSS CPUs to one NUMA node allowing the device driver to allocate memory from the local node The NUMA Scaling settings use all NUMA nodes on the system and the memory allocation is not specific to a particular node The driver ignore s the Preferred NUMA node setting SpeedDuplex AutoNeg default 10GbpsFullDuplex 1GbpsFullDuplex Emulex Drivers for Windows User Manual Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 SpeedDuplex is used for selecting link speed mainly for LOGBASE T adapters If it is set to the default it auto negotiates 100 Mbps 1 Gbps 10 Gbpswiththe switch peer Link speed can be forced to 1 Gbps if option 1GbpsFullDuplex is selected Link speed can be forced to 10 Gbps if option 10GbpsFullDuplex is selected 10 Gbps is the
64. 1 3 are analogous 8 Value 0 3 Default 2 0x2 Emulex Drivers for Windows User Manual Reset FC Only P011041 01A Rev A S lt 3 Configuration 43 EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol TraceBufSiz n TraceBufSiz sets the size in bytes for the internal Reboot driver trace buffer The internal driver trace buffer acts as an internal log of the driver s activity Value 250 000 2 000 000 or 0x3D090 0x1E8480 hexadecimal Default 250 000 0x3D090 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 depends 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 provides better throughput With I O Coalescing turned off the default setting each I O processes immediately one CPU interrupt per I O For systems with light loads the default setting provides better throughput Table 3 2 shows recommendations based upon the number of I Os per adapter Table 3 2 Recommended Settings for I O Coalescing I Os per Second Suggested CoalesceMsCnt Suggested Coalesce
65. 102 Optimizing Server Hardware and BIOS Configuration e cee eeee cette eee e eee 102 Windows Server Network Driver sssssissssssrisrstttti rin nn ttrt nee 102 NUMA Considerations for Windows Server 2012 R2 cccccceeceeeeteneeeceeeeeeeeneeaes 105 Checksum Offloading and Large Send Offloading LSO cccceceeeeeeeeeeeeeeaeees 106 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic 0 000 106 RCP Offloading TOE sc cisicnssctadecianaorscadcuataur a aE R e E A ENES 107 Receive Window Auto Tuning and Compound TOP sssssssssssssssrseereerererrrerrrrrere 110 Interrupt Coalescing ssssssssssssssssrsrrestrtttt eee ttrt ttt ttrt ettr EErEE EEEEEEEEEEEEEEEEEE 110 CPU Binding Considerations cect entered 111 Single TCP Connection Performance SettingS ccccccee eee e cece e eed 111 SCSI Driver Configuration ccciscsccscsstacssssccsteccsnscesasecssreceatesssrecsssesesccaessesesecs 112 Configuring iSCSI Driver OptiOns sec cisiscceesvssessecesssstseusesssaesasaaesedseesared ease 112 Interrupt Moderation Policy SettingS cccccccceecceeeeeee esses essen eeeeeeeeaeeeenae es 114 Creating Non Bootable Targets s ceiiistisiwedsasstiavornivsiitiewiarssiareiadssvereiuerann 114 Using the Microsoft iSCSI Initiator Service 0 eect eter 114 Logging into a Target Using the Microsoft Software Initiator cccccceeeseeeee ees 115 Windows Multipath I O Support s
66. 16 default 8 configuration 0Cel14000 Min 1 Max 16 default 8 Maximum RSS Min 1 Windows Server 2008 This parameter sets the maximum ine ety Max The number of CPU Windows Server 2008 R2 Pole TET oo RSS umber cores installed on your s This is the highest processor system j Windows POVAT ANL number of any processors from the Windows Server 2012 R2 RSSMaxProcGroup parameter Network Valid MAC address Windows Server 2008 This overrides the permanent MAC Address address for the interface The MAC The default setting is None Emulex Drivers for Windows User Manual Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 address must follow this format XX XX XX XX XX XX where X isa hexadecimal 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 P011041 01A Rev A gt G EMULEX 3 Configuration 50 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Acceptable Values 0 Disabled 1 Enabled default NetworkDirect Supported Operating Systems Windows Server 2012 R2 Definition The Network Direct feature enables an offloaded RDMA interface for SMB 3 0 network attached s
67. 170 Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID Severity Message Recommended Resolution 0x27 Error Firmware returned invalid Reload the firmware data in its configuration iSCSI login and offload are disabled 0x28 Warning Error Recovery is not being An unrecoverable error has occurred but error attempted Adapter is no recovery is not enabled A system reboot is longer functional required to make the adapter operational again 0x2b Informational The storage device is Informational message that provides the slot operating in Gen x gt mode capabilities where the iSCSI adapter is and installed in a lt yy gt x PCle installed slot 0x2c Error The firmware appears The adapter is no longer functional A system unresponsive Unrecoverable reboot is required to make the adapter Error operational again Ox2d Informational Reporting X of the total Y Informational event to indicate that not all sessions logged in by targets logged in by the firmware were firmware reported as available to the operating system If the total number of targets logged by the firmware is over the specified limits this error can be ignored Ox2f Warning Solicited command was This condition is detected by the OneConnect invalidated internally due to a firmware If this message is unexpected check
68. 172 SG EMULEX Appendix A Error and Event Log Information 173 iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID 0x4f Severity Warning Message Connection was invalidated internally due to an incoming unsolicited PDU that had immediate data on the connection that does not support it Emulex Drivers for Windows User Manual Recommended Resolution This condition is detected by the OneConnect firmware If this message is unexpected check your iSCSI configuration P011041 01A Rev A gt lt EMULEX Appendix B Configuring iSCSI through DHCP 174 Dynamic Host Configuration Protocol DHCP Recommendations Appendix B Configuring iSCSI through DHCP Dynamic Host Configuration Protocol DHCP Recommendations If you are using the DHCP server to obtain an IP address for the adapter Emulex recommends that you set up a reservation A reservation assigns a specific IP address based on the MAC address of the adapter If you do not reserve an IP address through DHCP then you must set the lease length for the adapter 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 of
69. 4 and 512 are accepted the memory used by the driver is the same as is used if large_io is set to 512 LDTO 20 seconds 0 seconds 3600 seconds LDTO in seconds This parameter determines the amount of time the driver waits for the controller s physical link to be available before reporting that the LUNs are unavailable to the operating system Iqd 128 Emulex Drivers for Windows User Manual 255 The LUN queue depth parameter configures the number of concurrent commands to a logical unit via Storport API StorPortSetDeviceQueueDepth The lqd parameter also sets the maximum number of concurrent commands allowed per LUN P011041 01A Rev A 3 Configuration gt lt EMULEX iSCSI Driver Configuration i Interrupt Moderation Policy Settings The Interrupt Moderation policy settings control the rate of interrupts for adapter hardware By default the driver implements an interrupt moderation scheme that is based on the I O load and the interrupt rate The default setting for im_policy tries to vary the interrupt rate between 3500 to 10000 interrupts per second In addition the iSCSI driver allows other configuration settings as shown in Table 3 11 Table 3 11 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 im_policy 2 Moderate The default value
70. 41 01A Rev A 189 sc Appendix E RoCE Switch Support 19Q gt C EMULEX DCBX Enabled Switch Connection PFC Mode Appendix E RoCE Switch Support Some switches do not support DCBX and most DCBX enabled switches do not fully support RoCE as a protocol At this time none of the known switch vendors Arista Brocade Cisco and Juniper allow configuring priority for RoCE specific traffic Additionally most of the known switch vendors do not support APP TLV of 0x8915 for RoCE ETS bandwidth and PFC configuration DCBX Enabled Switch Connection PFC Mode Manually enable priority 5 on the switch under a different priority group other than FCOE ISCSI NIC priority group Notes e If an OCe14000 series adapter is connected to a DCBX enabled switch the mode shifts from generic pause to PFC mode e If an OCe14000 series adapter is connected to a DCBX disabled switch generic pause mode is enabled e In absence of priority 5 on the switch side the OCe14000 series adapter maintains configuration for RoCE and PFC priority 5 This can result in packet losses unrecoverable errors or infinite retries for RoCE traffic Switch Configuration for PFC Priority 5 Using the documentation provided by your switch vendor configure your switch for the following e Priority pause frames using Priority 5 e MTU size of 4200 or higher e No drop policy To configure the switch 1 Create PG 1 as Priority 5 with a no drop policy for RoCE traffic 2 Assign
71. A Rev A gt EMULEX 3 Configuration 67 NIC Driver Configuration Table 3 4 NIC Driver Properties Statistics Continued Statistic Name Receive Packets Description The total number of packets received This includes both RSS and non RSS packets RSS Receive Packets The number of receive packets that were suitable for RSS Transmit Flow Control Pause Requests The number of times the network adapter sent a PAUSE frame to request that the peer stop sending data temporarily This indicates a potential bottleneck in the system Typically this bottleneck is the result of the DMA of packets from the adapter to host memory Receive Flow Control Pause Requests The number of times the network adapter received a PAUSE frame from the peer This indicates a potential bottleneck in the attached switch or network peer device This statistic only increments if the switch is correctly configured for flow control TCP Offloads Current Established The current number of TCP connections offloaded to the adapter s TOE TCP Offloads The total number of TCP connections that have been offloaded since the last statistics reset or the driver was reloaded TCP Offload Retransmits The number of packets retransmitted for TCP offloaded connections TCP Offload Receive Drops The number of packets dropped by in the offloaded TCP stack These drops may be the result of TCP protocol errors or bottlenecks
72. AMD Vi AMD I O Virtualization Technology or IOMMU Emulex PXESelect Configuration for SR lIOV The Emulex OCe11000 series adapters requires enabling firmware support for SR IOV within the Emulex PXESelect BIOS See the Boot for NIC iSCSI FCoE and RoCE Protocols User Manual for more information To enable firmware support in the PXESelect BIOS 1 Press lt Ctrl P gt during the Emulex PXE Select splash screen as the server boots A screen appears showing global options 2 Set the following options to use SR IOV Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration DG EMULEX NIC Driver Configuration 79 e Advanced mode Enable e Universal Multichannel UMC Disable 3 Save the settings and enable SR IOV for each PCI function The server reboots after this modification SR IOV Server Validation Use the following Microsoft PowerShell commands to determine if your server is capable of SR IOV e Get NetAdapterSriov e Get VmHost e Get VmNetworkAdapter e Get VmSwitch See the Microsoft documentation for more information Note Early SR IOV capable chipsets had errors that may prevent SR IOV from operating in Windows Server 2012 and Windows Server 2012 R2 The PowerShell command Get VmHost fl includes IovSupportReasons that indicates if the chipset suffers from this issue Enabling SR IOV on Unqualified Servers If Windows Server 2012 or Windows Server 2012 R2 detects an iss
73. CORE system this will install the OneCommand Manager Core Kit OMCORE 1 Install the OneCommand Manager Core Kit only To install the drivers using Silent Mode 1 Download the Onelnstall package from the Emulex website 2 Opena DOS window 3 Change directory to the folder containing your Onelnstall package The following are examples of silent mode commands Start Start Start Start Start Start wait OneInstall Setup 10 wait OneInstall Setup 10 wait OneInstall Setup 10 wait OneInstall Setup 10 wait OneInstall Setup 10 wait OneInstall Setup 10 Driver Kit Installer Each driver kit contains and loads all the Windows drivers for a specific protocol and includes ElxPlus FC driver package elxdrvr fc lt version gt exe A A A A A A 94 94 94 94 94 94 A A A A A A exe rexe sexe sexe sexe exe q2 q2 q2 q2 q2 q2 FCoE driver package elxdrvr fcoe lt version gt exe iSCSI driver package elxdrvr iscsi lt version gt exe Emulex Drivers for Windows User Manual ALL 1 DRIVERS 1 FCOE 1 NIC 1 OCM 1 ALLCORE 1 OCMCORE 1 P011041 01A Rev A 2 Installation gt G EMULEX AutoPilot Installer 20 e NIC RoCE driver package elxdrvr nic lt version gt exe Note Updating the NIC protocol driver can temporarily disrupt operation of any NIC teams configured on the system Loading the Driver Kit The driver kit copies the selected Emulex drivers and appl
74. 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 on page 22 3 When the AutoPilot Installer Welcome page appears select an adapter in the list and click Next The installation continues Consider the following e If you are updating the driver the existing port settings are used unless otherwise specified in the AutoPilot Installer configuration file These settings are pre selected but can be changed Set or change the settings then click Next e If you are initially installing a vendor specific version of the Emulex driver installation program a Driver Configuration page may be displayed This page includes one or more windows with questions that you must answer before continuing the installation process In this case answer each question and click Next on each window to continue Emulex Drivers for Windows User Manual P011041 01A Rev A 23 2 Installation 24 gt lt EMULEX AutoPilot Installer 4 Click Next The installation is completed automatically A dialog box is displayed if Windows requires a reboot After the installation has completed successfully the Finish dialog box appears 5 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory configuration information and task results e Print Installation
75. 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 dual channel adapter models are displayed in Device Manager as two adapters therefore you must update each adapter Select Install from a list or specific location Advanced and click Next Select Don t search I will choose the driver to install and click Next Click Have Disk and direct the Device Wizard to the location of be2iscsi inf If you have installed the driver installer kit in the default folder the path is C Program Files Emulex AutoPilot Installer iSCSI Drivers Storport x64 Windows Version Click OK Select Emulex OneConnect OCm lt your adapter model gt iSCSI Initiator Click Next Click Finish The driver installation has completed The driver will start automatically Installing or Updating the NIC Driver Note The Microsoft patch KB2846340 must be installed on your system This patch from Microsoft s Knowledge Base KB is available for Windows Server 2012 Windows Server 2008 R2 and Windows Server 2008 SP2 on the Microsoft website Windows Server 2008 1 2 Select Start gt Settings gt Control Panel gt Device Manager Open the Network Adapters item Emulex Drivers for Windows User Manual P011041 01A Rev
76. Connect completion with data PDU firmware If this message is unexpected check index your iSCSI configuration 0x48 Warning Command invalidation This condition is detected by the OneConnect completion notification firmware If this message is unexpected check your iSCSI configuration 0x49 Warning Unsolicited header This condition is detected by the OneConnect notification firmware If this message is unexpected check your iSCSI configuration Ox4a Warning Unsolicited data notification This condition is detected by the OneConnect firmware If this message is unexpected check your iSCSI configuration 0x4b Warning Unsolicited data digest This condition is detected by the OneConnect warning notification firmware If this message is unexpected check your iSCSI configuration 0x4c Warning TCP acknowledge based This condition is detected by the OneConnect notification firmware If this message is unexpected check your iSCSI configuration 0x4d Warning Connection was invalidated This condition is detected by the OneConnect internally the command and firmware If this message is unexpected check data were not on the same your iSCSI configuration connection Ox4e Warning Solicited command was This condition is detected by the OneConnect invalidated internally due to DIF warning Emulex Drivers for Windows User Manual firmware If this message is unexpected check your iSCSI configuration P011041 01A Rev A
77. Data Digest error the iSCSI configuration 0x30 Warning Connection was invalidated This condition is detected by the OneConnect internally the received PDU firmware If this message is unexpected check size was greater than the DSL the iSCSI configuration 0x31 Warning Connection was invalidated This condition is detected by the OneConnect internally the received PDU firmware If this message is unexpected check sequence size was greater the iSCSI configuration than the FBL MBL 0x32 Warning Connection was invalidated This condition is detected by the OneConnect internally a received PDU firmware If this message is unexpected check HDR had AHS the iSCSI configuration 0x33 Warning Connection was invalidated This condition is detected by the OneConnect internally due to a Header firmware If this message is unexpected check Digest warning the iSCSI configuration 0x34 Warning Connection was invalidated This condition is detected by the OneConnect internally due to a bad opcode firmware If this message is unexpected check in the PDU header the iSCSI configuration 0x35 Warning Connection was invalidated This condition is detected by the OneConnect internally due to a received ITT TTT that did not belong to this connection Emulex Drivers for Windows User Manual firmware If this message is unexpected check the iSCSI configuration P011041 01A Rev A SG EMULEX Appendix A Error and Event Log Informat
78. Driver Performance Tuning This section describes the tuning and configuration of the network drivers Optimizing Server Hardware and BIOS Configuration Adapter performance can be improved by selecting a more efficient PCIe packet payload size If the system BIOS allows selection of a larger PCIe packet size selecting at least a 512 byte PCIe packet payload size provides the best efficiency for PCIe data transfers This may be an option in the server s system BIOS The current value is displayed in Device Manager on the Status property page for the adapter Most computers offer multiple distinct memory channels which must be configured for channel interleaving for optimal performance Optimal interleaving is achieved by using the exact same DIMM configuration for each memory channel Check the manufacturer s documentation and BIOS parameters for details about optimizing memory bandwidth Typically all of the DIMM slots must be populated to make use of all memory channels As a general rule more DIMMs provide better performance by allowing a higher degree of memory access interleaving to occur However some servers decrease the memory speed if using more than two DIMMs per memory channel so it is important to consider the trade off for a particular server platform Some servers may allow memory mirroring or memory sparing where the total memory is divided in half and each location is stored twice This allows fault recovery if one memory loca
79. IOV using the OneCommand Manager application see the OneCommand Manager Application User Manual or the OneCommand Manager Command Line Interface User Manual NPar enables you to divide a 10GbE NIC port into multiple PCI functions with flexible bandwidth capacity allocation that appears to the operating system and network as separate NIC ports For example a single 1OGbE port appears as multiple physical devices showing in PCI configuration space as multiple functions Adapter Configuration NPar can be configured on OCe14000 series adapters in several ways including the Emulex adapter driver properties the adapter BIOS or using the OneCommand Manager application See the Boot for NIC iSCSI FCoE and RoCE Protocols User Manual for information on configuring the adapter BIOS If you are using the OneCommand Manager application see the OneCommand Manager Application User Manual On the host operating system side NPar provides up to 16 PCI functions per device using standard PCI configuration space if NParEP is enabled Four PCI functions can be mapped to a physical port on a 4 port adapter Eight PCI functions can be mapped to a physical port on an 2 port adapter Each function or partition is assigned a unique MAC address Partitions are available for virtual function assignment and for application segmentation using VLAN or IP subnets The partitions can be on separate subnets or VLANs Emulex Drivers for Windows User Manual P011041
80. M VMQ VPN vPort WMI WWN WWNN WWPN XRI 1 Introduction 16 Abbreviations receive side scaling receive selective acknowledgement storage area network serial attached SCSI Small Computer System Interface small form factor pluggable Service Level Interface Server Message Block Single Root I O Virtualization Secure Shell network Transmission Control Protocol TCP over Internet Protocol TCP Offload Engine TCP segmentation offload transmit User Datagram Protocol Unified Extensible Firmware Interface Universal Multi Channel virtual function virtual local area network VLAN identifier virtual machine virtual machine queue virtual private network virtual port Window Management Instrumentation world wide Name World Wide Node Name World Wide Port Name extensible resource indicator Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 17 gt lt EMULEX Onelnstall Installer 2 Installation You can install the Windows drivers in two ways Notes Onelnstall Installer contains all the Emulex Windows drivers Emulex Storport Miniport and NDIS Miniport drivers and the OneCommand Manager application in a single download package Driver kits and AutoPilot Installer provide installation options ranging from simple installations with a few mouse clicks to unattended installations that use predefined script files and text only installations If you are installing the NIC driver kit as a
81. 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 OxE1 Failed to authenticate remote Did in bits 8 31 OxE2 Authentication not support remote Did in bits 8 31 OxE3 Authentication ELS command timeout remote Did in bits 8 31 OxE4 Authentication transaction timeout remote Did in bits 8 31 OxE5 LS RJT other than Logical Busy received for Authentication transaction remote Did in bits 8 31 OxE6 LS RJT Logical Busy received for Authentication Transaction remote Did in bits 8 31 OxE7 Emulex Drivers for Windows User Manual P011041 01A Rev A Received Authentication Reject other than Restart remote Did in bits 8 31 149 gt EMULEX Appendix A Error and Event Log Information 150 FC FCoE Error and Event Logs Table A 4 Event Indications Continued Bits 0 7 OxE8 Interpretation Received Authentication Reject Restart remote Did in bits 8 31 OxE9 Received Authentication Negotiate remote Did in bits 8 31 OxEA Authentication spurious traffic remote Did in bits 8 31
82. RSS or TCP offloading choose the DPC processor The driver uses multiple parallel DPCs that are explicitly assigned to particular CPUs for processing both RSS and TCP offloading tasks Each TCP connection is assigned to a particular CPU for processing This provides the advantage of assigning CPU affinities by reducing CPU cache misses without any user configuration 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 can be controlled with show socket applications such as ntttcp from Microsoft Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX 3 Configuration 112 iSCSI Driver Configuration Use send and receive buffers that are larger than 128 Kb with an efficient application such as ntttcp Disable RSS and use an interrupt filter driver Experiment with all relative CPU affinities to find the best combination Disable timestamps and SACK because the test must run without dropping any packets Unbind unus
83. Related to RoCE This section describes QoS concepts and how to configure QoS for RoCE Priority Groups It is advisable to split traffic into two or more priority groups one priority group for RoCE and other groups for non RoCE traffic Many of the cluster applications use TCP and RoCE traffic simultaneously Some of them use TCP for establishing connections and share connection specific information As a result it is important to allocate enough bandwidth greater than 1 to non RoCE NIC traffic to avoid a slow Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q gt lt EMULEX NIC Driver Configuration connection establishment rate and starvation of NIC traffic Work conserving behavior ensures that each priority group gets enough bandwidth Based on this behavior non RoCE traffic must be given sufficient bandwidth ideally 30 70 L2 Flow Control If a port is operating in generic pause mode RoCE latencies can be adversely affected In this situation Emulex recommends configuring RoCE to use PFC for better results For switches and adapters that do not support PFC RoCE can continue to operate in generic pause mode Bandwidth allocation can still be configured for RoCE versus NIC traffic However this allocation cannot be guaranteed since all of the outgoing traffic can be paused in case of congestion Configuring QoS for RoCE If configuring QoS for RoCE consider the following points e A limit
84. 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 must be downloaded from the Emulex website and loaded Either the full or core driver package can be installed only one can be installed on a system To perform a software first installation 1 Run AutoPilot Installer using one of the two options listed in Running a Software Installation Interactively on page 22 The warning in Figure 2 1 appears AutoPilot Installer Warning D AutoPilot Installer cannot find any Emulex adapters in this system AutoPilot Installer can perform a driver pre installation allowing you to install your adapters later Click OK to pre install drivers or click Cancel to stop the installation Cancel Figure 2 1 AutoPilot Installer Warning Software First Installation 2 Click OK A Welcome page appears 3 Click Next The installation automatically progresses After the installation has completed successfully the Finish dialog box appears 4 View or print a report if desired e View Installation Report The installation report is a text file with current Emulex adapter inventory configuration information and task results e Print Installation Report The Win
85. RspCnt I Os lt 10000 0 8 10000 lt I Os lt 18000 1 8 18000 lt 1 Os lt 26000 1 16 1 Os gt 26000 1 24 CoalesceMsCnt The CoalesceMsCnt parameter controls the maximum elapsed time in milliseconds that the adapter waits before it generates a CPU interrupt The value range is 0 63 decimal or 0x0 0x3F hexadecimal 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 hexadecimal The default value is 8 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 44 gt C EMULEX FC FCoE Driver Configuration Note A system restart is required to make changes to CoalesceMsCnt and CoalesceRspCnt Performance Testing Three driver parameters must 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 to a maximum of 254 The QueueDepth parameter defaults to 32 If the defa
86. SI configuration P011041 01A Rev A 171 SG EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID Severity Message Recommended Resolution 0x42 Warning Command was invalidated This condition is detected by the OneConnect internally the corresponding firmware If this message is unexpected check ICD was not in a valid state your iSCSI configuration 0x43 Warning Command was invalidated This condition is detected by the OneConnect the received PDU had an firmware If this message is unexpected check invalid ITT your iSCSI configuration 0x44 Warning Command was invalidated This condition is detected by the OneConnect the received sequence buffer firmware If this message is unexpected check offset was out of order your iSCSI configuration 0x45 Warning Command was invalidated This condition is detected by the OneConnect internally a received PDU had firmware If this message is unexpected check an invalid DataSN your iSCSI configuration 0x46 Warning Connection invalidation This condition is detected by the OneConnect completion notification firmware If this message is unexpected check your iSCSI configuration 0x47 Warning Connection invalidation This condition is detected by the One
87. Server 2008 and Windows Server 2008 R2 To verify whether offloading is enabled type netstat nt This command displays a list of connections and their offloading state Offloads are disabled for specific ports or applications To view any TCP ports or applications that can 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 can 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 the check boxes for unused drivers In particular Network Load Balancing and some third party drivers prevent offloads IPSec is enabled Disable IPSec IP NAT is enabled Disable IP NAT The driver supports an Advanced Property to disable TCP offloading Make sure TCP offloading is enabled The TCP connection uses using IPv6 The driver supports offloading TCP connections only with IPv4 Note Packet sniffing applications such as Ethereal or Microsoft Network Monitor do not see TCP offloaded packets Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX Troubleshooting the iSCSI Driver 4 Troubleshooting 140 Troubleshooting
88. Table A 5 lists the internal firmware codes posted by the adapter firmware that explain why a particular ELS or FCP command failed at the FC level Table A 5 ELS FCP Command Error Status Codes Explanation Code Remote Stop Remote port sent an ABTS 0x2 Local Reject Local Reject error detail 0x3 LS_RJ T Received Remote port sent LS_RJ T 0x9 A_RJ T Received Remote port sent BA_RJT OxA CT Command Response Codes Table A 6 lists the codes that indicate the response to a FC Common Transport protocol command Table A 6 CT Command Response Codes Explanation Code FC Common Transport Reject 0x8001 FC Common Transport Accept 0x8002 Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX FC CT Reject Reason Codes Appendix A Error and Event Log Information FC FCoE Error and Event Logs Table A 7 lists the codes that indicate the reason a CT command was rejected Table A 7 FC CT Reject Reason Codes Explanation Code Invalid command code 0x01 Invalid version level 0x02 Logical busy 0x05 Protocol error 0x07 ELS Command Codes Table A 8 lists the FC protocol codes that describe the Extended Link Services commands that were sent Table A 8 ELS Command Codes Explanation Code Link Service Reject LS_RJ T 0x01 Accept ACC 0x02 N_Port Login PLOGI 0x03 Fabric Login FLOGI 0x04 N_Port Logout LOGO 0x05 Process Login PRLI 0x20 Pro
89. Troubleshooting 130 DG EMULEX Troubleshooting the FC FCoE Driver FCP Log Messages 0701 0749 Ipfc_mes0701 Issue Abort Task Set to PathId x x Targetld x x Lun x x Description The driver has issued a task management command for the indicated SCSI device address Severity Warning Log LOG_INIT verbose Action Review system configuration Ipfc_mes0703 Issue LUN reset to Pathld x x Targetid 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 Ipfc_mes0713 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 Ipfc_mes0714 Issued Bus Reset for PathId 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 Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 131 Troubleshooting the FC FCoE Driver Ipfc_mes0716 FCP Read Underrun expected d residual d Descripti
90. WWPN 3 automap by DID Value 0 3 Default 2 Class n Class selects the class of service on FCP Dynamic FC Only commands If set to 2 class 2 If set to 3 class 3 Value 2 3 Default 3 CoalesceMsCnt n CoalesceMsCn specifies wait time in milliseconds Reset LightPulse Only to generate an interrupt response if CoalesceRspCnt has not been satisfied Zero specifies an immediate interrupt response notification A non zero value enables response coalescing at the specified interval in milliseconds Value 0 63 decimal or 0x0 0x3F hexadecimal Default 0 0x0 CoalesceRspCnt n CoalesceRspCn specifies the number of response Reset LightPulse Only entries that trigger an Interrupt response Value 0 255 decimal or 0x1 0xFF hexadecimal Default 8 0x8 Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Table 3 1 Storport Miniport Driver Parameters Continued 3 Configuration FC FCoE Driver Configuration 37 Parameter ConfigScale Definitions ConfigScale sets the memory footprint profile in accord with the anticipated use case on a per port basis While the default value is 4 a value of 1 is considered to be the typical use case The ConfigScale parameter supersedes the ExtTransferSize parameter for OneConnect adapters For OneConnect adapters For all values except 0 up to 1024 targets can be discovered and mapped If ConfigScale 0 only 128 targets can be discovered and ma
91. Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Sets the CPU to be used to process transmit completions By default the driver intelligently chooses a CPU in the system so this parameter must only be set for advanced performance tuning Transmit Side Enabled Windows Server 2008 TSS distributes transmit Scaling TSS Disabled Windows Server 2008 R2 completions to be processed on multiple CPUs in parallel It uses Windows Server 2012 the RSS CPU table for distribution Windows Server 2012 R2 and therefore requires RSS to be enabled UDP Checksum Disabled Windows Server 2008 UDP offload checksum settings Offload IPv4 RX and TX Enabled default RX Enabled TX Enabled Emulex Drivers for Windows User Manual Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 offload the transmit or receive IPv4 UDP checksum computation Offloading checksums increases system efficiency P011041 01A Rev A gt G EMULEX 3 Configuration 60 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition UDP Checksum Disabled Windows Server 2008 UDP offload checksum settings Offload IPv6 RX and TX Enabled Windows Server 2008 R2 Offload the transmit or receive default Wi
92. Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Configuration File e path and file This string identifies the file to be checked and its location relative name to the Windows home folder In most cases the file to check is the Microsoft Storport driver For example system32 drivers storport sys This string is also used in dialogs and log file messages file version This is the minimum version that the file to be checked must have for the QFE to be considered installed It is specified as a text string using the same format as is used when displaying the files property sheet For example 5 2 1390 176 applicable OS This is used to determine if the QFE applies to the operating system platform present The acceptable value is Win2008 For example STORPORT QFES qfe QFE 83896 system32 drivers storport sys 5 2 1390 176 Win2008 Setting Up FC Driver Parameters STORPORT PARAMS This section specifies driver parameters Parameters are read exactly as they are entered and are written to the registry To change driver parameters modify this section of the AutoPilot configuration file Locate the STORPORT PARAMS section in the AutoPilot configuration file This section follows Optional Configuration File Changes Under the STORPORT PARAMS heading list the driver parameters and new values for the driver to us
93. X D4C6E5BE a Description The description for Event ID 11 in Source elxstor cannot be found The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer You may be able to use the AUXSOURCE flag to retrieve this description see Help and Support for details The following information is part of the event Device RadPontd Data Bytes Words 0000 Of 00 10 00 61 00 68 00 h A 0008 00 00 00 OO Ob 00 O4 c0 0010 Sb 00 29 00 00 00 00 00 Pe PEE v l OK l Cancel Figure A 1 Event Properties Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix A Error and Event Log Information 144 gt lt EMULEX FC FCoE Error and Event Logs Severity Scheme When the Event Viewer is launched there are three branches Application Security and System All ELXFC ELXCNA error log entries are found under the System branch and all ELXFC ELXCNA error log entries have the Event Viewer severity level of error e A severe error code indicates that the driver firmware or adapter is behaving abnormally and your intervention is required to correct the issue e A malfunction error code indicates that there is an issue with the system but your intervention is not required e A command error code indicates that an event has transpired but does not require your intervention An event may be issue oriented such as an inv
94. a 10Gb module is plugged into one of the ports the adapter switches to 10 Gbps no matter what speed the other port is running or even if I O is running on that port This behavior is a per adapter constraint another adapter can be running on a different speed Table C 1 lists negotiated speed specifications per an adapter s port connection Table C 1 Negotiated Speed Specification per Adapter Port Connection Port 0 Port 1 Port Link Status Speed 10 Gbps 10 Gbps Both ports link up 10 Gbps 10 Gbps 1Gbps Only Port 0 links up 10 Gbps 1 Gbps 10 Gbps Only Port 1 links up 10 Gbps 1 Gbps 1Gbps Both ports link up 1 Gbps 1 Gbps Only Port 0 links up 1 Gbps 1 Gbps Only Port 1 links up 1 Gbps 10 Gbps Only Port 0 links up 10 Gbps 10 Gbps Only Port 1 links up 10 Gbps Negotiating Speed on a Mezzanine Card A mezzanine card retains the first negotiated speed This could be either 10 Gbps or 1 Gbps depending on the connected switch type To change the speed on a mezzanine card 1 Remove the switch from both 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 P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 178 gt EMULEX AParg Driver Kit Parame
95. able 4 3 Troubleshooting the NIC Drivers Issue Performance is not as expected Answer Solution The adapter may be installed in the wrong type of PCle slot Verify that the adapter has been properly installed If TOE is enabled and performance is not as high as expected the operating system may not offload TOE connections For more information see TCP Offloading TOE on page 107 Frequent event log entries for link changes or statistics that show more than expected CRC errors occur 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 event 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 if the flow control setting differs among PCI functions If multiple PCI functions are exposed for a single 10GbE 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 10GbE port On servers that support PCle hot unpl
96. al PCI functions RSS does not appear in the Properties List Recv Segment Coalescing IPv4 Disabled default on Windows Server 2008 Windows Server 2008 R2 Enabled default on Windows Server 2012 Emulex Drivers for Windows User Manual Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 RSC merges multiple TCP segments and identifies them as a single coalesced unit to the operating system s TCP IP stack This reduces the per packet receive processing overhead and CPU usage if standard 1514 byte sized frames are in use Notes e If checksum offloads are disabled RSC must also be disabled RSC depends on checksum offloads for better performance Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled P011041 01A Rev A 53 gt G EMULEX 3 Configuration NIC Driver Configuration 54 Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Recv Segment Coalescing IPv6 Acceptable Values Disabled default on Windows Server 2008 Windows Server 2008 R2 Enabled default on Windows Server 2012 Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition RSC merges multiple TCP segments and identifies them as a single coalesced unit to t
97. alid fabric command sub type An event may not be issue oriented such as exhausted retries on PLOGI or PDISC Related Driver Parameter LogError The LogError driver parameter determines the minimum severity level to enable entry of a logged error into the system See the Configuration section for instructions on how to set driver parameters e If set to 0 all errors regardless of severity are logged e Ifset to 1 severe malfunction and command level errors are logged e If set to 2 both severe and malfunction errors are logged e If set to3 only severe errors are logged Note Set LogError to 1 if you are troubleshooting SAN connectivity or device discovery issues Format of an Error Log Entry An error log entry takes the form of an event This event is described by e Date date entry was logged e Source elxfc elxcna e Time time entry was logged e Category none e Type error e Event id 0 e User N A e Computer name of computer Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information FC FCoE Error and Event Logs Error Codes Tables This section provides tables listing error codes and their descriptions Severe Errors Table A 1 lists severe errors and their codes Table A 1 Severe Errors Bits 0 7 0x00 Interpretation Invalid link speed selection SLI2 3 mode 0x01 READ_REV failed SLI2 3 mode 0x02 In
98. ample 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 can be set to two special values e The delete value causes the key to be entirely deleted and the driver uses the default value This is appropriate for keys that are optional such as the Network Address e The default value sets the key to the driver s default value If the key is optional the default value may be equivalent to deleting the key For example occfg a emulex s vlan delete occfg a emulex s rss default Viewing Device Parameters The occfg exe program can query device parameters from either the registry or the device driver if running driver version gt 2 103 x x The registry and driver values may differ until the driver is reloaded If the driver reload fails for any reason such as another application has an open handle to the device driver it may be necessary to reboot the system to apply the registry changes Note If the driver has been disabled or if the driver failed to load due to any error the driver query returns 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 Modera
99. anced Transmission Selection 0 Disabled Flow Control 3 Rx amp Tx Enabled Flow Control IPv4 Checksum Offload IPv4 Checksum Offload Interrupt Moderation Interrupt Moderation Large Send Offload Large Send Offload Large Send Offload Large Send Offload Large Send Offload Large Send Offload Maximum Maximum Maximum Maximum Maximum Maximum Emulex Drivers for Windows User Manual V1 V1 V2 V2 V2 V2 Number of RSS Number of RSS Number of RSS Number of RSS RSS Processor RSS Processor 0 Disabled 3 Rx amp Tx Enabled 3 Rx amp Tx Enabled 4 Adaptive default 4 Adaptive default IPv4 1 Enabled IPv4 1 Enabled IPv4 1 Enabled IPv4 Enabled IPv6 Enabled IPv6 Enabled Processors lt not set gt Processors lt not set gt Queues Queues Number lt not set gt Number lt not set gt P011041 01A Rev A gt G EMULEX Driver Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Registry Registry Network Address lt not set gt Network Addre
100. apter initialization failed when issuing CFG_RING mailbox command Error LOG_INIT verbose This error could indicate a hardware or firmware issue If issues persist report these errors to Emulex technical support P011041 01A Rev A gt EMULEX 4 Troubleshooting 129 Troubleshooting the FC FCoE Driver Ipfc_mes0454 Adapter failed to init INIT_LINK mbxStatus x x Description Severity Log Action Adapter initialization failed when issuing INIT_LINK mailbox command Error LOG_INIT verbose This error could indicate a hardware or firmware issue If issues persist report these errors to Emulex technical support Ipfc_mes0458 Bring Adapter online Description Severity Log Action The FC driver has received a request to bring the adapter online This may occur when running HBAnyware Warning LOG_INIT verbose None required Ipfc_mes0460 Bring Adapter offline Description Severity Log Action The FC driver has received a request to bring the adapter offline This may occur when running HBAnyware Warning LOG_INIT verbose None required Ipfc_mes0463 Adapter firmware error hostStatus x x Infol OxA8 x x Info2 OxAC x amp x Description Severity Log Action Emulex Drivers for Windows User Manual The firmware has interrupted the host with a firmware trap error Error LOG_INIT verbose Review HBAnyware diagnostic dump information P011041 01A Rev A 4
101. apter transmits to a LOGbE switch with attached 1GbE clients the adapter can overwhelm the switch The switch is then forced to start dropping packets because although it may receive a 10 Gbps stream the client can only handle a 1 Gbps stream In this situation it may be beneficial to enable transmit flow control in the adapter and enable flow control for the 1OGbE switch port Note If multiple PCI functions are exposed for a single 10GbE port such as in a blade configuration the flow control parameter must be set the same on all adapters for the port The results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10GbE port For information on modifying the Flow Control parameter see Configuring NIC Driver Options on page 45 NUMA Considerations for Windows Server 2012 R2 NUMA assignments can affect network performance and CPU efficiency If your application is not NUMA aware and network traffic is moderate to heavy the CPU and memory access are managed by the operating system As a result the operating system can cross NUMA nodes or your application may be on the same NUMA node as other applications decreasing your network efficiency Regardless of whether your application is multi threaded and if data is not in parallel consider the NUMA CPU defaults Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt G EMULEX NIC Driver Configuration 105
102. arelative path LocalDriverLocation Drivers Storport Miniport Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax SR assuming installation into C Program Files Emulex AutoPilot Installer this path would logically become C Program Files Emulex AutoPilot Installer Drivers Storport Miniport e with the ProgramFiles environment variable LocalDriverLocation ProgramFiles Emulex AutoPilot Installer Driver Configuration File Location The optional setting ConfigFileLocation contains the path to the configuration file that should be used If this parameter is not specified AutoPilot Installer uses the file named APInstall cfg in the same folder as APInstall exe The format is the same as that of the other path settings Example APInstall silent SkipDriverInstall True configFileLocation MyConfiguration cfg Software Configuration Parameters DiagEnable Running Diagnostics Note The DiagEnable parameter cannot be specified on the command line it must be specified within the configuration file Default True By default AutoPilot Installer runs its diagnostics after all driver installation tasks have been completed To disable this function set this parameter to false ForceDriverTypeChange Forcing a Driver Type Change Default False When installing a driver set th
103. at SR IOV is working correctly SR IOV can also be verified from the host Hyper V server Note Because current versions of Windows Server 2012 require that SR IOV be enabled in different locations prior to creating the virtual switch if SR IOV is not working delete the virtual switch and create it again The SR IOV option is always available during switch creation Verifying SR IOV from the Virtual Machine To verify SR IOV from within the virtual machine From within the virtual machine select Server Manager gt Dashboard gt Tools gt Computer Management 6 Click Device Manager The Device Driver opens see Figure 3 4 on page 79 7 Open the Network Adapters item select the Emulex device and right click Select Properties from the context menu The Properties dialog box opens showing the Driver page see Figure 3 5 on page 80 Note The Emulex adapter may initially appear as a Network Adapter before the driver is loaded 8 Select the Statistics tab see Figure 3 7 on page 83 Information about the transmit and receive packets that are using the SR IOV virtual function are displayed specifically the number of Transmit Bytes and Receive Bytes that are transmitted directly to hardware from the virtual function If this number is greater than zero the device is successfully using the SR IOV direct hardware access Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX _ Statistic Management
104. ation Activation Parameter Definitions Requirement Adapter Protocol DriverTraceMask The DriverTraceMask parameter is only available Dynamic on operating systems that support extended system event logging If set to 0 the parameter is disabled If set to 1 error events logging is enabled If set to 4 warning events logging is enabled If set to 8 informational events logging is enabled The values can be masked to generate multi levels of events logging Values 0 1 4 and 8 Default 0 EnableAckO n Set to 1 to force sequence rather than frame level Reset FC only acknowledgement for class 2 traffic over an exchange This applies to FCP data exchanges on IREAD and IWRITE commands Value 0 1 decimal Default 1 EnableAUTH EnableAUTH enables fabric authentication This Reboot FC only up to and parameter requires the authentication to be including 8 Gb supported by the fabric Authentication is enabled if this value is set to 1 Value 0 1 Default 0 EnableFDMI n If set to 1 enables management server login on Reset fabric discovery This allows FDMI to operate on switches that have FDMI capable firmware If set to 2 FDMI operates and uses the host name feature of FDMI Value 0 2 decimal Default 0 EnableNPIV n If set to 1 enables NPIV Requires NPIV supported Reboot firmware for the adapter Value 0 1 Default 0 disabled Notes e Torun the driver using NPIV or SLI 3 optimization the f
105. ation 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 can be a local hard drive or a network share Removable media are not searched Example LocalDriverLocation d drivers new Storport Note On x64 and 32 bit systems the path specified by LocalDriverLocation must contain at least one instance of an FC FCoE iSCSI and NIC driver AutoPilot Installer automatically selects the most recent revisions that it finds NoSoftwareFirstInstalls Prohibiting Software First Installations Default False If this parameter is set to true AutoPilot Installer prevents unattended installations from performing software first installations This way you can run 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 mana
106. ations to ensure that all network adapters can share limited computer resources yet it can maintain maximum performance if the system has resources available P011041 01A Rev A gt G EMULEX 3 Configuration NIC Driver Configuration 52 Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Preferred NUMA Node Acceptable Values Not present or a value from 0 65535 Optional No default setting is set Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Most modern multi socket servers have separate memory controllers for each CPU socket These systems have NUMA latencies for a given CPU core to access the local versus remote memory node By setting this property the driver attempts to use both memory and CPU cores from the given NUMA node If the Preferred NUMA node is not set the driver uses the preferred NUMA node as specified by the computer s BIOS For best performance the network applications must use memory and CPU affinity from the same NUMA node This level of tuning is primarily noticeable when multiple adapters are running Receive Buffers 64 32768 inclusive The default value is 896 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 This determines the number of Eth
107. ator Service You can use the Microsoft iSCSI Initiator Service to configure and manage the adapter The Microsoft Initiator Service is available as a free download from www microsoft com See the documentation that accompanies it for detailed information Note If you install the Microsoft iSCSI Initiator Service you need to select only the Initiator Service check box and not the Software Initiator check box Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration DG EMULEX iSCSI Driver Configuration 115 The Microsoft iSCSI Initiator Service sets its own initiator name After you have installed it you must replace this with a custom initiator name To assign a name 1 Inthe Microsoft iSCSI Initiator Service under the general tab click Change 2 Type your initiator name and click OK Logging into a Target Using the Microsoft Software Initiator If you install the Software Initiator you must select the adapter initiator when logging into the target To select the initiator 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 adapter 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 MPIO must be installed from the Server
108. ccceeeee cece eee ees 102 Statistics and Fine Tuning lt ceccins rectid caw oreeseiawiereesdiiwsecreoeieenereweues 103 iSCSI Driver OLIN scotia posta cpceeecacaneteesbececeuansacaeauteenicardeleenecaderes 113 imi policy SSEENIGSs ciiai inni ea aE Enea EA Ea AE RE Eaa 114 LDTO and ETO Information on the Windows Server ccccceeeeeeeeeeeeee eens 118 General MTOublesShOouing wicccstcieaccsendoalateareedetactawatorieeis ieeetatidensiedads 119 Cisco Nexus Switch Situations vine csttesuaecensduetrsg cual wanarchstweseragaadeeuares 120 Troubleshooting the NIC DriverS cccccceceeseeeeeeaee sense seats neaneneanenens 137 Troubleshooting TCP Offload Failures accra 139 Cisco Nexus Switch Situations for iSCSl acccccce a 140 Troubleshooting the iSCSI Driver sssssssssrssereessrsrrrrrrrrrererrsrrrrrrerere 140 Severe Err O Shrii EDA ERE RE OE EEA EAE AE AEEA 145 Malfunction Errors creacecsticsorensts ehrcesehanadrecteas Guideiebandarseietecantdeienass 147 COMIMANG El OrS s cesvisweveceeveswevedeewiuecetytaniencceiensereenteeratiseanee 148 Event WI aunt Savnt arti tase epee ence capac taesbececctansadaeacteericardelessacadteren 149 ELS FCP Command Error Status COdGS cs ccsintrssiscadsudearessscredessdciesderes 151 CT Command Response Code s ive sicccsstversr nis eeewdisiveste sss eearniaee 151 FC CT Reject Reason Codes s scicietasveieleacnesacerbeieencivarameesiaaaeensiees 152 ELS Command Codes ssssssesrrrrnrrrrrrrrtnnrirrrrtnarnrrrnna
109. cece nee tes 127 FCP Log Messages 0701 0749 0 rennet nes 130 Link Log Messages 1302 1306 cc cece eee nent ened 133 Tag Messages 1400 1401 0 0 0 nn nett e teen netae 134 NPIV Messages 1800 1899 ccccccc cece eee eee eee eee eeeeeeeeeeeee sate ttrrrrrrrrrrrrrrrr 134 ELS Messages 1900 1999 scccicoriaret nenten a an a ei 135 Troubleshooting the NIC Drivers s s ssssssssunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 137 Monitoring TCP OffloadS isss irencirisirenreserirsonTipenerst nd Een i ERANT EST ADEE RO EnEn TNES 138 TCP Offload Pam Ss ica cve cans aastchcencnadrsautthaticsasitaecerneestianssiaecctesiaieaeieda 139 Troubleshooting the iSCSI Driver ssssssssnnnnnsnssnunnnnnnnnnnnnnnnnnnnnnnnnnunnnnnnnnn 140 Troubleshooting the Cisco Nexus Switch Configuration c eceeeee eee eee eee 140 iSCSI Driver Troubleshooting cccciccccretesticceasaceestaseneeeadigeancdensiaeeadseaacaneacaas 140 Appendix A Error and Event Log Information sccccccseeesseceeeeeescereesseeres 143 FC FCoE Error and Event LOGS iiscscccsssssssscscsassstecsasascccnsasscsstscsssaccscsscassaes 143 Viewing the FC FCoE Error l0Gucciccocaisidenccetascermecetanecanacedansedendacanneesagekal 143 Severity Scheme sicicciuierieataitiiedianiense RAEE EE E E EEEa 144 Related Driver Parameter LogErTOT sssssssssssssssessrrrrrrrrrrrrrrrrrrrrrrrrrrrrerrrerrn 144 Format of an Error Log ENUY ece ierre ciiin pasini nae
110. cess Logout PRLO 0x21 Discover F_Port Service Params FDISC 0x51 Discover Address ADISC 0x52 Register State Change Notify RSCN 0x61 SCSI Status Codes Table A 8 lists the SCSI status codes returned from a SCSI device which receives a SCSI command Table A 9 SCSI Status Codes Explanation Code GOOD 0x00 CHECK CONDITION 0x02 BUSY 0x08 RESERVATION CONFLICT 0x18 QUEUE FULL 0x28 Emulex Drivers for Windows User Manual P011041 01A Rev A 152 Appendix A Error and Event Log Information 153 gt lt EMULEX FC FCoE Error and Event Logs Local Reject Status Codes Table A 10 list the codes supplied by the Emulex adapter firmware that indicate why a command was failed by the adapter Table A 10 Local Reject Status Codes Explanation Code SEQUENCE TIMEOUT Possible bad cable link noise 0x02 INVALID RPI Occurs if the link goes down 0x04 NO XRI Possible host or SAN problem 0x05 TX_DMA FAILED Possible host system issue 0x0D RX_DMA FAILED Possible host system issue 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 responding 0x18 LINK DOWN Queued cmds returned at link down 0x51A OUT OF ORDER DATA Possible bad cable or noise 0x1D SRB Status Codes Table A 11 lists the SCSI Request Block status codes provided by the driver to the operating system based upon the respons
111. command errors and their codes Table A 3 Command Errors Bits 0 7 0x43 Interpretation Fabric login succeeded 0x46 ELS command failed 0x47 Exhausted retries on ELS command 0x4A PLOGI accepted 0x56 LOGO accepted 0x59 PRLI accepted 0x63 Fabric name server response 0x6B ELS RSCN processed 0x71 LOGO received from fabric 0x79 FDISC accepted 0xA2 Emulex Drivers for Windows User Manual P011041 01A Rev A SCSI address assigned to discovered target 148 gt EMULEX Appendix A Error and Event Log Information FC FCoE Error and Event Logs Table A 3 Command Errors Continued Bits 0 7 0x43 Interpretation Fabric login succeeded 0xA4 Report LUNs error initial I O to discovered target 0xA5 Local error indication on FCP command 0xA8 Data overrun OxA9 FCP command error OxAA SCSI check condition 0xAD Local reject indication on FCP command OxAE Error on SCSI pass through command OxAF Error on Menlo CT command Event Indicators Table A 4 lists event indications and their codes Table A 4 Event Indications Bits 0 7 0x18 Interpretation Port shutdown event SLI2 3 mode 0x19 Port in off line state SLI2 3 mode 0x1A Port in on line state SLI2 3 mode 0x1B Port in off line state SLI2 3 mode OxA7 Data underrun 0xD0
112. cores installed on your system Emulex Drivers for Windows User Manual Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 This property sets the maximum number of processors that can be used for RSS P011041 01A Rev A gt G EMULEX 3 Configuration 49 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition Maximum Windows Server 2008 Windows Server 2008 If RSS is enabled this parameter Number of RSS for OCe11102 legacy Windows Server 2008 R2 Controls the number of receive Queues 0Ce11102 advanced queues Typically thisis left at the mode LPe16000 Windows EIYELE maximum value Windows reduces OCe14000 Windows Server 2012 R2 the number of queues as necessary e Min 1 Max 4 based on the number of installed default 4 CPU cores Windows Server 2008 R2 This value can be reduced during Windows Server 2012 performance tuning for a Windows Server 2012 R2 particular application It is 0Ce11102 legacy possible that system performance Min 1 Max 4 may improve by limiting the Default 4 number of RSS queues e 0Cel1102 advanced For OCe11102 adapters greater mode Min 1 Max 8 than 4 RSS queues requires that Default 8 Advanced Mode Support be LPe16000 Min 1 enabled in the BIOS controller Max
113. cted Check the registry configuration for range The driver will use the default any new valid values added to the driver value for this configuration parameter parameters For more information on valid instead driver values see Table 3 10 iSCSI Driver Options on page 113 0x31840006 The iSCSI driver failed to load due to This failure occurred due to a failed memory memory allocation failure allocation in the driver Check low memory conditions 0x31840001 The iSCSI driver failed to load because This failure may be due to the firmware not initialization failed during normal bootup Emulex Drivers for Windows User Manual being present or currently running This failure may also indicate a hardware issue P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 163 Table A 14 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x31640004 An internal API failed in the iSCSI This failure may indicate a low memory driver during initialization condition 0x3164000D The driver failed to allocate its This message indicates a low memory complete memory requirement and condition will attempt to load with reduced capabilities Total number of targets available will be reduced 0x14831000 There was an Unrecoverable Error This may be due to hardware errors or due to detected by the iSCSI drive
114. dapter PCIe functions on the system Individual iSCSI PCIe functions cannot have their own set of parameters Table 3 10 provides descriptions of the different iSCSI driver options and their possible values Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Table 3 10 iSCSI Driver Options 3 Configuration iSCSI Driver Configuration 113 Parameter ETO Default Value 90 seconds Minimum Value 0 seconds Maximum Value 3600 seconds Description ETO in seconds This parameter determines the amount of time the driver waits for the target to be available after it has lost connection im_policy The Interrupt Moderation policy parameter controls the rate of interrupts for the adapter For more information see Interrupt Moderation Policy Settings on page 114 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 Storport driver Note If the large_io parameter is set to 512 the amount of physical memory consumed by the driver increases Also although intermediate values between 6
115. dapters a p Relabilty and Performance Eei DVD CD ROM dii wR a O Human Interface Devices g Storage W cg IDE ATA ATAPI controllers D Keyboards i Sea bg Vc ing devices a 5 Monitors SAP Network adapters Emulex OneConnect OCe 11102 I NIC TOE 10 EF Emulex OneConmect OCe11102 1 NIC TOE 9 F Ports COM amp LPT Ej Processors E Storage controlers lt Dell SAS 6 R Integrated Controler Emulex OneConnect OCe 11102 1 iSCSI Initiator lt Emulex OneConnect OCe11102 I iSCSI Initiator lt gt Microsoft iSCSI Initiator lt gt Microsoft Mult Path Bus Driver 6 4 System devices Universal Serial Bus controlers Figure 3 1 Partial View of Windows Device Manager 2 Right click the network adapter for which you wish to modify advanced properties 3 Click Properties and click the Advanced tab see Figure 3 2 on page 65 4 From the list of properties click the property parameter you want to modify then select the new value of the property by selecting from the Value list 5 Click OK Emulex Drivers for Windows User Manual P011041 01A Rev A SXG EMULEX 3 Configuration 65 NIC Driver Configuration Note Modifying properties causes the network driver to reload and some TCP connections may be temporarily dropped Emulex OneConnect 0Ce11102 IT N E Propertie x L Diver Detais Resources Power Management General Advanced Status Statistics Diagnostics SE EMULEX Advanced Pro
116. detected 2399141890 Ox8F 000002 The AutoPilot Configuration file is not found 2399141891 0x8F000003 Disabled adapters detected in the system 2399141892 Ox8F 000004 The selected driver is 64 bit and this system is 32 bit 2399141893 0x8F000005 The selected driver is 32 bit and this system is 64 bit 2399141894 Ox8F000006 Installation activity is pending AutoPilot Installer cannot run until it is resolved 2399141895 0x8F000007 GUI Mode only You cancelled execution because you did not wish to perform a software first install 2399141896 0x8F000008 No drivers found 2399141897 0x8F000009 One or more adapters failed diagnostics 2399141904 0x8F000010 GUI Mode only You chose to install drivers even though a recommended QFE or Service Pack was not installed 2399141920 0x8F000020 GUI Mode only You chose to stop installation because a recommended QFE or Service Pack was not installed 2399141899 0x8F00000B Unattended installation did not find any drivers of the type specified in the config file 2399141900 0x8F00000C A silent reboot was attempted but according to the operating system a reboot is not possible 2399141901 0x8F00000D GUI Mode only A driver package download was cancelled 2399141902 0x8F00000E Non Enterprise No adapters were found in the system 2399141903 0x8F00000F A required QFE or Service Pack was not detected on the system 2399141836 0x8F000030 AutoPilot Installer was not invoked from an account with Administra
117. dows print dialog box is displayed to select options for printing the installation report 5 Click Finish to exit the AutoPilot Installer Text Only Driver Installation Text based installation mode is used automatically when the driver kit installer runs on a server with the Server Core installation option of Windows Server During text based installations AutoPilot Installer uses a command prompt window The driver kit installer notifies you when the driver is installed and also gives you a chance to stop the installation Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 25 gt X EMULEX AutoPilot Installer Whether AutoPilot installer is launched from the command line or run as a program Windows always starts AutoPilot Installer as a separate stand alone task This means that AutoPilot Installer has its own command prompt window and cannot access others Unattended Driver Installation An unattended driver installation sometimes referred to as a quiet or silent installation requires no user input This is useful for performing an installation remotely from a command script or if you want to ensure that a custom configuration is not changed by a user during installation If 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 Op
118. e For example Driver Parameter LinkTimeout 45 See Table 3 1 Storport Miniport Driver Parameters on page 36 for a listing of driver parameters defaults and valid values Setting Up System Parameters SYSTEM PARAMS To change the system parameters create a SYSTEM PARAMS section in the APInstall cfg file Create this section under the Optional Configuration File Changes heading in the AUTOPILOT CONFIG section For example you can adjust the operating system s global disk timeout The timeout is stored in the registry under the key HKML CurrentControlSet Services disk and is specified with the following string TimeOutValue 0x3C where the number is the timeout value in seconds Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix D AutoPilot Installer Command Line and Configuration File Parameters 187 AutoPilot Installer Exit Codes AutoPilot Installer Exit Codes AutoPilot Installer sets an exit code to indicate whether an installation was successful or an error occurred These exit codes allow AutoPilot Installer to be used in scripts with error handling In unattended installations AutoPilot Installer sets the following exit codes listed in Table D 1 Table D 1 Unattended Installation Error Codes Error Code _ Hex Description 0 0x00000000 No errors 2399141889 0x8F000001 Unsupported operating system
119. e hyperthreaded CPU Enabling Windows to Use Up to Eight Processors Windows Server 2008 uses only four processors by default In order for the driver to use up to eight processors the registry must be changed and the system restarted Caution Use the registry editor at your own risk Using the registry editor can cause serious issues that may require you to reinstall the computer s operating system Emulex cannot guarantee that issues resulting from changes you make to the registry can be repaired Make a backup of your registry before making any changes For Windows Server 2008 set the registry keyword MaxNumRssCpus a DWORD type to 8 at the following location HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services Ndis Parameters Note Do not set the registry keyword to a value greater than the number of processors in the system or 16 whichever is smaller For Windows Server 2008 R2 and Windows Server 2012 the operating system uses all available CPU cores for RSS without manual configuration TCP Offloading TOE Note TOE is not supported by OCe14000 series adapters Some Emulex adapters and drivers support TCP offload which provides significant performance improvements The performance improvements are Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt G EMULEX NIC Driver Configuration 108 e A zero copy receive data path exists In contrast all non offloaded TCP packets are copied
120. e from a SCSI device in the SAN Table A 11 SRB Status Codes Explanation Code ERROR 0x04 BUSY 0x05 TIMEOUT 0x09 SELECTION TIMEOUT 0x0A COMMAND TIMEOUT 0x0B BUS RESET 0x0E DATA OVERUN 0x12 ASC ASCQ Additional Sense Code Additional Sense Code Qualifier information can be found in any SCSI specification document these codes contain detailed information about the status or condition of the SCSI device in question Emulex Drivers for Windows User Manual P011041 01A Rev A sc Appendix A Error and Event Log Information 154 gt lt EMULEX FC FCoE Error and Event Logs Additional Notes on Selected Error Codes These are error codes that may be seen more frequently than others or that indicate conditions that you might be able to solve by investigation and correction of issues in the SAN configuration Note The nomenclature of 0x is used as the prefix for the byte code fields because those byte codes are actually hexadecimal values Node Timeout Code 0xAA This event code indicates that a particular device has not been found if the message is logged during device discovery or that a particular device has been removed from the fabric If this message is seen determine if there is something wrong with the connection of that device to the SAN cables switches or switch ports or status of the target device itself SCSI Command Error 0x9A and SCSI Check Condition code 0x9B Code 0x9A i
121. e prompt netsh interface tcp set global autotuning disabled netsh interface tcp set global congestionprovider none 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 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt EMULEX NIC Driver Configuration 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 issues Increasing interrupt coalescing can improve total bandwidth for applications that transfer large data buffers Additionally servers running numerous parallel TCP connections can benefit from higher interrupt coalescing Some applications run slower with interrupt coale
122. e 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 No workaround exists for this issue If an iSCSI adapter is used to log in to an iSCSI target and the LUN configuration on the target is changed neither the adapter 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 adapter 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 P011041 01A Rev A gt EMULEX 4 Troubleshooting 142 Troubleshooting the iSCSI Driver Table 4 6 Troubleshooting the iSCSI Driver Continued Issue A login to new target fails after Microsoft iSCSI Initiator Service is installed Answer Solution If Microsoft iSCSI software is installed the service chooses a default IQN name for the adapter The Microsoft iSCSI service issues the request to the iSCSI driver using the WMI interface to set
123. eCommand Manager GUI Emulex Drivers for Windows User Manual P011041 01A Rev A DG EMULEX 3 Configuration QJ NIC Driver Configuration e OneCommand Manager CLI See the OneCommand Manager Command Line Interface Manual for information about enabling the RoCE profile using the OneCommand Manager CLI Confirming That the RoCE Profile Is Enabled To confirm that the RoCE profile is enabled use one of the following methods e Inthe Advanced tab of the Network Property page ensure that NetworkDirect is enabled see Figure 3 8 Diver Detais Everts Power Management General Advanced Status Statistics Diagnostics SEEMULEX Avinced Propety Contiguation RSS Profile hanas SROV Enabled Transm Butters Transma Side Scaling 3 Virtual Machine Queues The Network Direct feature enables an offloaded ROMA interface for SMB 3 0 network attached storage traffic using M Microsoft s SMB Direct protocol Emulex supports ROMA over _ Converged Ethernet ROCE For best performance priority flow control PFC should be configured on the network switch Emulex defaults to priority S for ROCE traffic although it will still work without PFC enabled Figure 3 8 Advanced Property Configuration RoCE Enabled e By using a PowerShell script o Get NetAdapterRDMA see Figure 3 9 Copyright 2013 Microsoft Corporation All rights reserved PS F Users Administrator gt Get NetAdapterRDMA InterfaceDescript
124. eads to the removal of all LUNs on the timed out devices Value 1 500 seconds or 0x0 OxFE hexadecimal Default 30 0x1E LogErrors LogErrors determine the minimum severity level Dynamic required to enable entry of a logged error into the system event log Errors are classified as severe malfunction or command level A severe error requires user intervention to correct a firmware or adapter issue An invalid link speed selection is an example of a severe error A malfunction error indicates that the system has issues 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 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 41 gt lt EMULEX FC FCoE Driver Configuration Table 3 1 Storport Miniport Driver Parameters Continued Activation Parameter Definitions Requirement Adapter Protocol NodeTimeout n The node timer starts when a node that is a Dynamic discovered target or adapter 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
125. ecified packet size or the size will be negotiated to the common smallest size P011041 01A Rev A gt G EMULEX 3 Configuration 51 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Performance Tuning Acceptable Values Maximum performance default e Dynamically balanced Statically balanced Emulex Drivers for Windows User Manual Supported Operating Systems Windows Server 2012 Definition This parameter selects the driver algorithm for performance tuning allowing you to balance raw networking throughput with overall system fairness among multiple devices and applications Maximum Performance This mode maximizes the network performance for this adapter This is the recommended mode However in systems with a large number of network or storage adapters this mode can limit the performance of other devices Statically Balanced This mode configures the network adapter to throttles CPU usage in all cases allowing more balance among hardware devices and applications If system responsiveness is poor this mode can improve the overall system behavior Dynamically Balanced Dynamic balancing adjusts the network adapter s performance based on system metrics such as CPU usage This mode can aggressively limit performance for the most stressful networking applic
126. ecord VirtualSubnetID 5001 ProviderAddress 192 x x x MACAddress 060600000007 Add the customer route records for Blue subnet CustomerAddress 10 0 0 5 Rule TranslationMethodEncap CustomerAddress 10 0 0 7 Rule TranslationMethodEncap Get NetVirtualizationCustomerRoute where VirtualSubnetID eq 5001 Remove NetVirtualizationCustomerRoute New NetVirtualizationCustomerRoute RoutingDomainID 11111111 2222 3333 4444 000000005001 VirtualSubnetID 5001 DestinationPrefix 10 0 0 0 24 NextHop 0 0 0 0 Metric 255 EFE HEHEHE HEHEHE HEETE FE HH ERP HE HHH HE HE HE HE HH HERE FE HE HE TE FE FE HE HH FE FE HE HE TE HE FE HE E TE HE FE HE HE E E H E RRR RRR RR RR HEEE HEHEHEHE E HE HEE H HH EE H HHRH HH Red Virtual Network Information Rout ingDomainID 11111111 2222 3333 4444 000000006001 VirtualSubnetID 6001 Both RDID and VSID are defined by administrators MUST be unique in the datacenter Customer Addresses VM Name Host VSID CA PA MAC DefaultGw ES a a i ee EOE Redl Hostl 6001 10 0 0 5 192 x x x 08 08 00 00 00 05 10 0 0 1 Red2 Host2 6001 10 0 0 7 192 x x x 08 08 00 00 00 07 10 0 0 1 Customer Routes DestPrefix NextHopGW Note dh cise Sawa A eae ae aoa ee eee eee eee ee eee ee eee ee eee 10 0 0 0 24 0 0 0 0 Onlink route for Red subnet Add the locator records for Red subnet Get NetVirtualizationLookupRecord where VirtualSubnetID
127. ection 23 s Flow 3 rss 0 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt lt EMULEX NIC Driver Configuration Selecting an Adapter In batch mode the a parameter must be followed by a substring that is contained within the adapter name The name is a combination of the device manager name for example Emulex OneConnect OCe11102 and the network connection name for example Local Area Connection The latter can be modified by using the Windows Network Connections applet ncpa cpl The most typical scenario involves setting parameters to be the same for all ports of a network adapter This is accomplished by specifying a emulex It is often 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 The occfg program is used to query and modify registry parameters for Emulex network devices The registry keys are stored at HKLM System CurrentControlSet Control Class 4D36E972 E325 11CE BFC 108002bE10318 where is the device instance number The occfg program allows you to modify registry keys on a set of network devices After the driver is modified it must be restarted to apply these parameter
128. ection maps to an RDMA queue pair Both the client and server must negotiate support for SMB Direct If available each TCP connection is offloaded to an RDMA queue pair CA C Users Adninistrator gt netstat xan Active NetworkDirect Connections Listeners SharedEndpoints Mode IfIndex Type Local Address Foreign Address D Kernel 26 Connection 26 2 1180 49281 26 2 1681 445 Kernel 26 Connection 26 2 11801 49282 2 71661 445 Kernel 26 Listener fe8G fded e692 8d6a 9cBex261 445 NA Kernel 26 Listener 26 2 116 261 445 NA Kernel 26 Listener 20 2 0 110 445 NA Kernel 25 Listener fe8 74f2 aa4d2 25734 b2dax251 445 NA Kernel 25 Listener 26 1 1180 251 445 NA Kernel 25 Listener 20 1 0 110 445 NA Figure 3 12 SMB Share Two RDMA Connections Per RDMA Enabled Network Interface The PowerShell command Get NetAdapterStatistics see Figure 3 13 on page 93 shows the RDMA Statistics which indicate the number of failed connection attempts opyright C 2013 Microsoft Corporation All rights reserved PS F Users Administrator gt Get NetAdapterStatistics Name Ethernet 14 5 7 Ethernet 15 569005 Figure 3 13 Get NetAdapterStatistics SMB Multichannel For each SMB session SMB multichannel establishes two SMB Direct connections to a particular server by default It also makes use of multiple RDMA capable NIC interfaces if available Opening a file share from a 2 port OCe14000 series adapter both por
129. ed QoS configuration is available through OneCommand Manager e A single traffic class group for RoCE exists per port e A single RoCE priority exists in PFC mode e Bandwidth allocation for priority groups is supported Notes e The Windows NIC driver does not support the Microsoft DCB QoS API e PowerShell commands cannot be used to configure QoS related parameters for the RoCE profile RoCE Adapter Side With DCBX enabled the switch settings are used for PFC Ensure that the switch settings match the adapter default Priority 5 used for RoCE and PFC Note PFC is enabled by default in OCe14000 series adapters Switch Side For information on switch side configurations see Appendix E RoCE Switch Support on page 190 0Ce14000 Series Adapter Defaults If using the OCe14000 series adapters for RoCE functionality the following defaults apply e Adapter boot time o PFC is disabled on all the ports in the NIC and the RoCE profile is enabled o Generic Pause is enabled on all the ports in the NIC and RoCE profile e Back to back connection OCe14000 OCe14000 o PFC is disabled by default o Generic Pause is enabled on the connected port Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration QQ DG EMULEX NIC Driver Configuration e DCBX enabled switch connection o If an OCe14000 series adapter is connected to a DCBX enabled switch it shifts the mode from Generic Pause to PFC o An OCe14000 serie
130. ed network protocols in the Network Connections property page Disable any firewall services IPSEC or NAT iSCSI Driver Configuration Table 3 10 lists the user configurable iSCSI driver options available on Windows Server It includes a description of the parameters their default values and their configuration limits Note Ifthe value given for a parameter is outside the supported range the driver logs an error in the Event Log and continues to load by using the parameter s default value Configuring iSCSI Driver Options The OneConnect Windows iSCSI driver parameters can be configured using the Advanced tab of the Device Manager Property Page To modify a configuration parameter 1 Select the Emulex OneConnect iSCSI adapter in the Windows Device Manager under Storage Controllers 2 Right click and select Properties The Device Manager Property page opens 3 Select the Advanced tab and make appropriate changes to the parameter as required 4 Reboot the system for the changes to take effect Notes The modifications to the driver parameters made using the Device Manager Property page are not immediately applied They take effect during the next driver load sequence either during the next reboot or a driver unload or load operation Although the Advanced Tab of the Device Manager Property page can be accessed from any OneConnect iSCSI adapter the parameter changes are uniformly applied to all the OneConnect iSCSI a
131. en met e The individual kit installation failed To check run the installation interactively If you encounter error messages when you run the installation interactively those issues would also apply to an unattended installation e If an individual package failed to install properly run that package s installer directly This method displays status and error messages that can be used to diagnose the issue The Onelnstall Installer does not provide these displays because each package is installed silently Windows Device Manager shows a code 10 or code 39 with a yellow or red exclamation point on the device The firmware image does not match the installed device drivers or the firmware is corrupt Using the OneCommand Manager application or one of the Windows PE offline or online utilities install a version of firmware that is compatible with the driver The firmware is corrupt or non responsive Using the OneCommand Manager application or one of the Windows PE offline or online utilities install a version of firmware that is compatible with the driver The Emulex iSCSI BIOS banner is not displayed during system POST Emulex Drivers for Windows User Manual Configure the motherboard BIOS to enable the Option ROM for the PCle slot in which the adapter is installed P011041 01A Rev A gt G EMULEX 4 Troubleshooting 120 Troubleshooting the FC FCoE Driver Troubleshooting the FC FCoE Driver Troubles
132. ens the installation report file e Validates the operating system e Discovers adapters and records the adapter inventory in the report file e Verifies mandatory configuration file parameters e Searches for drivers to install based on the LocalDriverLocation setting in the configuration file e Verifies if appropriate that the selected driver is either a different type than the currently installed driver or a more recent version of the currently installed driver e Copies the driver parameters from the configuration file into the registry for the driver s co installer FC and FCoE drivers only 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 An unattended installation can be performed in two ways e Install the driver silently e Run the driver kit installer separately Option 1 Install the Driver Silently Run the driver kit from a command prompt or script Specify the q quiet command line option For example elxdrv fc fcoe lt version gt exe q Note The name of the driver kit depends on the current version identifier For other command line options see AutoPilot Installer Command Line and Configuration File Parameters on page 178 Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 26 gt lt EMULEX Manually Installing or Updating the Emulex Protocol Drivers
133. ent log entry This error may indicate an incorrect configuration option for the iSCSI driver It may also indicate a low memory condition 0x12 Error Unrecoverable error detected An unrecoverable error was detected by the UE Low A iSCSI driver UE High B This may be caused by hardware errors or by FW Line C unhandled exceptions in the hardware or firmware 0x13 Error Hardware initialization failed The iSCSI driver detected a failure in the failing driver load Emulex Drivers for Windows User Manual 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 P011041 01A Rev A SG EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID 0x14 Severity Warning Message Failed to retrieve scatter gather list for a SCSI Request Block an IO has failed Recommended Resolution The iSCSI driver failed an I O request because it failed to retrieve a scatter gather 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 initialization failed An internal API
134. ernet receive buffers allocated per receive queue This number can be adjusted by the driver as needed Receive CPU Not Present or a value from 0 through number of CPUs on the system 1 Optional A default setting is not available Emulex Drivers for Windows User Manual Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Sets the logical CPU used for processing the non RSS receive packets By default the driver intelligently chooses a CPU in the system so this parameter must only be used for advanced performance tuning RSS packets are processed by the set of RSS CPUs provided by the Windows operating system P011041 01A Rev A gt G EMULEX 3 Configuration NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name Receive Side Scaling Acceptable Values Disabled Enabled default Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition Support for multiple RSS queues if enabled 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 For the OCe11102 adapter RSS is only supported on two primary adapters per device For addition
135. ers cccccecc cee eee tesa seen eeeeeeeeeeeeeeeeesetesaeeeneeenenaes 71 Viewing Device Parameters 0 ccc cee eee tetas 72 Resetting All Parameters vnc cnteeieatid aveadiatutetialareldtatvwlantdvantadenetesandaltadeemwnden 72 Displaying All Parameters ccccecce cece cee eeee eee e eee sees eee eeee esate sat esaeeeeneeneeaaees 73 Using Interactive ModE iicimrsusis comune cea airia AE AEREE A E AA A EAEE 75 Parameter Help tcictescanesiates tides ae neh ene EEO ETEA EEE E D 76 Using SR IOV with Emulex Devices sssssssssrrrrrerssssrrrrrrrrrrrsrrsrrrrrrerererrsrrr 76 ACVISOLY Sis eacvnk dovthen dead a a E En Eaa EEN E EN EN EEE AA DES 76 Server BIOS Configuration oserei ieie rneer niina sedate as EA E E EA 77 Emulex PXESelect Configuration for SR IOV s sssssssssesrrrrsssererirrrrrererirnrrerrr renn 77 SR IOV Server Validation scsiecccceis cuctiscestedeetan anr a a Ta AE ia 78 Verifying the Driver Version ccccccccceeceeeee eet seats EEE EEEE EEEE EEEE 79 Enabling SR IOV in the Emulex Device cece ec eet nent teeny 80 HYDE V cccituerttaadderiereanans amet tanita ERARE dansdadued NEE 81 Verifying SR OV sacissacacnaacacora cds seca taut Avyeteaennaeetecasedadawnoetensdasbaeasiasiaaateral 82 Configuring NVGRE for the OCe14000 series Adapters cccccceseeeeeeeeeeeenaeeenas 84 SClU Pica sdsiariitat ocdalgrenedtadtned E E 84 CONTI QUIET ON iy icis cnscantcingadecgunstynatdan R E E EET OSEE E EE EEE EA 84 C
136. erver 2008 system 1 Open the Programs and Features control panel 2 Select one of the following in the program list and click the Uninstall icon in the tool bar above the program list If you have User Access Control enabled click Continue when asked for permission e Emulex FC kit 2 xx xxx e Emulex FCoE kit 2 xx xxx e Emulex NIC 4 xx xxx e Emulex iSCSI kit 4 xx xxx 3 Click Yes when prompted to remove the kit After the kit is removed from the system click OK Server Core System To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files folder 2 Navigate to Emulex AutoPilot Installer 3 Run the following batch files e Uninstall_fc_kit bat e Uninstall_cna_kit bat e Uninstall_nic_kit bat e Uninstall_iscsi_kit bat The driver files are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installer folder is not removed so you can still view installation history and the drivers that have been installed on the system You can delete the reports folder at any time Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 32 gt G EMULEX Removing Emulex Driver Kits and Drivers Windows Server 2012 To uninstall a driver kit on a Windows Server 2012 system 1 Select Start gt Control Panel 2 From the Control Panel select Programs gt Uninstall a Program 3 Select one of the following in the program list and cl
137. et interface and if there is a successful ICMP Echo reply the iSCSI firmware uses Jumbo Frames for that connection The MTU used in this case is 8342 bytes If the large ping request is unsuccessful the firmware defaults to non jumbo mode and uses an MTU size of 1514 bytes The Max MTU value is displayed in the OneCommand Manager application for the iSCSI controller under the Port Information Tab on the Max MTU field The TCP MSS used for an active iSCSI connection is displayed in the OneCommand Manager application on the TargetSessions screen on the TCPMSS field iSCSI Error Handling The goal of iSCSI error handling is to be tolerant of link level and target level failures up to configured timeout values so that I O errors are not seen by the application or operating system The error handling is triggered under the following conditions e Loss of immediate link to the adapter such as a cable disconnect or port failure The adapter firmware detects the loss of link and notifies the driver If this occurs the driver queues the I O requests internally up to a configured timeout period so that the operating system does not see I O errors This timeout period is known as LDTO e Loss of connection to the target because of target or network disconnection at the target If the driver has I O requests pending with the target and the target becomes unavailable because the target is down has failed over or network issues are detected
138. ev A DE EMULEX 2 Installation 18 Onelnstall Installer OneCommand Manager application for Emulex adapters Note The Enterprise kit for the OneCommand Manager application does not operate locally on Windows Server Core You must install the OneCommand Manager Core Kit command line interface only to the Windows Server Core Loading the Onelnstall Package using Interactive Mode To install the drivers using Interactive Mode 1 ae WN 6 Download the OnelInstall package from the Emulex website Navigate to the Onelnstall package in Windows Explorer Double click the Onelnstall package The Welcome screen appears Click Next The Installation options screen appears Select the drivers and application that you want to install and click Next A progress screen appears while the Onelnstall installer loads the selected drivers and applications After the drivers and application software are loaded an Installation completed screen appears Click Finish Loading the Onelnstall Package using Silent Mode Notes Silent mode installation must be run from the command line If you run Onelnstall from a batch file or from a command line prompt the default Windows behavior starts OnelInstall then immediately continues with the next command It does not wait until Onelnstall has finished As a result the value of ERRORLEVEL will always be 0 because Windows successfully started Onelnstall It does NOT reflect an accura
139. everity Information Log LOG_ELS verbose Action No action needed informational Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 126 Troubleshooting the FC FCoE Driver Ipfc_mes0239 NameServer Response next DID value x x Description Severity Log Action See Also The driver received a nameserver response And this message is recorded for each DID included in the response data Information LOG DISCOVERY verbose No action needed informational Ipfc_mes0236 Ipfc_mes0240 NameServer Response Error CmdRsp x x ReasonCode x x Explanation x x Description Severity Log Action See Also The driver received a nameserver response containing a status error Error LOG DISCOVERY verbose Check Fabric configuration The driver recovers from this and continues with device discovery Ipfc_mes0236 Ipfc_mes0256 Start node timer on NPortld x x timeout value d Description Severity Log Action Starting timer for disconnected target with NPort ID and timeout value Information LOG _ELS verbose No action needed informational Ipfc_mes0260 Stop node timer on NPortlid x x SCSIId x x Description Severity Log Action Discontinuing timer for reconnected target with NPort ID and SCSI ID Information LOG_ELS verbose No action needed informational Ipfc_mes0262 Node timeout on NPortld x x SCSIId x x Description Severity Log
140. ex technical support 0x0009 9 Error Failed to register interrupt service Thisis an NDIS error Verify that routine hardware resource conflicts do not exist 0x0008 8 Error Failed to get TCP offload handlers Thisis an NDIS error Verify that the Emulex Drivers for Windows User Manual NDIS version is valid for the driver P011041 01A Rev A 159 gt EMULEX Table A 13 NIC Event Log Entries Continued Appendix A Error and Event Log Information iSCSI Error and Event Log Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x0007 7 Warning A memory allocation failure This warning occurred due to a occurred during driver load failed memory allocation Check low Performance may be reduced memory conditions Use a smaller MTU or disable TCP offload to reduce driver memory requirements 0x0006 6 Error Driver load failed due to memory This failure occurred due to a failed allocation failure memory allocation in the driver Check low memory conditions 0x0005 5 Error Failed to register scatter gather This failure occurred due to a failed DMA memory allocation in the operating system Check low memory conditions 0x0004 4 Error Failed to map device registers This failure occurred due to a failed memory allocation in the operating system Check low memory conditions 0x0003 3 Error Unsupported medium This is an internal NDIS error Check the operating system installatio
141. ex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information Table A 13 NIC Event Log Entries Continued 157 NIC Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0x00036 54 Warning Incompatible optics Replace the incompatible SFP Replace with compatible optics for transceivers with compatible ones card to function for the adapter to function correctly 0x00035 53 Warning Optics of two types Remove one SFP transceiver or installed Remove one optic or install a matching pair of SFP install matching pair of optics transceivers 0x00034 52 Warning Optics faulted incorrectly Reseat the SFP transceiver If the installed not installed Reseat issue is not resolved replace the optics if issue not resolved transceiver replace 0x00033 51 Warning SR IOV virtualization failed Check system BIOS settings or initialization Check system BIOS disable SR IOV for the adapter settings or disable SR IOV for the adapter 0x00032 50 Warning The Ethernet link is down due to Improve the cooling conditions for PHY over temperature condition the device Improve cooling for the device 0x00031 49 Warning RSS is limited to 4 queues Enable Enable Advanced Mode in the Advanced Mode in the PXE BIOS to PXESelect BIOS utility during boot to use up to 16 queues This may use up to 16 queues This may re
142. f 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 environment variable is not terminated with a slash so you must provide one in the string Windows environment variables are not case sensitive Configuration Identification AUTOPILOT ID This section appears at the beginning of every AutoPilot configuration file and contains revision and label information The revision entry identifies the file s version number and the date on which it was produced The label entry is used to identify the configuration that the file supports This section may appear
143. failed in the iSCSI driver during initialization This failure may indicate a low memory condition 0x16 Error An ACIT API failed An internal API failed in the iSCSI driver during initialization This failure may indicate a low memory condition 0x17 Error Unsupported hardware failing driver load Driver loading failed because the PCI Vendor ID and Device ID are not supported Check the adapter configuration 0x18 Error Memory could not be allocated failing driver load This failure occurred because of a failed memory allocation in the driver This failure may indicate a low memory condition 0x19 Warning WMI driver error code A The iSCSI driver failed a WMI IOCTL request from the port driver The event log entry includes the WMI request code in error An operation attempted from the Microsoft WMI application resulted in an error Check the operation being attempted for errors Oxla Warning WMI IOCTL error code A The iSCSI driver failed a WMI IOCTL request from the port driver because the request was failed by the ARM firmware The event log entry includes the request code in error An operation attempted from the Microsoft WMI application resulted in an error Check the operation being attempted for errors Ox1b Warning A configuration parameter is out of range Emulex Drivers for Windows User Manual The iSCSI driver failed to load a co
144. gement 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 Emulex Drivers for Windows User Manual P011041 01A Rev A o Appendix D AutoPilot Installer Command Line and Configuration File Parameters 182 gt EMULEX AutoPilot Installer Syntax You can change only the installation report folder the file name is auto generated In the following example x could be any available drive ReportLocation x autopilot reports installs SilentinstallEnable Enabling Unattended Installation Note Setting the SilentInstallEnable parameter to true in the configuration file is functionally equivalent to supplying the silent switch on the command line You cannot specify the SilentInstallEnable parameter on the command line Default False Setting this parameter to true causes AutoPilot Installer to operate with no user interaction SilentRebootEnable Enabling Silent Reboot Default False AutoPilot Installer s default behavior in unattended installations does not 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 stop if the system is restarted However Windows can be configured to sta
145. gt EMULEX LDTO LRO LSO LUN MAC MPIO MSI MSS MTU N A NAT NDIS NIC NPar NPIV NTFS NUMA NVGRE OS PCI PCle PDU PF PFC POST PT PT PXE QFE QoS RAID RCMD RDMA RFC RoCE ROM RSC RSCN 1 Introduction 15 Abbreviations link down timeout large receive offload large send offload logical unit number Media Access Control multipath input output message signaled interrupts maximum segment size maximum transmission unit not applicable network address translation Network Driver Interface Specification network interface card NIC partitioning N_Port ID Virtualization New Technology File System non uniform memory access network virtualization using generic routing encapsulation operating system Peripheral Component Interconnect interface Peripheral Component Interconnect express protocol data unit PCI function process flow control or priority flow control power on self test point to point Preboot Execution Environment Quick Fix Engineering quality of service redundant array of independent disks Remote Command Service remote direct memory access Request for Comments RDMA over Converged Ethernet read only memory receive segment coalescing registered state change notification Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX RSS Rx SACK SAN SAS SCSI SFP SLI SMB SR IOV SSH TCP TCP IP TOE TSO Tx UDP UEFI UMC VF VLAN VLAN ID V
146. he command line type sc query intelppm If the results indicate that the intelppm driver is running you must disable it At the command line type sc config intelppm start disabled On all systems it may be necessary to set the power options to High Performance See the operating system documentation for details Monitoring TCP Offloads To monitor TCP offloads in a command window type netstat t This command indicates the offload state for each TCP connection of the system Windows Server 2008 and later versions allows TCP offloads in more scenarios than previous versions of Windows Server In particular TCP offloads can occur with the Windows firewall enabled Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX TCP Offload Failure 4 Troubleshooting 139 Troubleshooting the NIC Drivers Table 4 4 lists common reasons why TCP offloads do not occur and their potential solutions Table 4 4 Troubleshooting TCP Offload Failures Reasons for No TCP Offload Chimney offload is disabled on the system Solutions For Windows Server 2008 and Windows Server 2008 R2 To determine whether Chimney offload is enabled or disabled at the command line type netsh interface tcp show global To enable Chimney offload at the command line type netsh interface tcp set global chimney enabled To disable Chimney offload at the command line type netsh interface tcp set global chimney disabled For Windows
147. he operating system s TCP IP stack This reduces the per packet receive processing overhead and CPU usage if standard 1514 byte sized frames are in use Notes If checksum offloads are disabled RSC must also be disabled RSC depends on checksum offloads for better performance Both RSC IPV4 and RSC IPV6 are coerced to zero if TCP Connection Offload IPV4 is enabled RSS Base Processor Group Min 1 Max 63 Windows Server 2012 This defines the base processor group for the RSS queues on the network adapter A processor group contains 64 logical processors This value can be modified in conjunction with the RSS Base Processor Number to explicitly select the desired RSS processors for the adapter RSS Base Processor Number Min 1 Max 63 Windows Server 2012 This defines the base processor number for the RSS queues on the network adapter within the given processor group A processor group contains 64 logical processors so this value ranges from 0 to 63 This value can be modified in conjunction with the RSS Base Processor Group to explicitly select the desired RSS processors for the adapter RSS Max Processor Group Min 0 Max The number of processor groups present on your system Emulex Drivers for Windows User Manual Windows Server 2012 RSS Max Processor Group allows you to set the maximum number of processor groups for the RSS CPUs P01104
148. he specific adapter The Windows drivers support the following protocols Note Fibre Channel FC FC over Ethernet FCoE Ethernet NIC which includes the TCP Offload Engine TOE Internet Small Computer System Interface iSCSI RDMA over Converged Internet RoCE for the OCe14000 series adapters TOE is not supported on OCe14000 series and LPe16202 adapters Driver Information This document explains how to install the Windows drivers on your system and configure the drivers capabilities based on the supported networking protocols FC and FCoE o Configuring the FC FCoE driver parameters o Improving server performance with FC FCoE drivers Ethernet and TOE o Configuring NIC driver options o Configuring SR IOV o Configuring NVGRE o Configuring RoCE supporting SMB Direct o Configuring Universal Multi channel UMC o Configuring NIC partitioning NPar for Dell adapters only o Tuning network driver performance iSCSI o Configuring iSCSI driver options o Creating non bootable targets o Configuring Multipath I O A NIC teaming package driver and manager are also available as a separate download The OneCommand NIC Teaming and VLAN Manager User Manual is available for download as well See the Emulex website for more information Emulex Drivers for Windows User Manual P011041 01A Rev A 1 Introduction 13 gt EMULEX Operating System Requirements Operating System Requirements One of the following ope
149. hooting the Cisco Nexus Switch Configuration Note LACP cannot be used on an FCoE port Table 4 2 Cisco Nexus Switch Situations Issue 1 Windows creates the NTFS partition but then reports that The hard disk containing the partition or free space you chose has a LUN greater than 0 Setup cannot continue Dell 1850 server N stuck during the GUI portion of the installation right from the beginning HP DL385G2 server Windows reboots successfully but then gets Solution Set up the FCoE switch ports as follows no priority flow control mode on untagged cos 0 e flowcontrol receive on flowcontrol send on spanning tree port type edge The system is showing an excessive number of I O timeouts as a result of the switch routing frames to the incorrect port Ensure that LACP is not used on the FCoE port Emulex Drivers for Windows User Manual P011041 01A Rev A 4 Troubleshooting 121 SG EMULEX Troubleshooting the FC FCoE Driver Event Trace Messages ELS Log Messages 0100 0130 Ipfc_mes0100 FLOGI failure ulpStatus x x ulpWord 4 x x Description An ELS FLOGI command that was sent to the fabric failed Severity Error Log LOG ELS verbose Action Check the fabric connection Ipfc_mes0101 FLOGI completes successfully NPortid x x RaTov x EdTov x x Description An ELS FLOGI command that was sent to the fabric succeeded Severity Information Log LOG ELS verbo
150. ia Piiniat ia iadaan 144 Error Codes TableSaennrarienror nn e e e E eeen aeea A 145 Viewing the FC FCoE Event Log irissscisesscce eek teed ienee bdce caved etewsenel bee ueere tins 151 Event Log Interpretation cccccccc cece eee eee sense eeeeeeeeeeeeeee sate saeecaeesenentngas 151 Additional Event Log Information ccc eee etter t eet ae 151 ASC ASCO e Er r E E O E enti canna A RN E 153 Additional Notes on Selected Error Codes ccceceeeee eee ne ee ee ee eee nee e teeta ens 154 NIC Error and Event LOGS ccsciccscsscsstaccsssccsseccssscesasessnscssacecssssscssesescrscasasesses 155 Viewing the NIC Error LOG crix cenvisncnsvereinscunveeneboes eisei Rares ipceckaps sapcennenenaes 155 ROCE Event LOG visesecresrssendsseaberearerecceieieceehseennereeaadseguawaredcousedensinerawres 155 NIG Event LOG iviccindicniarwcunestereniderriereereneveereeirans EEE EEE ETE 156 ISCSI Err r and Ev nt LO Goi sidrmasinnnivacmnseneivaraaneneiierka Aa 160 Viewing the iSCSI Error and Event Log on Windows Server 2008 ee es 160 iSCSI Error Log on Windows Server 2008 cccceeceeeeeseeeeeeeeeeeeeeteeeeeaneeennes 162 Viewing the iSCSI Error Log on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Window Server 2012 RA a E a E E AE E E tat 165 Emulex Drivers for Windows User Manual P011041 01A Rev A 6 DE EMULEX Table of Contents 7 Appendix B Configuring iSCSI through DHCP
151. ications onto your computer Note This procedure does not install drivers and no driver changes are made until you run the AutoPilot Installer To load the driver kit 1 Download the driver kit from the Emulex website to your system 2 Double click to run the driver kit The Emulex Kit Welcome page appears 3 Click Next The Installation Options page appears 4 Select one or both of the following options e Perform Installation of Software copies the driver kit for your operating system to your computer e Unpack All Drivers extracts all drivers to the current user s Documents folder Select this option to perform boot from SAN installations The Operation in progress page shows the kit file loading progress After the kit files are loaded the Installation completed page appears 5 If you wish to continue with the installation ensure that Start AutoPilot Installer is checked Click Next AutoPilot Installer AutoPilot Installer runs after the driver kit is loaded and the OneCommand Manager application is installed AutoPilot Installer can install drivers e Immediately after the driver kit has been loaded e Ata later time using an interactive installation e Through an unattended installation AutoPilot Installer provides e Command line functionality Initiates an installation from a command prompt or script Configuration settings can be specified in the command line e Compatibility verification Verifies that
152. ice Manager 2 Click the plus sign next to the Emulex PLUS driver class Right click the Emulex driver and click Uninstall 4 Click OK in the Confirm Device Removal window 9 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 35 DG EMULEX FC FCoE Driver Configuration 3 Configuration Note For information on configuring profile management see the OneCommand Manager Application User Manual or the OneCommand Manager Command Line Interface User Manual FC FCoE Driver Configuration The Emulex Storport Miniport driver has many options that you can modify to provide different behavior You can set Storport Miniport driver parameters using the OneCommand Manager application Refer to the OneCommand Manager Application User Manual for information on using this utility to configure the driver Configuring FC Driver Parameters Table 3 1 Storport Miniport Driver Parameters provides information such as the allowable range of values and factory defaults Parameters can be entered in decimal or hexadecimal format A parameter has one of the following activation requirements e Dynamic The change takes effect while the system is running e Reset An adapter reset from the utility is required before the change takes effect e Reboot A reboot of the entire machine is required before the change takes effect In this case you are prompted to perform a reboot when you exit the utility Notes e Ifyo
153. ick the Uninstall icon in the tool bar above the program list If you have User Access Control enabled click Continue when asked for permission e Emulex FC kit 2 xx xxx e Emulex FCoE kit 2 xx xxx e Emulex NIC 4 xx xxx e Emulex iSCSI kit 4 xx xxx 4 Click Yes when prompted to remove the kit After the kit is removed from the system click OK Server Core System To uninstall a driver kit on a Server Core system 1 From the system prompt navigate to the Program Files folder 2 Navigate to Emulex AutoPilot Installer 3 Run the following batch files e Uninstall_fc_kit bat e Uninstall_cna_kit bat e Uninstall_nic_kit bat e Uninstall_iscsi_kit bat The driver files are removed from the system On all platforms the reports folder in the Emulex AutoPilot Installer folder is not removed so you can still view installation history and the drivers that have been installed on the system You can delete the reports folder at any time Uninstalling the Emulex Drivers The Emulex Storport Miniport and Emulex PLUS ElxPlus drivers are uninstalled using the Device Manager Windows Server 2008 Note On Windows 2008 after the message Warning you are about to uninstall this device from your system is displayed you must select Delete the software for this device to uninstall the driver Emulex Storport Miniport Driver To uninstall the Emulex Storport Miniport driver 1 Select Start gt All Programs gt Administrative Tools g
154. iguration sisisicciier animist RAIL OO FC FCoE Driver CoOnfiGuratiom se sinsssdareainctinasseiatennsstenascecsseenssemaseetasim esdnnsen 35 Configuring FC Driver Parameters soccsicvssseveseciestiieen verve rstrecesrecaere cases eadins 35 Server Performance with FC Drivers sscescxcevieces eases laxeesantesadersapedesadveasee sacs 43 I O Coalescing icc iteecust seiie seer yecccdoe genet da oes wed oon eer anaa hie wed EA PEPENGET 43 Performance Testing ccccc ccc c eee eee e eee eee e eee eee ttt ttt ttrt EE EEEEEEEEEEEEEEEEEEEEEEEEEEH 44 NIC Driver Configur ti N sicciccndcncecapretadnetecdnteumetariaieseieieebeneeenae eared 45 Configuring NIC Driver Options cccccccce cece cece ee eset ee eee ee eaee esate eeaeeeenenennnes 45 Advisory PowerShell Behavior cccccccccccceeeeeceeeeeeeeeeeeeeeeateeateseteeeesgnesanenes 61 Considerations for Using UMC and NIC ccc cece eee eee etter 62 Configuring Windows Server NIC Driver Parametels ccccceeeeeeeeeeeeeeeeeennees 63 Modifying Advanced Properties cc cece cece eee nee nner eee 63 Statistics Property Page ssciic sca videvage cad ini eed seed pako Ci eee bbws yh dee the es ahi ee ee 65 Using OCCFG for Windows NIC Driver Options ccccccceeeceee esses seats eee ee ene ees 69 Displaying OCCFG Hel p 0 rene 69 Selectingan Adapter sisieudisssadastivelevad ga neeo eka cantawcead eacppeeddas dae Oya ees neat dead cc 71 Configuring Device ParaMet
155. iisscxtvtcaseoelepeeanbteesbleensteleiiebusscthaicemegotass 115 M ltipath SUpport rire n ieii a Eaa E A o EE AAA E EE 115 Logging into Targets for Multipath Support ce eect ented 116 Maximum Transmission Unit MTU for iSCSI Connections cceeeeeee eee 117 iSCSI Error Handling vs isccsteccasscoadestersactey letedebrneetaas goredsestigrersieg ieteiesens 117 Configuring LDTO and ETO on the Windows Server ceceee eee eee neta eee ened 118 Error Handling Under MultiPath MPIO and Cluster Configurations 0068 118 4 Troubleshooting ssssssssnnnnsnssnunnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnna LLO General Troubleshooti g srssririiiivosrisiinanrirrndisar innne aranana a naa 119 Emulex Drivers for Windows User Manual P011041 01A Rev A 5 Table of Contents gt EMULEX Troubleshooting the FC FCOE Driver ssssssssnssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 120 Troubleshooting the Cisco Nexus Switch Configuration ccceeeee eee eee es 120 EVENE Trace MESSAGES oc ciccivsseccoscedereasineeteeeekenediurenabs Sea evesdengardeee ERED a tiae 121 ELS Log Messages 0100 0130 c ccccccce cee eeeeeeet ease eeeseeeeeesatesatteanesneenas 121 Discovery Log Messages 0202 0262 0 ccece cece eee rreren eter eee eas 123 Mailbox Log Messages 0310 0326 cccccccececee tees eeeeeeeeeeeeeateaueesaeeeneeenenas 127 INIT Log Messages 0400 0463 0
156. in the network stack This copy dramatically increases the memory bandwidth and CPU requirements for receive data e Sending and receiving of acknowledgement packets is handled entirely in hardware reducing PCle bus usage and interrupts e TCP timers including delayed acknowledgement 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 must use 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 adapter receive path is zero copy for applications that prepost receive buffers or that issue a socket read before the data arrives Ideal applications use Microsoft s Winsock2 Asynchronous Sockets API which allows posting multiple receive buffers with asynchronous completions and posting multiple send operations with asynchronous completions Applications that do not prepost receive buffers may incur the penalty of the data copy and the performance improvement is significantly less noticeable Applications that transmit large amounts of data show excellent CPU efficiency using TCP offload TCP offload allows the network driver to accept large buffers of data to transmit Each buffer is roughly the same amount of processing work as a si
157. in the system for consuming receive data TCP Offload Transmit Rate The transmit data rate of the offloaded TCP connections This is the portion of the total Transmit Throughput contributed by offloaded TCP connections TCP Offload Receive Rate The receive data rate of the offloaded TCP connections VMQs Allocated The current number of Virtual Machine Queues allocated Interrupt Rate Emulex Drivers for Windows User Manual The number of interrupts per second generated by the adapter The interrupt rate can be tuned by modifying the Interrupt Moderation parameter P011041 01A Rev A gt EMULEX 3 Configuration NIC Driver Configuration Table 3 4 NIC Driver Properties Statistics Continued Statistic Name Receive Drops No Memory DMA Limited Description The number of packets dropped as a result of insufficient buffers posted by the driver This is generally the result of the CPU core used for any receive queue reaching 100 The system may lack sufficient CPU cycles to post receive buffers at the necessary rate A lot of small packets lead to this behavior on almost any CPU since the processing time for small packets is very high in the networking stack Using a teaming driver may also lead to this since it increases the CPU load during receive Increasing the number of Receive Buffers in the advanced property page may alleviate some of these drops in particular if the drops a
158. int or import the saved reg file and reboot Verifying the Driver Version To verify that the Emulex device driver meets the minimum requirements 1 Select Server Manager gt Dashboard gt Tools gt Computer Management 2 Click Device Manager The Device Manager opens a File Action Media Clipboard View Help 3 O 0O0 m gt is yen ov SSD NANOS SAREE SNELL AE we File Action View Help F l l raji la e m eB Be IPRS 2 WIN QosPoDsiHeG gt 7 Computer l D ey Disk drives J p A Display adapters 3 DVD CD ROM drives ae ef Floppy disk drives RETH i Floppy drive controllers Human Interface Devices a IDE ATA ATAPI controllers oN ah amp Keyboards rage Oms A Mice and other pointing devices E Monitors P Network adapters i Emulex OneConnect OCeiT10 1 NIC amp Microsoft Hyper V Network Adapter y Microsoft Hyper V Network Adapter 3 S Microsoft Hyper V Network Adapter 4 oui Microsoft Kernel Debug Network Adapter YD Ports COM amp LPT pd Print queues p Dp Processors b lt gt Storage controllers p gt 7 System devices eh eh ee ed ERVER GROUPS f groups 1 Servers total 1 Figure 3 4 Device Manager for Windows Server 2012 3 Open the Network Adapters item find the Emulex device and right click it Select Properties from the context menu The Properties dialog box opens showing the Driver page see Figure 3 5 on page 80 The Driver page contains the driver ve
159. ion Enabled nnect 0Cei4102 U NIC 3 Domain n x OneConnect OCe14102 U NIC 4 Ethernet 9 Emulex OneConnect OCe14401 UX NIC Figure 3 9 Get NetAdapterRDMA RoCE Enabled Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q2 gt lt EMULEX NIC Driver Configuration o Get NetOffloadGlobal see Figure 3 10 opyright C 2013 Microsoft Corporation All rights reserved S F Users Administrator gt Get NetOffloadGlobalSetting feceiveSideScaling Enabled eceiveSegmentCoalescing Enabled himney Disabled askOff load Enabled VetworkDirect Enabled NetworkDirectAcrossIPSubnets Blocked PacketCoalescingFilter Disabled Figure 3 10 Get NetOffloadGlobal RoCE Enabled If the profile is correct and NetworkDirect is enabled you will see active NetworkDirect listeners on IP addresses port 445 assigned to the NICs using netstat xan Using SMB Direct with NetworkDirect Because RoCE is supported in Windows using SMB Direct with NetworkDirect it is important that SMB Direct and NetworkDirect be configured correctly From the Advanced tab of the Network Interface Properties page 1 Enable the NetworkDirect parameter 2 Set the NetworkDirect MTU Emulex recommends a NetworkDirect MTU of 4096 bytes for OCe14400 series adapters Note The NetworkDirect MTU affects only RoCE traffic but the NIC traffic still uses the Packet Size MTU An SMB Server accepts an incoming c
160. ion iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID Severity Message Recommended Resolution 0x36 Warning Connection was invalidated This condition is detected by the OneConnect internally the received firmware If this message is unexpected check ITT TTT value was greater the iSCSI configuration than the maximum supported ITTs TTTs 0x37 Warning Connection was invalidated This condition is detected by the OneConnect internally due to an incoming firmware If this message is unexpected check TCP RST the iSCSI configuration 0x38 Warning Connection was invalidated This condition is detected by the OneConnect internally due to TCP protocol firmware If this message is unexpected check warning SYN received the iSCSI configuration maximum retransmits exceeded urgent received etc 0x39 Warning Connection was invalidated This condition is detected by the OneConnect internally due to TCP RST sent firmware If this message is unexpected check by the transmit side the iSCSI configuration 0x3a Warning Connection was invalidated This condition is detected by the OneConnect internally due to an incoming firmware If this message is unexpected check TCP FIN the iSCSI configuration 0x3b Warning Connection was invalidated This condition is detected
161. irmware version must be 2 72a0 or later If an earlier version is used the driver runs in SLI 2 mode and does not support NPIV e NPIV is not available on 1GFC and 2GFC adapters Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Table 3 1 Storport Miniport Driver Parameters Continued 3 Configuration 39 FC FCoE Driver Configuration Parameter ExtTransferSize Definitions 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 default transfer size is 512KB for all controller models If set to 1 the maximum transfer size is 1MB If set to 2 the maximum transfer size is 2MB If set to 3 the maximum transfer size is 4MB Value 0 3 Default 0 disabled Activation Requirement Adapter Protocol LightPulse adapters only including LPe15000 and LPe16000 HBAs FrameSizeMSB n 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 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
162. is a network virtualization method that uses encapsulation and tunneling to create large numbers of VLANs for subnets that can extend across dispersed data centers and layer 2 the data link layer and layer 3 the network layer The purpose is to enable multi tenant and load balanced networks that can be shared across on premises and cloud environments NVGRE was designed to solve issues caused by the limited number of VLANs that the IEEE 802 1Q specification enables which are inadequate for complex virtualized environments and make it difficult to stretch network segments over the long distances required for dispersed data centers Setup Hardware Resources e Two host servers e Virtual Machines Emulex recommends two per Hyper V host e One 10GDbE or 40GbE Ethernet Switch e Two OCe14000 series adapters one per host server Software Resources e Windows Server 2012 with Hyper V e Windows Server 2012 on the Virtual Machines e Add and Remove PowerShell Policy Scripts for each host server To set up NVGRE 1 On the Hyper V hosts and peer change the execution policy to allow PowerShell scripts to run e Set Execution Policy unrestricted Force e Run HostRegedit run this once on the Hyper V host only This sets the registry key to use VMQs and allows remote PowerShell scripts to be run on the host 2 Set up non blank administrator passwords on the peer to run remote PowerShell scripts 3 Copy the NIC driver to C driver on the Hyper V
163. is parameter to true to cause silent mode installations to update or install the Storport Miniport driver on each adapter in the system without regard for the currently installed driver type replacing any installation of the SCSIport Miniport or FC Port driver ForceDriverUpdate Forcing a Driver Version Update Default False By default if the same version of the driver is already installed an unattended installation proceeds with installing only the utilities To force a driver update even if the same version of the driver is installed set this parameter to true Note ForceDriverUpdate applies only to unattended installations in interactive installations this parameter is ignored and you are asked if the driver should be updated Emulex Drivers for Windows User Manual P011041 01A Rev A o Appendix D AutoPilot Installer Command Line and Configuration File Parameters 181 gt G EMULEX AutoPilot Installer Syntax 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 Configur
164. lation offloads Update firmware on the disabled 0Ce14000 adapter 0x4000003AL Informational N A N A 0x0000038L 56 Warning The device firmware does not Revert to default mode for ETS support ETS functionality in SR IOV support or multichannel mode 0x0049 73 Informational Correct optics installed This message is informational 2 is a place holder for the NIC controller name 0x0046 70 Warning Unqualified SFP module detected Replace the SFP module on 2 Port 3 from amp part number 5 2 is a holder for the NIC controller name 3 4 5 are placeholders for other arguments in the log message 0x0045 69 Informational SFP module detected on Port This message is informational 3 from YA part number 5 2 is a place holder for the NIC controller name 3 4 are placeholders for other arguments in the log message 0x00037 55 Warning This adapter may have an issue This adapter exposes a vulnerability recovering from corrupted use of to the VM that may allow the VM to SR IOV Assigning an SR IOV device crash the entire physical computer to a Virtual Machine could leave the This is no different than running a system vulnerable and lead to physical adapter SR IOV should only instability Emulex recommends be used if the VM has a trusted that you assign SR IOV devices only server administrator to Virtual Machines that run trusted workloads or consider disabling the use of SR IOV Emul
165. lder and C is your Windows system drive the path is C Program Files Emulex AutoPilot Installer Drivers Storport x64 HBA Click OK Select Emulex PLUS Click Next and click Next again to install the driver Click Finish The initial ElxPlus driver installation has completed Continue with manual installation of the Storport Miniport Driver See Installing or Updating the FC FCoE Storport Miniport Driver on page 28 for this procedure Updating the Emulex PLUS ElxPlus Driver Note Only one instance of the ElxPlus driver must be installed even if you have multiple adapter ports installed in your system To update an existing ElxPlus driver from the desktop 1 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 22 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 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 Emulex Drivers for Windows User Manual P011041 01A Rev A DE EMULEX 2 Installation 28 10 11 12 Manuall
166. le 64 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 45 DG EMULEX NIC Driver Configuration NIC Driver Configuration Notes e TOE is supported and enabled by default e TOE is not supported on LPe16202 CNAs and OCe14000 series adapters Configuring NIC Driver Options The Windows Server NIC driver supports configurable driver options through the Advanced Property page in the Windows Device Manager For information on how to configure the options through the Advanced Property page see Modifying Advanced Properties on page 63 For more information on NIC driver options see Network Driver Performance Tuning on page 102 You can also set configurable driver options using Microsoft PowerShell on Windows Server 2012 Refer to the documentation that accompanies the Windows Server 2012 operating system for more information on using PowerShell See Table 3 3 on page 46 for a list of NIC driver options Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 3 Configuration 46 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Option Name Class of Service 802 1p Acceptable Values Automatic Priority default Filtered Priority User Priority Disable Priority Emulex Drivers for Windows User Manual Supported Operating Systems Windows Server 2008
167. main memory is the other major concern for networking throughput The ideal situation is using high speed memory with all memory channels populated per CPU typically three or four DIMMs per CPU socket For the ideal performance the same DIMM size must be used in each memory channel to allow perfect memory channel interleaving Features such as memory sparing or memory mirroring dramatically decrease the memory bandwidth of the system and cause drops TCP connection offload may lead to increased drops as a result of no memory If TCP connection offload is used enabling flow control may reduce the drops Alternatively disabling TCP connection offload may improve performance P011041 01A Rev A gt EMULEX 3 Configuration NIC Driver Configuration Table 3 4 NIC Driver Properties Statistics Continued Statistic Name CRC Errors Description The number of packets dropped as the result of CRC errors on the layer 2 Ethernet packet In products that expose multiple PCle functions per Ethernet port this statistic is only incremented for the lowest PCI function per port since the packet cannot be further classified because of the error Receive IP Checksum Errors The number of receive packets with an incorrect IPv4 checksum These packets are provided to the TCP IP stack for disposal in the operating system Receive UDP Checksum Errors The number of receive packets with an incorrect UDP checksum These packets a
168. maximum supported link speed P011041 01A Rev A 55 3 Configuration 56 gt lt EMULEX NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition SR IOV Disabled default Note For 0Ce11102 SR IOV enables the adapter to Enabled LPe16202 and allocate virtual PCI functions for O0Ce14000 series each virtual machine in Hyper V adapters only Note that the virtual switch and virtual network adapter must have Windows POVAT ANNE SR IOV enabled in the Hyper V Windows Server 2012 R2 Manager SR IOV requires a platform with IOMMU virtualization VT d AMD Vi If using SR IOV the Emulex NIC driver must be installed on each virtual function within the virtual machine SR IOV provides a direct hardware interface from the virtual machine to the networking adapter which reduces latency and improves performance The Windows Server 2012 and Windows Server 2012 R2 SR IOV architecture establishes each Emulex virtual NIC with a corresponding emulated NIC This allows the virtual machine to seamlessly failover to the emulated NIC if SR IOV is disabled It also allows Live Migration to another system regardless of the installed NIC hardware Note The driver currently supports the following virtual functions for the following adapter families o OCel11
169. more information Note Ensure that SR IOV is enabled on the server and on the Emulex adapter prior to configuring the Hyper V virtual switch The Windows Server 2012 and Windows Server 2012 R2 Servers treat SR IOV as an offload an active active team with virtual function and an emulated adapter That means each Emulex SR IOV adapter is accompanied by a fully functional emulated NIC The emulated NIC is named Microsoft Virtual Network Adapter and the TCP IP stack is only bound to this device Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration DG EMULEX NIC Driver Configuration 82 After the Emulex driver is loaded the Emulex SR IOV virtual function is used for all unicast receive and transmit traffic The emulated NIC handles multicast and broadcast traffic If SR IOV is disabled the Emulex adapter is removed from the virtual machine and all traffic automatically uses the emulated NIC This technology allows Live Migration of Virtual Machines if using SR IOV Note If multiple adapters are added to the virtual machine Emulex recommends using MAC addresses to map the Emulex Network adapter to the corresponding Microsoft Virtual Network adapters Verifying SR IOV If SR IOV is enabled it can be verified by opening the Device Manager within the virtual machine and examining the information about the transmit and receive packets that are using the SR IOV virtual function This is the final verification th
170. mulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt X EMULEX NIC Driver Configuration oe help performance If the same four processor server uses RSS there are four parallel running 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 issue you can reduce the number of RSS CPUs or disable RSS entirely Poor RSS behavior is typical only in network performance testing applications that receive data but perform no other processing For other applications RSS allows the application to scale other processing tasks across all CPUs thereby improving overall performance RSS offers the most benefit for applications that create numerous short lived connections These applications are typically CPU limited instead of network bandwidth limited For information on modifying the RSS Queues parameter see Configuring NIC Driver Options on page 45 Note Microsoft currently does not schedule RSS processing on all hyper threaded CPUs For example only CPU 1 and 3 have RSS queues on a dual cor
171. n Severity Log Action See Also Received a PLOGI from a remote NPORT and its FC service parameters match this adapter Request can be accepted Information LOG _ELS verbose No action needed informational Ipfc_mes0112 Ipfc_mes0115 Unknown ELS command x x received from NPortld x x n Description Severity Log Emulex Drivers for Windows User Manual Received an unsupported ELS command from a remote NPORT Error LOG _ELS verbose P011041 01A Rev A gt G EMULEX 4 Troubleshooting 123 Troubleshooting the FC FCoE Driver Action See Also Check remote NPORT for potential issue Ipfc_mes0112 Ipfc_mes0128 Accepted ELS command OpCode x x Description Severity Log Action Accepted an ELS command from a remote NPORT Information LOG _ELS verbose No action needed informational Ipfc_mes0129 Rejected ELS command OpCode x x Description Severity Log Action Rejected ELS command from a remote NPORT Information LOG _ELS verbose No action needed informational Ipfc_mes0130 ELS command error ulpStatus x x ulpWord 4 x x Description Severity Log Action ELS command failure Error LOG ELS verbose Check remote NPORT for potential issue Discovery Log Messages 0202 0262 Ipfc_mes0202 Start Discovery Link Down Timeout x x initial PLOGICount d Description Severity Log Action Device discovery rediscovery after FLOGI FAN or RSCN has star
172. n iSCSI Driver Configuration 5 Log into the iSCSI target using WMI For more information see Logging into Targets for Multipath Support on page 116 6 Enable MPIO a Select Start gt Administrative Tools gt Server Manager b In the Server Manager tree click Features c In the Features area click Add Features d In the Add Features wizard on the Select Features page select the Multipath I O check box and click Next On the Confirm Installation Selections page click Install f After the installation is completed click Close on the Installation Results page g When prompted to restart the computer click Yes h Click Close 7 Discover all possible paths to all devices on the system a Open the MPIO control pane and 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 8 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 the disk and select the MPIO tab Logging into Targets for Multipath Support After you have successfull
173. n 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 issue 0x0001 1 Informational The driver successfully loaded This message is informational and indicates successful loading of the device driver iSCSI Error and Event Log This section provides information on iSCSi error and event logs Viewing the iSCSI Error and Event Log on Windows Server 2008 The iSCSI driver generates error codes in the system event log in the form of Event ID 11 errors These error codes can be viewed by using the Event Viewer application To view the error codes 1 2 3 4 Click the Start tab on the bottom of the screen Click Run Type eventvwr and click OK Click Windows Log Emulex Drivers for Windows User Manual P011041 01A Rev A 160 se s Appendix A Error and Event Log Information 161 gt lt EMULEX iSCSI Error and Event Log 5 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_INTERNAL_ADAPTER_ERROR which translates to an Event ID 11 entry in the system event log The following is an example of the iSCSI driver error code 0x11800003 viewed with the Event Viewer application see Figure A 2 on page 161 The window shows the drive
174. n page 96 e Passive mode Maximum passive connections are calculated using the following equation o 511 2 number of ports e Passive and Active mode Active and passive connection counts together must not exceed 511 2 number of ports as calculated above Emulex Drivers for Windows User Manual P011041 01A Rev A DG EMULEX 3 Configuration Q6 NIC Driver Configuration Table 3 5 shows the maximum number of SMB Direct active client mode connections that can be initiated on Windows Server 2012 and Windows Server 2012 R2 using the OCe14000 series adapters Table 3 5 SMB Direct Active Connections Client Mode Per Port for OCe14000 Series Adapters Adapter Type Windows Server 2012 Windows Server 2012 R2 1 port 40GbE adapter 31 15 2 port 10GbE adapter 15 7 4 port 10GbE adapter 7 3 The Maximum Queue Pair counts on a 1 port 2 port and 4 port OCe14000 series adapter are shown in Figure 3 16 Figure 3 17 and Figure 3 18 PS C Users Administrator OVIROCE gt Get NetAdapterkana MaxQueuePairCount 509 ifdesc Emulex Format List Property MaxQueuePairCount 7 Figure 3 16 Resource Counts on a 1 Port 10GbE or 40GbE OCe14000 Series Adapter x windows PowerShell PS C Users Administrator gt MaxQueuePairCount 25 MaxQueuePairCount 25 x PS C Users Admeinistrator gt MaxQuevePairCount 126 MaxQueuePairCount 126 MaxQuevePairCount 126 MaxQueucPairCount 125
175. n update to the Windows Server 2012 driver some parameter defaults are different from the inbox driver Emulex recommends that after you install the Emulex out of box driver you select reset to default on the Advanced tab of the Device Manager property page This returns all adapter and driver settings to the default values listed in this manual Low performance may occur if the Emulex NIC driver is installed on a system meeting the following conditions before installing Microsoft KB2846837 o A Windows 8 Windows 8 1 or Windows Server 2012 computer with multi core processors is in use o Three or more Ethernet ports are installed on the computer o RSS is enabled and sets the RSS profile to use the Closest parameter for the Ethernet adapters If these conditions exist install KB2846837 before installing the Emulex NIC driver Onelnstall Installer The Onelnstall Installer can be run in Interactive Mode or Silent Mode Note The Onelnstall Installer does not allow you to perform pre installation tasks or text only installations For these tasks use the driver kits The Onelnstall package is a self extracting executable file that installs the following software on your system All compatible protocol drivers o FC o FCoE o iSCSI o NIC o NIC RoCE ElxPlus driver supports the OneCommand Manager application persistent binding and LUN mapping and masking Emulex Drivers for Windows User Manual P011041 01A R
176. name for more information see Selecting an Adapter on page 71 The program prompts for an operation such as modifying or querying a parameter value 3 Follow the prompt The program provides a list of available registry parameters to modify or query 4 Type either the number of the corresponding option or a substring in the parameter name The substring must uniquely identify the parameter or occfg displays all potential options Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration gt lt EMULEX NIC Driver Configuration 19 5 To apply the parameters select the menu item to exit and reload the drivers Pressing lt Ctrl gt 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 displays help text and information regarding the legal values for each parameter This information can be dumped for all parameters by specifying the h option The following is an example help text for the RSS parameter RSS Receive Side Scaling RSS scales receive processing over multiple CPUs in parallel This scaling typically improves application performance however it tends to increase CPU usage on low end machines RSS is only supported on two primary adapters per device It will appear disabled for additional PCI functions in blade server configurations RSS requires Window
177. nd resulted in a Check Condition Warning LOG _FCP verbose Review SCSI error code values Ipfc_mes0730 Ipfc_mes0747 Target reset complete PathId x x Targetld x x Did x x Description Severity Log Action Remark A target reset operation has completed Warning LOG _FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0713 Ipfc_mes0748 Lun reset complete Pathld x Targetld x x Lun x x Description Severity Log Action Remark A LUN reset operation has completed Warning LOG _FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0703 Ipfc_mes0749 Abort task set complete Did x x SCSIId x x Description Severity Log Action Remark Emulex Drivers for Windows User Manual A task management has completed Warning LOG FCP verbose Review system configuration Possible side effect of cluster operations See also Message 0701 P011041 01A Rev A gt EMULEX 4 Troubleshooting 133 Troubleshooting the FC FCoE Driver Link Log Messages 1302 1306 Ipfc_mes1302 Invalid speed for this board d forced link speed to auto Description Severity Log Action The driver is re initializing the link speed to auto detect Warning LOG _LINK EVENT verbose None required Ipfc_mes1303 Link Up event tag x x link speed dG topology 0 Pt2Pt 1 AL d Descrip
178. ndicates 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 allows you to find out the status being reported by the target and to determine if there is an action that can be performed to return the device to functional status Nameserver Response Code 0x98 This code is useful in determining if the expected number of targets ina SAN configuration are being presented by the nameserver to the requesting adapter The number in byte 0x11 is the number of targets returned to the nameserver query made by the adapter If the number of targets does not match expectations examine the SAN configuration found in the switch tables and if that information shows targets or devices still missing check connections between the switch ports and those devices Context Allocation Failures A number of event codes for which the interpretation contains the phrase context allocation failure exist These types of events are referring to the internal memory constructs of the Emulex Storport Miniport driver and as such are intended for Emulex design engineers information If you encounter this type of code contact Emulex technical support for assistance Note Contex
179. ndows Server 2012 IPv6 UDP checksum computation RX Enabled Windows Server 2012 R2 Sind e Increases TX Enabled Virtual Enabled default Note For OCe11102 VMQs are dedicated hardware Machine Disabled LPe16202 and receive queues for virtual Queues OCe14000 only machines that filter receive packets based on the destination UA A MAC address or VLAN Receive with Hyper V buffers can be allocated for each queue from VM memory This improves network throughput by distributing processing of network traffic for multiple VMs among multiple processors It reduces CPU utilization by offloading receive packet filtering to NIC hardware VMQs prove beneficial when four or more VMs are in use Virtual Enabled default Note For OCe11102 VMQ enables direct DMA to VM Machine Disabled CNAs only Not memory Lookahead improves Queues applicable for packet steering performance by Lookahead LPe16202 and PCI prefetching adjacent header Split OCe14000 series buffer into a cache when adapters examining a packet Header Windows Server 2008 R2 buffers are continuous in physical memory since they belong to one pool For OCe11102 Lookahead split requires Advanced Mode Support and is enabled in the BIOS controller configuration Note Lookahead split is not supported for jumbo frames Virtual Enabled default Note For OCe11102 If this option is enabled with Machine Disabled LPe16202 and VMQs separate transmit queues Queues OCe14000 series are
180. nfiguration 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 Table 3 10 iSCSI Driver Options on page 113 for the correct range of values P011041 01A Rev A 168 SG EMULEX Appendix A Error and Event Log Information 169 iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID Severity Message Recommended Resolution Ox1d Warning A configuration parameter is The iSCSI driver ignored a configuration entry invalid because the entry was invalid Check the registry configuration for new driver parameter entries The invalid entry must be removed or corrected See Table 3 10 iSCSI Driver Options on page 113 for the correct range of values Oxle Error Failed to map Base Address The iSCSI driver was unable to load because it Register failing driver load was unable to map one or more PCI Base Address registers This failure may indicate a low memory condition or a hardware error Ox1f Error Hardware initialization has The hardware initialization has failed This failed error code A error causes the drive
181. ng unit CRC cyclic redundancy check CTCP Compound TCP DCB Data Center Bridging DCBX Data Center Bridging Capabilities Exchange DPC deferred procedure call DHCP Dynamic Host Control Protocol DID device ID Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX DIMM DMA DNS DOS DSM ETO ETS FC FC AL FCoE FCP FDMI FLOGI FW FSB GB GbE Gbps GUI HBA ICMP IEEE IET I O IOCB IOCTL IOMMU IOPs IP IPL IPs iSCSI IQN KB kb LACP LAN 1 Introduction 14 Abbreviations dual in line memory module direct memory access Domain Name Server disk operating system Device Specific Module extended time out Enhanced Transmission Selection Fibre Channel Fibre Channel Arbitrated Loop Fibre Channel over Ethernet Fibre Channel Protocol Fabric Device Management Interface fabric login firmware front side bus gigabyte gigabit Ethernet gigabits per second Graphical User Interface host bus adapter Internet Control Message Protocol Institution of Electrical and Electronics Engineers iSCSI Enterprise Target Input Output input output control block Input Output control input output memory management unit I O operations per second internet protocol initial program load IP Security internet Small Computer System Interface iSCSI Qualified Name Knowledge Base kilobyte Link Aggregation Control Protocol local area network Emulex Drivers for Windows User Manual P011041 01A Rev A
182. ngle TCP packet for non offloaded traffic The entire process of packetizing the data processing the incoming data acknowledgements and potentially retransmitting any lost data is handled by the hardware TCP Offload Exclusions Microsoft provides a method to exclude certain applications from being offloaded to the adapter Certain types of applications do not benefit effectively from TCP offload These include TCP connections that are short lived transfer small amounts of data at a time exhibit fragmentation from end to end or make use of IP options If an application sends less data than the MSS the driver like most TCP stacks uses a Nagling algorithm Nagling reduces the number of TCP packets on the network by combining small application sends into one larger TCP packet Nagling typically reduces the performance of a single connection to allow greater overall performance for a large group of connections During Nagling a single connection may have long pauses 200 ms between sending subsequent packets because the driver waits for more data from the application to append to the packet An application can disable Nagling using the TCP_NO_DELAY parameter TCP offload does not improve the performance for connections that Nagle because the performance is intentionally limited by the Nagling algorithm Telnet and SSH consoles are examples of connections that typically use Nagling Emulex Drivers for Windows User Manual P011041 01A Rev A
183. nnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnn 188 Command Script Example scciiiccrisseiscsriisedesssisessisssscsessscesdsarssnenssarssaenens 188 Appendix E RoCE Switch SUpport ssssssssnnsssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 190 DCBX Enabled Switch Connection PFC Mode s ssssssssssnnsnnssnannnnnnnnnnnnnnnnnnnnnnn 190 Emulex Drivers for Windows User Manual P011041 01A Rev A Table of Contents gt EMULEX Switch Configuration for PFC Priority 5 viceosiscivavactases temeaeismiargoienbearediensbs 190 Host Client Configuration SontcoscseGcnreber cau snka texaauwetebeesnapatstaeaaeuadebessenmatene 191 DCBX Disabled Switch Connection Generic Pause Mode cceeeee eee teeta eaten ees 191 Examples for Cisco SWICCH ccece cece eee e eee eee tees eee eeeeeeeeeeeeee sate satesateenneenenas 191 Verifying Switch Configuration in OneCommand Manager cceceee eee eer 194 Emulex Drivers for Windows User Manual P011041 01A Rev A 8 SXC EMULEX List of Figures 9Q List of Figures Figure 2 1 AutoPilot Installer Warning Software First Installation cccseeeeeeeenaes 24 Figure 3 1 Partial View of Windows Device Manager cceceeceeee este ee ee eee e eee 64 Figure 3 2 NIC Advanced Properties in Windows Server 2008 ccceee cece teeta eee 65 Figure 3 3 NIC Statistics Properties in Windows Server 2008 cceeee eee eee eens 66 Figure 3 4 Device Manager for Windows Server 2012
184. 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 adapter may not be functioning properly Check the adapter and reinstall the firmware if required 0x0e Warning iSCSI error was detected on session A ExpCmdSn B MaxCmdsSn C Emulex Drivers for Windows User Manual The iSCSI driver received an invalid iSCSI Command Sequence Number update from the target The event log entry indicates the session handle MaxCmdSN and ExpCmdsSN e Verify that the iSCSI target is certified by Microsoft Check for errors reported at the target The Emulex iSCSI adapter is only supported with certified targets e Check for software updates at the target vendor s website If applicable update the software e Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware P011041 01A Rev A SG EMULEX Appendix A Error and Event Log Information 167 iSCSI Error and Event Log Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 Continued Message ID Severity Message Recommended Resolution OxOf Warning The iSCSI target on session id The iSCSI d
185. number of shares that can be connected over RDMA Configuring UMC Note RoCE is not supported if UMC is enabled UMC allows you to divide a 10GbE port into multiple physical functions with flexible bandwidth capacity allocation These functions appear to the operating system and network as separate physical devices UMC can be configured on OCe14000 series adapters through the adapter BIOS or the OneCommand Manager application Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX 3 Configuration 100 NIC Driver Configuration e Toconfigure UMC using the adapter BIOS see the Boot for NIC iSCSI FCoE and RoCE Protocols User Manual e To configure UMC using the OneCommand Manager application see the OneCommand Manager Application User Manual or the OneCommand Manager Command Line Interface User Manual Refer to the Emulex Universal Multi Channel Reference Guide for additional information on UMC NPar Configuration Dell Only Notes e NPar is available only on Dell OCe14000 series adapters e If NPar is enabled RoCE cannot be configured on any function e Each partition must have standard NIC properties for stateless offload e SR IOV must be disabled on the adapter BIOS if NPar is used See the following documentation for information on disabling SR IOV on the adapter BIOS o To configure SR IOV using the adapter BIOS see the Boot for NIC iSCSI FCoE and RoCE Protocols User Manual o To configure SR
186. nvalid response Error LOG _ LINK EVENT verbose Review hardware configuration Contact Emulex technical support NPIV Messages 1800 1899 Ipfc_mes1800 NPIV FDISC failure VPI x x Error x x Reason x x Description Severity Log Action Virtual Port fails on a FDISC to the switch with the error and reason listed Error LOG _NPIV verbose Ensure that the switch supports NPIV Ipfc_mes1801 Memory allocation failure for NPIV port x x Description Severity Log Action Emulex Drivers for Windows User Manual Fails to allocated the block of memory for the Virtual Port Error LOG _NPIV verbose Ensure that the system has sufficient kernel memory P011041 01A Rev A ae 4 Troubleshooting 135 gt G EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes1802 Exceeded the MAX NPIV port x x Description Exceeded the number of Virtual Port allows on the adapter Severity Error Log LOG NPIV verbose Action Reduce the number of Virtual Ports Ipfc_mes1803 Virtual Port x x VPI x x successfully created Description Virtual Port ID is successfully created Severity Information Log LOG NPIV verbose Action No action needed informational Ipfc_mes1804 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 Ipfc_mes1900 x x sends ELS AUTH_CMD x x with TID x x Description
187. olicy type queuing output class roce90 Sample Switch PFC Verification on a Cisco Switch Ensure that the Mode is set to Auto and Operational Oper is On Cisco5548UP2 config show int eth 1 11 priority flow control Port Mode Oper VL bmap RxPPP TXPPP Ethernet1 11 Auto On 28 873 694950 Emulex Drivers for Windows User Manual P011041 01A Rev A sc Appendix E RoCE Switch Support 194 gt lt EMULEX DCBX Enabled Switch Connection PFC Mode Verifying Switch Configuration in OneCommand Manager Note You do not need to configure the OCe14000 series adapter in the OneCommand Manager application to enable RoCE with PFC You can use the OneCommand Manager GUI application or the OneCommand Manager CLI application to verify the switch configuration See the OneCommand Manager Application User Manual for more information on using the OneCommand Manager GUI application to verify the switch configuration See the OneCommand Manager Command Line Interface Manual for more information on using the OneCommand Manager CLI application to verify the switch configuration Emulex Drivers for Windows User Manual P011041 01A Rev A
188. ommon service parameters for fabric 0x37 Error reading common service parameters for nport 0x3B Failed to create node object 0x3C PRLI initiation failure 0x3D Recoverable UNREG base VPI error Bits 8 15 mailbox status 0x3E Recoverable UNREG VPI error Bits 8 15 mailbox status 0x42 Exhausted retries on FLOGI 0x45 ELS command rejected 0x49 Exhausted retries on PLOGI Ox4E World Wide Port Name mismatch on ADISC Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information FC FCoE Error and Event Logs Table A 2 Malfunction Errors Continued Bits 0 7 Ox4F Interpretation World Wide Node Name mismatch on ADISC 0x50 ADISC response failure 0x55 LOGO response failure 0x57 PRLI to non existent node 0x5A PRLI response error 0x5F CT command error 0x62 Name server response error 0x66 State Change Notification registration failure 0x6A Unrecognized ELS command received 0x6F Received PRLI from un typed source 0x73 Failed to pend PRLI for authentication 0x77 Failed to allocate Node object 0x7A REG_VPI failed 0xA3 Command context allocation failure OxAB SCSI command error OxAC Read check error 0xBO Node timeout device removal signaled to Storport Command Errors Table A 3 lists
189. on Severity Log Action See Also FCP device provided less data than was requested Supplement Information LOG _FCP verbose No action needed informational Ipfc_mes0730 Ipfc_mes0729 FCP command error ulpStatus x x ulpWord 4 x x XRI x x ulpWord 7 x x Description Severity Log Action Remarks The specified device failed an I O FCP command Warning LOG _FCP verbose Check the state of the target in question Ipfc_mes0730 is also recorded if it is a FCP Rsp error Ipfc_mes0730 FCP response error Flags x x SCSI status x x Residual d Description Severity Log Action Remark See Also The FCP command failed with a response error Warning LOG _FCP verbose Check the state of the target in question lpfc_mes0716 lpfc_mes0734 lpfc_mes0736 or lpfc_mes0737 is also recorded for more details if the corresponding SEVERITY level is set Ipfc_mes0729 Ipfc_mes0734 Read Check fcp_ parm x x Residual x Description Severity Log Action See Also Emulex Drivers for Windows User Manual The issued FCP command returned a Read Check Error Warning LOG _FCP verbose Check the state of the target in question Ipfc_mes0730 P011041 01A Rev A gt EMULEX 4 Troubleshooting 132 Troubleshooting the FC FCoE Driver Ipfc_mes0737 SCSI check condition SenseKey x x ASC x x ASCQ x x SrbStatus x x Description Severity Log Action See Also The issued FCP comma
190. on New SmbMultichannelConstraint on Target bench29client1 A Yes to All N No L No to All S Suspend 7 Help default is Y y InterfaceAlias Ethernet 5 InterfaceGuid be46d900 7861 4c62 b7a4 7a63f8b44543 InterfaceIndex 25 ServerName bench29client1 PSComputerName Select Administrator C Windows system32 cmd exe NUsers Adninistrator gt netstat xan Active NetworkDirect Connections Listeners SharedEndpoints Mode IfIndex Type Local Address Foreign Address Kernel scti 21 118 49367 Kernel 25 io 20 1 2118 49368 Kernel i Kernel gt Kernel 25 Listener Kernel 25 Listener 20 1 0 110 445 NA ee File Home Share View T F gt Network bench29client c v Search c Figure 3 15 SMB Multichannel Constraint SMB Direct Resource Usage This section describes how to use SMB Direct resources Active Connections Active connections describe the connections that a client makes to a server Passive connections describe the connections that a server allows the client to complete The maximum number of active connections per port for an adapter are required if setting the ConnectionCountPerRdmaNetworkInterface parameter Use Table 3 5 on page 96 to determine the correct number of maximum active connections based on your OCe14000 series adapter and operating system Note Passive and active connection limits for both the OCe14000 series adapters are e Active mode See Table 3 5 o
191. onfiguration a On the host and peer systems ensure that Tx pause flow control and Rx pause flow control are enabled on all the ports and interfaces that are RoCE enabled using operating system standard tools 2 Switch Configuration a Enable Tx generic pause flow control and Rx generic pause flow control on each port participating in the cluster b Enable Jumbo Frames or set the MTU to at least 4200 or greater Note Some switches have jumbo frame size support disabled on the port and global level by default Examples for Cisco Switch This section provides information for configuring a Cisco switch Sample Class maps for RoCE on a Cisco Switch Note Not all switch settings are shown Cisco5548UP2 config show class map Type gos class maps class map type gos match any class fcoe match cos 3 class map type gos match all class roce match cos 5 class map type gos match any class default match any Emulex Drivers for Windows User Manual P011041 01A Rev A sc Appendix E RoCE Switch Support 192 gt C EMULEX DCBX Enabled Switch Connection PFC Mode Type queuing class maps class map type queuing class fcoe match qos group 1 class map type queuing class roce match qos group 5 class map type queuing class default match qos group 0 Type network qos class maps class map type network qos class fcoe match qos group 1 class map type network qos class roce match qos group 5 class map type netwo
192. onfiguration 62 DG EMULEX NIC Driver Configuration e If the feature is not enabled the driver does not report any current capabilities At that point PowerShell searches the registry for keys related to the feature and reports their values These are either the default values INF or the last configured user values if overwritten by the user Default values are only intended as maximum upper bounds they are not guaranteed resources supported in every configuration As a result the driver can only report a feature s current capabilities accurate for the present configuration if the feature is currently enabled However standard PowerShell commands report whatever is present in the registry if the feature is not enabled This can conflict with what the driver actually supports in the current configuration Determining What PowerShell Is Reporting Registry and Driver Reported Capabilities You can usually tell whether PowerShell is using capabilities reported by the driver or is picking up registry values e SR IOV Check the output of Get NetAdapterSRIOV CurrentCapabilities for CurrentCapabilities If CurrentCapabilities is empty the driver is not currently enabled for SR IOV Any reported fields in Get NetAdapterSriov fl are based on registry values If CurrentCapabilities is not null the driver is enabled for SR IOV Get NetAdapterSriov fields are based on what the driver reports NetAdapter commands behave in this manner
193. onfiguring RoCE for the OCe14000 Series AdapterS sssssisrrrererrrerrrrrrrrrrreen 90 Emulex Drivers for Windows User Manual P011041 01A Rev A 4 Table of Contents gt G EMULEX Enabling the RoCE Profile on the Client Side 90 Confirming That the RoCE Profile Is Enabled cece cette eterna 91 Using SMB Direct with NetworkDirect ccccceceeee eset esse eeeeeeeteeeeeseteeeesenesatens 92 Mapping the RoCE Enabled Client to the Server Side Storage ccccceeeeeeeeeeeeeaees 93 SMB MULEICHANNEL sis cnaied nir als annanies gasaacna reside capadieiions docaesesiehdaav arellcanca cans 93 SMB Direct RESOURCE USAGE ites it tnudaneets pete rineeetadeetaninutiad EEEE EA AEE 95 QoS Concepts Related to ROCE cece need 97 Configuring QoS for ROCE siise sc cca tanec ci seeds inani eens pedai gs ede a eak 98 Performance Considerations c cece eee e ence eee een nent EEn 99 Configuring UNG sperpero eorne Aeae VEAN EE ENE EAEN AE thes EREITEA ENE AIEA 99 NPar Configuration Dell Only ssssssssessssssrrrrrrererrrrsrrrrrrrrrerrrrrrrrrrrreere 100 Adapter Configuratio M s ersoraneiniiiiniiin eniin iian E EEEE EAEE E E wand anus 100 NPar Partition SUPPOMt 2it cce5sun arasia aa ATEENA crane EREE E EEEE EKRAANE 101 NPar Considerations wc cdiacsianeiteeteetalma ads felwieataidatheednlatiiein qanghvoaw eet aad 101 Network Driver Performance TUNING cccceeceeeeeeeeeee teens teense eeaeteenateenaees
194. onnection request from an SMB Client when the NetworkDirect MTU on the server is at least as large as the NetworkDirect MTU on the initiating client 3 Use the netstat xan command to enumerate the active NetworkDirect connections and listeners see Figure 3 11 A NetworkDirect enabled driver creates listeners on any configured IPv4 or IPv6 addresses and the link local IPv6 address SMB Direct listeners listen on port 445 ies C Users Adninistrator gt netstat xan Active NetworkDirect Connections Listeners SharedEndpoints Mode IfIndex Type Local Address Foreign Address Kernel 26 Listener fe8O fded e692 8d6a 9cBex261 445 NA Kernel 26 Listener z 110x226 445 NA Kernel 26 Listener 2 116 445 NA Kernel Listener 28 74F22 aa42 5734 b2dax251 445 NA Kernel 25 Listener 110225 1 445 NA Kernel 25 Listener 26 1 8 118 445 NA Figure 3 11 Active NetworkDirect Connections and Listeners Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q3 DG EMULEX NIC Driver Configuration Mapping the RoCE Enabled Client to the Server Side Storage Using an available network share with the proper permissions configured open an SMB share from the Windows Run command or from the command prompt by typingnet use devicename computername sharename By default this creates two RDMA connections per SMB Direct enabled network interface on a particular server see Figure 3 12 on page 93 Each SMB Direct conn
195. 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 P011041 01A Rev A gt EMULEX 4 Troubleshooting 4 Troubleshooting 119 General Troubleshooting Your system may operate in an unexpected manner in certain circumstances This section contains reference tables on event codes and error messages and provides information regarding unusual situations General Troubleshooting Table 4 1 General Troubleshooting Issue The operating system fails to install or does not successfully install the driver Answer Solution Verify that the operating system is supported by the driver The AutoPilot Installer fails If the AutoPilot Installer fails the Diagnostics window shows that the adapter failed If the adapter fails 1 Select the adapter to view the reason why the adapter failed 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 The Onelnstall Installer fails If the Onelnstall Installer fails it may be because The operating system prerequisites have not be
196. p 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 If an NDIS driver is being installed Windows Server 2008 picks up the first available driver it finds if manually on a Windows Server 2008 an NDIS driver is being installed manually Therefore an NDIS5 system the installer installs the driver will be installed even if a Windows NDIS6 driver is first driver it finds even if it isnot available An event log message advises you to update to the the latest version of the driver latest driver for best performance The system crashes or appears to Several possible causes for this issue exist hang In the case of a hang there e Certain systems require an updated BIOS to properly manage could be a message indicating that the power states of newer Intel and AMD processors Check the driver experienced a hardware with your vendor for information regarding BIOS and firmware malfunction updates that may be required to run well with the latest releases of the Windows operating systems Also certain BIOS settings may be required For example Emulex recommends that you disable any low power processor states and low power settings for PCle 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 t
197. pause is negotiated with the network switch and used only for the FCoE protocol packets The NIC function can also use priority pause if supported by the switch This requires tagging packets in the operating system with the correct priority value and enabling ETS in the driver properties Configurations that support multiple PCI functions per port generally configure flow control from the switch or blade configuration application Since flow control is an Ethernet port property it must be the same for all PCI functions using the same port If multiple PCI functions are exposed for a single 1OGbE port such as in a blade configuration the flow control parameter must be set the same on all adapters for the port The results are unpredictable if the setting differs among PCI functions because this is a shared property of the 10GbE port Examples Flow control greatly improves the following situations e The adapter is installed in a 4x PCle slot or an underpowered server system If the PCle bus does not provide 10 Gbps of throughput due to chipset limitations or the bus width the adapter cannot maintain 10 Gbps of incoming receive data It starts dropping packets quickly In this situation it may be beneficial to enable receive flow control in the adapter and enable flow control in the attached switch for all devices This helps to slow down the transmitters e The adapter transmits to 1GbE devices especially non TCP protocol If the ad
198. perating systems support the new event logging mechanism introduced by Storport Custom event messages are logged for a variety of events with different severity such as informational warning or error The source of the events indicates the service name and every event includes a unique ID and a symbolic name See Table A 15 for a description of the error log codes Table A 15 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 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 system match with driver version does not match the version of the firmware on the adapter Install a driver that is compatible with the firmware 0x05 Warning Port link is down check Check the links to the adapter connection to the adapter 0x06 Info Port link is up N A 0x07 Error Link down timeout expired on The link on the adapter is down for a period the port all targets are lost exceeding the LDTO value If the adapter 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 adapter If the link is re established any sessions that previously existed are reestablished and the devices are
199. perty Configuration Class of Service 802 1p Enhanced Trensmission Selection Network Address Packet Size VLAN Identifier 802 19 Configuration parameters must be set correctly for the device to operate on the network These parameters typically require corresponding changes to the network switch or network peer device OK Cancel Figure 3 2 NIC Advanced Properties in Windows Server 2008 Statistics Property Page Use the Statistics Properties tab to view the performance of the device and network By viewing the statistics properties you can troubleshoot issues and performance tune the system for example you can assess how different device properties change the system performance To view the statistics properties 1 Enter the Windows Device Manager using one of the following options e Click Start gt Control Panel gt System and click the Device Manager hyperlink e Click Start gt Run then type devmgmt msc e Click OK The Windows Device Manager is displayed see Figure 3 1 on page 64 2 Right click the network adapter for which you wish to view the statistics properties 3 Click Properties then click the Statistics tab see Figure 3 3 on page 66 From the list of properties select the property parameter you want to view Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 66 DG EMULEX NIC Driver Configuration Table 3 4 on page 66 lists the NIC driver properties stati
200. pped A value of 0 limits the maximum XRIs to 512 Note Use ConfigScale 0 to minimize the driver s per port memory foot print If ConfigScale is set to e 0 the maximum transfer size is limited to 500 KB e 1 the maximum transfer size is limited to 1012 KB e 2 the maximum transfer size is limited to 2036KB o Use ConfigScale 2 if connecting to tape devices e 3 the maximum transfer size is limited to 2036KB which is the best setting if you are running performance benchmarks in a non production environment e 4 the maximum transfer size is limited to 512KB Emulex 16GFC adapters ConfigScale is always set at 4 The maximum transfer size is set according to the value of the ExtTransferSize parameter Values 0 1 2 3 and 4 Default 4 Note For Emulex 16GFC adapters only the value of 4 is valid Activation Requirement Adapter Protocol OneConnect and Emulex 16GFC adapters Reboot DiscoveryDelay n DiscoveryDelay controls whether the driver waits for n seconds to start port discovery after link up If set to 0 immediate discovery after link up If set to 1 or 2 the number of seconds to wait after link up before starting port discovery Value 0 2 seconds decimal Default 0 Emulex Drivers for Windows User Manual Dynamic P011041 01A Rev A gt G EMULEX Table 3 1 Storport Miniport Driver Parameters Continued 3 Configuration 38 FC FCoE Driver Configur
201. quire a firmware update require a firmware update See the Downloads section of the Emulex website for compatible firmware 0x00030 48 Warning SR IOV is not enabled Update the Update the firmware enable SR IOV firmware enable SR IOV in the in the server BIOS and enable server BIOS and enable SR IOV and SR IOV and Advanced Mode in the Advanced Mode in the PXE BIOS PXESelect BIOS utility See the Downloads section of the Emulex website for compatible firmware 0x0002f 47 Warning VMQ offload is disabled Disable Disable SR IOV support in the SR IOV support in PXE BIOS to use PXESelectBIOS utility to use VMQ VMQ 0x0002e 46 Error Device is not supported on Windows 7 Operating System 0x0002d 45 Error Error recovery failed The device is See the Downloads section of the no longer operational Update all Emulex website for compatible drivers and firmware firmware and drivers 0x0002c 44 Warning Error recovery is disabled on the This message is informational system The device is no longer operational 0x0002b 43 Informational The driver successfully recovered _ This message is informational from an error Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information Table A 13 NIC Event Log Entries Continued NIC Error and Event Logs Message ID Hexadecimal Decimal Severity Message Recommended Resolution 0
202. r Following unhandled exceptions in the hardware or this error log entry the next 3 entries firmware indicate the error codes 0x138e0103 The iSCSI driver failed an IOCTL This error may indicate an incorrect request because the number of scatter configuration option for the iSCSI driver It may gather elements required for the also indicate a low memory condition IOCTL buffer exceeded the firmware limit Following this error log entry the next entry will indicate the IOCTL opcode and the payload length requested 0x138d0101 The iSCSI driver detected an error This may indicate a target is in error or may offloading the iSCSI connection The point to transient network connectivity issues operation will be retried again It may also indicate a firmware error Following this error log entry the next entry will indicate the session handle and the firmware error code 0x12990013 The iscsi driver did not receive an e Verify that the iSCSI target is certified by iSCSI command window update within Microsoft Check for errors reported at the 25 seconds during I O operations target The Emulex iSCSI adapter is only Following this error log entry the next supported with certified targets entry will indicate the session handle e Check for software updates at the target where this error occurred The iSCSI vendor s website If applicable update the driver will trigger a session recovery software on the session and continue Check for software
203. r 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 ACIE Ij Ble edon yew Window Hp lelz e ODE DBIe Ej Computer Management Loca E i Sytem Toots gt 1 beds tone Ei Evert Viewer Bere MII B1SH23 etre fen OYA SERVEREN My App cation Giens ALIDA 11 9023 bedret Neen 1 WA SERVEREN Seosty Aren HII MIAZ bedrot toea E KA SERVEREN Li D Error MLIO 11923 bedrot ken MOO A SERVEREN SQudscicos A a x Performance Logs and Alert Evert NA SERVEREN Bh Device Manager fig Storage l KA SERVEREN O EP Removable Storage Q Dye fouce be icsi N NA SERVEREN Oik Defragmenter Q Tim SRA AM Cega None 7035 SYSTEM SERVEREN Deck Management Q type Ena Evert D 11 E N WA SERVEREN E fp Services and Appbcatiors Q Ue NA Ra 7085 SYSTEM SERVEREN Computer SERVEREN PTSAIW w NA SERVEREN Q 7035 SYSTEM SERVEREN Q Description T NA SERVEREM Q 7035 NETWORK SER SERVEREN Q 73 NA SERVEREN G aH NYA SERVEREN Q 4295 NYA SERVEREN g u WA SERVEREN G 15 NA SERVEREN NA SERVEREN G 1 NYA SERVERIN nA SERVERIN Br nA SCRVIRDY 13 Wa SANEREN ry KA SERVEREN g 1 na SERVEREN WA SERVEREN KA SERVEREN 13 wA SERVEREN Qin ALSO 81 05 10 DEON teon 10016 NETWORK SER SERVEREN Bere ALIOD 81 05 10 DEON Neon 10016 NETWORK SER
204. r information on modifying the CheckSum Offload or Large Send Offload parameter see Configuring NIC Driver Options on page 45 Receive Side Scaling RSS for Non Offloaded IP TCP Network Traffic The adapter can process TCP receive packets on multiple processors in parallel This is ideal for applications that are CPU limited Typically these applications have numerous client TCP connections that may be short lived Web servers and database servers are prime examples RSS typically increases the number of transactions per second for these applications Understanding RSS To better understand RSS it helps to understand the interrupt mechanism used in the network driver Without RSS a network driver receives an interrupt when a network packet arrives This interrupt can occur on any CPU or it may be limited to a set of CPUs for a given device depending on the server architecture The network driver launches one DPC that runs on the same CPU as the interrupt Only one DPC ever runs at a time In contrast with RSS enabled the network driver launches multiple parallel DPCs on different CPUs For example on a four processor server that interrupts all processors without RSS the DPC jumps from CPU to CPU but it only runs on one CPU at a time Each processor is busy only 25 percent of the time The total reported CPU usage of the system is about 25 percent more if other applications are also using the CPU This is a sign that RSS may E
205. r 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 0x20 Warning Initial memory allocation The driver failed to allocate its complete failed driver is running with memory requirement and attempts to load with reduced capabilities reduced capabilities The total number of targets available is reduced This message indicates a low memory condition 0x21 Info Target Reconnected for N A Session id N 0x22 Info Interrupt Redirection N A capability is enabled 0x23 Warning Interrupt Redirection Update the firmware to the latest version capability is not supported by this firmware Update your firmware 0x24 Error Device is not supported on The iSCSI adapter family is not supported on Windows 7 Operating System the Windows 7 client operating systems failing driver load 0x25 Info Interrupt Redirection N A capability is not supported by this hardware 0x26 Warning Logical link on the The iSCSI function may have been disabled in OneConnect Port is down traffic is disallowed on this function Emulex Drivers for Windows User Manual the PXESelect utility If you disabled it intentionally you can ignore this message P011041 01A Rev A SG EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log
206. r to install and click Next Note Using the OEMSETUP INF file to update Emulex s FC FCoE Storport Miniport driver overwrites customized driver settings If you are updating from a previous installation write down the settings Following the installation use the OneCommand Manager application to restore the previous settings Click Have Disk and direct the Device Wizard to the location of oemsetup inf If you have installed the driver installer kit in the default folder the path is C Program Files Emulex AutoPilot Installer FC or FCoE Drivers Storport x64 HBA Click OK Select Emulex LightPulse LPX000 PCI Slot X Storport Miniport Driver your adapter model is displayed here Click Next Click Finish Emulex Drivers for Windows User Manual P011041 01A Rev A DE EMULEX 2 Installation 29 Manually Installing or Updating the Emulex Protocol Drivers The driver installation has completed The driver will start automatically If the adapter is connected to a SAN or data storage device a blinking yellow light on the back of the adapter indicates a link up condition Installing or Updating the iSCSI Driver To update or install the iSCSI driver from the desktop OND OP Se Ne 10 11 12 13 14 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
207. rating systems must be installed on an x64 server Notes Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 x64 versions Enterprise and Server Core installation Note Microsoft patch KB2846340 must be installed on your system to successfully install the NIC driver If the patch is not installed on your system the installation stops and prompts you to install it This patch from Microsoft s Knowledge Base KB is required for Windows Server 2008 SP2 Windows Server 2008 R2 and Windows Server 2012 and for Windows 7 and Windows 8 client operating systems Windows 7 Ultimate Enterprise or Professional edition x64 only supported only on OneConnect OCe11100 series Converged Network Adapters CNAs Windows 8 and Window 8 1 x64 base version Professional and Enterprise x64 only supported only on OCe11100 series CNAs Windows 7 x64 Windows 8 x64 and Windows 8 1 x64 drivers are Emulex signed You must accept the Emulex certificate to install these kits Support is provided by Emulex but not by Microsoft Check the Emulex website for required updates to the Windows operating system or the Emulex drivers Abbreviations AL_PA arbitrated loop physical address API application programming interface ARI alternative routing ID interpretation BIOS basic input output system CHAP Challenge Handshake Authentication Protocol CLI command line interface CNA Converged Network Adapter CPU central processi
208. ration NIC Driver Configuration 59 Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Name TCP Offload Optimization Acceptable Values Optimize Latency Optimize Throughput default Supported Operating Systems Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Definition This parameter only applies to TCP connection offload which must be enabled in the Protocol Offloads section Most applications perform better with TCP Offload Optimization set to Optimize Throughput which handles large data transfers with minimal CPU impact Setting this parameter to Optimize Latency causes receive data to be delivered to the application without waiting for a TCP push flag This causes additional receive indications that typically decrease total throughput Transmit Buffers 64 256 inclusive The default setting is 256 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Transmit Buffers sets the number of Ethernet transmits that may be posted to the hardware at any given time The default value is sufficient to achieve maximum performance Reducing this value conserves system memory Transmit CPU Not Present or a value from 0 through number of CPUs 1 Optional A default setting is not available
209. rd 0 x x WWN word 1 x x NPortid x x Description Severity Log Action Emulex Drivers for Windows User Manual The driver assigned a SCSI ID to a discovered mapped FCP target BindType 0 DID 1 WWNN 2 WWPN Information LOG DISCOVERY verbose No action needed informational P011041 01A Rev A 4 Troubleshooting 125 DG EMULEX Troubleshooting the FC FCoE Driver Ipfc_mes0230 Cannot assign SCSIid to WWN word 0 x x WWN word 1 x x NPortid x x Description SCSI ID assignment failed for discovered target Severity Warning Log LOG ELS verbose Action Review system configuration Ipfc_mes0232 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 Ipfc_mes0235 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 Ipfc_mes0236 Issuing command to name server type x x Description The 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 lpfc_mes0240 Ipfc_mes0238 NameServer response DID count d Description Received a response from fabric name server with N DIDs S
210. re provided to the TCP IP stack for disposal in the operating system Receive TCP Errors The number of receive packets with an incorrect TCP checksum These packets are provided to the TCP IP stack for disposal in the operating system Tunnels allocated Number of interfaces converted to tunnel interfaces Used with NVGRE offload enabled and on Tenants allocated Number of interfaces converted into tenant interfaces Used with NVGRE offload enabled and on and VMQ Virtual Functions allocated Number of PCle virtual functions created by the SR IOV supporting adapter Using OCCFG for Windows NIC Driver Options The occfg exe program supports configuring parameters for the network functions on Emulex Ethernet adapters either through interactive mode with a set of menus or command line mode that is scriptable If you performed a standard driver installation the occfg exe is located in the following directory Directory of C Program Files Emulex AutoPilot Installer NIC Drivers NDIS lt platform gt lt OS gt The following section describes how to use the occfg exe program to configure the Windows device driver from the command line Displaying OCCFG Help To display help use the option by typing occfg The following text is displayed OneConnect Network Config Copyright 2011 Emulex 0 0 9999 0 Usage occfg exe options Emulex Drivers for Windows User Manual P011041 01A Rev A
211. re the result of bursts of small receive packets on the network However if the CPU is the limit increasing the buffer resources does not help because the driver cannot post them fast enough Enabling RSS is another strategy to reduce drops since it allows the NIC driver to use additional CPU cores The number of RSS queues can be increased to increase the total number of posted buffers available to the adapter Enabling RSC can also reduce CPU consumption in the networking stack by combining multiple TCP packets into one larger packet For best performance the system BIOS must be set to Maximum Performance or manually disable C states The transitions to low power C states may cause a steady trickle of drops due to increased latencies from packet reception until the driver s interrupt processing code is invoked Receive Drops No Fragments CPU Limited Emulex Drivers for Windows User Manual The number of receive packets dropped because of a DMA bottleneck from the network adapter to host memory This may be caused by bottlenecks in either the PCle bus or main memory In the Status tab of the Custom property page the Emulex NIC reports the PCle link parameters and the maximum supported parameters For example installing a 8x device in a 4x PCle slot cuts the available PCle bandwidth in half The PCle MTU and Read Request size are also reported and these can be configurable in the system BIOS The performance of the
212. received during standby AT ANONS SORN S Windows Server 2012 R2 In Blade server configurations 2012 inbox drivers i u ip Note For 0Ce11102 Wake on Lan is only supported Wake on LAN is dapt two primary adapters per dis bled hy defoilt ee ieee Additional PCI functions and not overwritten a a disabled on driver updates pp i Advisory PowerShell Behavior Issues with Capabilities Reported by Standard PowerShell Commands Get NetAdapter Driver parameter default registry values are initially populated from the driver installation INF file Thereafter the registry is written to only if the default settings are explicitly overridden PowerShell uses these registry values to report capabilities with the result that the registry values may not always reflect what is supported in the current configuration The default settings can be modified through the Driver Properties page standard PowerShell commands and utilities like occfg for more information on occfg see Using OCCFG for Windows NIC Driver Options on page 69 Standard PowerShell Get NetAdapter commands behave in the following manner e Ifthe feature is currently enabled the driver reports its current capabilities PowerShell reports all of the feature capabilities based on what the driver indicates These are guaranteed to be what the NIC supports in the current configuration Emulex Drivers for Windows User Manual P011041 01A Rev A 3 C
213. river Parameters Continued 3 Configuration 42 FC FCoE Driver Configuration Parameter ScanDown n Definitions 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 Activation Requirement Reboot Adapter Protocol 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 LightPulse Only SrbTimeout SrbTimeout limits the SCSI timeout value to 60 seconds if 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 1 0 timeout behavior where an 1 0 will be returned in a maximum timeout of 60 seconds on long I O timeouts If set to 1 enabled If set to 0 disabled Values 0 1 Default 0 Topology Topology values can be 0 3 If set to 0 0x0 FC AL If set to 1 0x1 PT PT fabric If set to 2 0x2 FC AL first then attempt PT PT If set to 3 0x3 PT PT fabric first then attempt FC AL Topology fail over requires firmware version v3 20 or higher If the firmware does not support topology fail over options 0 2 and
214. river did not receive an iSCSI N failed to open the command command window update for up to 25 seconds window within configured during O operations The event log entry timeout 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 adapter is only supported with certified targets e Check for software updates at the target vendor s website If applicable update the software e Check for driver and firmware updates at the Emulex website If applicable update the driver and firmware 0x10 Warning Encountered an error The iSCSI driver detected an error while offloading an iSCSI offloading the iSCSI connection The operation connection error code N is retried up to five times The session handle and the adapter 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 an adapter firmware error 0x11 Warning The IOCTL opcode A requires The iSCSI driver failed an IOCTL request more scatter gather elements because the number of scatter gather elements than allowed Transfer length required for the IOCTL buffer exceeded the is B adapter firmware limit The IOCTL opcode and the payload length requested are included in the ev
215. rk connection name Get VM Get vmswitch Get vmnetworkadapter VMName fl vmname switch macaddress ipaddress virtualsub Get netvirtualizationprovideraddress Get netvirtualizationlookuprecord Get netvirtualizationcustomerroute Get netadapter wnvnic Get netadapterbinding componentID ms_netwnv Get netadapterencapsulatedpackettaskoffload wnvnic Get netadapteradvancedproperty wnvnic Disable netadatperSriov wnvnic Disable netadapterEncapsulationPacketTaskOffload wnvnic Get help NetVirtualization Get netadapterstatistics wnvnic Under the Host Device Manage gt Network Adapters gt Emulex Statistics tab check the following e VMQs Allocated e Tunnels Allocated e Tenants Allocated Verification 1 Ping Launch Policy Scripts on each host Ping using the t option pings will respond a b c Run the Remove Policy script on one host server d Pings will stop responding e Add policies pings will respond Change the VM IP Address For example change 10 0 0 5 on one host and 10 0 0 7 on the other Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration QQ DG EMULEX NIC Driver Configuration Without NVGRE you would not be able to use the same IP address as the other VM Ensure that you see the WNVNIC interface using the PowerShell command get netadapter e If you are unable to see the NVGRE Ethernet connection make sure that the Hyper V s control panel network connections property
216. rk qos class default match qos group 0 Sample Policy maps for RoCE on a Cisco Switch Note Not all switch settings are shown Type gos policy maps policy map type qos class roce class type gos class roce set qos group 5 class type gos class fcoe set gqos group 1 class type gos class default set qos group 0 policy map type gos class rocenofcoe class type gos class roce set qos group 5 class type gos class default set qos group 0 Type queuing policy map policy map type queuing class roce90 class type queuing class roce bandwidth percent 90 Emulex Drivers for Windows User Manual P011041 01A Rev A sc Appendix E RoCE Switch Support 193 gt C EMULEX DCBX Enabled Switch Connection PFC Mode class type queuing class default bandwidth percent 10 Type network qos policy maps policy map type network qos class rocenofcoe class type network qos class roce pause no drop mtu 4200 class type network qos class default mtu 9216 multicast optimize Sample Port Configuration for RoCE on a Cisco Switch Note The Port flow control should be off and the Priority Flow Control should be on Auto PFC flow is not explicitly displayed on this switch interface Ethernet1 15 description RoCE configuration switchport mode trunk switchport trunk allowed vlan 102 spanning tree port type edge trunk service policy type qos input class rocenofcoe service policy type queuing input class roce90 service p
217. rsion number Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 80 DG EMULEX NIC Driver Configuration General Advanced Status Statistics Diagnostics Driver Details I Events Resources Power Management Bij Emulex OneConnect 0Ce11102 1 NIC TOE ae Driver Provider Emulex Driver Date 2 15 2012 Driver Version 0 0 9999 3417 Digital Signer Emulex To view details about the driver files Update Driver To update the driver software for this device if the device fails after updating the driver roll back to the previously installed driver Disables the selected device Roll Back Driver Uninstall To uninstall the driver Advanced Figure 3 5 Emulex NIC Driver Properties Page 4 Click Driver Details A window opens displaying the driver name Enabling SR IOV in the Emulex Device To enable SR IOV in the Emulex device 1 Select Server Manager gt Dashboard gt Tools gt Computer Management 2 Click Device Manager The Device Manager opens see Figure 3 4 on page 79 3 Open the Network Adapters item find the Emulex device and right click it Select Properties from the context menu The Properties dialog box opens see Figure 3 5 on page 80 4 Click the Advanced tab The Advanced Property Configuration page opens see Figure 3 6 on page 81 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 81 DG EMULEX NIC Driver
218. rt link status SLI4 mode Bits 31 24 Port ID Bits 23 16 Link ID Bits 15 8 Link status OxF0 Unresponsive adapter port SLI4 mode OxF4 ULP Unrecoverable Error low part SLI4 mode Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information 147 FC FCoE Error and Event Logs Table A 1 Severe Errors Continued Bits 0 7 Interpretation 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 OXxFE Invalid Completion Queue Entry SLI4 mode Malfunction Errors Table A 2 lists malfunction errors and their codes Table A 2 Malfunction Errors Bits 0 7 0x05 Interpretation SET_VAR command failed 0x11 SET_VAR command failed reinitialization 0x21 Spurious mailbox command interrupt 0x31 Unrecognized mailbox command completion 0x32 Duplicate link attention event tag unchanged 0x33 Invalid link attention no link state indicated 0x34 Duplicate link attention link state unchanged 0x35 Error reading common service parameters for port 0x36 Error reading c
219. rt up without requiring you to log in You must ensure that 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 QFEs also known as KB updates based on the checks you have specified in the STORPORT QFES section By default the installation terminates if the QFE check fails To enable a driver installation to proceed even if a check for QFEs fails set this parameter to true Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters 183 gt G EMULEX AutoPilot Configuration File AutoPilot Configuration File The AutoPilot configuration file is organized into sections grouped according to related commands Six main sections exist e AUTOPILOT ID Configuration Identification e AUTOPILOT CONFIG Software Configuration e STORPORT CONFIGURATION Configuration Prompts Vendor Specific Questions e STORPORT QFES QFE Checks e STORPORT PARAMS Setting Up FC Driver Parameters e SYSTEM PARAMS Setting Up System Parameters Each section begins with a heading The heading is required even if there are no settings in the section The only section not required is the Installation Prompts section which has the heading STORPORT CONFIGURATION That section cannot exist i
220. rtrrrranttrrrrnnne 152 SCSI St tyS CONES keanaan a a aan aa a a a 152 Local Reject Status Codes 3 cc s nsteeccesecntaranswestemiersacdedetauimesienraneteaxtes 153 SRB Status COES kerisi aran aaae AEE AE AA A EEA EE A 153 RoCE Event Log EntrieS sssssssrssessssrrrrrrrrrrerrrrrrrrrrrrrrrerrrerrrrrrerere 155 NIC Event Log EntrieS ssssssssrreererssrrrrrrrrerrrrrrrrrrrrrrrrttrrsrrrrrrerere 156 iSCSI Error Log Entries on Windows Server 2008 ccccceeceeeeeeeeeeeaeeeees 162 iSCSI Error Log Entries on Windows 7 Windows 8 Windows 8 1 Windows Server 2008 R2 Windows Server 2012 and Windows Server 202 R2 ae ETa E ET ia EE a a ia a EE 165 Data String Parameters for Option 43 cdccscvennescpeevepnevitcevesnas iecewcandvias 175 P011041 01A Rev A 10 SG EMULEX Listof Tables 11 Table C 1 Negotiated Speed Specification per Adapter Port Connection s es 177 Table D 1 Unattended Installation Error Cod S ccccccecseeeeseeeseeeesaeeeeaeeeenaeeeas 187 Emulex Drivers for Windows User Manual P011041 01A Rev A XC EMULEX 1 Introduction 12 Driver Information 1 Introduction This product supports the Emulex OneConnect family of converged network adapters CNAs and the Emulex LightPulse family of host bus adapters HBAs and CNAs Note 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 t
221. rtt rnrn rrt rtrt rnnr rrr E EErEE EEEE E Errr ren 143 Figure A 2 iSCSI ErrOfissctccsdscccdecaasicaiacsdissddsdcctis tnt n rnnr rrt ttn PRESE EREEREER E RERE E EEEn 161 Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX List of Tables Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 3 10 Table 3 11 Table 3 12 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 5 Table 4 6 Table A 1 Table A 2 Table A 3 Table A 4 Table A 5 Table A 6 Table A 7 Table A 8 Table A 9 Table A 10 Table A 11 Table A 12 Table A 13 Table A 14 Table A 15 Table B 1 Emulex Drivers for Windows User Manual List of Tables Storport Miniport Driver Parameters cscciceecccswccesy swe dpaecepee chess vatcansertsnvers 36 Recommended Settings for I O Coalescing cece eee e eee eee e 43 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options cseeeeeee ees 46 NIC Driver Properties Statistics ssssssrsrrrrrererrrrrsrrrrrrerererrrrrrrrrere 66 SMB Direct Active Connections Client Mode Per Port for OCe14000 Series ACAD lEl Gis c ctsc cutee cciacdetteketadiesecvescedeehsisYadareedueededas 96 Parameters Tor ROCK sciss evel ai bevel cts erie ree ees 97 RoCE Parameters Available for Viewing ccccce cece sete erent erent eneenenente ns 97 Windows Server Performance Tuning Situations
222. ry 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 run deladjct reg 3 Click Yes The elxadjct key is removed from the registry Windows Server 2012 The Emulex Storport Miniport and Emulex PLUS ElxPlus drivers are uninstalled using the Device Manager Note On Windows 2012 and Windows 2012 R2 after the message Warning you are about to uninstall this device from your system is displayed you must select the checkbox Delete the software for this device to uninstall the driver Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 34 gt G EMULEX Removing Emulex Driver Kits and Drivers Emulex Storport Miniport Driver To uninstall the Emulex Storport Miniport driver in Windows Server 2012 1 Select Server Manager gt Dashboard gt Tools gt Computer Management gt Device Manager 2 Double click the adapter from which you want to remove the Storport Miniport driver A device specific console window is displayed Select the Driver tab 3 Click Uninstall and click OK to uninstall ElxPlus Driver Note Uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled To uninstall the ElxPlus driver 1 Select Server Manager gt Dashboard gt Tools gt Computer Management gt Dev
223. s In batch mode occfg automatically restarts 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 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 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 can 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 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 72 NIC Driver Configuration gt G EMULEX ri 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 ex
224. s 17 Loading the Onelnstall Package using Interactive Mode eceeeee eee eee eee eens 18 Loading the Onelnstall Package using Silent Mode ccecceeee eect eee eee eee ees 18 Command Format ssrrenseriin ionni n An rE E D E TE EEEE EE ade aia ey danas 18 Driver Kit Install r sapssecasscawsssasnsausienissnamaseniassanasiaiaseiasaeianeanssienaneaniaamaneen 19 Loading the Driver Mt cccescew oetveeie teen diate sak sdindiideetniawr eae cerniaweeds 20 A toPilot Installer ransana aaae 20 Starting Installers from a Command Prompt or Script cccceceeeeeeeee seer eene ees 21 Running a Software Installation Interactively ccccccccee cease eee ee eeee essen eeae eens 22 Option 1 Automatically Run the AutoPilot Installer l a 22 Option 2 Run the AutoPilot Installer Separately ccecceec cece eee eee eee ee eee 22 Hardware First Installation or Driver Update cccccccecesee cess eeeeeeeneeeenee eens 23 Software First Instango ilicscstetauleteSusvaseie slateasncbsdanicapedsdatiusnsideancusseeadante 24 Text Only Driver InStallationicwscccicccsiccecexscastnctdescascssicdvasseyetdsnetinasiadzadauseis 24 Unattended Driver Installation o cccescsescssccsssesasteecsieees vewesieeceivessienesenessians 25 Option 1 Install the Driver Silently cece eee eee ne 25 Option 2 Run the Driver Kit Installer Separately nnnc 26 I stallation Failure ou ts ve wes hl Gre Vege ks hoy ca euee haeeeueeed mane monet
225. s 2008 and later Registry Key RSS Default Value 1 Enable Valid Values 0 Disable 1 Enable Using SR IOV with Emulex Devices This section describes how to use SR IOV with Emulex devices Advisory OCe11100 series adapters may have an issue recovering from the corrupted use of SR IOV Assigning an SR IOV device to a virtual machine could leave the system vulnerable and lead to instability Emulex recommends that you assign SR IOV devices only to virtual machines that run trusted workloads or consider disabling SR IOV This advisory is highlighting a use case where a rogue non Emulex digitally signed driver is installed by the system administrator on a virtual machine It is then possible for that rogue driver to cause issues with an OCe11100 series networking adapter While there are many benefits to using SR IOV with virtualized workloads these benefits should be weighed against the potential risks in doing so As an example see the Microsoft TechNet Blog cited in the link below where the benefits and usage of the Windows Server 2012 Hyper V switch versus NIC SR IOV are noted http www emulex com downloads sr iov html Emulex Drivers for Windows User Manual P011041 01A Rev A XG EMULEX 3 Configuration 77 Notes NIC Driver Configuration The operating system comes with an Emulex inbox driver Emulex recommends that you use the Emulex out of box driver For a list of supported drivers and adapters see the la
226. s adapter configures RoCE traffic for priority 5 e Manually enable priority 5 on the switch under a different priority group other than the FCoE iSCSI NIC priority group Note If you do not enable priority 5 on the switch side the OCe14000 series adapter maintains its configuration for PFC mode priority 5 This configuration can result in packet losses unrecoverable errors or infinite retries for RoCE traffic e DCBX disabled switch connection o If an OCe14000 series adapter is connected to a DCBX disabled switch generic pause mode is enabled Performance Considerations The following recommended settings can improve SMB performance over TCP including RDMA However the configuration must be tuned to provide line rate with TCP network traffic 1 Disable TCP Autotuning 2 NIC MTU must be greater than ROMA MTU which is recommended to be set at 4096 NIC MTU size of 9014 is recommended 3 On Windows Server 2012 R2 disable the bandwidth throttling option on the SMB client side to improve throughput this parameter has no effect on Windows Server 2012 Set SmbClientConfiguration EnableBandwidthThrottling 0 4 Ona 40GbE link with a single client server configuration increase the queue pair count to a minimum of 8 for better throughput Set ItemProperty Path HKLM SYSTEM CurrentControlSet Services LanmanWorkstation Parameters ConnectionCount PerRdmaNetworkInterface Value 8 Force Note This will reduce the maximum
227. s in the AutoPilot Installer being run as APInstall exe SilentRebootEnable True localDriverLocation qd drivers new Storport Parameter values that contain spaces such as path names must be enclosed in quotes To add such a setting to APargs you must insert backslashes before the quotes around the value and then add quotes around the entire APargs expression For example the command line all on one line elxdrv fc fcoe lt version gt exe APargs ReportLocation C Documents and Settings Administrator My Documents reports This results in AutoPilot Installer being run as APInstall exe ReportLocation C Documents and Settings Administrator My Documents reports To pass multiple parameters to the AutoPilot Installer and minimize errors you can run the utility kit installer interactively delay AutoPilot Installer execution and then run the AutoPilot Installer command The procedure is described in Option 2 Run the AutoPilot Installer Separately on page 22 and Unattended Driver Installation on page 25 Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters SG EMULEX AutoPilot Installer Syntax La You can specify a non default directory for the driver kit by specifying an installation folder on the command line For example elxdrv fc fcoe lt version gt exe install C Emulex This option can be used in conjunction with
228. scing enabled such as applications that depend on the completion of the current network transfer before they post additional work If an application sends and receives one network message before posting the next message it is considered latency bound For latency bound applications an interrupt is required to proceed to the next work item so reducing the number of interrupts directly reduces the network throughput The Microsoft iSCSI Initiator is generally considered a latency bound application unless the I O sizes are very large When tuning the system you must balance the extra CPU usage caused by interrupts with the potential decrease in total throughput for latency bound applications CPU Binding Considerations Windows applications can set a processor affinity which binds a program to a particular CPU in a multiple processor computer Emulex does not recommend manually configuring CPU affinity due to the recent additions to the Windows networking stack 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
229. se Action No action needed informational Ipfc_mes0102 PLOGI completes to NPortld x x Description The adapter performed an N PLOGI into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Ipfc_mes0103 PRLI completes to NPortlid x x TypeMask x x Fcp2Recovery x x Description The adapter performed a PRLI into a remote NPort Severity Information Log LOG_ELS verbose Action No action needed informational Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 122 Troubleshooting the FC FCoE Driver Ipfc_mes0104 ADISC completes to NPortid x x Description Severity Log Action The adapter performed an ADISC into the remote NPort Information LOG_ELS verbose No action needed informational Ipfc_mes0105 LOGO completes to NPortld x x Description Severity Log Action The adapter performed a LOGO into a remote NPort Information LOG ELS verbose No action needed informational Ipfc_mes0112 ELS command x x received from NPortld x x Description Severity Log Action Remarks Received the specific ELS command from a remote NPort Information LOG _ ELS verbose No action needed informational Ipfc_mes0114 and Ipfc_mes0115 are also recorded for more details if the corresponding severity level is set You can use the XRI to match the messages Ipfc_mes0114 PLOGI chkparm OK Descriptio
230. series adapters support ARI The system hardware such as the motherboard and BIOS must support ARI o ARI must be enabled in the system BIOS o The operating system must support ARI such as the Windows Server 2012 and later Any management tools that you use must support ARI such as OneCommand Manager 10 2 and later For Dell NPar support see NPar Configuration Dell Only on page 100 Configuring Windows Server NIC Driver Parameters The Windows Server NIC drivers support driver options through the Advanced Property page in Windows Device Manager Modifying Advanced Properties Modify the advanced properties for the driver for Windows with the Windows Device Manager For more information on advanced properties see Network Driver Performance Tuning on page 102 To modify the advanced properties 1 Enter the Windows Device Manager using one of the following options Click Start gt Control Panel gt System and click the Device Manager hyperlink Click Start gt Run and type devmgmt msc Click OK Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 64 gt lt EMULEX NIC Driver Configuration The Windows Device Manager is displayed see Figure 3 1 E Server Manager File Action View Help gt Amem e ws En Server tanope ORLSIOEEIPD Actions a Roles a Fea E OELLE10 GE3 P1 Device Manager E Computer z E Diagnostics foe Disk dri More Actions fe paee E E Display a
231. slot will not provide any additional performance 0x001c 28 Error Vital product data is not initialized Use the offline flash utility to correctly reconfigure the device 0x0015 21 Warning Firmware version does not match The firmware version and driver driver version must match This is a warning message but Emulex recommends 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 or the operating system 0x0013 19 Error Resource conflict The operating system failed to allocate resources for the device Check low memory conditions and operating system hardware resource conflicts 0x0012 18 Error Failed to enable bus mastering Verify that the BIOS allows bus mastering and that no resource conflicts exist 0x0011 17 Error The driver is incompatible with the The driver is loaded on the incorrect device hardware device Verify that the correct driver is installed 0x0010 16 Warning The network driver was reset This may indicate a system hang or hardware issue Verify that other system devices are working properly 0x000c 12 Informational The Ethernet link is down This message is informational 0x000b 11 Informational The Ethernet link is up This message is informational 0x000a 10 Error The network device detected an A hardware error occurred Verify error that the firmware flash image is not corrupted Contact Emul
232. ss lt not set gt NetworkDirect 1 Enabled NetworkDirect 1 Enabled 3 Configuration 74 NIC Driver Configuration NetworkDirect MTU 1024 1024 NetworkDirect MTU 1024 0x400 1024 Packet Size 9014 9014 Packet Size 9014 0x2336 9014 Performance Tuning 0 Maximum Performance Performance Tuning 0 Maximum Performance Preferred NUMA Node lt not set gt Preferred NUMA Node lt not set gt RSS Base Processor Group lt not set gt RSS Base Processor Group lt not set gt RSS RSS RSS RSS RSS RSS Receive Buffers Base Processor Number Base Processor Number Max Processor Group Max Processor Group Profile 1 Profile 1 896 lt not set gt lt not set gt lt not set gt lt not set gt Receive Buffers 1280 0x500 Receive CPU lt not set gt Receive CPU lt not set gt Receive Side Scaling Receive Side Scaling 1 1 Recv Segment Coalescing IPv4 Recv Segment Coalescing IPv4 Recv Segment Coalescing IPv6 Closest Processor Closest Processor Enabled Enabled Enabled Enabled Enabled Enabled Recv Segment Coalescing IPv6 SR IOV SR IOV Emulex Drivers for Windows User Manual Disabled Disabled 0 0 P011041 01A Rev A gt G EMULEX Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry
233. sssssssnnnnnnnnnnnnsnnnnnnnnnnnnnnnnn 174 Dynamic Host Configuration Protocol DHCP Recommendations seeesseeeeeeeees 174 Vendor Specific Option 43 ccc ccccccce cece eee e eens eee e eee teen nese teen EEE 174 Format of Vendor Specific Option 43 ccccccceee eects eeeeeeeee senate eens enaneenanes 174 Description of Mandatory and Optional Parameters cccccceeeeeeee eset ee ene ees 175 Appendix C Port Speed Specifications ssssssssnsssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 177 Negotiating Speed on a Mezzanine Card ssssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 177 Appendix D AutoPilot Installer Command Line and Configuration File Parameters s ssssssnnnnnnnnnnnnnnsnnnunnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 178 AParg Driver Kit Parameter and Appending to the APinstall exe File sssssssssssssss 178 AutoPilot Installer Sy nt ax icis aaa 179 Path SpecifierS ssssssssrnnusrsssrsrrrrrrr trta n rnrn rttr trann rnrn rnrn rtan rar rr rr rrr ruren 179 Configuration File Location ssssssssrsrreererrrersrsrrrrrrerrrrrrrrrrrrrrrrrrerrrrrrrr 180 Software Configuration Parameters cccccsccecseeeeeseeeeseeseesenseneesennesanes 180 DiagEnable Running Diagnostics ccecceeeeeeeeeeeeeeeeeeeeeesateceeeeneenesanenas 180 ForceDriverTypeChange Forcing a Driver Type Change 0 eeeeeeeee eee eee eee 180 ForceDriverUpdate Forcing a Driver Version Update ccccccceceeeeeeeeeeeaeeees 180
234. stall or update the previously installed utility without reinstalling the drivers 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 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 SAN Unattended installation You can run the driver kit and AutoPilot Installer with no user interaction from a command line or script Unattended installation works for both hardware first and software first installations and all driver kits An unattended installation operates in silent mode also referred to as quiet mode and creates an extensive report file with installation status Complete driver and utilities documentation can be downloaded from the Emulex website www emulex com Starting Installers from a Command Prompt or Script If a driver kit or AutoPilot Installer is run from a command prompt or command script batch file the Windows command processor does not wait for the installer to run to completion As a result you cannot check the exit code of the installer before the next command is executed Emulex recommends that for command line invocation always use the start command with the wait op
235. stics Transmit Throughput Receive Throughput Transmit Bytes Receive Bytes Transmit Packet Rate Receive Packet Rate Transmit Packets Receive Packets RSS Receive Packets Receive How Control Pause Requests TCP Offloads Currently Established TCP Offloads TCP Offload Retransmits TCP Offload Receive Drops TCP Offload Transmit Rate TCP Offload Receive Rate VMQs Allocated Interrupt Rate Receive Drops No Memory DMA limited s eeooccce a zg Figure 3 3 NIC Statistics Properties in Windows Server 2008 Table 3 4 NIC Driver Properties Statistics Statistic Name Description Transmit Throughput The data rate for this adapter on the network including all packet headers It is expressed in terms of bits per second where 1 byte 8 bits This is computed as the average over approximately three seconds Receive Throughput The receive rate for this adapter Transmit Bytes The total number of bytes transmitted by this adapter since the last statistics reset or the last driver reload Receive Bytes The total number of bytes received by this adapter Transmit Packet Rate The rate of transmit packets for the adapter Receive Packet Rate The rate of receive packets for the adapter Transmit Packets The total number of packets transmitted by the adapter since the last statistics reset or the driver was reloaded Emulex Drivers for Windows User Manual P011041 01
236. t AutoPilot performs in the order that they are completed The fourth section records the results of each task When all driver installation tasks are completed an updated adapter inventory is recorded If you cancel AutoPilot Installer that fact is recorded along with the time 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 RCMD service was installed a script similar to the following would run remote execution remd serverl g emulex autopilot installer fc apinstall exe if errorlevel 1 goto serverlok echo AutoPilot reported an error upgrading Server 1 if not errorlevel 2147483650 goto unsupported echo Configuration file missing goto serverlok unsupported if not errorlevel 2147483649 goto older echo Unsupported operating system detected older if not errorlevel 2001 goto none Emulex Drivers for Windows User Manual P011041 01A Rev A echo The driver found is the same or older than the existing
237. t Computer Management Emulex Drivers for Windows User Manual P011041 01A Rev A DE EMULEX 2 Installation 33 Removing Emulex Driver Kits and Drivers 2 Click Device Manager 3 Double click the adapter from which you want to remove the Storport Miniport driver A device specific console window is displayed Select the Driver tab 4 Click Uninstall and click OK to uninstall ElxPlus Driver Note Uninstall the ElxPlus driver only if all adapters and installations of Emulex miniport drivers are uninstalled To uninstall the ElxPlus driver 1 Select Start gt All Programs gt Administrative Tools gt Computer Management Click Device Manager Click the plus sign next to the Emulex PLUS driver class Right click the Emulex driver and click Uninstall Sb AP O29 Click OK in the Confirm Device Removal window Older Versions of the Emulex Storport Miniport Driver To uninstall or update an earlier version of the Storport Miniport driver prior to version 1 20 you must remove the registry settings for the adjunct driver prior to manually installing a new driver Caution Use the registry editor at your own risk Using the registry editor can cause serious issues that may require you to reinstall the computer s operating system Emulex cannot guarantee that issues resulting from changes you make to the registry can be repaired Make a backup of your registry before making any changes To remove the adjunct driver regist
238. t allocation failures are rare Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix A Error and Event Log Information 155 gt EMULEX NIC Error and Event Logs NIC Error and Event Logs This section provides information on NIC error and event logs Viewing the NIC Error Log For Windows Server operating systems the 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 Click System Click the be2net error under System Events to show the event details RoCE Event Log The Windows Device Manager generates error log codes if any errors occur during the installation of the NIC or RoCE driver Each log contains a Message ID Severity and Symbolic Link The Message ID is unique and tracks the error message if it is not displayed Oy Gh a Table A 12 shows the list of error codes the severity of the error the message displayed the meaning of the error and the recommended resolutions When reporting an issue with the adapter to Emulex check the event log and report any of these entries that are displayed Table A 12 RoCE Event Log Entries Message ID Hexadecimal Recommended Resolution Decimal Severity Message Ox3F 63 Warning lt adapter gt Incorrect RoCE Select the RoCE 2
239. te Onelnstall exit code To remedy this run setup as follows START wait OneInstall Setup lt version gt exe echo ERRORLEVEL The start wait ensures that the command does not return until Setup has exited The value of ERRORLEVEL now accurately reflects the Onelnstall exit code Command Format The format of the command is OneInstall Setup lt version gt exe lt install mode gt lt options gt Where lt version gt is the version number of the Onelnstall Package Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX lt install mode gt is one of the following q0 Interactive non silent install This is the default 2 Installation 19 Driver Kit Installer qi non Interactive install This option displays status pages q2 Silent install This option is completely silent no pages are displayed q This is the same as q1 lt options gt specifies the kit or kits to install ALL 1 Install all drivers and the OneCommand Manager application Default Note On a CORE system this will install all drivers and the OneCommand Manager Core Kit ALLCORE 1 Install all drivers and the OneCommand Manager Core Kit DRIVERS 1 Install all drivers FC 1 Install the FC driver only FCOE 1 Install the FCoE Driver only NIC 1 Install the NIC Driver only ISCSI 1 Install the iSCSI Driver only OCM 1 Install the OneCommand Manager Enterprise Kit only Note On a
240. ted 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 the number of nodes being discovered for link discovery RSCN CNT is the number of nodes being discovered for RSCN discovery There will be a value in either DISC CNT or RSCN CNT depending on which discovery is being performed Information LOG DISCOVERY verbose No action needed informational Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 4 Troubleshooting 124 Troubleshooting the FC FCoE Driver Ipfc_mes0204 Discovered SCSI Target WWN word 0 x x WWN word 1 x x DID x x RPI x x Description Severity Log Action Device discovery found SCSI target Information LOG DISCOVERY verbose No action needed informational Ipfc_mes0214 RSCN received Word count d Description Severity Log Action Received RSCN from fabric Information LOG DISCOVERY verbose No action needed informational Ipfc_mes0215 RSCN processed DID x x Description Severity Log Action Processed RSCN from fabric Information LOG DISCOVERY verbose No action needed informational Ipfc_mes0225 Device Discovery completes Description Severity Log Action This indicates successful completion of device re discovery after a link up Information LOG DISCOVERY verbose No action needed informational Ipfc_mes0229 Assign SCSIid x x to WWN wo
241. ter and Appending to the APInstall exe File Appendix D AutoPilot Installer Command Line and Configuration File Parameters The AutoPilot Installer can initiate an installation from a command prompt or script You can run the AutoPilot Installer manually from the command line or a script or you can run it automatically through the driver kit When run manually from the command line or script the command line parameters can be passed If you specify the q switch with the driver kit installer command the driver kit installer runs in unattended mode and automatically invokes the APInstall exe with its silent switch See Unattended Driver Installation on page 25 for more information AParg Driver Kit Parameter and Appending to the APinstall exe File If you specify a value for the APargs driver kit parameter this value is appended to the APInstall exe command line For example if you execute this installer file as elxdrv fc fcoe lt version gt exe q APargs SilentRebootEnable True After installing the AutoPilot Installer the driver kit automatically executes it as APInstall exe silent SilentRebootEnable True To specify more than one parameter separate the settings by one or more spaces and put quotes around the entire APargs expression For example the command line all on one line elxdrv fc fcoe lt version gt exe APargs SilentRebootEnable True localDriverLocation d drivers new Storport This result
242. test Windows Drivers release notes which are available for download from the Emulex website SR IOV is not supported with RoCE configurations SR IOV is not supported with UMC SR IOV is supported only on the following adapters in NIC mode installed on Windows Server 2012 and Windows Server 2012 R2 with an installed Emulex NIC driver o LPe16202 CNAs o OCe11000 series NIC adapters o OCe14000 series adapters The driver supports the following virtual functions for the following adapter families o OCe11100 series adapters support a maximum of 24 virtual functions per port o OCe14000 series adapters support a maximum of 2 port 10Gb Ethernet 31 virtual functions per physical function 4 port 10GbE 31 virtual functions per physical function 1 port 40GbE 63 virtual functions per physical function Server BIOS Configuration SR IOV requires support in the server chipset beyond standard virtualization technologies including operating system control of PCle and interrupt remapping The server may have BIOS options to control SR IOV and typically these are disabled by default The following may need modification in your system BIOS during boot Enable Virtualization such as Intel VT x or AMD V This is required for any virtual machine Explicitly enable SR IOV in the system BIOS The specific name for this option varies between vendors For instance it may be called Intel VT d Virtualization Technology for Direct I O
243. that the drives were lost If any I Os were in progress the system may see I O errors or failures 0x11990007 The iSCSI driver received a TMF that is The operating system version is not supported not supported and rejected this request The error log entry immediately following this entry will indicate the TMF function code that was rejected 0x11940008 The iSCSI driver received a TMF Abort This may indicate a slow connection to the request for an I O request that is not target Check network connectivity to the present with the driver target for any errors 0x1184000B Firmware returned invalid data in its Reload the firmware configuration iSCSI login and offload are disabled 0x11840002 The iSCSI driver encountered a This failure indicates that the driver version mismatched version of the firmware running on the system does not match the running on the board This error may firmware version on the board Correct this by be followed by error codes running the installer from the desired version 0x31840001 or 0x31880001 indicating that the iSCSI driver failed to load 0x11840001 The iSCSI driver detected a failure in This failure indicates that the hardware has the hardware during initialization not been initialized or is malfunctioning This This error may be followed by error may also indicate that the firmware is not codes 0x31840001 or 0x31880001 running correctly indicating that the iSCSI driver failed to load 0x1180
244. the iSCSI Driver This section provides troubleshooting information for the iSCSI driver Troubleshooting the Cisco Nexus Switch Configuration Note LACP cannot be used on an iSCSI port Table 4 5 provides troubleshooting information for the Cisco switch Table 4 5 Cisco Nexus Switch Situations for iSCSI Issue Solution The system is showing an excessive number of Ensure that LACP is not used on the iSCSI I O timeouts as a result of the switch routing frames to the incorrect port port iSCSI Driver Troubleshooting Table 4 6 provides troubleshooting information for the iSCSI driver Table 4 6 Troubleshooting the iSCSI Driver Issue Overall failure Answer Solution Use the iSCSlSelect utility to clear the Adapter Configuration See the Emulex Boot for NIC iSCSI FCoE and RoCE Protocols User 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 adapter link is down See iSCSI Error Log on Windows Server 2008 on page 162 and look for specific event codes to confirm Unable to create a memory dump file on a system booted over iSCSI Make sure the disk has enough free disk space to create the dump file If a full memory dump is selected the disk must have free space at least equivalent to the amount of physical memory in the system Unable to log in to target from WMI
245. this new IQN name Therefore any IQN name that was configured earlier such as by using iSCSISelect is overridden and the new IQN name will be in effect Although this does 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 If software based iSCSI targets are logged into the adapter Event ID 56 Driver SCSI 000000 appears in the Windows event viewer This issue has been observed on Windows Server 2008 R2 under the following conditions e The iSCSI target isa software based target MSiSCSI IET StarWind that uses a local hard drive or a RAM disk for its backend LUN Different adapter ports are involved in the login A SAS controller is present on the system Emulex Drivers for Windows User Manual This occurs caused because of an issue with the data reported by the iSCSI target in the Product Identification field in response to the standard inquiry from the adapter 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 If Windows encounters the same Product Identification field for different LUNs with the same Bus Target LUN field it records
246. tion Severity Log Action Remarks A link up event was received It is also possible for multiple link events to be received together Error LOG _ LINK EVENT verbose If numerous link events are occurring check physical connections to the FC network Ipfc_mes1304 is recorded if Map Entries gt 0 and the corresponding mode and SEVERITY level is set Ipfc_mes1305 Link down even tag x x Description Severity Log Action A link down event was received Error LOG LINK EVENT verbose If numerous link events are occurring check physical connections to the FC network Ipfc_mes1306 Link Down timeout Description Severity Log Action Emulex Drivers for Windows User Manual The link was down for greater than the configuration parameter HLinkTimeOut seconds All I O associated with the devices on this link will fail Warning LOG _LINK EVENT verbose Check adapter cable connection to SAN P011041 01A Rev A gt EMULEX 4 Troubleshooting 134 Troubleshooting the FC FCoE Driver Tag Messages 1400 1401 Ipfc_mes1400 Tag out of range Contextindex x x MaxIndex x x ulpCommand x x Description Severity Log Action Firmware has generated an invalid response Error LOG_LINK_EVENT verbose Review hardware configuration Contact Emulex technical support Ipfc_mes1401 Invalid tag Contextindex x x ulpCommand x x Description Severity Log Action Firmware has generated an i
247. tion TA small server is struggling to keep up with Disable RSS enable TCP offload enable jumbo packets larger servers on the network and increase the interrupt moderation to allow fewer interrupts per second A general purpose server such as Active Use TCP offload and enable RSS Directory server DHCP server or a DNS server exists Analyzing Performance Issues You can use the Windows Performance Monitor perfmon to view statistics for each network device To view statistics for each network device 1 Click Start gt Run gt perfmon to launch the Windows Performance Monitor 2 Right click and select Add Counters to add additional statistics Table 3 9 is a partial list of statistics to use for troubleshooting performance issues For network performance all of the counters from the table are useful Network Interface TCPv4 IPv4 and Processor Table 3 9 Statistics and Fine Tuning Situation Answer Solution Network Interface gt Packets Received Errors If this is incrementing even a small amount a physical issue may exist on the network such as a loose connection or bad cable causing CRC errors in Ethernet packets Find and eliminate the physical issue Network Interface gt Packets Received If this is incrementing dramatically the computer system Discarded may be receiving a lot of unsolicited traffic using network resources IPv4 gt Fragmented Datagrams sec If this is greater than 0
248. tion 4 Adaptive Default Emulex OneConnect OCe11102 I NIC TOE Local Area Connection Registry RSS 0 Disable Driver RSS 0 Disable Resetting All Parameters Resetting all parameters restores the default values for each adapter This is accomplished by using the command occfg a emulex x Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX Displaying All Parameters 3 Configuration 73 NIC Driver Configuration To display the current value of all parameters use either p or q command line options This shows the registry value or driver value of the parameter or both when using pq together For example occfg exe a SLOT 5 Port 1 pq OneConnect Network Config Copyright 2011 Emulex 10 4 164 0 Emulex OneConnect OCe14102 UX D 2 port PCIe 10GbE CNA SLOT 5 Port 1 Display all properties Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Registry Driver Class of Service 802 1p 1 Auto Priority Pause Class of Service 802 1p 1 Auto Priority Pause Encapsulated Task Offload 1 Enabled Encapsulated Task Offload 1 Enabled Enhanced Transmission Selection 0 Disabled Enh
249. tion This causes the command processor to wait for the installer to finish before it continues For more information on command line installation and configuration parameters see Appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 178 Emulex Drivers for Windows User Manual P011041 01A Rev A DE EMULEX 2 Installation 22 AutoPilot Installer Running a Software Installation Interactively Two options are available when performing an installation interactively These options assume you have already downloaded the driver kit from the Emulex website e Option 1 allows you to automatically run the AutoPilot Installer which completes the driver kit loading and installation with a few mouse clicks e Option 2 allows you to run the AutoPilot Installer separately This option is recommended when o Changing installation settings for a limited number of systems o Familiarizing yourself with AutoPilot Installer configuration options Option 1 Automatically Run the AutoPilot Installer Use this option unless you have specific configuration needs 1 Double click the driver kit or run it from a command line See Appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 178 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
250. tion 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 adapter to support DMA at 20 Gbps of data 10 Gbps read 10 Gbps write However most of the memory demands come from the processor accessing the data for either packet copies in the non offloaded networking stack or application Increasing the clock speed of the memory interface to the processor can be critical for achieving the best networking performance This interface may be the FSB Intel s QPI or AMD s HyperTransport Windows Server Network Driver Table 3 8 describes ways to use various NIC driver properties and Microsoft Windows properties to performance tune a system Table 3 8 Windows Server Performance Tuning Situations Situation Answer Solution A large number of short lived TCP Enable RSS increase the number of RSS queues and connections such as web server or e mail disable TCP offload server exist Large data transfers such as to a file server Use TCP connection offload web server with file downloads or an FTP server exist Large data transfers such as to a backup Enable jumbo packets and use TCP offload server exist Emulex Drivers for Windows User Manual P011041 01A Rev A NIC Driver Configuration SG EMULEX 3 Configuration 1Q3 Table 3 8 Windows Server Performance Tuning Situations Continued Situation Answer Solu
251. tomerRoute 2 Configure the Host Provider Addresses and Routes required for this setup Host PA Address amp Route information required by the VM policy Host Hostname PA s VM VirtualSubnetID gt Set on the VMNetworkAdapter on eash host Sm a ty kt ae a a a a a a a a a a a ae at ae E nents eee reyes ee eae ges neat scale Hostl example hostl 192 x x x Blue1 5001 Red1 6001 Host2 example host2 192 x x x Blue2 5001 Red2 6001 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 88 NIC Driver Configuration gt G EMULEX 2 1 Host1 a Configure Provider Address and Route Get the interface assign the PA and the default route Get NetVirtualizationProviderAddress where _ ProviderAddress eq 192 x x x Remove NetVirtualizationProviderAddress b Set VirtualSubnetID on the VM network port Get VMNetworkAdapter Bluel where MacAddress eq 060600000005 Set VMNetworkAdapter VirtualSubnetID 0 Get VMNetworkAdapter Redi where MacAddress eq 080800000005 Set VMNetworkAdapter VirtualSubnetID 0 Policy Script Information Verify or modify the following list of components for your specific conditions e Network connection name of the NIC attached to the virtual switch e Binding network connection to the Microsoft filter driver ms_netwnv Caution Do not change the filter driver name e VM Names e VM MAC Addresses e VMSID Vir
252. tor level privileges 2391419952 0x8F000040 AutoPilot Installer has detected unsupported adapters on the system 2399141968 0x8F 000050 Unattended software first installations are disallowed 2399141984 0x8F000060 You cancelled APInstall before any driver utility installation occurred 2399142000 0x8F000070 You cancelled APinstall after driver utility installation occurred Emulex Drivers for Windows User Manual P011041 01A Rev A Appendix D AutoPilot Installer Command Line and Configuration File Parameters gt lt EMULEX AutoPilot Installer Installation Reports Table D 1 Unattended Installation Error Codes Continued Error Code Hex Description 2399142032 0x8F000090 APInstaller encountered an error while parsing the command line Report file contains details AutoPilot Installer Installation Reports During each installation the AutoPilot Installer produces a report describing events that occurred during the installation This report contains the following sections Note The first section provides basic information including the time and date of the installation the name of the machine on which the installation was performed the version number of AutoPilot Installer and the identification of the configuration file that was used The second section provides an inventory of the Emulex adapters as they were before AutoPilot Installer performed any actions The third section lists the tasks tha
253. torage traffic using Microsoft s SMB Direct protocol For best performance pPFC must be configured on the network switch Emulex defaults to priority PFC 5 for ROCE traffic although it will still work without PFC enabled Network 256 Direct MTU 512 1024 default Windows Server 2012 R2 The MTU or frame size for ROCE traffic can be configured with this parameter 2048 4096 NVGRE Task Disabled Windows Server 2012 NVGRE Task Offload enables the Offload offloading of network Enabled default also known as Encapsulated Task Offload Windows Server 2012 R2 Note For 0Ce14000 series adapters only virtualization using GRE tunneling on the NIC adapter NVGRE offload works in conjunction with VMQ 1514 default 9014 8222 4088 Packet Size Emulex Drivers for Windows User Manual Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Configures packet size for OneConnect NIC adapters only 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 J umbo frames are IPv4 only frames IPv6 packets will be fragmented by LSO Switches and the peer must be configured to accept the sp
254. ts are RDMA enabled connected back to back to another 2 port OCe14000 series adapter both ports are also RDMA enabled creates two SMB Direct connections per interface see Figure 3 14 on page 94 Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration Q4 gt lt EMULEX NIC Driver Configuration Fite Home Share View d I Network bench29clienti c v Administrator C Windows system32 cmd exe Users fAdnministrator gt netstat xan ctive NetworkDirect Connections Listeners SharedEndpoints Mode IfIndex Type Local Address Foreign Address Kernel 26 Connection 26 2 6 1186 49369 20 2 0 100 445 Kernel Connection 20 2 6 116 49376 20 2 0 100 445 Kernel Connection 26 1 1161 49367 26 1 18661 445 Kernel Connection 26 1 1161 49368 WAS ES ee 05 BP oh Kernel Listener 26 2 6 116 445 NA Kernel Listener 26 1 110 251 445 NA Kernel 3 Listener fe8G 74F2 aad2 5734 2b2dax251 445 NA Kernel Listener 206 1 6 116 445 NA Users fdnministrator gt Figure 3 14 Two SMB Direct Connections Per Interface The number of connections initiated per RDMA capable NIC interface to a particular server can be configured using a registry key and the following PowerShell command Set ItemProperty Path HKLM SYSTEM CurrentControlSet Services LanmanWorkstation Parameters ConnectionCount PerRdmaNetworkInterface Type DWORD Value lt n gt Force SMB multichannel constraints can be used
255. tual Machine Subnet ID e HOST IP Address Provider Address Physical NIC IP Address for NVGRE e VM IP Address Customer Address IP Address on each vNIC per VM e Subnet Masks Verification and Troubleshooting Verify that the host provider addresses can ping each other If pings fail perform the following steps 1 Shutdown all VMs on all of the hosts Remove the policies Remove the vport0 virtual switch Reboot the hosts Create a vport0 switch Sy Ol ye On each VM add a new adapter and use the vswitch name that you just created Note Do not share the NIC with the host operating system 7 Apply the polices 8 Power up the VMs 9 Ping the provider addresses MS_NETWNV sys must only be bound to WNVNIC physical NIC If ms_netwnv is bound to a vswitch or Hyper V adapter unbind it from the host server For example Disable netadapterbinding vEthernet ComponentID ms_netwnv Emulex Drivers for Windows User Manual P011041 01A Rev A gt G EMULEX 3 Configuration 89 NIC Driver Configuration Verify that all of the IP addresses and MAC addresses used in the add and remove policy scripts match the VM IP s MACs using ipconfig all Create firewall rules to allow ICMP ping packets 1 New NetFirewallRule DisplayName Allow ICMPv4 In Protocol ICMPv4 2 New NetFirewallRule DisplayName Allow ICMPv4 Out Protocol ICMPv4 Direction Outbound PowerShell commands shown w WNVNIC used as the netwo
256. twork Adapters item Double click the desired Emulex adapter Select the Driver tab Click Update Driver The Update Driver wizard starts Click Browse my computer for driver software Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All dual channel adapter models are displayed in the Device Manager as two adapters therefore you must update each adapter Click Let me pick from a list of device drivers on my computer Select the network adapter that matches your hardware and click Have Disk Direct the Device Wizard to the location of ocnd63 inf Select the desired oemsetup inf file and click Open If you have installed the driver installer kit in the default folder the path is C Program Files Emulex AutoPilot Installer Drivers NDIS x64 NIC Win2012 Emulex Drivers for Windows User Manual P011041 01A Rev A 2 Installation 31 gt G EMULEX Removing Emulex Driver Kits and Drivers 10 Click Next 11 After the device driver finishes installing click Close The driver installation has completed The driver will start automatically Removing Emulex Driver Kits and Drivers This section details procedures to uninstall the driver kits Uninstalling Emulex Driver Kits Note Ifyou uninstall the Emulex driver kit AutoPilot Installer is automatically uninstalled Windows Server 2008 To uninstall a driver kit on a Windows S
257. u are creating custom unattended installation scripts any driver parameter can be modified and included in the script e Ifthe Adapter Protocol column is blank the parameter is supported on both LightPulse and OneConnect adapters LightPulse only indicates that the parameters is supported only on LightPulse adapters FC only indicates that the parameters is supported on LightPulse and non LightPulse FC adapters e The Windows driver enumerates 1024 targets across all physical and virtual ports with 8G Fibre Channel and 16G Fibre Channel adapters However setting ConfigScale to 0 changes the support to 128 targets See ConfigScale in Table 3 1 Storport Miniport Driver Parameters on page 36 Emulex Drivers for Windows User Manual P011041 01A Rev A gt EMULEX 3 Configuration 36 FC FCoE Driver Configuration Most parameters default to a setting that optimizes adapter performance Table 3 1 Storport Miniport Driver Parameters Activation Parameter Definitions Requirement Adapter Protocol AutoMap n AutoMap controls the way targets are assigned Reboot SCSI IDs Discovered targets are assigned persistent SCSI IDs according to the selected binding method Persistent bindings do not take effect with the driver in stand alone mode 0 automap is disabled The OneCommand Manager application persistently sets the SCSI address of a discovered FCP capable FC node target 1 automap by WWNN 2 automap by
258. ually Installing or Updating the Emulex Protocol Drivers You can install or update the Emulex protocol drivers and utilities manually without using AutoPilot Installer The Emulex PLUS ElxPlus driver supports the OneCommand Manager application persistent binding and LUN mapping and masking Note The ElxPlus driver must be installed before you install the Emulex protocol drivers Emulex Drivers for Windows User Manual P011041 01A Rev A DE EMULEX 2 Installation 27 Manually Installing or Updating the Emulex Protocol Drivers Installing the Emulex PLUS ElxPlus Driver for the First Time Note Only one instance of the ElxPlus driver must be installed even if you have multiple adapter ports installed in your system To install the ElxPlus driver from the desktop 1 10 Run the driver kit installer but do not run AutoPilot Installer See Running a Software Installation Interactively on page 22 for instructions Select Start gt Settings gt Control Panel gt Add Hardware The Add Hardware Wizard window appears Click Next Select Yes I have already connected the hardware and click Next Select Add a new hardware device and click Next Select Install the hardware that I manually select from a list Advanced and click Next Select Show All Devices and click Next Click Have Disk and direct the Device Wizard to the location of elxplus inf If you have installed the driver installer kit in the default fo
259. uding but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product described in this manual at any time and without any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this manual Emulex disclaims any undertaking to give notice of such changes Emulex 3333 Susan Street Costa Mesa CA 92626 Note References to OCe11100 series products also apply to OCe11100R series products Emulex Drivers for Windows User Manual P011041 01A Rev A Table of Contents gt G EMULEX Table of Contents List Of FIQUIES a cisaisinnr nmana ie aaia aa List OF Tabl6S ciiccissiccctcstertitadscrsscnnserenciretiae tears mrteaesneienrerersaeiiensae LO 1 Introduction ssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnna L2 Driver INfOrMatiON cateiccncasdcwesasnneansssasansdaniswimmsaneiaqiamennssmnnsieenaewiassansiewsnmed 12 Operating System Requirements sssssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 13 Ab br viati nS sc daceicseandeceaninansarnasanah santaanes tentanie E EE 13 2 NSC AN OM issos inean a aa a a Lo Onelnstall Installer i iccciiicicssccciarsrestdiscecsssecssersdas scatsaseasesissrsisenisadeesendie
260. ue with the system I O remapping hardware you may still be able to use SR IOV by explicitly enabling SR IOV in the registry using lovEnableOverride Note Emulex recommends this procedure only for trusted virtual machines Caution Use the registry editor at your own risk Using the registry editor can cause serious issues that may require you to reinstall the computer s operating system Emulex cannot guarantee that issues resulting from changes you make to the registry can be repaired Make a backup of your registry before making any changes Backing Up and Editing the Registry 1 Create a system restore point Open the registry editor by running regedit exe at the command prompt Select the hive the top level key and export it to a reg file Save the reg file to a location off of the server as a precaution ae WN Navigate to HKLM Software Microsoft Windows NT CurrentVersion Virtualization D Create a DWORD type entry named IovEnableOverride 7 Set the value of IovEnableOverride to 1 8 Reboot the system Emulex Drivers for Windows User Manual P011041 01A Rev A 3 Configuration 79 gt lt EMULEX NIC Driver Configuration 9 Ifthe system does not boot press lt F8 gt and select Previous Known Good or use the system restore function while booting from an operating system installation disc or recovery disc 10 If the system boots but does not work properly restore from a previous restore po
261. ug the system may hang or produce a bugcheck if a PCle hot unplug or replace is attempted Hot unplug is not supported in this release If 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 Emulex Drivers for Windows User Manual The system may not support Wake on LAN on the PCle slot in which the adapter is installed Check the system documentation to determine whether the system is capable of Wake on LAN operation A system BIOS setting may not be correct for Wake on LAN to work as expected Check the system documentation to determine whether Wake on LAN must be enabled in the system BIOS Wake on LAN may not be supported by the chipset as reported by the firmware The driver reports the value that is reported by the firmware The system may not go to a lower power state because another software component device or driver is preventing it Microsoft provides several useful references for troubleshooting Wake on LAN configuration issues in the Microsoft TechNet Library on the Microsoft website P011041 01A Rev A 4 Troubleshooting 138 Troubleshooting the NIC Drivers gt EMULEX Table 4 3 Troubleshooting the NIC Drivers Continued Issue Answer Solution When running Windows Server 2008 Apply the 979614 hotfix as described on the Microsoft website the computer restarts and shows various Sto
262. ult setting is not a high enough value performance degradation may occur due to Storport throttling its device queue CoalesceMsCnt CoalesceMsCnt defaults to zero If you are using a performance evaluation tool such as IOMETER and if you expect the I O activity to be greater than 8000 I Os per second set CoalesceMsCnt to 1 and reinitialized with an adapter reset or system reboot CoalesceRspCnt CoalesceRspCnt defaults to 8 For all other values up to the maximum of 63 the adapter does not interrupt the host with a completion until either CoalesceMsCnt milliseconds has elapsed or CoalesceRspCnt responses are pending The value of these two driver parameters reduces the number of interrupts per second which improves overall CPU utilization However there is a point where the number of I Os per second is small relative to CoalesceMsCnt and this will slow down the completion process causing performance degradation Examples Test Scenario One e IOMETER is running with an I O depth of 1 I O per device in a small scale configuration 16 devices In this case the test does not exceed the adapter s performance limits and the number of I Os per second are in the low thousands e Recommendation set CoalesceMsCnt to 0 or use the default value Test Scenario Two e IOMETER is running with an I O depth of 48 I Os per device in a small scale configuration 16 devices e Recommendation set QueueDepth to be greater than 48 for examp
263. updates at the Emulex website If applicable update the software 0x127b0012 The iSCSI driver received an invalid e Verify that the iSCSI target is certified by iSCSI Command Sequence Number update from the target Following this error log entry the next three entries will indicate the session handle and the iSCSI parameters MaxCmdSN and ExpCmdsSN respectively Emulex Drivers for Windows User Manual Microsoft Check for errors reported at the target The Emulex iSCSI adapter is only supported with certified targets e Check for software updates at the target vendor s website If applicable update the software e Check for software updates at the Emulex website If applicable update the software P011041 01A Rev A gt EMULEX Appendix A Error and Event Log Information iSCSI Error and Event Log 164 Table A 14 iSCSI Error Log Entries on Windows Server 2008 Continued Message ID Message Description Recommended Resolution 0x12790006 Aconnection to the target was lost for Check the connection to the target or the state a period exceeding the ETO The error of the target device If the target is made log entry immediately following this available any sessions that existed previously entry will indicate the session ID of are re established and the devices are the target that lost the connection available for I O There will be event log entries from the disk subsystem indicating
264. utoPilot Installer e Supply parameters on the command line See Appendix D AutoPilot Installer Command Line and Configuration File Parameters on page 178 for details After you have finished this step you can run AutoPilot Installer at a later time using either of the following methods Note If you are supplying options using the command line you must run AutoPilot Installer from the command line e Select Programs gt Emulex gt AutoPilot Installer in the Start menu e Run AutoPilot Installer from the command line Type c Program Files Emulex AutoPilot Installer lt driver type gt APInstall exe Note The location of APInstaller exe may differ on your system depending on your system s Program Files location You can also specify a different location when you install the driver package Hardware First Installation or Driver Update The driver kit must be downloaded from the Emulex website and loaded Notes e Updating the NIC protocol driver can temporarily disrupt operation of any NIC teams configured on the system e 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
265. valid adapter type SLI2 3 mode 0x03 Invalid adapter type SLI2 3 mode 0x04 CONFIG PORT failed 0x06 READ_CONFIG failed 0x07 CONFIG RING 0 failed 0x08 CONFIG RING 2 failed 0x09 CONFIG_RING 1 failed Ox0A CONFIG_RING 3 failed 0x0B INIT_LINK failed SLI2 3 mode 0x0C INIT_LINK failed SLI2 3 mode 0x0D READ_REV failed SLI2 3 mode Ox0E Invalid adapter type SLI2 3 mode OxOF Invalid adapter type SLI2 3 mode 0x10 CONFIG_PORT failed reinitialization 0x12 READ_CONFIG command failed reinitialization 0x13 CONFIG_RING 0 failed reinitialization 0x14 CONFIG_RING 1 failed reinitialization 0x15 CONFIG_RING 2 failed reinitialization 0x16 CONFIG_RING 3 failed reinitialization 0x17 Unresponsive adapter port SLI2 3 mode Ox1C Firmware trap infol SLI2 3 mode 0x1D Firmware trap info2 SLI2 3 mode 0x1E Over temperature error condition SLI2 3 mode Ox1F Firmware initiated adapter port reset SLI2 3 mode 0x20 Adapter port error attention SLI2 3 mode 0x22 Emulex Drivers for Windows User Manual P011041 01A Rev A Over temperature warning SLI2 3 mode 145 Appendix A Error and Event Log Information 146 gt lt EMULEX FC FCoE Error and Event Logs Table A 1 Severe Errors Continued
266. value 802 1p of zero P011041 01A Rev A gt G EMULEX 3 Configuration 47 NIC Driver Configuration Table 3 3 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 and Windows Server 2012 R2 NIC Driver Options Continued Option Supported Operating Name Acceptable Values Systems Definition Enhanced Disabled default Windows Server 2008 If ETS is enabled the driver filters e e Enabled Windows Server 2008 R2 oa r o on ection 1p priority tag into multiple Windows Server AOL separate transmit rings The Windows Server 2012 R2 network switch must be configured for ETS to group priorities into a Notes priority group or traffic class Each priority group can be OCe11102 CNAS assigned a QoS bandwidth limit on y For example one network priority ETSis not supported can support priority flow control to in conjunction with achieve loss less network traffic VMQ technology ETS Using separate hardware is not available if interfaces in the driver allows SR IOV is enabled each priority to progress at a different rate or pause temporarily without affecting the other priorities If ETS is enabled all configurations regarding bandwidth and priority flow control must be performed on the network switch The adapter will learn the configuration using the DCBX protocol Flow Control Disabled Windows Server 2008 Flow control is almost always RX and TX Enabled Windows Server 2008 R2 P F Pri P i default i
267. vices to load on sc config MpsSvc start demand demand To stop firewall services Net stop MpsSvc To temporarily disable firewall netsh advfirewall set all state off services Enabling certain Windows networking features such as network bridging VPN and routing can 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 adapter To disable these functions use the Services Control panel or the following commands at the command line prompt net stop accesspolicy net stop sharedaccess net stop ipnat Windows TCP Parameters Emulex does not recommend modifying the TCP registry parameters such as TcpAckFrequency provided by Microsoft The default parameters are suitable for a wide variety of situations with or without using TCP offloading Receive Window Auto Tuning and Compound TCP Windows Server adds several features to the host TCP stack such as receive window auto tuning and CTCP These features affect only non offloaded TCP traffic Performance of some 10GDE stress applications can suffer with these features enabled In particular when receive window auto tuning is enabled some bi directional data stream test performance degradation may occur 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 lin
268. while creating the requested number of SMB Direct connections Please reduce the connection count to a supported value Setting RoCE Parameters You can set the RoCE adapter parameters using OneCommand Manager PowerShell scripts or by using the Network Interface Property page Note See the OneCommand Manager Application User Manual for more information on using the OneCommand Manager GUI application to configure RoCE or see the OneCommand Manager Command Line Interface for information on using the OneCommand Manager CLI to configure RoCE The parameters in Table 3 6 can be modified from the Network Interface Property page Table 3 6 Parameters for RoCE Parameter Description NetworkDirect This parameter enables an offloaded RDMA interface for SMB 3 0 network attached storage traffic using Microsoft s SMB Direct protocol NetworkDirect MTU This parameter configures the maximum transmission unit frame size for RoCE traffic Note For optimal performance Emulex recommends setting the MTU size to 4096 The parameters in Table 3 7 can be viewed using the Statistics Property Page see Figure 3 3 on page 66 Table 3 7 RoCE Parameters Available for Viewing Parameter Description RoCE QP Allocated Indicates the number of established queue pairs for RoCE RoCE Transmit Throughput The transmit data rate of RoCE traffic RoCE Receive Throughput The receive data rate of RoCE traffic QoS Concepts
269. width 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 the Windows Server and it allows TCP connections to negotiate the optimal packet size that avoids IP fragmentation Flow Control The adapter 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 adapter can either respond to flow control packets by temporarily pausing transmits or send flow control PAUSE packets if the transmitter is overwhelming the system s receive bandwidth For best performance flow control must be enabled on the switches as well as on adapters Emulex Drivers for Windows User Manual P011041 01A Rev A SG EMULEX 3 Configuration 105 NIC Driver Configuration Receive and transmit flow control are enabled by default Flow control is not available if using FCoE on a converged network adapter In this situation priority
270. x0002a 42 Warning Legacy driver loaded Move to the NDIS 6 20 driver for Windows Server 2008 R2 for best performance 0x0029 41 Warning Legacy driver loaded Move to the NDIS 6 x driver for Windows Server 2008 for best performance 0x0028 40 Warning The firmware is outdated and does The firmware and the driver are not not support TOE offloads for this compatible versions See the driver Update the firmware Downloads section of the Emulex website for compatible firmware and drivers 0x0026 38 Warning The device firmware does not The firmware and the driver are not support RSS functionality for this compatible versions See the network adapter Downloads section of the Emulex website for compatible firmware and drivers 0x0025 37 Warning The device firmware does not The firmware and the driver are not support TCP offload functionality compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers 0x0024 36 Error The device firmware does not The firmware and the driver are not support network functionality compatible versions See the Downloads section of the Emulex website for compatible firmware and drivers 0x0023 35 Warning The Ethernet link is down due toa The Ethernet link is down due to the remote fault remote partner signaling a fault Check the peer device for errors 0x0022 34 Warning The Ethernet link is down due toa The Ethernet link is down due toa local fault link down event
271. y Installing or Updating the Emulex Protocol Drivers Select Don t Search I will choose the driver to install Click Have Disk and direct the Device Wizard to the location of the 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 x64 Click OK Select Emulex PLUS Click Next to install the driver Click Finish The ElxPlus driver update is finished Continue with the manual installation of the Storport Miniport Driver Installing or Updating the FC FCoE Storport Miniport Driver To update or install the FC FCoE Storport Miniport driver from the desktop 1 ae YN 10 11 12 13 14 Select Start gt Settings gt Control Panel gt System Select the Hardware tab Click Device Manager Open the SCSI and RAID Controllers item Double click the desired Emulex adapter Note The driver affects only the selected adapter If there are other adapters in the system you must repeat this process for each adapter All dual channel adapter models are displayed in Device Manager as two adapters and each adapter must be updated Select the Driver tab Click Update Driver The Update Driver wizard starts Select No not this time Click Next on the Welcome to the Hardware Update Wizard window Select Install from a list or specific location Advanced and click Next Select Don t search I will choose the drive
272. y installed and enabled MPIO support on a Windows Server you must log in to the target This section describes the steps to log into iSCSI targets through the WMI GUI For information on using the iSCSI Select utility to log into an iSCSI target see the Emulex Boot for NIC iSCSI FCoE and RoCE Protocols User 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 adapter port to use for login After the target login is complete select the target and click the Details or Properties button depending on the Windows operating system to see the multiple sessions connected Emulex Drivers for Windows User Manual P011041 01A Rev A 116 xs 3 Configuration 117 gt C EMULEX iSCSI Driver Configuration Maximum Transmission Unit MTU for iSCSI Connections Because the Emulex OneConnect adapter is a multi function adapter the MTU settings for iSCSI functions are different than the ones for NIC functions For iSCSI there is no explicit way to configure MTU from the OneCommand Manager application Instead this value is auto negotiated by the firmware Before establishing a TCP connection for an iSCSI Login the iSCSI firmware issues an ICMP Echo with a large payload to the iSCSI target If Jumbo Frames has been enabled on all the switches leading to the target as well as on the targ

Emulex® Drivers Version 10.4 for Windows

Contents

Download Pdf Manuals

Related Search

Related Contents

Emulex&reg; Drivers Version 10.4 for Windows

Contents

Download Pdf Manuals

Related Search

Related Contents

Emulex® Drivers Version 10.4 for Windows