Users Guide
Table Of Contents
- Intel® Ethernet Adapters and Devices User Guide
- Overview
- Installation
- Device Features
- Adaptive Inter-Frame Spacing
- Data Center Bridging (DCB)
- Direct Memory Access (DMA) Coalescing
- Dynamic Device Personalization (DDP)
- Firmware Link Layer Discovery Protocol (FW-LLDP)
- Forward Error Correction (FEC) Mode
- Flow Control
- Gigabit Master Slave Mode
- Interrupt Moderation Rate
- IPv4 Checksum Offload
- Jumbo Frames
- Large Send Offload (IPv4 and IPv6)
- Link State on Interface Down
- Locally Administered Address
- Log Link State Event
- Low Latency Interrupts
- Malicious Driver Detection (MDD) for VFs
- Max Number of RSS Queues Per Vport
- Network Virtualization using Generic Routing Encapsulation (NVGRE)
- NIC Partitioning
- Performance Options
- Power Options
- Priority & VLAN Tagging
- PTP Hardware Timestamp
- Quality of Service
- Remote Direct Memory Access (RDMA)
- RDMA on Linux
- RDMA for Microsoft Windows Network Direct (ND) User-Mode Applications
- RDMA Network Direct Kernel (NDK)
- RDMA Routing Across IP Subnets
- Enabling Priority Flow Control (PFC) on a Microsoft Windows Server Operating ...
- Verifying RDMA operation with Microsoft PowerShell
- RDMA for Virtualized Environments
- RDMA for NDK Features such as SMB Direct (Server Message Block)
- Accessing Remote NVM Express* drives using RDMA
- Receive Buffers
- Receive Side Scaling
- Setting Speed and Duplex
- Software Timestamp
- SR-IOV (Single Root I/O Virtualization)
- TCP Checksum Offload (IPv4 and IPv6)
- TCP/IP Offloading Options
- Thermal Monitoring
- Transmit Buffers
- UDP Checksum Offload (IPv4 and IPv6)
- UDP Segmentation Offload (IPv4 and IPv6)
- Wait for Link
- Microsoft* Windows* Driver and Software Installation and Configuration
- Linux* Driver Installation and Configuration
- Overview
- Supported Adapters
- Supported Linux Versions
- NIC Partitioning
- igb Linux* Driver for the Intel® Gigabit Adapters
- ixgbe Linux* Driver for the Intel® 10 Gigabit Server Adapters
- ixgbevf Linux* Driver for the Intel® 10 Gigabit Server Adapters
- i40e Linux Driver for the Intel Ethernet Controller 700 Series
- ice Linux Driver for the Intel Ethernet Controller 800 Series
- iavf Linux Driver
- VMWare ESX Drivers and Support
- Remote Boot
- Firmware
- Troubleshooting
- Transitioning from i40evf to iavf
- Known Issues
- Regulatory Compliance Statements
- FCC Class A Products
- FCC Class B Products
- Safety Compliance
- EMC Compliance
- Hazardous Substances Compliance
- Regulatory Compliance Markings
- FCC Class A User Information
- FCC Class B User Information
- EU WEEE Logo
- Manufacturer Declaration European Community
- China RoHS Declaration
- Class 1 Laser Products
- End-of-Life / Product Recycling
- Customer Support
- Adapter Specifications
- Intel® 40 Gigabit Network Adapter Specifications
- Intel® 40GbE Network Daughter Cards (NDC) Specifications
- Intel® 25 Gigabit Network Adapter Specifications
- Intel® 25 Gigabit Network Mezzanine Card Specifications
- Intel® 10 Gigabit Network Adapter Specifications
- Intel® 10 Gigabit Network Mezzanine Card Specifications
- Intel® 10GbE Network Daughter Cards (NDC) Specifications
- Intel® Gigabit Network Adapter Specifications
- Intel® Gigabit Network Mezzanine Card Specifications
- Intel® Gigabit Network Daughter Cards Specifications
- Standards
- X-UEFI Attributes
- Legal Disclaimers
Remote Boot
170
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 <IP Address>;" in dhcpd.conf to
show the correct DHCP server IP address.
Microsoft Windows iSCSI Boot Issues
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 con-
tinuously reboot the system.
To work around this limitation follow these steps:
1. Using Registry Editor, expand the following registry key:
\System\CurrentControlSet\Services\Tcpip\Parameters
2. Create a DWORD value called DisableDHCPMediaSense and set the value to 0.
Support for Platforms Booted by UEFI iSCSI Native Initiator
Starting with version 2.2.0.0, the iSCSI crash dump driver gained the ability to support platforms booted using the native
UEFI iSCSI initiator over supported Intel Network Adapters. This support is available on Microsoft Windows Server operating
systems.
Since network adapters on UEFI platforms may not provide legacy iSCSI option ROM, the boot options tab in DMIX may not
provide the setting to enable the iSCSI crash dump driver. If this is the case, the following registry entry has to be created:
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-
08002BE10318}\<InstanceID>\Parameters
DumpMiniport REG_SZ iscsdump.sys
Moving iSCSI adapter to a different slot:
In a Windows* installation, if you move the iSCSI adapter to a PCI slot other than the one that it occupied when the drivers
and MS iSCSI Remote Boot Initiator were installed, then a System Error may occur during the middle of the Windows Splash
Screen. This issue goes away if you return the adapter to its original PCI slot. We recommend not moving the adapter used
for iSCSI boot installation. This is a known OS issue.
If you have to move the adapter to another slot, then perform the following:
1. Boot the operating system and remove the old adapter
2. Install a new adapter into another slot
3. Setup the new adapter for iSCSI Boot
4. Perform iSCSI boot to the OS via the original adapter
5. Make the new adapter iSCSI-bootable to the OS
6. Reboot
7. Move the old adapter into another slot
8. Repeat steps 2 - 5 for the old adapter you have just moved
Uninstalling Driver can cause blue screen
If the driver for the device in use for iSCSI Boot is uninstalled via Device Manager, Windows will blue screen on reboot and
the OS will have to be re-installed. This is a known Windows issue.
Adapters flashed with iSCSI image are not removed from the Device Manager during uninstall
During uninstallation all other Intel Network Connection Software is removed, but drivers for iSCSI Boot adapters that have
boot priority.