- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can't find any documents about how to use N3000 as a plain NIC to send/receive packet. Can anyone help me? Thanks.
When I run './nvmupdate64e ', it outputs this message, how could I resolve the problem 'Device not found'?
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.33.15.1
Copyright (C) 2013 - 2019 Intel Corporation.
WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.
Inventory in progress. Please wait [|.........]
Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Controller 7.00(7.00) 0D58 00:007 Update not
XXV710 Intel(R) FPGA Programmable available
Acceleration Card N3000 for
Networking
02) Intel(R) Ethernet Controller 7.00(7.00) 0D58 00:009 Update not
XXV710 Intel(R) FPGA Programmable available
Acceleration Card N3000 for
Networking
03) Intel(R) Ethernet 10G 2P X540-t 4.04(4.04) 1528 00:067 Update not
Adapter available
Tool execution completed with the following status: Device not found.
Press any key to exit.
Here is the output when I run 'ls -la /sys/class/net'. I can't see the XL710 device (enp61s0f0)
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth0 -> ../../devices/pci0000:00/0000:00:01.1/0000:01:00.0/net/eth0
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth1 -> ../../devices/pci0000:00/0000:00:01.1/0000:01:00.1/net/eth1
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth10 -> ../../devices/pci0000:40/0000:40:03.2/0000:44:00.0/net/eth10
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth11 -> ../../devices/pci0000:40/0000:40:03.2/0000:44:00.0/net/eth11
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth2 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:08.0/0000:07:00.0/net/eth2
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth3 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:08.0/0000:07:00.1/net/eth3
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth4 -> ../../devices/pci0000:00/0000:00:01.0/0000:02:00.0/net/eth4
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth5 -> ../../devices/pci0000:40/0000:40:03.0/0000:43:00.0/net/eth5
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth6 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:10.0/0000:09:00.0/net/eth6
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth7 -> ../../devices/pci0000:00/0000:00:01.0/0000:02:00.1/net/eth7
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth8 -> ../../devices/pci0000:40/0000:40:03.0/0000:43:00.1/net/eth8
lrwxrwxrwx 1 root root 0 Oct 5 14:58 eth9 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:10.0/0000:09:00.1/net/eth9
lrwxrwxrwx 1 root root 0 Oct 5 14:58 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l0 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l0
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l1 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l1
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l2 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l2
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l3 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l3
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l4 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l4
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l5 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l5
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l6 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l6
lrwxrwxrwx 1 root root 0 Oct 5 14:58 npacf0g0l7 -> ../../devices/pci0000:00/0000:00:03.0/0000:05:00.0/0000:06:09.0/0000:08:00.0/fpga/intel-fpga-dev.0/intel-fpga-fme.0/pac_n3000_net.2.auto/net/npacf0g0l7
Here are some other info which might be helpful.
sudo fpgainfo fme
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** FME ******//
Object Id : 0xF100000
PCIe s:b:d.f : 0000:08:00.0
Device Id : 0x0b30
Numa Node : 0
Ports Num : 01
Bitstream Id : 0x23000010000000
Bitstream Version : 0.2.3
Pr Interface Id : 901dd697-ca79-4b05-b843-8138cefa2846
Boot Page : user
sudo fpgainfo bmc
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** BMC SENSORS ******//
Object Id : 0xF100000
PCIe s:b:d.f : 0000:08:00.0
Device Id : 0x0b30
Numa Node : 0
Ports Num : 01
Bitstream Id : 0x23000010000000
Bitstream Version : 0.2.3
Pr Interface Id : 901dd697-ca79-4b05-b843-8138cefa2846
( 1) Board Power : 45.12 Watts
( 2) 12V Backplane Current : 2.07 Amps
( 3) 12V Backplane Voltage : 11.95 Volts
( 4) 1.2V Voltage : 1.20 Volts
( 6) 1.8V Voltage : 1.82 Volts
(
sudo fpgainfo phy
Board Management Controller, MAX10 NIOS FW version D.2.1.24
Board Management Controller, MAX10 Build version D.2.0.7
//****** PHY ******//
Object Id : 0xF100000
PCIe s:b:d.f : 0000:08:00.0
Device Id : 0x0b30
Numa Node : 0
Ports Num : 01
Bitstream Id : 0x23000010000000
Bitstream Version : 0.2.3
Pr Interface Id : 901dd697-ca79-4b05-b843-8138cefa2846
//****** PHY GROUP 0 ******//
Direction : Line side
Speed : 10 Gbps
Number of PHYs : 8
//****** PHY GROUP 1 ******//
Direction : Host side
Speed : 10 Gbps
Number of PHYs : 8
//****** Intel C827 Retimer ******//
Port0 10G : Down
Port1 10G : Down
Port2 10G : Down
Port3 10G : Down
Port4 10G : Down
Port5 10G : Down
Port6 10G : Down
Port7 10G : Down
Retimer A Version : 101c.1064
Retimer B Version : 101c.1064
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
For the Plain NIC to sent/receive packet, you may refer the document below
- https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-ias-n3000.pdf
- Page 53/92. Session 9.2 Test Using Packet Generator, Figure 21. Do shows some setup for the packet send and receive. Please let me know if anything is not clear on that
For the device not found problem
- Do appreciate if you can provide me below info.
to check your driver version.- Run command $ lspci | grep -i acc
- Run Command $ modinfo i40e
- Run Command $ modinfo iavf
- what server are you using ?
- For the network i40 Linux driver, version 2.13.10 Linux driver is no longer supported.
- IF, you are not using the latest driver.
I do advise you to try to update your existing into 2.14.13 version of the i40e driver - If you are unclear about the step to update, you may refer to session 6.2 following instructions below
Let me know if this helps.
Regards,
WeiChuan_C_Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the reply.
I am using N3000-2.
The server is 'Dell PowerEdge R720 server, 2x Intel Xeon E5-2680 @ 2.8GHz'.
Here is the output and I think I already use the latest version for driver.
I guess the eth2, eth3, eth6, eth9 are the XL710 interfaces. But I don't know why they don't show as something like enp136s0f0.
# modinfo iavf
filename: /lib/modules/4.19.106-rt45/updates/drivers/net/ethernet/intel/iavf/iavf.ko
version: 4.2.7
license: GPL
description: Intel(R) Ethernet Adaptive Virtual Function Driver
author: Intel Corporation, <linux.nics@intel.com>
alias: i40evf
srcversion: 4C49C36C0BBB502CAD9AE77
alias: pci:v00008086d00001889sv*sd*bc*sc*i*
alias: pci:v00008086d000037CDsv*sd*bc*sc*i*
alias: pci:v00008086d00001571sv*sd*bc*sc*i*
alias: pci:v00008086d0000154Csv*sd*bc*sc*i*
depends:
retpoline: Y
name: iavf
vermagic: 4.19.106-rt45 SMP mod_unload
# modinfo i40e
filename: /lib/modules/4.19.106-rt45/updates/drivers/net/ethernet/intel/i40e/i40e.ko
version: 2.16.11
license: GPL
description: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver
author: Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion: 9F2F404BC11E97DE3056D7C
alias: pci:v00008086d0000158Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000158Asv*sd*bc*sc*i*
alias: pci:v00008086d000037D3sv*sd*bc*sc*i*
alias: pci:v00008086d000037D2sv*sd*bc*sc*i*
alias: pci:v00008086d000037D1sv*sd*bc*sc*i*
alias: pci:v00008086d000037D0sv*sd*bc*sc*i*
alias: pci:v00008086d000037CFsv*sd*bc*sc*i*
alias: pci:v00008086d000037CEsv*sd*bc*sc*i*
alias: pci:v00008086d00000D58sv*sd*bc*sc*i*
alias: pci:v00008086d00000CF8sv*sd*bc*sc*i*
alias: pci:v00008086d00001588sv*sd*bc*sc*i*
alias: pci:v00008086d00001587sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000104Esv*sd*bc*sc*i*
alias: pci:v00008086d000015FFsv*sd*bc*sc*i*
alias: pci:v00008086d00001589sv*sd*bc*sc*i*
alias: pci:v00008086d00001586sv*sd*bc*sc*i*
alias: pci:v00008086d0000101Fsv*sd*bc*sc*i*
alias: pci:v00008086d00001585sv*sd*bc*sc*i*
alias: pci:v00008086d00001584sv*sd*bc*sc*i*
alias: pci:v00008086d00001583sv*sd*bc*sc*i*
alias: pci:v00008086d00001581sv*sd*bc*sc*i*
alias: pci:v00008086d00001580sv*sd*bc*sc*i*
alias: pci:v00008086d00001574sv*sd*bc*sc*i*
alias: pci:v00008086d00001572sv*sd*bc*sc*i*
depends:
retpoline: Y
name: i40e
vermagic: 4.19.106-rt45 SMP mod_unload
parm: debug:Debug level (0=none,...,16=all) (int)
parm: l4mode:L4 cloud filter mode: 0=UDP,1=TCP,2=Both,-1=Disabled(default) (int)
# lspci | grep -i acc
08:00.0 Processing accelerators: Intel Corporation Device 0b30
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I follow the instructions to update XL710 drivers, it shows 'Update not available' and 'Devices not found'. I paste the output at the beginning of the question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Max,
Thanks for the information. Most of your drivers seem to be in the latest version.
From Hardware sides
- Based on the information available in the readme notes for the Intel® Ethernet X722 drivers,
- the devices are based on the Intel Ethernet X710, XL710, X722,
- and XXV710 controllers may fail to load with a yellow bang error.
- This may be because the device is connected to a switch that is not advertising traffic class 0.
- Maybe you can try to disconnect the device from the switch or configure the switch to advertise TC0,
and restart your system.
If the hardware confirm no issue, you may try step below
- Appreciate if you get me the logs following, so that we can narrow down the issue
- https://cdrdv2.intel.com/v1/dl/getContent/332161?wapkw=Intel%C2%AE%20Ethernet%20NVM%20Update%20Tool:%20%22Quick%22%20Usage%20Guide%20for%20Linux
- Section 6.1 Troubleshooting Using Debug Logs
Please let me know if you need any further clarification,
looking forward to hear back from you
Regards,
WeiChuan_C_Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Max,
Any update for the Debug logs ?
Let me know if you have any questions.
Looking forward to hear back from you.
Regards,
WeiChuan_C_Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Max
There is no reply from you.
I am setting this case to closed-pending,
This loop will be close after 5 days if still no reply
Hoping to hear back from you.
Regards,
WeiChuan_C_Intel
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page