Intel(R) Network Adapter Software Release Notes =============================================== October 15, 2012 Contents ======== - Supported Operating Systems - Viewing the User Guide - Intel(R) PROSet for Windows* Device Manager - Upgrading to Intel PROSet for Windows Device Manager - Intel Fiber Optic Adapters - Intel 10GbE Server Adapters - Quad Port Server Adapter Notes - Saving and Restoring Adapter Settings - Intel I/O Accelerated Technology - Installing Support for Teaming and VLANs - Teaming Notes - Power Management and System Wake - Microsoft Windows Server 2012 Notes - Microsoft Windows Server 2008 R2 - Microsoft Windows Server 2008 Notes - Linux Notes - SR-IOV Notes - Intel(R) iSCSI Remote Boot Notes - Intel(R) FCoE Boot Notes - Known Issues - Customer Support - Supported Adapters - Legal / Disclaimers Supported Operating Systems =========================== 32-bit Operating Systems ------------------------ Basic software and drivers are supported on the following operating systems: - Microsoft* Windows Server* 2008 - Red Hat Enterprise Linux (RHEL) 5.8 64-bit Operating Systems ------------------------ - Microsoft Windows Server 2012 - Microsoft Windows Server 2008 - RHEL 6.2 - RHEL 5.8 - SUSE Linux Enterprise Server (SLES) 11 SP2 - SLES 10 SP4 Viewing the User Guide ======================= Additional information can be found in the User's Guide. To access it: 1. Click "View User Guides" from the autorun screen or navigate to the MANUAL directory and double-click index.htm OR 2. Go to Dell web support site: http://www.support.dell.com/support/edocs/network/IntelPRO/ Intel(R) PROSet for Windows* Device Manager =========================================== Intel PROSet functionality is now integrated with the Windows Device Manager. To configure Intel adapters, open the Windows Device Manager. Do not open adapter, team, or VLAN properties from the network control panel, as you may be prompted to reboot your system. You must upgrade PROSet when upgrading drivers. Failure to do so will result in instability and missing tabs in Windows Device Manager. You must have administrator rights to install or use Intel PROSet for Windows Device Manager. Intel recommends the following procedure for installing drivers: 1) Cancel any Found New Hardware Wizard screens that open. 2) Start the autorun located on the CD or in your download directory. 3) Click "Install Drivers and Software" and follow the instructions in the install wizard. For software and driver versions prior to Release 16.2, if you have Fibre Channel over Ethernet (FCoE) boot enabled on any devices in the system, you will not be able to upgrade your drivers. You must disable FCoE boot before upgrading your ethernet drivers. This issue is resolved in Release 16.2 and beyond. Intel PROSet fails to install ----------------------------- A possible cause could be the Windows Modules Installer service is disabled. The installer for Intel PROSet requires this service. You can enable this service from the Administrative Tools -> Component Services control panel. Intel Fiber Optic Adapters ========================== Caution: The fiber optic ports may utilize Class 1 or Class 1M laser devices. Do not stare into the end of a fiber optic connector connected to a "live" system. Do not use optical instruments to view the laser output. Using optical instruments increases eye hazard. Laser radiation is hazardous and may cause eye injury. To inspect a connector, receptacle or adapter end, be sure that the fiber optic device or system is turned off, or the fiber cable is disconnected from the "live" system. Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure. The laser module contains no serviceable parts. Intel 10GbE Server Adapters =========================== Intel 10GbE adapters are not supported on DOS NDIS2 or DOS ODI-16. Attaching the cable to the Intel(R) 10 Gigabit AF DA Dual Port Server Adapter may require significant force. The cable must be latched in for proper operation. Intel 10GbE Network Adapter Known Issues ----------------------------------------- Supported SFP or SFP+ module not recognized by the system --------------------------------------------------------- If you try to install an unsupported module, the port may no longer install any subsequent modules, regardless of whether the module is supported or not. The port will show a yellow bang under Windows Device manager and an event id 49 (unsupported module) will be added to the system log when this issue occurs. To resolve this issue, the system must be completely powered off. Lower than expected performance on dual port 10GbE devices ---------------------------------------------------------- Some PCI-E x8 slots are actually configured as x4 slots. These slots have insufficient bandwidth for full 10G Ethernet line rate with dual port 10G Ethernet devices. The driver can detect this situation and will write the following message in the system log: "PCI-Express bandwidth available for this card is not sufficient for optimal performance. For optimal performance a x8 PCI-Express slot is required." If this error occurs, moving your adapter to a true x8 slot will resolve the issue. Unexpected Reboot after enabling Jumbo Frames --------------------------------------------- If you have a 10GbE adapter installed in an Intel I/OAT capable system with Direct Cache Access enabled, do not enable 9K jumbo frames on Windows Server 2008. Doing so may cause the system to reboot under normal to heavy receive traffic. Link Loss on 10GbE Devices with Jumbo Frames enabled ---------------------------------------------------- You must not lower Receive_Buffers or Transmit_Buffers below 256 if jumbo frames are enabled on an Intel(R) 10GbE Device. Doing so will cause loss of link. Failed connection and possible system instability ------------------------------------------------- If you have non-Intel networking devices capable of Receive-Side Scaling installed in your system, the Microsoft Windows registry keyword "RSSBaseCPU" may have been changed from the default value of 0x0 to point to a logical processor. If this keyword has been changed then devices based on Intel(R) 82598 or 82599 10 Gigabit Ethernet Controllers might not pass traffic. Attempting to make driver changes in this state may cause system instability. Set the value of RSSBaseCpu to 0x0, or to a value corresponding to a physical processor, and reboot the system to resolve the issue. Firmware version for Intel(R) Ethernet X520 10GbE Dual Port KX4-KR Mezz is missing in OMSA Network Page ----------------------------------------------------------------------- The OpenManage* Server Administrator (OMSA) does not list the firmware version of the Intel(R) Ethernet X520 10GbE Dual Port KX4-KR Mezz under the OMSA-Network page. When using DMIX to identify the adapter, the Activity LED blinks and the Link LED is solid -------------------------------------------------------------------- For the following adapters, if you use the Identify Adapter feature in DMIX, the Activity LED correctly blinks a green light. The Link LED displays a solid green light for 10G ports even if a network link is not present. - Intel(R) Ethernet X520 10GbE Dual Port KX4 Mezz - Intel(R) Ethernet X520 10GbE Dual Port KX4 Mezz - Intel(R) Ethernet X520 10GbE Dual Port KX4-KR Mezz - Intel(R) Ethernet Server Adapter X520-2 - Intel(R) Ethernet 10G 2P X520 Adapter - Intel(R) Ethernet 10G 4P X520/I350 rNDC - Intel(R) Ethernet 10G 2P X520-k bNDC - Intel(R) Ethernet 10G 2P X540-t Adapter - Intel(R) Ethernet 10G 4P X540/I350 rNDC Intel Gigabit Server Adapters ============================= Intel Gigabit Network Adapter Known Issues ------------------------------------------ Virtual NIC does not obtain IP address -------------------------------------- This issue affects devices based on the Intel(R) 82576 Controller. Virtual NICs with VMQ enabled might not automatically acquire IP addresses in the 32-bit Windows 2008 VM. Using static IP address will resolve the issue. Connecting Intel PRO/1000 PT and PRO/1000 PT Dual Port Server Adapters Back-to-Back ---------------------------------------------------------------------- When connecting any combination of two Intel PRO/1000 PT or PRO/1000 PT Dual Port Server Adapters back-to-back, make sure both connected ports do not have the Power Saver Option feature set to "Reduce power when cable disconnected." If this option is selected on both adapter ports, they may not be able to establish link. Using Wake on LAN and Intel PRO/1000 PT, PT Dual Port, and PF Server Adapters ----------------------------------------------------------------------------- Wake on LAN (WOL) is disabled by default on these adapters. Before allowing a system containing one of these adapters to go into hibernation, use BootUtil to enable Wake on LAN (WOL) on the adapter. Once the system is in a hibernate state, only a magic packet will wake it up. Other directed packets will have no effect. Intel Gigabit Network Adapters (copper only) do not detect active link during load time ----------------------------------------------------------------- Some Intel Gigabit Network adapters, especially copper adapters, cannot detect an active link during load time. To resolve this issue, try the following workarounds. - Re-attach to the server without reloading the driver. - For DOS-based installations, add a delay of 4 to 5 seconds in the batch file after the load driver command. - Load the configuration by manually entering commands. - Set adapter to link at 1000 Mbps only. Intel PRO/1000 Adapter will not have Link when forced to operate at 10 or 100 Mbps with a link partner also forced to the same state ------------------------------------------------------------------- Unless copper Gigabit Adapters are set to auto-negotiate, they are not MDI/MDI-X aware. When an Intel PRO/1000 Adapter is forced to operate at 10 or 100 Mbps, the adapter will not have a link with the link partner under the following circumstances: - If a link partner is also forced to operate at 10 or 100 Mbps, is connected back to back, and is connected using a regular cable instead of a crossover cable. - If a link partner is also forced to operate at 10 or 100 Mbps, connected to a switch, and connected using a crossover cable instead of a regular cable. Quad Port Server Adapter Notes ============================== Hot Plug operations are not supported by the Intel(R) Gigabit ET Quad Port Server Adapter. Downshifting ------------ When connecting to any Gigabit switch via a faulty CAT 5 cable where one pair is broken, the adapter does not downshift from 1 Gig to 100Mbps. For the adapter to downshift, it must identify two broken pairs in the cable. System does not boot -------------------- Your system may run out of I/O resources and fail to boot if you install more than four quad port server adapters. Moving the adapters to different slots or rebalancing resources in the system BIOS may resolve the issue. This issue affects the following Adapters: * Intel(R) Gigabit 4P I350-t Adapter * Intel(R) Gigabit ET Quad Port Server Adapter Saving and Restoring Adapter Settings ===================================== You can save and then restore adapter settings through the script SavResDX.vbs. Intel PROSet is required for SavResDX.vbs to function correctly. The Restore operation requires the same OS as when the configuration was saved. Major Operating system upgrades and saving your configuration ------------------------------------------------------------- Your network device settings, including teams and VLANs, are not saved when you upgrade your operating system. You must reinstall your network drivers and software and reconfigure your network devices. This applies for upgrading from one version of Microsoft Windows to another, not applying a service pack. Intel(R) I/O Acceleration Technology ==================================== Intel I/OAT requires the following to operate on Microsoft Windows Operating Systems: - A server chipset and BIOS that are Intel I/OAT capable - Microsoft Windows Server 2008 or later - An adapter or network connection that is Intel I/OAT-capable - The RSS advanced setting must be enabled - Under TCP/IP Offloading Options, both Offload Receive IP Checksum and Offload Receive TCP Checksum must be enabled. For more information about the Scalable Networking Pack, please see http://support.microsoft.com/kb/912222/article. Intel I/OAT Known Issues ------------------------ Unexpected reboot on driver update ---------------------------------- If a Direct Cache Access (DCA)-capable device has registered with the QuickData driver to perform DCA, the driver will not unload. When the QuickData driver is updated, the operating system will force a reboot. Installing Support for Teaming and VLANs ======================================== You must install Intel PROSet for Windows Device Manager if you want to use adapter teams or VLANs. Intel PROSet for Windows Device Manager is installed from the Product CD with the same process used to install drivers. You must have administrator rights to install or use Intel PROSet for Windows Device Manager. Intel recommends the following procedure for installing drivers: 1) Cancel any Found New Hardware Wizard screens that open. 2) Start the autorun located on the CD or in your download directory. 3) Click "Install Drivers and Software" and follow the instructions in the install wizard. NOTE: Be sure to check Advanced network Services for teaming and VLAN support. If Intel PROSet for Windows Device Manager was installed without ANS support, you can install support by clicking Install Base Drivers and Software on the autorun, or running setup.exe, and then selecting the Modify option when prompted. On the Custom Setup page, select "This feature will be installed on local hard drive from the Advanced Networking Services" check boxes, then continue with the installation wizard. If the base drivers and Intel PROset are preinstalled from the Dell Factory, install the intermediate (teaming) driver: 1. Double click on setup.exe in c:\install\IntelAdvanced. 2. Click on Modify from the Program Maintenance menu. 3. Check Advanced Network Services. 4. Click on Next then Install. Teaming Notes ============= Intel devices that are not supported by Intel(R) PROSet can still be added to teams. These devices are supported by the Multi-Vendor Teaming functionality of ANS teams. Microsoft's LBFO teaming ------------------------ Intel(R) Advanced Network Services teaming and VLANs are incompatible with Microsoft’s Load Balancing and Failover (LBFO) teaming. Do not create an LBFO team using ports that are part of an ANS team or ANS VLAN. DCB is not compatible with Microsoft Server 2012 NIC Teaming (LBFO) ------------------------------------------------------------------- Data Center Bridging (DCB) is incompatible with Microsoft Server 2012 NIC Teaming (LBFO). Do not create an LBFO team using Intel 10G ports when DCB is installed. Do not install DCB if Intel 10G ports are part of an LBFO team. Install failures and persistent link loss may occur if DCB and LBFO are used on the same port. RLB is not supported when a team is added to a virtual NIC ---------------------------------------------------------- Virtual NICs cannot be created on a team with Receive Load Balancing enabled. Receive Load Balancing is automatically disabled if you create a virtual NIC on a team. Team setup requirement ---------------------- Before creating a team, make sure each adapter is configured similarly. Check each adapter's settings in Intel PROSet. Settings to check include QoS Packet Tagging, Jumbo Frames, and the various offloads. If team members implement Advanced features differently, the team will align the settings with the least capable adapter. Changing Offload Settings for an Adapter in an ANS Team ------------------------------------------------------- When you disable an offload setting for an adapter in an ANS team, the team reloads and the team capabilities are recalculated. As a result, the offload setting is disabled for the remaining adapters in the team. Intel PROSet does not reflect the fact that the offload setting is disabled for the remaining adapters in the team. If you re-enable the offload setting for the original adapter in the team, the settings will not be applied until the system is rebooted or the team is reloaded. IEEE 802.3ad teaming on Cisco trunks ------------------------------------ When implementing 802.3ad teams on Cisco switch ports in trunking mode, set the native/untagged VLAN for these ports to ID 1. Otherwise, you may experience traffic loss or lack of failover between aggregators. See your Cisco documentation for information about setting the native VLAN ID. Teaming Known Issues -------------------- Network Connections window shows the team as disabled or network cable unplugged ---------------------------------------------------------------- After adding a VLAN to the team, this is normal. The connection protocols are now bound to the VLAN on the team. You can configure the connection protocols in the Properties for the VLAN. Team name doesn't change in Device Manager ------------------------------------------ If you modify a team name from the team property sheet, it may take several minutes for the name to change in Device Manager. Closing and opening Device Manager will load the new name. Removing a teamed adapter from a hot-plug system ------------------------------------------------ When you physically remove an adapter that is part of a team or a VLAN, you must reboot or reload the team/VLAN before using that adapter in the same network. This will prevent Ethernet address conflicts. Changing speed and duplex of adapters in a team ----------------------------------------------- When you add an adapter to a Link Aggregation team using Intel PROSet, make sure that the adapter is running at the same speed and duplex of the other adapters in the team. Compatibility notes for Multi Vendor Teaming -------------------------------------------- Attempting to hot-add a non-Intel adapter to a team may cause system instability. If you do hot-add a non-Intel adapter to a team, make sure you restart the computer or reload the team. Non-Intel adapter not added to team ----------------------------------- A non-Intel adapter might not be added correctly to a team if the following has occurred: The non-Intel adapter was previously removed (via Device Manager) from a team, and a VLAN was later added to that team. Subsequently, the team was uninstalled from Device Manager. If you create a new team that includes the non-Intel adapter, and the non-Intel adapter is not successfully added to that team, follow these steps to add the adapter: Click Modify Team on the Settings tab of the team properties dialog box. On the Adapters tab, select the non-Intel adapter, then click OK. IEEE 802.3ad teaming with Foundry switches ------------------------------------------ Foundry switches require an even number of ports in an aggregated link. If you remove an adapter from an 802.3ad team connected to a Foundry switch, make sure you maintain an even number of adapters in the team. Receive Side Scaling value is blank ----------------------------------- Changing the Receive Side Scaling setting of an adapter in a team may cause the value for that setting to appear blank when you next check it. It may also appear blank for the other adapters in the team. The adapter may be unbound from the team in this situation. Disabling and enabling the team will resolve the issue. Power Management and System Wake ================================ Not all systems support every wake setting. There may be BIOS or Operating System settings that need to be enabled for your system to wake up. In particular, this is true for Wake from S5 (also referred to as Wake from power off). Microsoft Windows Server 2008 R2 does not support wake on directed packet. Systems with this operating system will not wake on a ping. System does not wake when expected ---------------------------------- Under Microsoft Windows Server 2008 R2, the system may not wake when sent an ARP packet. Forcing your system into Home Networking mode (instead of work or public mode) will resolve the issue. You can set the network mode during install or from the Networking Control Panel. However, if the network is disconnected and reconnected, and a DHCP server is not available or if there is no default gateway defined, it appears to the operating system that the network is undefined and the OS will reset it to public. Under Microsoft Windows Server 2012, the system may not wake even though Wake on LAN settings are enabled. Disabling Fast Startup in the operating system should resolve the issue. System does not wake on link ---------------------------- On a driver-only installation, if you change 'Wake on Link Settings' to Forced and change 'Wake on Magic Packet' and 'Wake on Pattern Match' to Disabled, the system may not wake up when expected. In order to "Wake on Link" successfully, check the Power Management tab and make sure that “Allow this device to wake the computer” is checked. You may also need to change 'Wake on Magic Packet' or 'Wake on Pattern Match' to Enabled. Directed Packets may not wake the system ---------------------------------------- On some systems, quad port server adapters may not wake when configured to wake on directed packet. If you experience problems waking on directed packets, you must configure the adapter to use Magic Packets*. Power Management options are unavailable or missing --------------------------------------------------- If you install only the base drivers, later install Intel(R) PROSet for Windows Device Manager, then remove Intel PROSet, the settings on the Power Management tab on the Adapter Property Sheet may be unavailable or missing altogether. You must reinstall Intel PROSet to resolve the issue. System Wakes-Up from a Removed VLAN ----------------------------------- If a system goes into standby mode, and a directed packet is sent to the IP address of the removed VLAN, the system will wake-up. This occurs because a directed packet bypasses VLAN filtering. Intel PRO Adapters ignore consecutive Wake Up signals while transitioning into standby mode ----------------------------------------------------------- While sending a system into standby, occasionally a wake up packet arrives before the system completes the transition into standby mode. When this happens, the system ignores consecutive wake up signals and remains in standby mode until manually powered up using the mouse, keyboard, or power button. WOL and Standby options not available when connecting to a Gigabit Only switch (copper adapters only) ----------------------------------------------------------------------- When a copper media adapter is connected to a Gigabit-only switch, the WOL and Standby features are unavailable. This is due to the power consumption level of the adapter. The Intel PRO/1000 PF Server Adapters support WOL but use fiber media. WOL not supported on Intel(R) 10GbE 2P X520k bNDC ------------------------------------------------- WOL is not supported on the Intel(R) 10GbE 2P X520k bNDC with Dell 10Gb Ethernet Pass Through. Microsoft Windows Server* 2012 Notes ==================================== Please refer to Microsoft Technet for information on how to configure settings on a Windows Server 2012 Core installation. A utility (prosetcl.exe) for configuring Intel(R) PROSet and Advanced Network Services (ANS) is installed on your hard drive when you install Intel PROSet and ANS. The utility (prosetcl.exe) is installed in the Program Files\Intel\DMIX\CL directory. See the prosetcl.txt file for command descriptions and syntax examples. Microsoft Windows Server 2012 does not support the following devices: Intel(R) PRO/1000 PT Dual Port Server Adapter Intel(R) PRO/1000 PT Server Adapter Intel(R) PRO/1000 PF Server Adapter In Intel(R) PROSet for Windows Device Manager, the help text may not initially appear. The text should appear after switching between tabs a few times in Intel(R) PROSet. Microsoft Windows Server 2008 R2 Notes ====================================== Microsoft Windows Server 2008 R2 does not support Wake on directed packet. Systems using this operating system will not wake on a ping or other directed packet. Please refer to Microsoft Technet for information on how to configure settings on a Windows Server 2008 Core installation. See the dmscript.txt file for script descriptions. Flow Control is off by default ------------------------------ The inbox drivers for Intel network devices in Windows 7 and Windows Server 2008 R2 have flow control turned off by default. SNMP errors in the System Event Log ----------------------------------- Under Microsoft Windows 7 or Windows Server 2008 R2, you may see the following error in the System Event Log: "The SNMP Service encountered an error while accessing the registry key "SYSTEM\CurrentControlSet\Servcies\SNMP\Parameters\TrapConfiguration" The Windows 7 SNMP service start up isn’t properly configuring the service with a TrapConfiguration key. Perform the following to correct the issue: 1. Open Services applet (run services.msc). 2. Right click on SNMP Service, then select Properties. 3. Click on the Traps tab. Enter "public" for the Community name and click Add to list. 4. Click on the Security tab. Click the Add button. Enter "public" and click on the Add button. Microsoft Windows Server 2008 Notes =================================== Virtual Network Manager does not detect NIC hot plug event ---------------------------------------------------------- If you hot-remove a NIC, the attached VNIC does not detect the hot plug event and remains bound to the NIC instead of reverting to Internal. The NIC also remains available in the Virtual Network Manager. Uninstalling the driver before you remove the NIC will resolve this issue. This is only an issue on Windows Server 2008. Unexpected reboot on driver update ---------------------------------- If a direct Cache Access (DCA)-capable device has registered with the QuickData driver to perform DCA, the driver will not unload. When the QuickData driver is updated, the operating system will force a reboot. Bug checks and system instability when passing traffic with misconfigured Jumbo Packets setting ------------------------------------------------------------------------- If you are experiencing bug checks or system instability when passing traffic, please check your Jumbo Packet settings. If Jumbo Packets are not configured correctly, a mis-sized packet may be sent to the affected system. This results in the bug checks and system instability. Uninstall does not uninstall driver ----------------------------------- When the drivers are uninstalled on Microsoft Windows Server 2008, the operating system immediately re-installs the in-box drivers. This will cause a number to be appended to the device's displayed name. Interrupt Test not supported on adapters supporting MSI-X under Windows Server 2008 ----------------------------------------------------------------------------------- The Interrupt Test is not supported in the diagnostics in PROSet. Adapters with this limitation are: Intel Gigabit VT Quad Port Server Adapter Intel Gigabit ET Quad Port Server Adapter Intel Gigabit ET Dual Port Server Adapter Intel Gigabit ET Quad Port Mezzanine Card Intel 10 Gigabit XF SR Server Adapter Intel 10 Gigabit AT Server Adapter Intel Ethernet Server Adapter X520-2 Intel Ethernet X520 10GbE Dual Port KX4 Mezz Intel Ethernet X520 10GbE Dual Port KX4-KR Mezz FIFO Test not supported on the following Intel 10 Gigabit Server Adapters ------------------------------------------------------------------------- The FIFO Test is not supported in the diagnostics in PROSet. The adapters with this limitation are: Intel 10 Gigabit XF SR Server Adapter Intel 10 Gigabit AT Server Adapter Intel 10 Gigabit AF DA Dual Port Server Adapter Network Adapters Do Not Retain Device State After DUP Drivers Are Updated ------------------------------------------------------------------------- In a Windows Server 2008 environment, disabled ports may become enabled when updating the DUP driver package. Linux Notes =========== HeaderDataSplit is not supported in 82599-based adapters. Configuring the Driver on Different Distributions ------------------------------------------------- Configuring a network driver to load properly when the system is started (0=legacy, 1=MSI, 2=MSI-X) is distribution dependent. Typically, the configuration process involves adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well as editing other system startup scripts and/or configuration files. Many popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, refer to your distribution documentation. If during this process you are asked for the driver or module name, the name for the Linux Base Driver for the Gigabit Family of Adapters is e1000e. As an example, if you install the e1000e driver for two Gigabit adapters (eth0 and eth1) and set the speed and duplex to 10full and 100half, add (0=legacy, 1=MSI, 2=MSI-X) the following to modules.conf or modprobe.conf: alias eth0 e1000e alias eth1 e1000e options e1000e Speed=10,100 Duplex=2,1 The same method can be used to associate an e1000 driver with a legacy device and the e1000e driver with a PCIe device. alias eth0 e1000 alias eth1 e1000e Enabling WOL in Linux Using Ethtool and BootUtil ------------------------------------------------ By default, WOL is disabled. In a Linux environment, WOL is enabled using ethtool and, in some instances, using BootUtil is required. Only port A (port 0) can be enabled through ethtool without using BootUtil. To enable WOL using ethtool on other ports, WOL must be enabled with BootUtil first. SR-IOV Notes ============ SR-IOV support in different server systems ------------------------------------------ SR-IOV is not supported on AMD servers. SR-IOV is only supported on Intel(R) 10GbE Server Adapters: - Intel(R) Ethernet X520 10GbE Dual Port KX4-KR Mezz - Intel(R) Ethernet Server Adapter X520-2 - Intel(R) Ethernet 10G 2P X540-t Adapter - Intel(R) Ethernet 10G 2P X520 Adapter - Intel(R) Ethernet 10G 4P X540/I350 rNDC - Intel(R) Ethernet 10G 2P X520-k bNDC Operating systems supporting SR-IOV ----------------------------------- Linux drivers are provided for the following versions: Red Hat Enterprise Linux (RHEL): - RHEL 5.8 - RHEL 6.2 SUSE Linux Enterprise Server (SUSE): - SLES 10 SP4 (Intel® 64 only) Cannot Create Virtual Functions in RHEL 6.1 x64 ----------------------------------------------- Using RHEL6.1 native ixgbe driver, you cannot Create Virtual Functions. Use the driver version from support.dell.com and make sure you remove the native driver using modprobe -r before you load it. Intel(R) iSCSI Remote Boot Notes ================================ A device cannot be uninstalled if it is configured as an iSCSI primary or secondary port. Disabling the iSCSI primary port also disables the secondary port. To boot from the secondary port, change it to be the primary port. iSCSI Remote Boot Known Issues ------------------------------ A Windows Reboot message appears when changing settings ------------------------------------------------------- When iSCSI Boot is installed on an Intel PCI Express network adapter but not enabled, the reboot message posted in Windows can be disregarded when teams or VLANs are created or when configuration changes are made to any base driver advanced feature. iSCSI Remote Boot: Connecting back-to-back to a target with a Broadcom LOM -------------------------------------------------------------------------- Connecting an iSCSI boot host to a target through a Broadcom LOM may occasionally cause the connection to fail. Use a switch between the host and target to avoid this. iSCSI Remote Boot Firmware may show 0.0.0.0 in DHCP server IP address field --------------------------------------------------------------------------- In a Linux base DHCP server, the iSCSI Remote Boot firmware shows 0.0.0.0 in the DHCP server IP address field. The iSCSI Remote Boot firmware looks at the DHCP server IP address from the Next-Server field in the DHCP response packet. However, the Linux base DHCP server may not set the field by default. Add "Next-Server ;" in dhcpd.conf to show the correct DHCP server IP address. Intel(R) FCoE Boot Notes ======================== When installing Windows Server 2008 with a local disk and capturing the OS image, it should be noted that the image file must be on a separate local disk other than the operating system boot disk. The OS may have an additional system reserved partition that needs to be included in the image file. Thus, it is advisable to image the OS disk rather than just the OS partition. Installing Windows Server 2008 directly to the FCoE disk is currently not supported. Known Issues ============ Priority & VLAN Setting is not supported when DCB is enabled ------------------------------------------------------------ If you enable an adapter that has Data Center Bridging (DCB) enabled, immediately opening the adapter’s property sheet may show the Priority & VLAN setting as available. Changing the setting while it is available is not supported and may have adverse affects on performance. After the driver and Fibre Channel over Ethernet stacks finish loading, this setting will be grayed out. Unexpected NMI with 82599-based NICs ------------------------------------ If you set the PCIe Maximum Payload Size to 256 bytes in your system BIOS and install an 82599-based NIC, you may receive an NMI when the NIC attains link. This happens when the physical slot does not support a payload size of 256 Bytes even if the BIOS does. Moving the adapter to a slot that supports 256 bytes will resolve the issue. Consult your system documentation for information on supported payload values. VLANs are not supported on VMQ enabled adapters and teams --------------------------------------------------------- If you create a VLAN on a VMQ enabled adapter, the VMQ setting will automatically be set to disabled. The same will happen if you create a VLAN on a team whose member adapters have VMQ enabled. Unexpected Connectivity Loss ---------------------------- If you uncheck the “Allow the computer to turn off this device to save power” box on the Power Management tab and then put you system to sleep, you may lose connectivity when you exit sleep. You must disable and enable the NIC to resolve the issue. Installing Intel(R)PROSet for Windows Device Manager will also resolve the issue. Network stack will not enable RSC ------------------------------------------------------- If Intel Data Center Bridging (DCB) is installed (FCoE, iSCSi, or both), the network stack will not enable Receive Segment Coalescing (RSC). Modifying ETS while traffic is running causes Intel x520 to blast PFC pauses resulting in volume drop. ----------------------------------------------------------------------------------------------------- In certain scenarios, servers or storage arrays connected to the switch may experience excessive traffic loss when ETS thresholds are changed. Servers and storage arrays connected to the switch using Intel X520 converged adapters may experience excessive traffic loss when the switch's ETS thresholds in a DCB output policy while converged traffic is running. Workaround: Please use the following procedure to change ETS thresholds in a DCB policy that is already applied to an interface or a group of interfaces: 1) Create a new ETS output policy with the desired values. 2) Apply the new ETS output policy on the appropriate interfaces, which will replace the previous policy. Note: Refer to Dell Force10 documentation and Release Notes to configure DCB policies Customer Support ================ - Main Dell web support site: http://www.support.dell.com Supported Adapters ================== Copper Adapters --------------- - Intel PRO/1000 PT Server Adapter - Intel PRO/1000 PT Dual Port Server Adapter - Intel Gigabit ET Quad Port Server Adapter - Intel Gigabit ET Dual Port Server Adapter - Intel Gigabit 2P I350-t Adapter - Intel Gigabit 4P I350-t Adapter - Intel 10 Gigabit AT Server Adapter - Intel 10 Gigabit Dual Port AF DA Server Adapter - Intel Ethernet Server Adapter X520-T2 - Intel Ethernet 10G 2P X540-t Adapter - Intel Ethernet 10G 2P X520 Adapter Fiber Optic Adapters -------------------- - Intel PRO/1000 PF Server Adapter - Intel 10 Gigabit XF SR Server Adapter - Intel Ethernet Server Adapter X520-2 Mezzanine Cards --------------- - Intel Gigabit ET Quad Port Mezzanine Card - Intel Gigabit 4P I350-t Mezz - Intel Ehernet X520 10GbE Dual Port KX4 Mezz - Intel Ethernet X520 10GbE Dual Port KX4-KR Mezz Network Daughter Cards ---------------------- - Intel Gigabit 4P I350-t rNDC - Intel Gigabit 4P X540/I350 rNDC - Intel Ethernet 10G 4P X540/I350 rNDC - Intel Ethernet 10G 2P X520-k bNDC Legal / Disclaimers =================== Copyright (C) 2002-2012, Intel Corporation. All rights reserved. Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein. * Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners' benefit, without intent to infringe.