- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
There are a permanent problem with XL710/X710 cards
Latest firmware and driver. Only 6Mbps of out traffic. What to do?
# ./nvmupdate64e
Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.39.20.2
Copyright(C) 2013 - 2022 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 Converged 9.16(9.10) 1584 00:059 Up to date
Network Adapter XL710-Q1
02) Intel(R) Ethernet 10G 2P X520 64.33(40.21 154D 00:216 Update not
Adapter available
# ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: Not reported
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 40000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000000f (15)
drv probe link timer
Link detected: yes
# ethtool -i eth0
driver: i40e
version: 2.22.8
firmware-version: 9.10 0x8000cffe 1.3179.0
expansion-rom-version:
bus-info: 0000:3b:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
# ethtool -m eth0
Identifier : 0x0d (QSFP+)
Extended identifier : 0x10
Extended identifier description : 1.5W max. Power consumption
Extended identifier description : No CDR in TX, No CDR in RX
Extended identifier description : High Power Class (> 3.5 W) not enabled
Connector : 0x23 (No separable connector)
Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Encoding : 0x05 (64B/66B)
BR, Nominal : 10300Mbps
Rate identifier : 0x00
Length (SMF,km) : 0km
Length (OM3 50um) : 0m
Length (OM2 50um) : 0m
Length (OM1 62.5um) : 0m
Length (Copper or Active cable) : 3m
Transmitter technology : 0x00 (850 nm VCSEL)
Laser wavelength : 0.000nm
Laser wavelength tolerance : 0.000nm
Vendor name : CISCO-FINISAR
Vendor OUI : 00:90:65
Vendor PN : FCBN410QE2C03-C2
Vendor rev : A
Vendor SN : FIW231301GE-B
Date code : 190326
Revision Compliance : Revision not specified
Module temperature : 0.00 degrees C / 32.00 degrees F
Module voltage : 0.0000 V
Feb 17 13:35:22 152224 kernel: [ 69.611804] ixgbe 0000:d8:00.0 0000:d8:00.0 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
Feb 17 13:35:22 152224 kernel: [ 69.611806] ixgbe 0000:d8:00.0 0000:d8:00.0 (uninitialized): allow_unsupported_sfp Enabled
Feb 17 13:35:22 152224 kernel: [ 69.612058] i40e 0000:3b:00.0: fw 9.110.72185 api 1.15 nvm 9.10 0x8000cffe 1.3179.0
Feb 17 13:35:22 152224 kernel: [ 69.706791] Adding 4907004k swap on /dev/md1. Priority:-2 extents:1 across:4907004k SSFS
Feb 17 13:35:22 152224 kernel: [ 69.783438] i40e 0000:3b:00.0: MAC address: 3c:fd:fe:c1:14:98
Feb 17 13:35:22 152224 kernel: [ 69.786689] i40e 0000:3b:00.0: FW LLDP is enabled
Feb 17 13:35:22 152224 kernel: [ 69.790283] i40e 0000:3b:00.0: couldn't add VEB, err I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_ENXIO
Feb 17 13:35:22 152224 kernel: [ 69.790285] i40e 0000:3b:00.0: couldn't add VEB
Feb 17 13:35:22 152224 kernel: [ 69.790285] i40e 0000:3b:00.0: Couldn't create FDir VSI
Feb 17 13:35:22 152224 kernel: [ 69.797404] ipmi_si IPI0001:00: The BMC does not support clearing the recv irq bit, compensating, but the BMC needs to be fixed.
Feb 17 13:35:22 152224 kernel: [ 69.817429] i40e 0000:3b:00.0 eth0: NIC Link is Up, 40 Gbps Full Duplex, Flow Control: None
Feb 17 13:35:22 152224 kernel: [ 69.822673] [drm] P2A bridge disabled, using default configuration
Feb 17 13:35:22 152224 kernel: [ 69.822674] [drm] AST 2500 detected
Feb 17 13:35:22 152224 kernel: [ 69.822680] [drm] Analog VGA only
Feb 17 13:35:22 152224 kernel: [ 69.822687] [drm] dram MCLK=800 Mhz type=1 bus_width=16 size=01000000
Feb 17 13:35:22 152224 kernel: [ 69.822825] i40e 0000:3b:00.0: PCI-Express: Speed 8.0GT/s Width x8
Feb 17 13:35:22 152224 kernel: [ 69.831222] [TTM] Zone kernel: Available graphics memory: 131897378 kiB
Feb 17 13:35:22 152224 kernel: [ 69.831222] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
Feb 17 13:35:22 152224 kernel: [ 69.831223] [TTM] Initializing pool allocator
Feb 17 13:35:22 152224 kernel: [ 69.831226] [TTM] Initializing DMA pool allocator
Feb 17 13:35:22 152224 kernel: [ 69.844372] fbcon: astdrmfb (fb0) is primary device
Feb 17 13:35:22 152224 kernel: [ 69.860283] cryptd: max_cpu_qlen set to 1000
Feb 17 13:35:22 152224 kernel: [ 69.866540] ipmi_si IPI0001:00: Found new BMC (man_id: 0x002a7c, prod_id: 0x091c, dev_id: 0x20)
Feb 17 13:35:22 152224 kernel: [ 69.868842] AVX2 version of gcm_enc/dec engaged.
Feb 17 13:35:22 152224 kernel: [ 69.868842] AES CTR mode by8 optimization enabled
Feb 17 13:35:22 152224 kernel: [ 69.870208] Console: switching to colour frame buffer device 128x48
Feb 17 13:35:22 152224 kernel: [ 69.875295] i40e 0000:3b:00.0: Features: PF-id[0] VFs: 128 VSIs: 130 QP: 32 RSS FD_ATR CloudF DCB VxLAN Geneve NVGRE PTP VEPA
Feb 17 13:35:22 152224 kernel: [ 69.884436] ast 0000:03:00.0: fb0: astdrmfb frame buffer device
Feb 17 13:35:22 152224 kernel: [ 69.896142] alg: No test for pcbc(aes) (pcbc-aes-aesni)
Feb 17 13:35:22 152224 kernel: [ 69.921397] [drm] Initialized ast 0.1.0 20120228 for 0000:03:00.0 on minor 0
Feb 17 13:35:22 152224 kernel: [ 69.980158] EXT4-fs (md2): Ignoring removed nobh option
Feb 17 13:35:22 152224 kernel: [ 70.035135] EXT4-fs (md2): barriers disabled
Feb 17 13:35:22 152224 kernel: [ 70.069310] ipmi_si IPI0001:00: IPMI kcs interface initialized
Feb 17 13:35:22 152224 kernel: [ 70.071844] IPMI SSIF Interface driver
Feb 17 13:35:22 152224 kernel: [ 70.229650] EXT4-fs (md2): mounted filesystem with writeback data mode. Opts: journal_checksum,journal_async_commit,discard,barrier=0,data=writeback,nobh
Feb 17 13:35:22 152224 kernel: [ 70.279474] audit: type=1400 audit(1676630122.020:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1142 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.279480] audit: type=1400 audit(1676630122.020:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1142 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.280268] audit: type=1400 audit(1676630122.020:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=1143 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.280273] audit: type=1400 audit(1676630122.020:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=1143 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.280276] audit: type=1400 audit(1676630122.020:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=1143 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.281513] audit: type=1400 audit(1676630122.024:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=1141 comm="apparmor_parser"
Feb 17 13:35:22 152224 kernel: [ 70.295073] Process accounting resumed
Feb 17 13:35:22 152224 kernel: [ 70.356942] EDAC MC0: Giving out device to module skx_edac controller Skylake Socket#0 IMC#0: DEV 0000:3a:0a.0 (INTERRUPT)
Feb 17 13:35:22 152224 kernel: [ 70.357013] EDAC MC1: Giving out device to module skx_edac controller Skylake Socket#0 IMC#1: DEV 0000:3a:0c.0 (INTERRUPT)
Feb 17 13:35:22 152224 kernel: [ 70.357118] EDAC MC2: Giving out device to module skx_edac controller Skylake Socket#1 IMC#0: DEV 0000:ae:0a.0 (INTERRUPT)
Feb 17 13:35:22 152224 kernel: [ 70.357183] EDAC MC3: Giving out device to module skx_edac controller Skylake Socket#1 IMC#1: DEV 0000:ae:0c.0 (INTERRUPT)
Feb 17 13:35:22 152224 kernel: [ 70.532250] intel_rapl: Found RAPL domain package
Feb 17 13:35:22 152224 kernel: [ 70.532261] intel_rapl: Found RAPL domain dram
Feb 17 13:35:22 152224 kernel: [ 70.532264] intel_rapl: DRAM domain energy unit 15300pj
Feb 17 13:35:22 152224 kernel: [ 70.536520] intel_rapl: Found RAPL domain package
Feb 17 13:35:22 152224 kernel: [ 70.536531] intel_rapl: Found RAPL domain dram
Feb 17 13:35:22 152224 kernel: [ 70.536534] intel_rapl: DRAM domain energy unit 15300pj
Feb 17 13:35:22 152224 kernel: [ 70.541547] power_meter ACPI000D:00: Found ACPI power meter.
Feb 17 13:35:22 152224 kernel: [ 70.541587] power_meter ACPI000D:00: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
Feb 17 13:35:22 152224 kernel: [ 70.934610] ixgbe 0000:d8:00.0: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
Feb 17 13:35:22 152224 kernel: [ 70.936372] ixgbe 0000:d8:00.0: 32.000 Gb/s available PCIe bandwidth (5 GT/s x8 link)
Feb 17 13:35:22 152224 kernel: [ 70.936699] ixgbe 0000:d8:00.0 eth1: MAC: 2, PHY: 1, PBA No: G28774-000
Feb 17 13:35:22 152224 kernel: [ 70.936701] ixgbe 0000:d8:00.0: a0:36:9f:13:f4:2c
Feb 17 13:35:22 152224 kernel: [ 70.936702] ixgbe 0000:d8:00.0 eth1: Enabled Features: RxQ: 32 TxQ: 32 FdirHash
Feb 17 13:35:22 152224 kernel: [ 70.938809] ixgbe 0000:d8:00.0 eth1: Intel(R) 10 Gigabit Network Connection
Feb 17 13:35:22 152224 kernel: [ 70.939189] ixgbe 0000:d8:00.1 0000:d8:00.1 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
Feb 17 13:35:23 152224 kernel: [ 71.447574] power_meter ACPI000D:00: Found ACPI power meter.
Feb 17 13:35:23 152224 kernel: [ 71.447620] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Feb 17 13:35:23 152224 kernel: [ 72.247057] ixgbe 0000:d8:00.1: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
Feb 17 13:35:23 152224 kernel: [ 72.248740] ixgbe 0000:d8:00.1: 32.000 Gb/s available PCIe bandwidth (5 GT/s x8 link)
Feb 17 13:35:23 152224 kernel: [ 72.249066] ixgbe 0000:d8:00.1 eth2: MAC: 2, PHY: 1, PBA No: G28774-000
Feb 17 13:35:23 152224 kernel: [ 72.249068] ixgbe 0000:d8:00.1: a0:36:9f:13:f4:2e
Feb 17 13:35:23 152224 kernel: [ 72.249069] ixgbe 0000:d8:00.1 eth2: Enabled Features: RxQ: 32 TxQ: 32 FdirHash
Feb 17 13:35:23 152224 kernel: [ 72.251115] ixgbe 0000:d8:00.1 eth2: Intel(R) 10 Gigabit Network Connection
Feb 17 13:35:24 152224 kernel: [ 72.274629] ixgbe 0000:d8:00.0 rename3: renamed from eth1
Feb 17 13:35:24 152224 kernel: [ 72.303085] ixgbe 0000:d8:00.1 eth3: renamed from eth2
Feb 17 13:35:24 152224 kernel: [ 72.347677] ixgbe 0000:d8:00.0 eth2: renamed from rename3
Feb 17 13:35:25 152224 kernel: [ 74.003025] 8021q: 802.1Q VLAN Support v1.8
Feb 17 13:35:25 152224 kernel: [ 74.003033] 8021q: adding VLAN 0 to HW filter on device eth0
Feb 17 13:35:25 152224 kernel: [ 74.003400] i40e 0000:3b:00.0: PTP external clock not supported.
Feb 17 13:35:31 152224 kernel: [ 79.825446] ------------[ cut here ]------------
Feb 17 13:35:31 152224 kernel: [ 79.825462] NETDEV WATCHDOG: eth0 (i40e): transmit queue 0 timed out
Feb 17 13:35:31 152224 kernel: [ 79.825492] WARNING: CPU: 19 PID: 0 at /build/linux-4.19-7d6em1/linux-4.19-4.19.232/net/sched/sch_generic.c:466 dev_watchdog+0x20e/0x220
Feb 17 13:35:31 152224 kernel: [ 79.825493] Modules linked in: 8021q garp stp mrp llc intel_rapl skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ast ttm intel_uncore iTCO_wdt iTCO_vendor_support drm_kms_helper raid0 ixgbe(O) intel_rapl_perf i40e(O) pcspkr mei_me joydev drm lpc_ich ioatdma pcc_cpufreq intel_auxiliary(O) sg i2c_algo_bit mei i2c_i801 evdev mfd_core dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad button tcp_bbr sch_fq ip_tables x_tables hid_generic usbhid hid ext4 crc16 mbcache jbd2 crc32c_generic fscrypto raid1 md_mod sd_mod crc32c_intel ahci nvme xhci_pci libahci nvme_core xhci_hcd libata usbcore scsi_mod usb_common bonding autofs4
Feb 17 13:35:31 152224 kernel: [ 79.825560] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G O 4.19.0-0.bpo.19-amd64 #1 Debian 4.19.232-1~deb9u1
Feb 17 13:35:31 152224 kernel: [ 79.825562] Hardware name: Supermicro SYS-229U-TN24R4T-2-IN001/X11DPU, BIOS 3.8a 10/28/2022
Feb 17 13:35:31 152224 kernel: [ 79.825575] RIP: 0010:dev_watchdog+0x20e/0x220
Feb 17 13:35:31 152224 kernel: [ 79.825581] Code: 00 49 63 4e e0 eb 92 4c 89 e7 c6 05 1d ff ac 00 01 e8 46 a4 fc ff 89 d9 48 89 c2 4c 89 e6 48 c7 c7 70 5e 4d a7 e8 e2 22 a5 ff <0f> 0b eb c0 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
Feb 17 13:35:31 152224 kernel: [ 79.825583] RSP: 0018:ffff9b19ff8c3e88 EFLAGS: 00010286
Feb 17 13:35:31 152224 kernel: [ 79.825585] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Feb 17 13:35:31 152224 kernel: [ 79.825587] RDX: 0000000000040400 RSI: 00000000000000f6 RDI: 0000000000000300
Feb 17 13:35:31 152224 kernel: [ 79.825588] RBP: ffff9af9f3a6745c R08: 0000000000000048 R09: ffff9b1a7ff9ebc0
Feb 17 13:35:31 152224 kernel: [ 79.825590] R10: ffff9b19ff8df830 R11: 0000000000000000 R12: ffff9af9f3a67000
Feb 17 13:35:31 152224 kernel: [ 79.825595] R13: 0000000000000013 R14: ffff9af9f3a67480 R15: 0000000000000020
Feb 17 13:35:31 152224 kernel: [ 79.825599] FS: 0000000000000000(0000) GS:ffff9b19ff8c0000(0000) knlGS:0000000000000000
Feb 17 13:35:31 152224 kernel: [ 79.825604] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 17 13:35:31 152224 kernel: [ 79.825608] CR2: 0000560dd864fe78 CR3: 000000291740a006 CR4: 00000000007606e0
Feb 17 13:35:31 152224 kernel: [ 79.825613] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 17 13:35:31 152224 kernel: [ 79.825617] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Feb 17 13:35:31 152224 kernel: [ 79.825618] PKRU: 55555554
Feb 17 13:35:31 152224 kernel: [ 79.825618] Call Trace:
Feb 17 13:35:31 152224 kernel: [ 79.825622] <IRQ>
Feb 17 13:35:31 152224 kernel: [ 79.825628] ? pfifo_fast_reset+0x100/0x100
Feb 17 13:35:31 152224 kernel: [ 79.825635] call_timer_fn+0x2b/0x130
Feb 17 13:35:31 152224 kernel: [ 79.825640] run_timer_softirq+0x1cf/0x400
Feb 17 13:35:31 152224 kernel: [ 79.825645] ? tick_sched_handle+0x22/0x60
Feb 17 13:35:31 152224 kernel: [ 79.825648] ? tick_sched_timer+0x37/0x70
Feb 17 13:35:31 152224 kernel: [ 79.825653] __do_softirq+0x10d/0x2c3
Feb 17 13:35:31 152224 kernel: [ 79.825659] irq_exit+0xc2/0xd0
Feb 17 13:35:31 152224 kernel: [ 79.825663] smp_apic_timer_interrupt+0x74/0x130
Feb 17 13:35:31 152224 kernel: [ 79.825666] apic_timer_interrupt+0xf/0x20
Feb 17 13:35:31 152224 kernel: [ 79.825668] </IRQ>
Feb 17 13:35:31 152224 kernel: [ 79.825674] RIP: 0010:cpuidle_enter_state+0xb2/0x330
Feb 17 13:35:31 152224 kernel: [ 79.825680] Code: f4 40 46 59 e8 6f 09 b0 ff 49 89 c7 0f 1f 44 00 00 31 ff e8 70 14 b0 ff 80 7c 24 17 00 0f 85 1c 02 00 00 fb 66 0f 1f 44 00 00 <4c> 2b 7c 24 08 48 ba cf f7 53 e3 a5 9b c4 20 4c 89 f8 49 c1 ff 3f
Feb 17 13:35:31 152224 kernel: [ 79.825684] RSP: 0018:ffffb1484c91fe70 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
Feb 17 13:35:31 152224 kernel: [ 79.825691] RAX: ffff9b19ff8e7140 RBX: ffff9b19ff8ef880 RCX: 000000000000001f
Feb 17 13:35:31 152224 kernel: [ 79.825695] RDX: 0000001295f764eb RSI: 00000000294a5374 RDI: 0000000000000000
Feb 17 13:35:31 152224 kernel: [ 79.825699] RBP: ffffffffa76b6f60 R08: 0000000000000002 R09: 0000000000026a00
Feb 17 13:35:31 152224 kernel: [ 79.825704] R10: 00000000ffffffff R11: 0000000000000f40 R12: ffff9b19f8cc1600
Feb 17 13:35:31 152224 kernel: [ 79.825708] R13: 0000000000000003 R14: 0000000000000003 R15: 0000001295f764eb
Feb 17 13:35:31 152224 kernel: [ 79.825716] do_idle+0x1f6/0x270
Feb 17 13:35:31 152224 kernel: [ 79.825722] cpu_startup_entry+0x6f/0x80
Feb 17 13:35:31 152224 kernel: [ 79.825729] start_secondary+0x1a4/0x200
Feb 17 13:35:31 152224 kernel: [ 79.825735] secondary_startup_64+0xa4/0xb0
Feb 17 13:35:31 152224 kernel: [ 79.825738] ---[ end trace 38b909abebbe1af6 ]---
Feb 17 13:35:31 152224 kernel: [ 79.825750] i40e 0000:3b:00.0 eth0: tx_timeout: VSI_seid: 387, Q 0, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
Feb 17 13:35:31 152224 kernel: [ 79.825754] i40e 0000:3b:00.0 eth0: tx_timeout recovery level 1, hung_queue 0
Feb 17 13:35:31 152224 kernel: [ 79.826784] i40e 0000:3b:00.0: VSI seid 387 Tx ring 0 disable timeout
Feb 17 13:35:31 152224 kernel: [ 79.826912] i40e 0000:3b:00.0: PTP external clock not supported.
Feb 17 13:35:31 152224 kernel: [ 79.948114] i40e 0000:3b:00.0: VF BW shares not restored
Feb 17 13:35:31 152224 kernel: [ 79.948472] i40e 0000:3b:00.0: PTP external clock not supported.
Feb 17 13:35:37 152224 kernel: [ 85.713443] i40e 0000:3b:00.0 eth0: tx_timeout: VSI_seid: 387, Q 2, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
Feb 17 13:35:37 152224 kernel: [ 85.713457] i40e 0000:3b:00.0 eth0: tx_timeout recovery level 2, hung_queue 2
Feb 17 13:35:37 152224 kernel: [ 85.714549] i40e 0000:3b:00.0: VSI seid 387 Tx ring 0 disable timeout
Feb 17 13:35:37 152224 kernel: [ 85.714676] i40e 0000:3b:00.0: PTP external clock not supported.
Feb 17 13:35:40 152224 kernel: [ 88.946063] i40e 0000:3b:00.0: VF BW shares not restored
Feb 17 13:35:40 152224 kernel: [ 88.946383] i40e 0000:3b:00.0: PTP external clock not supported.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
# dcbtool sc eth0 dcb off
... on the server and
# set protocols dcbx interface et-0/0/5 priority-flow-control no-auto-negotiation
on the switch. Nothing has changed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's looks like the same problem with juniper switch https://community.intel.com/t5/Ethernet-Products/VF-creation-failure-x710-Intel-adapter/td-p/664706
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
Thank you for posting in Intel Ethernet Communities.
Could you please explain further what you mean by permanent problem with XL710/X710 NIC? This would help us to understand better and be able assist you.
There's also a features support matrix for X710/XXV710/XL710 below for your reference:
Please let us know if you have questions or need clarifications.
We will follow up after 3 business days in case we don't hear from you.
Best regards,
Irwan_Intel
Intel® Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Irwan!
First time we used Intel X710-4 4x10Gbps links in bonding and have a problem https://community.intel.com/t5/Ethernet-Products/Intel-X710-4-NETDEV-WATCHDOG-eth5-i40e-transmit-queue-4-timed/td-p/1454101/jump-to/first-unread-message
after that we changed it by XL710-Q1 card 40Gbps link but no more 6Mbps of out traffic still remains
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
Thank you for the information. In this case, I will need to investigate further with my team.
We would check on the compatibility of the media and cables.
Do you mind sharing the media types you use for the XL710?
1)QSFP+ connectivity - support on QSFP connections for 40GbE-SR4,40GbE-LR4 and QSFP+ CR4 direct attach copper physical media.
2)Devices based on the Intel® Ethernet Controller XL710 (4x10 GbE, 1x40 GbE,and 2x40 GbE) have an expected total throughput for the entire device of 40 Gb/s in each direction.
3)In order for an adapter based on the XL710 controller 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 limit the throughput of the adapter.
Looking forward to hearing from you, in case of no response we will follow up in 3 business days.
Best Regards,
Irwan_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Do you mind sharing the media types you use for the XL710?
In my first message you can see output of ethtool -m command:
Vendor name : CISCO-FINISAR
Vendor PN : FCBN410QE2C03-C2
Length (Copper or Active cable) : 3m
As you can see below XL710 controller insert into PCIe 3.0 16x slot
# lspci -v -s 0000:3b:00.0
3b:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02)
Subsystem: Intel Corporation Ethernet Converged Network Adapter XL710-Q1
Flags: bus master, fast devsel, latency 0, IRQ 312, NUMA node 0
Memory at 388000000000 (64-bit, prefetchable) [size=8M]
Memory at 388001000000 (64-bit, prefetchable) [size=32K]
Expansion ROM at b8600000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=129 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [e0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 98-14-c1-ff-ff-fe-fd-3c
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1b0] Access Control Services
Capabilities: [1d0] #19
Kernel driver in use: i40e
Kernel modules: i40e
# dmidecode --type 9
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.
Handle 0x0050, DMI type 9, 17 bytes
System Slot Information
Designation: RSC-U2N4-6 SLOT1 PCI-E X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Long
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:d8:00.0
Handle 0x0052, DMI type 9, 17 bytes
System Slot Information
Designation: RSC-R1UW-E8R SLOT1 PCI-E X8
Type: x8 PCI Express 3 x8
Current Usage: Available
Length: Short
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:ff:00.0
Handle 0x0054, DMI type 9, 17 bytes
System Slot Information
Designation: AOC-2UR6N4 SLOT1 PCI-E 3.0 X16
Type: x16 PCI Express 3 x16
Current Usage: In Use
Length: Long
ID: 1
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:3b:00.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
Sorry for asking but we need to have clear understanding over the issues. Could we know what are you trying to achieve?
And the issue is that you are getting no more than 6Mbps of out traffic speed with XL710-Q1 NIC under the bonding links. Is that correct?
Looking forward to hearing from you.
Best Regards,
Irwan_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
First time I used X710-4 adapter add 2 ports of this adapter to existing linux software bonding of two ports X520 adaper
in atop eth0, eth1 - X520 and eth4 eth5 - X710-4 ports
NET | eth1 20% | pcki 91779 | pcko 356873 | sp 10 Gbps | si 202 Mbps | so 2078 Mbps | | coll 0 | mlti 2 | erri 0 | erro 0 | drpi 0 | drpo 0 |
NET | eth0 20% | pcki 86600 | pcko 354871 | sp 10 Gbps | si 164 Mbps | so 2067 Mbps | | coll 0 | mlti 2 | erri 0 | erro 0 | drpi 0 | drpo 0 |
NET | bond0 10% | pcki 347666 | pcko 715227 | sp 40 Gbps | si 735 Mbps | so 4159 Mbps | | coll 0 | mlti 8 | erri 0 | erro 0 | drpi 0 | drpo 0 |
NET | eth5 2% | pcki 90581 | pcko 1846 | sp 10 Gbps | si 235 Mbps | so 6433 Kbps | | coll 0 | mlti 2 | erri 0 | erro 0 | drpi 0 | drpo 0 |
NET | eth4 1% | pcki 78709 | pcko 1625 | sp 10 Gbps | si 133 Mbps | so 6461 Kbps | | coll 0 | mlti 2 | erri 0 | erro 0 | drpi 0 | drpo 0 |
As you can see on eth4 - 6461 Kbps, eth5 - 6433 Kbps, at the same time eth1 - 2078 Mbps, eth0 - 2067 Mbps.
Bonding of 4 ports X710-4 didn't work at all. I thought it might be a problem with the adapter or cable.
After that X710-4 was replaced by XL710-Q1 and named eth0, bonding was deleted. It was aatached by new Cisco DAC to the switch. But in atop were no more 6Mbps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
Thank you for the informations. To do further troubleshoot, Could you please run this command and share the output.
1) ethtool - m output shows that this AOC has a nominal BR of 10300Mbps (10G not 40G).
We're not sure if this cable has been tested by Intel for compatibility, you might need to check with Cisco on that.
2) We also need to authenticate the card, please provide picture on both side of the NIC card.
3) Also it would help to see how the card is configured from epct.
epct -devices branding
then
epct -nic=1 -get
where nic number is the correct nic identified by the previous command.
4) Please run SSU to gather the logs. You may download the utility below:
Looking forward to your reply.
Best Regards,
Irwan_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1) ethtool - m output shows that this AOC has a nominal BR of 10300Mbps (10G not 40G).
# ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: Not reported
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 40000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000000f (15)
drv probe link timer
Link detected: yes
2) We also need to authenticate the card, please provide picture on both side of the NIC card.
3) Also it would help to see how the card is configured from epct.
epct -devices branding
then
epct -nic=1 -get
where nic number is the correct nic identified by the previous command.
# ./epct64e -nic=1 -get
Ethernet Port Configuration Tool
EPCT version: v1.39.32.05
Copyright 2019 - 2023 Intel Corporation.
Available Port Options:
======================================
Active Port
Option Option (Gbps)
======== =============================
X 1x40
4x10
4x10G
1x40G
2x40G
Warning: Any changes to the port option configuration will require a reboot before the device will function correctly.
All actions succeeded.
# ./epct64e -devices branding
Ethernet Port Configuration Tool
EPCT version: v1.39.32.05
Copyright 2019 - 2023 Intel Corporation.
NIC Seg:Bus Ven-Dev Mode Adapter Name
=== ======= ========= =========== =============================================
1) 000:059 8086-1584 1x40 Intel(R) Ethernet Converged Network Adapter
XL710-Q1
4) Please run SSU to gather the logs. You may download the utility below:
In atachment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
Thank you for the information. I have forwarded this information to our next level.
Their update;
The card looks fine. but the cable may not be compatible, that may be why ethtool -m shows 10G while ethtool shows it is connected at 40G. ethtool -m is actually querying the cable itself.
Could you please verify the cable compatibility with Cisco for XL710 NIC card?
Please also find our compatibility link to check the list.
Looking forward to your reply.
Regards,
Irwan_Intel
Intel Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem was resolved by such configuration on Juniper switch:
set protocols dcbx interface et-0/0/5.0 disable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AndriiV,
I hope this message finds you well. I am just sending a follow up if you have any questions from our previous post. If so, please let us know.
In case we do not hear from you, I will make a follow up on March 10th 2023 . Thank you.
Best regards,
Irwan_Intel
Intel® Customer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello AndriiV,
Good day and I hope this message finds you well!
Please be informed that we will now close this request since we haven't received any response from our previous follow ups. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.
Best Regards,
Irwan_Intel
Intel Customer Support
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page