- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Fodora 20 system was installed with quad-port XL710 NIC. By default, the NIC driver creates 4 queues per port and both IPv4+UDP/TCP(udp4/tcp4) and IPv6+UDP/TCP(udp6/tcp6) for RSS are enabled. It loads IPv4+UDP/TCP traffic with different IPs to different queues(cores).
But All IPv6+UDP/TCP traffic with different IPs was directed to only one queue(one core). Reconfiguration of rx-flow-hash for udp6 or tcp6 by ethtool did not solve the issue.
The other problem is all IPv4 or IPv6 traffic with different IPs was also directed to only one queue when only IPv4 or IPv6 RSS enabled.
System: Fedora 20
Kernel: 3.19.8-100.fc20.x86_64
NIC: quad-port XL710
Driver: i40e
Version: 1.2.2-k
Firmware-version: f4.1 a1.1 n04.10 e80001109
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Thanks for your post. I'll check on this.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Please update the firmware and driver of the XL710 Card. You may download the firmware and driver below:
1. http://sourceforge.net/projects/e1000/files/i40e%20stable/1.3.39.1/ Intel Ethernet Drivers and Utilities - Browse /i40e stable/1.3.39.1 at SourceForge.net
2. https://downloadcenter.intel.com/download/24769/NVM-Update-Utility-for-Intel-Ethernet-Converged-Network-Adapter-XL710-X710-Series Download NVM Update Utility for Intel® Ethernet Converged Network Adapter XL710 & X710 Series
Try to re-configure your network and in case you still experience the same issue, please provide us your adapter's details - ethtool -i
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
I tried ./nvmupdate64e -l XL710_update.log and ./nvmupdate64e -l XL710_update.log -o XL710.xml -b -c nvmupdate.cfg and It failed to update firmware.The message is shown below:
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.25.20.03
Copyright (C) 2013 - 2015 Intel Corporation.
WARNING: TO AVOID DAMAGE TO YOUR DEVICE, DO NOT EXIT OR REBOOT OR POWER OFF THE SYSTEM DURING THIS UPDATE
Inventory in progress. Please wait [*.........]
Num Description Device-Id B:D Adapter Status
=== ====================================== ========= ===== ====================
01) Intel(R) Ethernet Connection I217-LM 8086-153A 00:25 Not supported
02) Intel(R) Ethernet Converged Network Ad 8086-1572 01:00 Update not available
...
Tool execution completed with the following status: All operations completed successfully
Press any key to exit.
More info of the i40e driver(I upgraded the driver to v1.3.39.1) :
ethtool -i p2p1
driver: i40e
version: 1.3.39.1
firmware-version: 4.10 0x80001109 0.0.0
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
The cfg file has 8086/1572 ID presented. Is update issue related to EEPID?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Nope. EEPID should not be an issue updating the firmware. However, you may try to load the older version (ver 1.0) first then the latest version (ver 1.25). See below:
1. https://downloadcenter.intel.com/download/25222/NVM-Update-Utility-for-Intel-Ethernet-Converged-Network-Adapter-XL710-X710-Series NVMUpdateTool-EFI_ver 1.0
2. https://downloadcenter.intel.com/download/24769/NVM-Update-Utility-for-Intel-Ethernet-Converged-Network-Adapter-XL710-X710-Series NVMUpdateTool-EFI_ver 1.25
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Sandy.
Looks like I have the same problem (firmware upgrade) and running nvmupdate64e of version 1.0 (by the way, nvmupdate64e -v outputs NVMUpdate version 1.24.33.08) gives the same result '01) Intel(R) Ethernet Converged Network Ad 8086-1572 05:00 Update not available'
Appreciate your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Blick,
Thanks for contacting Intel.
Please provide us the results of your ethtool -i so we may further check on your adapter's details. Thanks.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
1). I tried both Linux and EFI updating with NUP tool (nvmupdate64e.efi)1.0 and then 1.25. Both NUP tool 1.0 and 1.25 failed to do the updating. It still showed the message of "Update not available"
Both tools have the same logs:
nvmupdate64e.efi -l mylog3.log
Unsupported device found - DeviceId: 153A
Config file read.
Inventory
Logs on terminal:
...
01) Intel(R) Ethernet Connection I217-LM 8086-153A 00:25 Not supported
02) Intel(R) Ethernet Converged Network Ad 8086-1572 01:00 Update not available
...
2). We tried different versions of drivers for Linux updating using NUP tool 1.0(nvmupdate64e), but all failed.
$ethtool -i p2p1
driver: i40e
version: 1.2.48.2
firmware-version: f4.1.24827 a1.1 n4.10 e1109
bus-info: 0000:01:00.0
...
$ethtool -i p2p1
driver: i40e
version: 1.3.46
firmware-version: 4.10 0x80001109 0.0.0
bus-info: 0000:01:00.0
...
$dmesg
...
[ 1353.630862] i40e 0000:01:00.1 p2p2: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None
[ 1375.192134] Program nvmupdate64e tried to access /dev/mem between bf818000->bf820000.
[ 1375.263965] Program nvmupdate64e tried to access /dev/mem between bf810000->bf818000.
[ 1375.338876] Program nvmupdate64e tried to access /dev/mem between bf808000->bf810000.
[ 1375.408982] Program nvmupdate64e tried to access /dev/mem between bf800000->bf808000.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Thanks for updating us on your test results. We are checking on this.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom and blick,
I would also like to request for the serial numbers of your network cards. You can find it on the white bar code sticker on the card. We will need all the numbers on the sticker. Thanks.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
Here is the picture of the sticker on the quad-port (4x10G) XL710 NIC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Thanks for quick response. I'm afraid your network card is not an Intel Retail Card. This could be the reason why it doesn't work with our firmware.
Network Card Details:
Your Card's Part No. H39664-002
Part no. of Intel Retail Card: H58361-xyz
Intel® Ethernet Converged Network Adapter X710DA4
Reference Website:
Retail Intel® Ethernet Adapter PCI Device ID and Part Number List
http://www.intel.com/support/network/sb/CS-012904.htm http://www.intel.com/support/network/sb/CS-012904.htm
For further support and troubleshooting, we suggest to contact your system manufacturer.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Blick,
You may also check the part number of your network card to see whether it is an Intel Retail card or an OEM card. Please refer to my reply to lscom.
Happy Halloween everyone!
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
I replaced the NIC with Intel retailed one and updated it with FW v4.53.
The IPv6+UDP/TCP is working. But both IPv4 and IPv6 only are still not working. only "sd" is turned on for udp4, tcp4, udp6 and tcp6 when changing rx-flow-hash by ethtool. Upon these setttings, all traffic with different IPs will be steered to one queue only.
$ ethtool -i p2p1
driver: i40e
version: 1.3.46
firmware-version: 4.53 0x80001da6 0.0.0
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
$ethtool -n p2p1 rx-flow-hash udp4
UDP over IPV4 flows use these fields for computing Hash flow key:
IP SA
IP DA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi lscom,
Thank you for the update. we will check on this.
rdgs,
wb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear lscom,
Good day. I apologize for not getting back to you sooner.
I would like to clarify what "sd" means on the statement below.
lscom wrote:
But both IPv4 and IPv6 only are still not working. only "sd" is turned on for udp4, tcp4, udp6 and tcp6 when changing rx-flow-hash by ethtool.
Hope to hear from you again.
Sincerely,
Sandy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sandy,
"sd" means IP Source address and IP destination address.
The option of "sd" for rx-flow-hash will enable NIC to only use IP source and destination addresses to compute RSS flow Hash. However the NIC will not compute RSS Hash value with different IP addresses in this scenario. In order to get RSS Hash computed, I have to add UDP/TCP ports as part of Hash keys.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi Iscom, there's new release of driver available in this site, you may want to try it out.
https://sourceforge.net/projects/e1000/files/i40e%20stable/ https://sourceforge.net/projects/e1000/files/i40e%20stable/
regards,
vince
![](/skins/images/7FC17B7B85029576C25F1E43CE255B51/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page