Intel XL710-Q2 User Manual
  1. Manuals
  2. Brands
  3. Intel Manuals
  4. Computer Hardware
  5. XL710-Q2
  6. User manual

Intel XL710-Q2 User Manual

Ethernet adapters and devices
Hide thumbs Also See for XL710-Q2:
Table of Contents

Advertisement

Quick Links

®
Intel
Ethernet Adapters and Devices
User Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the XL710-Q2 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Intel XL710-Q2

Summary of Contents for Intel XL710-Q2

  • Page 1 ® Intel Ethernet Adapters and Devices User Guide...

  • Page 2: Installing The Network Adapter

    Gen3 x8 slot. Installing it in a shorter slot, or a Gen2 or Gen1 slot, will limit the throughput of the adapter. Some older Intel® Ethernet Adapters do not have full software support for the most recent versions of Microsoft Windows*. Many older Intel Ethernet Adapters have base drivers supplied by Microsoft Windows.

  • Page 3: Hardware Compatibility

    The latest BIOS for your system One open PCI Express slot NOTE: The Intel® 10 Gigabit AT Server Adapter will only fit into x8 or larger PCI Express slots. Some systems have physical x8 PCI Express slots that actually support lower speeds. Please...

  • Page 4: Cabling Requirements

    Multi-mode fiber with 62.5 micron core diameter; maximum length is 275 meters. Connector type: LC. Copper Cables Maximum lengths for Intel® 10 Gigabit Server Adapters and Connections that use 10GBASE-T on Cat- egory 6, Category 6a, or Category 7 wiring, twisted 4-pair copper: Maximum length for Category 6 is 55 meters.

  • Page 5: Installation Overview

    To ensure compliance with CISPR 24 and the EU's EN55024, Intel® 10 Gigabit Server Adapters and Connections should be used only with CAT 6a shielded cables that are properly terminated according to the recommendations in EN50174-2. 10 Gigabit Ethernet over SFP+ Direct Attached Cable (Twinaxial) Length is 10 meters max.

  • Page 6: Optimizing Performance

    In order for an Intel® X710/XL710 based Network Adapter to reach its full potential, you must install it in a PCIe Gen3 x8 slot. Installing it in a shorter slot, or a Gen2 or Gen1 slot, will impact the throughput the adapter can attain.
  • Page 7 Increase the allocation size of Driver Resources (transmit/receive buffers). However, most TCP traffic patterns work best with the transmit buffer set to its default value, and the receive buffer set to its min- imum value. When passing traffic on multiple network ports using an I/O application that runs on most or all of the cores in your system, consider setting the CPU Affinity for that application to fewer cores.

  • Page 8: Remote Storage

    Software configuration of DCBX parameters via dcbtool/lldptool are not supported. iSCSI Over DCB Intel® Ethernet adapters support iSCSI software initiators that are native to the underlying operating system. In the case of Windows, the Microsoft iSCSI Software Initiator, enables connection of a Windows host to an external iSCSI storage array using an Intel Ethernet adapter.
  • Page 9 ® Intel Ethernet FCoE (Fibre Channel over Ethernet) Fibre Channel over Ethernet (FCoE) is the encapsulation of standard Fibre Channel (FC) protocol frames as data within standard Ethernet frames. This link-level encapsulation, teamed with an FCoE-aware Ethernet-to- FC gateway, acts to extend an FC fabric to include Ethernet-based host connectivity. The FCoE specification focuses on encapsulation of FC frames specific to storage class traffic, as defined by the Fibre Channel FC-4 FCP specification.
  • Page 10 Point to Point (PT2PT) Mode In Point to Point mode, there are only two ENodes, and they are connected either directly or through a lossless Ethernet switch:...

  • Page 11: Intel ® Boot Agent

    Intel Boot Agent The Intel® Boot Agent is a software product that allows your networked client computer to boot using a program code image supplied by a remote server. Intel Boot Agent complies with the Pre-boot eXecution Environment (PXE) Version 2.1 Specification. It is compatible with legacy boot agent environments that use BOOTP protocol.

  • Page 12: Virtualization Support

    Intel Ethernet iSCSI Boot Intel® Ethernet iSCSI Boot provides the capability to boot a client system from a remote iSCSI disk volume located on an iSCSI-based Storage Area Network (SAN). NOTE: Release 20.6 is the last release in which Intel® Ethernet iSCSI Boot supports Intel® Eth- ernet Desktop Adapters and Network Connections.
  • Page 13 (for example, setting LAA on the interface, changing the primary adapter on a team, etc.), will cause the VNIC to lose connectivity. In order to prevent this loss of connectivity, Intel® PROSet will not allow you to change settings that change the MAC address.
  • Page 14 NOTE: Support for the Intel PROSet command line utilities (prosetcl.exe and crashdmp.exe) has been removed, and is no longer installed. This functionality has been replaced by the Intel Netcmdlets for Microsoft* Windows PowerShell*. Please transition all of your scripts and processes to use the Intel Netcmdlets for Microsoft Windows PowerShell.
  • Page 15 Each Intel® Ethernet Adapter has a pool of virtual ports that are split between the various features, such as VMQ Offloading, SR-IOV, Data Center Bridging (DCB), and Fibre Channel over Ethernet (FCoE). Increasing the number of virtual ports used for one feature decreases the number available for other features. On devices that support it, enabling DCB reduces the total pool available for other features to 32.
  • Page 16 SR-IOV architecture includes two functions: Physical Function (PF) is a full featured PCI Express function that can be discovered, managed and configured like any other PCI Express device. Virtual Function (VF) is similar to PF but cannot be configured and only has the ability to transfer data in and out.

  • Page 17: Installation

    Installation NOTE: For installation on Windows Server 2016 Nano Server, see Installing on Nano Server below. Network Direct Kernel (NDK) features are included in the Intel base drivers. Follow the steps below to install user-mode Network Direct (ND) iWARP features.
  • Page 18 Legal / Disclaimers Copyright (C) 2016, 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. Intel is a trademark of Intel Corporation in the U.S. and/or other countries.

  • Page 19: Installing The Adapter

    Installing the Adapter Select the Correct Slot One open PCI-Express slot, x4, x8, or x16, depending on your adapter. NOTE: Some systems have physical x8 PCI Express slots that actually only support lower speeds. Please check your system manual to identify the slot. Insert the Adapter into the Computer 1.
  • Page 20 Length is 100 meters max for Category 6a. Length is 100 meters max for Category 7. NOTE: For the Intel® 10 Gigabit AT Server Adapter, to ensure compliance with CISPR 24 and the EU’s EN55024, this product should be used only with Category 6a shielded cables that are properly terminated according to the recommendations in EN50174-2.
  • Page 21 Intel gigabit adapters. Intel Gigabit and 10 Gigabit Server Adapters using copper connections automatically accommodate either MDI or MDI-X connections. The auto-MDI-X feature of Intel gigabit copper adapters allows you to directly connect two adapters without using a cross-over cable.
  • Page 22 For connections based on the X710/XL710 controller, support is dependent on your system board. Please see your vendor for details. In all cases Intel recommends using Intel optics; other modules may function but are not val- idated by Intel. Contact Intel for supported media types.
  • Page 23 LR Modules Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV- Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDZ- Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDDZ- QSFP Mod- ules Intel TRIPLE RATE 1G/10G/40G QSFP+ SR (bailed) (40G not sup- E40GQSFPSR ported on 82599) The following is a list of 3rd party SFP+ modules that have received some testing.
  • Page 24 PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY, AND ARE NOT RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF ANY THIRD PARTY'S PRODUCT BY INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE BY ANY THIRD PARTY AND THE THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE INFORMATION REGARDING CERTAIN OPTIC MODULES AND CABLES WITH THE ABOVE SPECIFICATIONS.

  • Page 25: Pci Hot Plug Support

    OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR SELECTION OF VENDOR BY CUSTOMERS.
  • Page 26 Intel network adapter. NOTES: The MAC address and driver from the removed adapter will be used by the replacement adapter unless you remove the adapter from the team and add it back in. If you do not remove and restore the replacement adapter from the team, and the original adapter is used elsewhere on your network, a MAC address conflict will occur.
  • Page 27 Install the Drivers NOTE: This will update the drivers for all supported Intel® network adapters in your system. Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network cable.
  • Page 28 4. Follow the instructions to complete the installation. 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 setup64.exe, and then selecting the Modify option when prompted.
  • Page 29 DMIX PROSet for Windows Device Manager "0", do not install Intel PROSet feature (default). If the Intel PROSet feature is already installed, it will be uninstalled. "1", install Intel PROSet feature. The DMIX property requires BD=1. NOTE: If DMIX=0, ANS will not be installed. If DMIX=0 and Intel PROSet, ANS, and FCoE are already installed, Intel PROSet, ANS, and FCoE will be uninstalled.
  • Page 30 Parameter Definition NOTE: Even if FCOE=1 is passed, FCoE will not be installed if the operating system and installed adapters do not support FCoE. ISCSI iSCSI "0", do not install iSCSI (default). If iSCSI is already installed, it will be uninstalled. "1", install FCoE.
  • Page 31 If you specify a path for the log file, the path must exist. If you do not specify a complete path, the install log will be created in the current directory. You do not need to specify default values. To install the base drivers, Intel PROSet, and ANS, the following examples are equivalent: DxSetup.exe...
  • Page 32 The /liew log option provides a log file for the Intel PROSet installation. NOTE: To install teaming and VLAN support on a system that has adapter base drivers and Intel PROSet for Windows Device Manager installed, type the command line D:\DxSetup.exe ANS=1.

  • Page 33: Compatibility Notes

    ® Using Intel PROSet for Windows* Device Manager Intel® PROSet for Windows* Device Manager is an extension to the Windows Device Manager. When you install the Intel PROSet software, additional tabs are automatically added to Device Manager. NOTES: You must have administrator rights to install or use Intel PROSet for Windows Device Man- ager.
  • Page 34 You cannot change the speed or duplex of Intel adapters that use fiber cabling. Intel 10 Gigabit adapters that support 1 gigabit speed allow you to configure the speed setting. If this option is not present, your adapter only runs at its native speed.

  • Page 35: Advanced Tab

    More specific instructions are available in the Intel PROSet help. Advanced Tab The settings listed on Intel PROSet for Windows Device Manager's Advanced tab allow you to customize how the adapter handles QoS packet tagging, Jumbo Packets, Offloading, and other capabilities. Some of the following features might not be available depending on the operating system you are running, the specific adapters installed, and the specific platform you are using.
  • Page 36 There are also several BIOS, platform, and application settings that will affect your potential energy savings. A white paper containing information on how to best configure your platform is available on the Intel website. Flow Control Enables adapters to more effectively regulate traffic.
  • Page 37 Interrupt Moderation Rate Sets the Interrupt Throttle Rate (ITR). This setting moderates the rate at which Transmit and Receive interrupts are generated. When an event such as packet receiving occurs, the adapter generates an interrupt. The interrupt interrupts the CPU and any application running at the time, and calls on the driver to handle the packet. At greater link speeds, more interrupts are created, and CPU rates also increase.
  • Page 38 Jumbo Packets can be implemented simultaneously with VLANs and teaming. If a team contains one or more non-Intel adapters, the Jumbo Packets feature for the team is not supported. Before adding a non-Intel adapter to a team, make sure that you disable Jumbo Packets for all non-Intel adapters using the software shipped with the adapter.
  • Page 39 The team's LAA if the team has an LAA configured. Intel PROSet does not use an adapter's LAA if the adapter is the primary adapter in a team and the team has an LAA. Log Link State Event This setting is used to enable/disable the logging of link state changes.
  • Page 40 Performance Options Performance Profile Performance Profiles are supported on Intel® 10GbE adapters and allow you to quickly optimize the performance of your Intel® Ethernet Adapter. Selecting a performance profile will automatically adjust some Advanced Settings to their optimum setting for the selected application. For example, a standard server has optimal performance with only two RSS (Receive-Side Scaling) queues, but a web server requires more RSS queues for better scalability.
  • Page 41 Advanced tab in Intel® PROSet. For other versions of the Windows operating system, tagging is enabled using the "Priority/VLAN Tagging" setting on the Advanced tab in Intel® PROSet. Once QoS is enabled in Intel PROSet, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.
  • Page 42 Receive Buffers Defines the number of Receive Buffers, which are data segments. They are allocated in the host memory and used to store the received packets. Each received packet requires at least one Receive Buffer, and each buffer uses 2KB of memory. You might choose to increase the number of Receive Buffers if you notice a significant decrease in the performance of received traffic.
  • Page 43 2 queues are used when good throughput and low CPU utilization are required. 4 queues are used for applications that demand maximum throughput and transactions per second. 8 and 16 queues are supported on the Intel® 82598-based and 82599-based adapters. NOTES: The 8 and 16 queues are only available when PROSet for Windows Device Manager is installed.
  • Page 44 Node to the physical port, if available. This setting is read-only and cannot be configured. Performance Tuning The Intel Network Controller provides a new set of advanced FCoE performance tuning options. These options will direct how FCoE transmit/receive queues are allocated in NUMA platforms. Specifically, they direct what target set of NUMA node CPUs can be selected from to assign individual queue affinity.
  • Page 45 FCoE NUMA Node Count = 1 FCoE Starting NUMA Node = 0 FCoE Starting Core Offset = 8 Example 2: Using one or more ports with queues allocated across multiple NUMA nodes. In this case, for each NIC port the FCoE NUMA Node Count is set to that number of NUMA nodes. By default the queues will be allocated evenly from each NUMA node: FCoE NUMA Node Count = 2 FCoE Starting NUMA Node = 0...
  • Page 46 Distributed Multi-Root PCI/Memory Architecture Example 4: The number of available NUMA node CPUs is not sufficient for queue allocation. If your platform has a processor that does not support an even power of 2 CPUs (for example, it supports 6 cores), then during queue allocation if SW runs out of CPUs on one socket it will by default reduce the number of queues to a power of 2 until allocation is achieved.
  • Page 47 NOTE: This feature is enabled and configured by the equipment manufacturer. It is not available on all adapters and network controllers. There are no user configurable settings. Monitoring and Reporting Temperature information is displayed on the Link tab in Intel® PROSet for Windows* Device Manger. There are three possible conditions: Temperature: Normal Indicates normal operation.
  • Page 48 The setting is: Off for copper Intel gigabit adapters with a speed of "Auto". On for copper Intel gigabit adapters with a forced speed and duplex. On for fiber Intel gigabit adapters with a speed of "Auto".
  • Page 49 Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team, as this may cause system instability.
  • Page 50 VLANs can co-exist with teaming (if the adapter supports both). If you do this, the team must be defined first, then you can set up your VLAN. The Intel PRO/100 VE and VM Desktop Adapters and Network Connections can be used in a switch based VLAN but do not support IEEE Tagging.
  • Page 51 Not all team types are available on all operating systems. Be sure to use the latest available drivers on all adapters. Not all Intel devices support Intel ANS or Intel PROSet. Intel adapters that do not support Intel ANS or...
  • Page 52 Intel PROSet may still be included in a team. However, they are restricted in the same way non-Intel adapters are. See Multi-Vendor Teaming for more information. You cannot create a team that includes both Intel X710/XL710-based devices and Intel® I350-based devices.
  • Page 53 The Team Properties window appears, showing team properties and settings. Once a team has been created, it appears in the Network Adapters category in the Computer Management window as a virtual adapter. The team name also precedes the adapter name of any adapter that is a member of the team.
  • Page 54 Intel ANS teaming and VLANs are not compatible with Microsoft's LBFO teams. Intel® PROSet will block a member of an LBFO team from being added to an Intel ANS team or VLAN. You should not add a port that is already part of an Intel ANS team or VLAN to an LBFO team, as this may cause system instability.
  • Page 55 If you are using a Windows-based computer, adapters that appear in Intel PROSet may be included in a team. NOTE: In order to use adapter teaming, you must have at least one Intel server adapter in your system. Furthermore, all adapters must be linked to the same switch or hub.
  • Page 56 If an Intel AMT enabled device is part of a team, it must be designated as the primary adapter for the team.
  • Page 57 3. Click Set Primary or Set Secondary. 4. Click OK. The adapter's preferred setting appears in the Priority column on Intel PROSet's Team Configuration tab. A "1" indicates a preferred primary adapter, and a "2" indicates a preferred secondary adapter.
  • Page 58 Switch Fault Tolerance (SFT) Switch Fault Tolerance (SFT) supports only two NICs in a team connected to two different switches. In SFT, one adapter is the primary adapter and one adapter is the secondary adapter. During normal operation, the secondary adapter is in standby mode. In standby, the adapter is inactive and waiting for failover to occur. It does not transmit or receive network traffic.
  • Page 59 Static Link Aggregation teaming requires that the switch be set up for Static Link Aggregation teaming and that spanning tree protocol is turned off. An Intel AMT enabled adapter cannot be used in an SLA team. IEEE 802.3ad: Dynamic Link Aggregation IEEE 802.3ad is the IEEE standard.
  • Page 60 Manually verify that the frame setting for the non-Intel adapter is the same as the frame settings for the Intel adapters. If a non-Intel adapter is added to a team, its RSS settings must match the Intel adapters in the team.

  • Page 61: Power Management Tab

    If your system has a Manageability Engine, the Link LED may stay lit even if WoL is disabled. Power Options The Intel PROSet Power Management tab includes several settings that control the adapter's power consumption. For example, you can set the adapter to reduce its power consumption if the cable is disconnected.
  • Page 62 These control the type of packets that wake up the system from standby. For some adapters, the Power Management tab in Intel PROSet includes a setting called Wake on Magic Packet from power off state. Enable this setting to explicitly allow wake-up with a Magic Packet* from shutdown under APM power management mode.
  • Page 63 Intel® Ethernet Converged Network Adapter XL710-Q1 Intel® Ethernet Converged Network Adapter XL710-Q2 Most Intel 10GbE Network Adapters do not support Wake on LAN on any port. The Intel® Ethernet Converged Network Adapter X550-T1 and Intel® Ethernet Converged Network Adapter X550-T2 have a manageability/AUX power connector. These devices only support WoL if AUX power is supplied via this connector.Note that this is system and adapter specific.
  • Page 64 NetAdapterAdvanceProperty cmdlet from Windows PowerShell*, or any other cmdlet not provided by Intel. Doing so may cause the team to stop using that adapter to pass traffic. You may see this as reduced performance or the adapter being disabled in the ANS team. You can resolve this issue by changing the setting back to its previous state, or by removing the adapter from the ANS team and then adding it back.
  • Page 65 The Restore operation requires the same OS as when the configuration was Saved. Intel® PROSet for Windows* Device Manager must be installed for the SaveRestore.ps1 script to run. For systems running a 64-bit OS, be sure to run the 64-bit version of Windows PowerShell, not the 32-bit (x86) version, when running the SaveRestore.ps1 script.
  • Page 66 Save Example To save the adapter settings to a file on a removable media device, do the following. 1. Open a Windows PowerShell Prompt. 2. Navigate to the directory where SaveRestore.ps1 is located (generally c:\Program Files\Intel\Wired Networking\DMIX). 3. Type the following: SaveRestore.ps1 –Action Save –ConfigPath e:\settings.txt...
  • Page 67 Intel Network Drivers for DOS The NDIS2 (DOS) driver is provided solely for the purpose of loading other operating systems -- for example, during RIS or unattended installations. It is not intended as a high-performance driver. You can find adapter drivers, PROTOCOL.INI files, and NET.CFG files in the PRO100\DOS or PRO1000\DOS directory in the download folder.
  • Page 68 DRIVERNAME This is the only parameter required for all configurations. This parameter is essentially an "instance ID". Each instance of the driver must create a unique instance name, both to satisfy DOS driver requirements, and to make it possible to find the parameters for the instance in the PROTOCOL.INI file. When the driver initializes, it tries to find previously loaded instances of itself.
  • Page 69 Syntax: SLOT = [0x0..0x1FFF] SLOT = [0..8191] Examples: SLOT = 0x1C SLOT = 28 Default: The driver will Auto-Configure if possible. Normal Beha- The driver uses the value of the parameter to decide which adapter to control. vior: Possible Errors: If only one adapter is installed, and the value does not correctly indicate the adapter slot: A message indicates that the value does not match the actual configuration...
  • Page 70 Syntax: ADVERTISE = [ 1 | 2 | 4 | 8 | 0x20 | 0x2F]: 0x01 = 10 Half, 0x02 = 10 Full, 0x04 = 100 Half, 0x08 = 100 Full, 0x20 = 1000 Full, 0x2F = all rates Example: ADVERTISE = 1 Default: 0x2F (all rates are supported) Normal Beha-...
  • Page 71 Syntax: UseLastSlot = [ 0 | any other value ] Example: USELASTSLOT = 1 Default: Normal Behavior: 0 = Disabled, any other value = Enabled Possible Errors: None TXLOOPCOUNT This parameter controls the number of times the transmit routine loops while waiting for a free transmit buffer. This parameter can affect Transmit performance.
  • Page 72 For more information on DCB, including the DCB Capability Exchange Protocol Specification, go to http://www.ieee802.org/1/pages/dcbridges.html DCB for Windows Configuration: Intel Ethernet Adapter DCB functions can be configured using Windows Device Manager. Open the adapter's property sheet and select the Data Center tab. You can use the Intel® PROSet to perform the following tasks:...
  • Page 73 Using iSCSI over DCB with ANS Teaming The Intel® iSCSI Agent is responsible for maintaining all packet filters for the purpose of priority tagging iSCSI traffic flowing over DCB-enabled adapters. The iSCSI Agent will create and maintain a traffic filter for an ANS Team if at least one member of the team has an "Operational"...

  • Page 74: Linux Configuration

    Initiator and Intel® Ethernet adapters will support them. Please consult your distribution documentation for additional configuration details on their particular Open iSCSI initiator. Intel® 82599 and X540-based adapters support iSCSI within a Data Center Bridging cloud. Used in conjunction with switches and targets that support the iSCSI/DCB application TLV, this solution can provide guaranteed minimum bandwidth for iSCSI traffic between the host and target.

  • Page 75: Remote Boot

    ROM. UEFI specific *.FLB images are included in the downloaded release media. The "Boot Options" tab in Intel® PROSet for Windows Device Manager will allow the UEFI *.FLB image to be installed on the network adapter.
  • Page 76 Enable Remote Boot If you have an Intel Desktop Adapter installed in your client computer, the flash ROM device is already available in your adapter, and no further installation steps are necessary. For Intel Server Adapters, the flash ROM can be enabled using the BootUtil utility. For example, from the command line type:...
  • Page 77 A network boot option will appear in the boot options menu when the UEFI PXE network stack and Intel UEFI network driver have been loaded. Selecting this boot option will initiate a PXE network boot. Configuring UEFI Network Stack for TCP/UDP/MTFTP An IP-based network stack is available to applications requiring IP-based network protocols such as TCP, UDP, or MTFTP.
  • Page 78 Intel® Boot Agent Configuration Boot Agent Client Configuration The Intel® Boot Agent software provides configuration options that allow you to customize the behavior of the Intel Boot Agent software. You can configure the Intel Boot Agent in any of the following environments:...
  • Page 79 Configuring the Intel® Boot Agent in a Microsoft Windows Environment If you use the Windows operating system on your client computer, you can use Intel® PROSet for Windows* Device Manager to configure and update the Intel Boot Agent software. Intel PROSet is available through the device manager.
  • Page 80 Use BIOS Setup Boot Order. only Try local drives only Legacy OS 0 = Disabled If set to 1, the Intel Boot Agent will enable PME in the adapter’s PCI Wakeup (Default configuration space during initialization. This allows remote wakeup Support. (For Value) under legacy operating systems that don’t normally support it.
  • Page 81 Overview For the Intel® Boot Agent software to perform its intended job, there must be a server set up on the same network as the client computer. That server must recognize and respond to the PXE or BOOTP boot protocols that are used by the Intel Boot Agent software.
  • Page 82 PCI configuration space could not be read. Machine is probably not PCI compliant. reading PCI con- The Intel Boot Agent was unable to read one or more of the adapter's PCI con- figuration figuration registers. The adapter may be mis-configured, or the wrong Intel Boot space.
  • Page 83 == xx PXE-E51: No The Intel Boot Agent did not receive any DHCP or BOOTP responses to its initial DHCP or request. Please make sure that your DHCP server (and/or proxyDHCP server, if BOOTP offers one is in use) is properly configured and has sufficient IP addresses available for received.
  • Page 84 After booting, my computer experiences problems After the Intel® Boot Agent product has finished its sole task (remote booting), it no longer has any effect on the client computer operation. Thus, any issues that arise after the boot process is complete are most likely not related to the Intel Boot Agent product.
  • Page 85 If you have an Intel® Gigabit VT Quad Port Server Adapter, Intel® PRO/1000 PT Quad Port LP Server Adapter, or an Intel® PRO/1000 PF Quad Port Server Adapter with two or more ports configured for PXE, you may experience POST hangs on some server systems. If this occurs the suggested workaround is move the adapter to another system and disable PXE on all but one port of the Adapter.
  • Page 86 Diagnostics information may include the following items: Item Description The Printed Wire Assembly number identifies the adapter's model and version. Number The unique Ethernet address assigned to the device. Address Memory The memory address assigned by the BIOS for memory-mapped adapter access. The I/O port address assigned by the BIOS for I/O-mapped adapter access.

  • Page 87: Iscsi Boot Configuration

    Boot POST Setup Intel® Ethernet iSCSI Boot features a setup menu which allows two network ports in one system to be enabled as iSCSI Boot devices. To configure Intel® iSCSI Boot, power-on or reset the system and press the Ctrl-D key when the message "Press <Ctrl-D>...
  • Page 88 One network port in the system can be selected as the primary boot port by pressing the 'P' key when highlighted. The primary boot port will be the first port used by Intel® Ethernet iSCSI Boot to connect to the iSCSI target. Only one port may be selected as a primary boot port.
  • Page 89 Boot Port Selection Menu. Intel® iSCSI Boot Configuration Menu The Intel® iSCSI Boot Configuration Menu allows you to configure the iSCSI Boot and Internet Protocol (IP) parameters for a specific port. The iSCSI settings can be configured manually or retrieved dynamically from a...
  • Page 90 Initiator Name - Enter the iSCSI initiator name to be used by Intel® iSCSI Boot when connecting to an iSCSI target. The value entered in this field is global and used by all iSCSI Boot-enabled ports in the system.
  • Page 91 DHCP for iSCSI target is not enabled. iSCSI CHAP Configuration Intel® iSCSI Boot supports Mutual CHAP MD5 authentication with an iSCSI target. Intel® iSCSI Boot uses the "MD5 Message Digest Algorithm" developed by RSA Data Security, Inc. The iSCSI CHAP Configuration menu has the following options to enable CHAP authentication: Use CHAP - Selecting this checkbox will enable CHAP authentication for this port.
  • Page 92 Intel® PROSet for Windows* Device Manager Many of the functions of the Intel® iSCSI Boot Port Selection Setup Menu can also be configured or revised from Windows Device Manager. Open the adapter's property sheet and select the Data Options tab. You must install the latest Intel Ethernet Adapter drivers and software to access this.
  • Page 93 LUN: LUN ID configured on iSCSI target system. Default is zero. Target name: iSCSI target name to uniquely identify an iSCSI target in IQN format. Example: iqn.1986-03.com.intel:target1 DHCP Host Name Option 12: Configure option 12 with the hostname of the iSCSI initiator.

  • Page 94: Iscsi Troubleshooting

    Booting and installing. This means that there are no additional steps outside of the installer that are necessary to install to an iSCSI target using an Intel Ethernet Server Adapter. Please refer to the SLES10 documentation for instructions on how to install to an iSCSI LUN.
  • Page 95 BIOS all reduce the memory area available to Intel Ethernet iSCSI Boot. Disable these devices and reboot the system to see if Intel iSCSI Boot is able to initialize. If disabling the devices in the system BIOS menu does not resolve the problem then attempt to remove unused disk devices or disk controllers from the system.
  • Page 96 Refer to your network switch documentation on how to dis- able Spanning Tree Protocol. Error message Intel Ethernet iSCSI Boot was not able to detect a valid PnP PCI displayed: BIOS. If this message displays Intel Ethernet iSCSI Boot cannot run "PnP Check Structure...
  • Page 97 Verify that the target is configured to iSCSI target system." allow the Intel iSCSI Remote Boot initiator access to a LUN. When installing Linux to If these error messages are seen, unused iscsi interfaces on NetApp NetApp Filer, after a Filer should be disabled.
  • Page 98 Microsoft Initiator does not boot without link on boot port: After setting up the system for Intel® Ethernet iSCSI Boot with two ports connected to a target and successfully booting the system, if you later try to boot the system with only the secondary boot port connected to the target, Microsoft Initiator will continuously reboot the system.
  • Page 99 NDIS Driver May Not Load During iSCSI Boot F6 Install With Intel® PRO/1000 PT Server Adapter If you are using two Intel® PRO/1000 PT Server Adapters in two PCI Express x8 slots of a rack mounted Xeon system, Windows installation can be done only via a local HDD procedure.
  • Page 100 Do not set LAA on ports with iSCSI Boot enabled. Intel® Ethernet iSCSI Boot version does not match between displayed versions on DMIX and the scrolling text during boot If a device is not set to primary but is enumerated first, the BIOS will still use that device's version of iSCSI Boot.
  • Page 101 Automatic creation of iSCSI traffic filters for DCB is only supported on networks which make use of IPv4 addressing The iSCSI for Data Center Bridging (DCB) feature uses Quality of Service (QOS) traffic filters to tag outgoing packets with a priority. The Intel iSCSI Agent dynamically creates these traffic filters as needed on networks using IPv4 addressing.
  • Page 102 Intel® Ethernet FCoE Configuration Using Intel® PROSet for Windows* Device Manager Many FCoE functions can also be configured or revised using Intel PROSet for Windows* Device Manager, accessed from the FCoE Properties button within the Data Center tab. You can use Intel PROSet to perform the following tasks:...
  • Page 103 Fibre Channel target, and detect the boot disk. Intel® PROSet for Windows* Device Manager Many of the functions of the Intel® Ethernet FCoE Boot Port Selection Setup Menu can also be configured or revised using Intel® PROSet for Windows Device Manager.
  • Page 104 New Installation on a Windows Server* system. 2. Verify that the FCoE Boot disk is available in the Fabric View tab of Intel® PROSet for Windows Device Manager, and verify that you are online using Windows Disk Manager. 3. Open a command prompt, run the fcoeprep.bat batch file. To find the batch file, navigate to the \APPS\FCOEBOOT\Winx64\Setup directory.
  • Page 105 Intel® Ethernet FCoE Boot Option ROM Setup FCoE Port Selection Menu To configure Intel® Ethernet FCoE Boot, switch on or reset the system and press Ctrl-D when the message "Press <Ctrl-D> to run setup..." is displayed. After pressing Ctrl-D, you will be taken to the Intel®...
  • Page 106 FCoE Boot Targets Configuration Menu FCoE Boot Targets Configuration: Discover Targets is highlighted by default. If the Discover VLAN value displayed is not what you want, enter the correct value. Highlight Discover Targets and then press Enter to show targets associated with the Discover VLAN value. Under Target WWPN, if you know the desired WWPN you can manually enter it or press Enter to display a list of previously discovered targets.
  • Page 107 FCoE Target Selection Menu...
  • Page 108 Keyboard Shortcuts: Up/Down, TAB and SHIFT-TAB to move between the controls.  Left/Right/Home/End/Del/Backspace in the edit boxes. Press the Esc key to leave the screen. UEFI Setup for Intel® FCoE Boot Once you complete the configuration, it will be stored in the system's firmware memory.
  • Page 109 Before beginning the configuration, update the adapter's UEFI FCoE Option ROM using the BootUtil tool and the latest BootIMG.FLB file. Use the following command: BOOTUTIL64E.EFI -up=efi+efcoe -nic=PORT -quiet where PORT is the NIC adapter number (in the following example nic=1) NOTE: The UEFI FCoE driver must be loaded before you perform the following steps.
  • Page 110 1. From the FCoE Configuration menu, select Add an Attempt. All supported ports are displayed. 2. Select the desired port. The FCoE Boot Targets Configuration screen is displayed. 3. Select Discover Targets to automatically discover available targets (alternatively, you can manually enter the fields on the FCoE Boot Targets Configuration screen).
  • Page 111 5. Select the desired target from the list. The FCoE Boot Targets Configuration screen is displayed with completed fields for the selected target. 6. Press F10 (Save) to add this FCoE attempt. The FCoE Configuration screen is displayed with the newly added FCoE attempt listed.
  • Page 112 Deleting an Existing FCoE Attempt 1. From the FCoE Configuration menu, select Delete Attempts. 2. Select one or more attempts to delete, as shown below (note that the example now shows three added attempts). 3. To delete the selected attempts, choose Commit Changes and Exit. To exit this screen without deleted the selected attempts, choose Discard Changes and Exit.
  • Page 113 For specific information on configuring your FCoE target system and disk volume, refer to instructions provided by your system or operating system vendor. Listed below are the basic steps necessary to setup Intel® Ethernet FCoE Boot to work with most FCoE targets. The specific steps will vary from one vendor to another.

  • Page 114: Suse* Linux Enterprise Server

    Windows Server installation. 2. Verify that the FCoE Boot disk is available in the Fabric View tab of Intel® PROSet for Windows Device Manager, and verify that you are online using Windows Disk Manager. 3. Open a command prompt, run the fcoeprep.bat batch file. To find the batch file, navigate to your archi- tecture's directory within the \APPS\FCOEBOOT\Winx64\Setup directory.

  • Page 115: Red Hat Enterprise Linux

    Booting and installing. This means that there are no additional steps outside of the installer that are necessary to install to an iSCSI target using an Intel Ethernet Server Adapter. Please refer to the RHEL 6 documentation for instructions on how to install to an iSCSI LUN.
  • Page 116 When setting the port to a boot port in Intel PROSet for Windows Device Manager, a message shows that the user should restart the system for the changes to be effective but does not force a restart. As a result the user level applications are in boot mode (i.e., Data Center Tab is grayed out) but kernel level drivers haven’t been...
  • Page 117 If an FCoE-booted port loses link for longer than the time specified in the Linkdown Timeout advanced setting in the Intel® Ethernet Virtual Storage Miniport Driver for FCoE, the system will crash. Linkdown Timeout values greater than 30 seconds may not provide extra time before a system crash.

  • Page 118: Troubleshooting

    Insert the adapter in another slot. Check for conflicting or incompatible hardware devices and settings. Replace the adapter. Check the Intel support website for possible documented issues. Select your adapter from the adapter family list. Check the Frequently Asked questions section.
  • Page 119 The device does not connect at the When Gigabit Master/Slave mode is forced to "master" mode expected speed. on both the Intel adapter and its link partner, the link speed obtained by the Intel adapter may be lower than expected. The adapter stops working without Run the adapter and network tests described under "Test the...
  • Page 120 Problem Solution Adapter". Make sure the proper (and latest) driver is loaded. Make sure that the link partner is configured to auto-negotiate (or forced to match adapter) Verify that the switch is IEEE 802.3ad-compliant. The link light is on, but communications Make sure the proper (and latest) driver is loaded. ...

  • Page 121: Multiple Adapters

    Operating System - Networking feature implementation will vary by operating system version, such as offloading and multiprocessor threading. Testing the Adapter Intel's diagnostic software lets you test the adapter to see if there are problems with the adapter hardware, the cabling, or the network connection. Testing from Windows...

  • Page 122: Dos Diagnostics

    Responder Testing The Intel adapter can send test messages to another Ethernet adapter on the same network. This testing is available in DOS via the diags.exe utility downloaded from Customer Support.
  • Page 123 1. Boot to MS-DOS. 2. Navigate to the \DOSUtilities\UserDiag directory, then type DIAGS at the prompt and press <Enter>. The test utility program automatically scans the hardware and lists all Intel-based adapters. They are listed in this manner: If you have only one network connection in your system, this screen will be bypassed.
  • Page 124 Change Test Options The test setup screen allows you to configure and select the specific tests desired. Each option is toggled by moving the cursor with the arrow keys and pressing <Enter> to change the option. The number of tests is simply entered from the keyboard in the appropriate box.

  • Page 125: Indicator Lights

    Indicator Lights The Intel Server and Desktop network adapters feature indicator lights on the adapter backplate that serve to indicate activity and the status of the adapter board. The following tables define the meaning for the possible states of the indicator lights for each adapter board.
  • Page 126 Single Port QSFP+ Adapters The Intel® Ethernet Converged Network Adapter XL710-Q1 has the following indicator lights: Label Indication Meaning Green Linked at 40 Gb Yellow Linked at 1/10 Gb  ACT/LNK Blinking On/OFF Actively transmitting or receiving data No link. The Intel® Ethernet Converged Network Adapter X520-Q1 has the following indicator lights:...
  • Page 127 Linked at 1 Gb Blinking On/OFF Actively transmitting or receiving data No link. The Intel® 10 Gigabit AF DA Dual Port Server Adapter and Intel® Ethernet Server Adapter X520 series of adapters have the following indicator lights: Label Indication Meaning Linked to the LAN.
  • Page 128 Quad Port SFP/SFP+ Adapters The Intel® Ethernet Converged Network Adapter X710-4 has the following indicator lights: Label Indication Meaning Green Linked at 10 Gb Yellow Linked at 1 Gb Blinking On/OFF Actively transmitting or receiving data No link. The Intel® Ethernet Converged Network Adapter X520-4 has the following indicator lights:...
  • Page 129 Dual Port Copper Adapters The Intel® Ethernet Converged Network Adapter X550-T2 has the following indicator lights: Label Indication Meaning Green Linked at 10 Gb.  Link Yellow Linked at 1 Gb. Linked at 100 Mbps. Blinking On/Off Actively transmitting or receiving data.
  • Page 130 The Intel® Ethernet Server Adapter X520-T2 has the following indicator lights: Label Indication Meaning Green Linked at 10 Gb. Link Yellow Linked at 1 Gb. No link. Blinking On/Off Actively transmitting or receiving data. Activity No link.
  • Page 131 Identity. Use the "Identify Adapter" button in Intel Orange PROSet to control blinking. See Intel PROSet Help flashing for more information. The Intel® PRO/1000 MT and GT Dual Port Server Adapters have the following indicator lights for each port: Label Indication Meaning Green on The port is connected to a valid link partner.
  • Page 132 The adapter is not sending or receiving network data.  100 Operating at 100 Mbps. Operating at 10 Mbps. The Intel® PRO/100 S Dual Port Server adapter (with 64 bit PCI Connector) has the following indicator lights: Label Indication Meaning  ACT/LNK...
  • Page 133 Single Port Copper Adapters The Intel®Ethernet Converged Network Adapter X550-T1 has the following indicator lights: Label Indication Meaning Green Linked at 10 Gb.  Link Yellow Linked at 1 Gb. Linked at 100 Mbps. No link. Activity Blinking On/Off Actively transmitting or receiving data.
  • Page 134 Linked at 1 Gb No link. Activity Blinking On/Off Actively transmitting or receiving data. The Intel® 10 Gigabit AT Server Adapter has the following indicator lights: Label Indication Meaning Green on The adapter is connected to a valid link partner.
  • Page 135 The Intel® PRO/1000 PT Server Adapter has the following indicator lights: Label Indication Meaning Green on The adapter is connected to a valid link partner. Green  ACT/LNK Data activity flashing No link. 10 Mbps Green 100 Mbps 10=OFF Orange 1000 Mbps...
  • Page 136 The Intel® Gigabit CT2, Gigabit CT, PRO/1000 T, and PRO/1000 MT Desktop Adapters have the fol- lowing indicator lights: Label Indication Meaning Green on The adapter is connected to a valid link partner. Green Data activity flashing  ACT/LNK No link.
  • Page 137 10 Mbps 10/100/1000 Green 100 Mbps Yellow 1000 Mbps The Intel® PRO/100+, PRO/100 M, PRO/100 S , and PRO/100 VE and VM Desktop adapters and Net- work Connections have the following indicator lights: Label Indication Meaning  ACT/LNK The adapter and switch are receiving power;...
  • Page 138 Quad Port Copper Adapters The Intel® Ethernet Converged Network Adapter X710-T4 has the following indicator lights: Label Indication Meaning Green on The adapter is connected to a valid link partner. Green flashing Data activity No link. Green 10 Gbps Yellow...
  • Page 139 1000 Orange PROSet to control blinking. See Intel PROSet Help flashing for more information. 10 Mbps The Intel® PRO/1000 MT, GT and PT Quad Port Server Adapters have the following indicator lights for each port: Label Indication Meaning Green on The port is connected to a valid link partner.
  • Page 140  ACT/LNK Blinking PROSet to control blinking. See Intel PROSet Help for more information. No link. The Intel® PRO/1000 MF, PF, and Gigabit EF Dual Port Server Adapters have the following indicator lights for each port: Label Indication Meaning The adapter is connected to a valid link partner.
  • Page 141  ACT/LNK Blinking PROSet to control blinking. See Intel PROSet Help for more information. No link. The Intel® PRO/1000 MF and PF Server Adapters have the following indicator lights: Label Indication Meaning The adapter is connected to a valid link partner.
  • Page 142 The Intel® PRO/1000 XF Server Adapter has the following indicator lights: Label Indication Meaning The adapter is connected to a valid link partner. No link. Data is being transmitted or received. No data activity. Identity. Use the "Identify Adapter" button in Intel Flashing PROSet to control blinking.
  • Page 143 Quad Port Fiber Adapters The Intel® Ethernet Server Adapter I340-F4 has the following indicator lights: Label Indication Meaning The adapter is connected to a valid link part- Green on ner.  GRN=1G Green flash- Data activity No link.
  • Page 144 The Intel® PRO/1000 PF Quad Port Server Adapter has the following indicator lights: Label Indication Meaning Green on The adapter is connected to a valid link partner.  ACT/LNK Green flashing Data activity No link.

  • Page 145: Known Issues

    Dropped Receive Packets on Half-Duplex 10/100 Networks If you have an Intel PCI Express adapter installed, running at 10 or 100 Mbps, half-duplex, with TCP Segment Offload (TSO) enabled, you may observe occasional dropped receive packets. To work around this problem, disable TSO or update the network to operate in full-duplex or 1 Gbps.
  • Page 146 PFC may not pause traffic as expected. If you mapped more than one priority to a Traffic Class, enabling only one of the priorities and disabling the others will work around the issue. Installing Intel’s DCB implementation will also resolve this issue. This issue affects Microsoft Windows Server 2012 and Server 2012 R2.
  • Page 147 VLAN Creation Fails on a Team that Includes a Non-Intel Phantom Adapter If you are unable to create a VLAN on a team that includes a non-Intel phantom adapter, use Device Manager to remove the team, then recreate the team without the phantom adapter, and add the team to the VLAN.
  • Page 148 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® 82598 or 82599 10 Gigabit Ethernet Controllers might not pass traffic. Attempting to make driver changes in this state may cause system instability.
  • Page 149 Intel X710 based devices may maintain link on any and all ports as long as power is provided to the device, regardless of the device's or system’s power state. Intel X710/XL710 based devices do not support Microsoft Windows Server 2008R2 or Windows Server 2012 as SR-IOV Guest operating systems.

  • Page 150: Regulatory Compliance Statements

    Intel® Ethernet Server Adapter X520-2 Intel® Ethernet SFP+ LR Optics RMN FTLX1471 Intel® Ethernet Converged Network Adapter X520-4 Intel® Ethernet Converged Network Adapter X520-Q1 Intel® 10 Gigabit AF DA Dual Port Server Adapter Intel® 10 Gigabit CX4 Dual Port Server Adapter...

  • Page 151: Safety Compliance

    Intel® 10 Gigabit XF SR Dual Port Server Adapter Intel® 10 Gigabit XF SR Server Adapter Intel® 10 Gigabit XF LR Server Adapter Intel® Ethernet Server Adapter I340-T2 Intel® Ethernet Server Adapter I340-T4 Intel® Ethernet Server Adapter I350-T2 Intel® Ethernet Server Adapter I350-T4 Intel®...

  • Page 152: Regulatory Compliance Markings

    EN 60950-1:2006/A11:2009/A1:2010/A12:2011 (European Union) IEC 60950-1:2005 (2nd Edition); Am 1:2009 (International) EU LVD Directive 2006/95/EC EMC Compliance – The following standards may apply: Class A products: FCC Part 15 – Radiated & Conducted Emissions (USA) CAN ICES-3(A)/NMB-3(A) – Radiated & Conducted Emissions (Canada) CISPR 22 –...

  • Page 153: Vcci Class A Statement

    CAUTION: If the device is changed or modified without permission from Intel, the user may void his or her authority to operate the equipment.

  • Page 154: Fcc Class B User Information

    Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. CAUTION: If the device is changed or modified without permission from Intel, the user may void his or her authority to operate the equipment.

  • Page 155: Electromagnetic Compatibility Notices

    NOTE: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Electromagnetic Compatibility Notices FCC Declaration of Conformity Statement The following products have been tested to Comply with FCC Standards for Home or Office Use.

  • Page 156: Manufacturer Declaration

    EU WEEE Logo Manufacturer Declaration European Community Manufacturer Declaration Intel Corporation declares that the equipment described in this document is in conformance with the requirements of the European Council Directive listed below: Low Voltage Directive 2006/95/EC EMC Directive2004/108/EC RoHS Directive 2011/65/EU...
  • Page 157 WARNING: In a domestic environment, Class A products may cause radio interference, in which case the user may be required to take adequate measures. Responsible Party Intel Corporation, Mailstop JF3-446 5200 N.E. Elam Young Parkway Hillsboro, OR 97124-6497 Phone 1-800-628-8686...

  • Page 158: End-Of-Life / Product Recycling

    China RoHS Declaration Class 1 Laser Products Server adapters listed above may contain laser devices for communication use. These devices are compliant with the requirements for Class 1 Laser Products and are safe in the intended use. In normal operation the output of these laser devices does not exceed the exposure limit of the eye and cannot cause harm.

  • Page 159: Customer Support

    Customer Support Intel support is available on the web or by phone. Support offers the most up-to-date information about Intel products, including installation instructions, troubleshooting tips, and general product information. Web and Internet Sites Support: http://www.intel.com/support Corporate Site for Network Products:...

  • Page 160: Legal Disclaimers

    Software, including but not limited to use with non-Intel component products, is not licensed hereunder. 2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Software.
  • Page 161 Software, including but not limited to use with non-Intel component products, is not licensed hereunder. 2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to you a non-exclusive, non-assignable, copyright license to use the Software.
  • Page 162 Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the Software as Intel may select.

  • Page 163: Limited Lifetime Hardware Warranty

    Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein. Intel, the Intel logo, and Itanium are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other countries.

  • Page 164: Returning A Defective Product

    Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any time within ninety (90) days of purchase, you may return your Intel adapter to the original place of purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively, accepting returns and refunding money back to their customers may return Intel adapters to their original place of purchase.
  • Page 165 Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use of the adapter product in such applications by Licensee or Sublicensees.

This manual is also suitable for:

X520-q1X710-2Xl710-q1X710-4X520-4X550-t2 ... Show all

Table of Contents