Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5348 Discussions

e810-CQDA2 epct claims corrupted port configuration.

PrimalNaCl
Beginner
‎04-12-2024 06:18 PM
2,058 Views

 

Greetings,

I'm having some trouble getting my e810-CQDA2 to come up w/100G.  The epct tool claims there is a corrupted port configuration.  Any idea how to fix that?

 

 

$ sudo ./epct64e -devices
Ethernet Port Configuration Tool
EPCT version: v1.41.03.01
Copyright 2019 - 2024 Intel Corporation.

An invalid port option is set for [00.052.000.00-01] Intel(R) Ethernet 100G 2P E810-C Adapter.

NIC Seg:Bus:Fun   Ven-Dev   Connector Ports Speed    Quads  Lanes per PF
=== ============= ========= ========= ===== ======== ====== ============
 1) 000:052:00-01 8086-1592 QSFP      2     N/A      N/A    N/A

Error: Corrupted port configuration.

 

dmesg shows some weirdness. 

 

sudo dmesg | 2>&1 egrep 'enp52|ice:|NULL' | grep -v systemd
[    1.269009] acpi device:55: hash matches
[    1.643569] ice: Intel(R) Ethernet Connection E800 Series Linux Driver
[    1.643571] ice: Copyright (c) 2018, Intel Corporation.
[    2.432298] ice 0000:34:00.1: DDP package already present on device: ICE OS Default Package version 1.3.30.0
[    2.518095] (NULL net_device): Potential misconfiguration of the Ethernet port detected. If it was not intended, please use the Intel (R) Ethernet Port Configuration Tool to address the issue.
[    3.557428] ice 0000:34:00.1 enp52s0f1np1: renamed from eth0
[    3.600885] ice 0000:34:00.0 enp52s0f0np0: renamed from eth2
[   11.321994] enp52s0f0np0 speed is unknown, defaulting to 1000
[   11.322331] enp52s0f0np0 speed is unknown, defaulting to 1000
[   11.322690] enp52s0f0np0 speed is unknown, defaulting to 1000
[   11.326172] enp52s0f0np0 speed is unknown, defaulting to 1000
[   14.037258] enp52s0f0np0 speed is unknown, defaulting to 1000
[   14.095751] enp52s0f0np0 speed is unknown, defaulting to 1000
[   14.367656] enp52s0f0np0 speed is unknown, defaulting to 1000
[   15.444656] enp52s0f0np0 speed is unknown, defaulting to 1000
[   15.447150] ice 0000:34:00.1 enp52s0f1np1: Potential misconfiguration of the Ethernet port detected. If it was not intended, please use the Intel (R) Ethernet Port Configuration Tool to address the issue.
[   15.515317] ice 0000:34:00.1 enp52s0f1np1: NIC Link is up 10 Gbps Full Duplex, Requested FEC: NONE, Negotiated FEC: NONE, Autoneg Advertised: Off, Autoneg Negotiated: False, Flow Control: None
[   15.515322] ice 0000:34:00.1 enp52s0f1np1: Potential misconfiguration of the Ethernet port detected. If it was not intended, please use the Intel (R) Ethernet Port Configuration Tool to address the issue.
[   17.530750] enp52s0f0np0 speed is unknown, defaulting to 1000
[   17.937567] enp52s0f0np0 speed is unknown, defaulting to 1000
[  561.686796] ice 0000:34:00.1 enp52s0f1np1: NIC Link is Down
[  567.703795] enp52s0f1np1 speed is unknown, defaulting to 1000
[  578.387058] ice 0000:34:00.1 enp52s0f1np1: NIC Link is up 10 Gbps Full Duplex, Requested FEC: NONE, Negotiated FEC: NONE, Autoneg Advertised: Off, Autoneg Negotiated: False, Flow Control: None
[  578.387064] ice 0000:34:00.1 enp52s0f1np1: Potential misconfiguration of the Ethernet port detected. If it was not intended, please use the Intel (R) Ethernet Port Configuration Tool to address the issue.
[ 4982.852744] enp52s0f0np0 speed is unknown, defaulting to 1000
[ 4982.905486] enp52s0f0np0 speed is unknown, defaulting to 1000
[ 4983.322311] enp52s0f0np0 speed is unknown, defaulting to 1000
[ 4983.932686] enp52s0f0np0 speed is unknown, defaulting to 1000

 

I have a known working Arista 100G fiber transceiver in the top-most port of the card and a Mellanox 10G fiber transceiver in the bottom port.  Before I inserted the Mellanox transceiver dmesg was complaining about unsupported modules.  The "Corrupted port configuration" error from epct was also still a thing.  The only reason I bring it up is I had seen this community post indicating the e810 was "open optic" so it was curious as to why the driver would emit such a thing?  Is it purely advisory?  That port isn't failing to come up because of that is it?  If it's advisory, fine, if it's blocking me, why given the "open optic" assertion?  The Arista optics seem to work fine in everything else that isn't vendor locked.  So why should this be an issue in the supposed non-vendor-locked e810?

 

It should be stated that the 10G port/module (Mellanox) is working.

 

$ ifconfig
enp52s0f0np0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 40:a6:b7:95:ca:70  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp52s0f1np1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.86.213  netmask 255.255.255.0  broadcast 192.168.86.255
        inet6 fe80::46fb:f5a5:b462:d72a  prefixlen 64  scopeid 0x20<link>
        ether 40:a6:b7:95:ca:71  txqueuelen 1000  (Ethernet)
        RX packets 67986  bytes 66447371 (66.4 MB)
        RX errors 0  dropped 192  overruns 0  frame 0
        TX packets 29760  bytes 4586757 (4.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 3723  bytes 462752 (462.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3723  bytes 462752 (462.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

Can get 'line speed' per iperf3

 

$ iperf3 -c 192.168.86.216
Connecting to host 192.168.86.216, port 5201
[  5] local 192.168.86.213 port 54548 connected to 192.168.86.216 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  1.15 GBytes  9.90 Gbits/sec    1   1.45 MBytes       
[  5]   1.00-2.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.45 MBytes       
[  5]   2.00-3.00   sec  1.15 GBytes  9.91 Gbits/sec    0   1.48 MBytes       
[  5]   3.00-4.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.48 MBytes       
[  5]   4.00-5.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.66 MBytes       
[  5]   5.00-6.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.66 MBytes       
[  5]   6.00-7.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.66 MBytes       
[  5]   7.00-8.00   sec  1.15 GBytes  9.90 Gbits/sec    0   1.66 MBytes       
[  5]   8.00-9.00   sec  1.15 GBytes  9.91 Gbits/sec    0   2.50 MBytes       
[  5]   9.00-10.00  sec  1.15 GBytes  9.89 Gbits/sec   83   2.19 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  11.5 GBytes  9.90 Gbits/sec   84             sender
[  5]   0.00-10.00  sec  11.5 GBytes  9.90 Gbits/sec                  receiver

iperf Done.

Connecting to host 192.168.86.216, port 5201
Reverse mode, remote host 192.168.86.216 is sending
[  5] local 192.168.86.213 port 39966 connected to 192.168.86.216 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   1.00-2.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   2.00-3.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   3.00-4.00   sec  1.15 GBytes  9.89 Gbits/sec                  
[  5]   4.00-5.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   5.00-6.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   6.00-7.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   7.00-8.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   8.00-9.00   sec  1.15 GBytes  9.90 Gbits/sec                  
[  5]   9.00-10.00  sec  1.15 GBytes  9.90 Gbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  11.5 GBytes  9.90 Gbits/sec    0             sender
[  5]   0.00-10.00  sec  11.5 GBytes  9.90 Gbits/sec                  receiver

iperf Done.

 

 

So it seems something is not ideal wrt to the 100G...whether that's just an extreme dislike of the Arista optics or the corrupt setting.  Again, those exact optics work fine in two MikroTik CRS504-4XQ-IN and an Arista DCS-7160-32CQ-F switch.

 

Any assistance would be grand!
Thanks!

UPDATE (won't let me reply):

I pulled the Mellanox optic and I get the unsupported module in dmesg again.

[ 8077.500316] ice 0000:34:00.0 enp52s0f0np0: An unsupported module type was detected. Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules
[ 8086.749719] ice 0000:34:00.0 enp52s0f0np0: NIC Link is up 100 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: NONE, Autoneg Advertised: On, Autoneg Negotiated: False, Flow Control: None
[ 8086.749727] ice 0000:34:00.0 enp52s0f0np0: An unsupported module type was detected. Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules
[ 8088.948143] ice 0000:34:00.0 enp52s0f0np0: NIC Link is Down
[ 8089.050091] ice 0000:34:00.0 enp52s0f0np0: NIC Link is up 100 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: NONE, Autoneg Advertised: On, Autoneg Negotiated: False, Flow Control: None
[ 8089.050097] ice 0000:34:00.0 enp52s0f0np0: An unsupported module type was detected. Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules
[ 8089.548226] ice 0000:34:00.0 enp52s0f0np0: NIC Link is Down
[ 8089.749519] ice 0000:34:00.0 enp52s0f0np0: NIC Link is up 100 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: NONE, Autoneg Advertised: On, Autoneg Negotiated: False, Flow Control: None
[ 8089.749526] ice 0000:34:00.0 enp52s0f0np0: An unsupported module type was detected. Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules
[ 8106.245805] ice 0000:34:00.1 enp52s0f1np1: NIC Link is Down
0 Kudos

Link Copied

9 Replies
Azeem_Intel
Employee
‎04-17-2024 02:41 PM
2,024 Views

Hi PrimalNaCl,


Greetings for the day!


Hope you are doing well. Sure, we will help you with that. Before we proceed, could you please confirm the EPCT driver version? If it is out of date, please update it and check again.

 

Ethernet Port Configuration Tool (All Supported OSs) (intel.com)


Please do not hesitate in contact us, we are more than glad to assist you.

 

Best Regards,


Azeem_Intel

0 Kudos
Copy link
Azeem_Intel
Employee
‎04-19-2024 02:29 PM
1,981 Views

Hi PrimalNaCl,


Greetings for the day!

 

This is the first follow-up regarding the issue (e810-CQDA2 epct claims corrupted port configuration.) you reported to us.

We wanted to inquire whether you had the opportunity to review the plan of action (POA) we provided.


Please do not hesitate in contact us, we are more than glad to assist you.

 

Best Regards,


Azeem_Intel

0 Kudos
Copy link
Azeem_Intel
Employee
‎04-22-2024 05:05 PM
1,893 Views

Hi PrimalNaCl,



Greetings for the day!



This is the second follow-up regarding the reported issue. We're eager to ensure a swift resolution and would appreciate any updates or additional information you can provide.



Please do not hesitate in contact us, we are more than glad to assist you.



Best Regards,


Azeem_Intel


0 Kudos
Copy link
PrimalNaCl
Beginner
‎04-22-2024 05:46 PM
1,885 Views
In response to Azeem_Intel

Greetings,

 

If you mean the base adapter driver, that was from the complete driver pack (all OS') v29.0.1.  The epct tool came from the link you cited...as you can see from my output the tool is "EPCT version: v1.41.03.01".  On __linux__, from that archive, there is only the executable tool.  With the default ubuntu ice driver I was getting the corrupted port config error.  After installation of the Intel driver from the complete driver pack v29.0.1 the linux epct tool (Linux_x64 version) worked.  On windows, there is a iqvsw64e.sys driver...which is version 1.5.0.3.

 

However, that appears to have no been the issue wrt my connectivity woes.  It appears that I need to update my fw.  The optics appear to work fine but require that I manually remove and reinsert the tranceiver from the _card_ qsfp28 cage to get the green LEDs to illuminate/heartbeat/blink.  Perhaps a handshaking issue?  A fw update to v4.40 appears to resolve this issue on actual Intel cards.  The cards I have, in spite of being claimed and sold as genuine Intel, appear to be Dell cards.

And Dell's update process, even w/extracted bits, does not appear to work either.  Everything either indicates the card is not found or not found and there is no update for it.   Dell's tooling complains that the nvmupdate.cfg file is corrupt.  Clearly they are doing something extra special during their process but I cannot determine what that might be.  I had _HOPED_, beyond hope apparently, that all of this might go away and resolve itself from an efi shell w/your efi tooling and their fw.  No changes.

 

Here's the inventory as take from the efi version of the tool:

<?xml version="1.0" encoding="UTF-8"?>
<DeviceInventory lang="en">
	<Instance vendor="8086" device="1592" subdevice="000B" subvendor="8086" bus="52" dev="0" func="0" PBA="K98023-005" port_id="Port 1 of 2" display="Intel(R) Ethernet 100G 2P E810-C Adapter">
		<Module type="PXE" version="2.6.2" update="0">
		</Module>
		<Module type="EFI" version="4.1.23" update="0">
		</Module>
		<Module type="Netlist" version="3.0.24.0" update="0">
		</Module>
		<Module type="NVM" version="80008942" update="0">
		</Module>
		<VPD>
			<VPDField type="String">E810-C 100GbE Controller</VPDField>
			<VPDField type="Readable" key="V0">FFV20.5.13</VPDField>
			<VPDField type="Readable" key="PN">DWNRF</VPDField>
			<VPDField type="Readable" key="MN">1028</VPDField>
			<VPDField type="Readable" key="V1">DSV1028VPDR.VER2.2</VPDField>
			<VPDField type="Readable" key="V3">DTINIC</VPDField>
			<VPDField type="Readable" key="V4">DCM1001FFFFFF2101FFFFFF3201FFFFFF4301FFFFFF5401FFFFFF6501FFFFFF7601FFFFFF8701FFFFFF</VPDField>
			<VPDField type="Readable" key="V5">NPY8</VPDField>
			<VPDField type="Readable" key="V6">PMTD</VPDField>
			<VPDField type="Readable" key="V7">NMVIntel Corp</VPDField>
			<VPDField type="Readable" key="V8">L1D0</VPDField>
			<VPDField type="Readable" key="V9">LNK164163</VPDField>
			<VPDField type="Checksum" key="RV">80</VPDField>
			<VPDField type="Writable" key="Y0">CCF1</VPDField>
		</VPD>
		<MACAddresses>
			<MAC address="40A6B795CA70">
			</MAC>
		</MACAddresses>
	</Instance>
	<Instance vendor="8086" device="1592" subdevice="000B" subvendor="8086" bus="52" dev="0" func="1" PBA="K98023-005" port_id="Port 2 of 2" display="Intel(R) Ethernet 100G 2P E810-C Adapter">
		<Module type="PXE" version="2.6.2" update="0">
		</Module>
		<Module type="EFI" version="4.1.23" update="0">
		</Module>
		<Module type="Netlist" version="3.0.24.0" update="0">
		</Module>
		<Module type="NVM" version="80008942" update="0">
		</Module>
		<VPD>
			<VPDField type="String">E810-C 100GbE Controller</VPDField>
			<VPDField type="Readable" key="V0">FFV20.5.13</VPDField>
			<VPDField type="Readable" key="PN">DWNRF</VPDField>
			<VPDField type="Readable" key="MN">1028</VPDField>
			<VPDField type="Readable" key="V1">DSV1028VPDR.VER2.2</VPDField>
			<VPDField type="Readable" key="V3">DTINIC</VPDField>
			<VPDField type="Readable" key="V4">DCM1001FFFFFF2101FFFFFF3201FFFFFF4301FFFFFF5401FFFFFF6501FFFFFF7601FFFFFF8701FFFFFF</VPDField>
			<VPDField type="Readable" key="V5">NPY8</VPDField>
			<VPDField type="Readable" key="V6">PMTD</VPDField>
			<VPDField type="Readable" key="V7">NMVIntel Corp</VPDField>
			<VPDField type="Readable" key="V8">L1D0</VPDField>
			<VPDField type="Readable" key="V9">LNK164163</VPDField>
			<VPDField type="Checksum" key="RV">80</VPDField>
			<VPDField type="Writable" key="Y0">CCF1</VPDField>
		</VPD>
		<MACAddresses>
			<MAC address="40A6B795CA71">
			</MAC>
		</MACAddresses>
	</Instance>
</DeviceInventory>

 

The error in the update:

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.40.5.5
Copyright(C) 2013 - 2023 Intel Corporation.

FS5:\e810\EFI2x64\nvmupdate64e.efi -rd -b -o efi_backup_nvm_image.bin -l efi_nvm_update_log.txt -c nvmupdate.cfg -u 

Config file read.
Unsupported device found - DeviceId: 1539.
No devices to update.
Post update inventory

nvmupdate.cfg:

CURRENT FAMILY: 1.0.0
CONFIG VERSION: 1.20.0

BEGIN DEVICE
DEVICENAME: Intel(R) Ethernet 100G 2P E810-C Adapter
VENDOR: 8086
DEVICE: 1592
SUBVENDOR: 8086
SUBDEVICE: 000B
NVM IMAGE: tacoma_rapids_inj.bin
OROM IMAGE: BootIMG.FLB
EEPID: 8001C967
SKIP NETLIST: FALSE
IMAGE DOWNGRADE: TRUE
RESET TYPE: REBOOT
CURRENT GFID: 0157-1590
ORIGINAL GFID: 0157-1590
REVISION: 02
REPLACES: 80008942
END DEVICE

 

Any other known way to get fw onto the card?  I've tried linux, windows, and efi shell.  I've tried Dell's update wad...which just results in an empty modal window and, as mentioned, manual updating w/the Dell stuff doesn't work either.

 

Thanks.

In response to Azeem_Intel
0 Kudos
Copy link
Azeem_Intel
Employee
‎04-22-2024 06:24 PM
1,879 Views

Hi PrimalNaCl,


Greetings for the day!

 

Thank you for your response. Could you please share a snapshot of the defective part with the serial number visible? Additionally, please let us know if this product was purchased separately or with the machine.


Please do not hesitate in contact us, we are more than glad to assist you.

 

Best Regards,


Azeem_Intel


0 Kudos
Copy link
Azeem_Intel
Employee
‎04-25-2024 05:32 PM
1,821 Views

Hi PrimalNaCl,


Greetings for the day!

 

This is the first follow-up regarding the issue (e810-CQDA2 epct claims corrupted port configuration.) you reported to us.


We wanted to inquire whether you had the opportunity to review the plan of action (POA) we provided.

 

Best Regards,


Azeem_Intel


0 Kudos
Copy link
PrimalNaCl
Beginner
‎04-25-2024 09:08 PM
1,813 Views
In response to Azeem_Intel

It was purchased from an ebay seller listing the items as Intel parts.  There is no bradyID sticker.  I was only able to sleuth out them being Dell cards was through cracking open Dell's firmware bundle and looking at the nvmupdate.cfg for the matching subdevice variant.

 

The seller, w/some help/pressure from ebay has agreed to take the cards back and issue a refund.  As such this is no longer going to be an issue for me.

 

Thanks!  

In response to Azeem_Intel
0 Kudos
Copy link
Sachinks
Employee
‎04-26-2024 05:27 AM
1,786 Views

Hello PrimalNaCl,


Good day!


Thank you for the update. Glad to know that you were able to get a refund on the product. Kindly let us know if we can close this thread.


Regards,

Sachin KS


0 Kudos
Copy link
PrimalNaCl
Beginner
‎04-26-2024 08:38 AM
1,773 Views

Ok to close.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.