E810-C does not forward lldp

[StefanMajer]

Hi, 

I have a Server running ubuntu-20.04 with two E810-C cards connected to two Edgecore AS7732-12. This is the first server with the 810 series card, the farm we have is equipped with xxv710 25G models. 

We run a small lldpd https://github.com/metal-stack/go-lldpd on all machines to send custom TLVs via lldp. This is required for our bare metal provisioning.

This works fine for XXV710 and X550 type ethernet cards, but not with the e800 family.

The only lldpd which is able to send lldp frames is lldpad, but this daemon does not allow to send SystemName/SystemDescription with own content.

All other lldpd implementation does not work. We are pretty sure this is due the fact that this card has DCB as a hard requirement. 

Any hints howto make vanilla lldp daemons work here ?

Greetings

Stefan Majer

Details:

lspci

3b:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)
d8:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-C for QSFP (rev 02)

root@100gtest:# ethtool --show-priv-flags lan0
Private flags for lan0:
link-down-on-close : off
fw-lldp-agent : off
vf-true-promisc-support: off
mdd-auto-reset-vf : off
legacy-rx : off

root@100gtest:# ethtool -k lan0
Features for lan0:
rx-checksumming: on
tx-checksumming: on
tx-checksum-ipv4: on
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: on
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: on
scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: on
tx-tcp-segmentation: on
tx-tcp-ecn-segmentation: on
tx-tcp-mangleid-segmentation: off
tx-tcp6-segmentation: on
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: on
receive-hashing: on
highdma: on
rx-vlan-filter: on
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: on
tx-gre-csum-segmentation: on
tx-ipxip4-segmentation: on
tx-ipxip6-segmentation: on
tx-udp_tnl-segmentation: on
tx-udp_tnl-csum-segmentation: on
tx-gso-partial: on
tx-tunnel-remcsum-segmentation: off [fixed]
tx-sctp-segmentation: off [fixed]
tx-esp-segmentation: off [fixed]
tx-udp-segmentation: on
tx-gso-list: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: on
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
rx-gro-hw: off [fixed]
tls-hw-record: off [fixed]
rx-gro-list: off

root@100gtest:# ethtool -i lan0
driver: ice
version: 0.8.2-k
firmware-version: 2.30 0x80005d1e 1.2877.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

[StefanMajer]

Hi Intel Support,

I tried to first update the network card firmware with the nvmeupdate64e from this package: E810_NVMUpdatePackage_v2_50_Linux.tar.gz
This is actually still not possible:

# ethtool -i lan0
driver: ice
version: 0.8.2-k
firmware-version: 2.10 0x80004341 1.2789.0
expansion-rom-version:
bus-info: 0000:65:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

# uname -a

Linux intel-test 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

# 

./nvmupdate64e

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.37.5.1
Copyright(C) 2013 - 2021 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 [+.........]
Tool execution completed with the following status: The configuration file could not be opened/read, or a syntax error was discovered in the file.
Press any key to exit.

Log says:

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

./nvmupdate64e -a /root/E810/Linux_x64/ -l update.log

Config file read.
Error: Config file GFID doesn't match NVM image version [config: Current: 0x01571598, Original: 0x01571598]
[image: Current: 0x00000000, Original: 0x00000000].

I really do not understand how the firmware update should be done on a fleet (more than 100 servers) ? I can not update the the kernel driver of this specific card for the sole purpose to patch the firmware.

Please elaborate

Greetings

Stefan Majer

[Caguicla_Intel]

Hello Stefan,

Good day!

This is just a follow up to check if you are able to read our previous message. If yes, feel free to let us know if you have additional questions and clarifications.

Awaiting to hear from you.

Should there be no reply, we will follow up after 3 business days.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

Thank you for the reply. 

Please allow us to re-escalate this request to our higher level. We will give you an update as soon as possible but no later than 2-4 business days.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

Good day!

It seems that you are reporting a new issue on your same adapter. With this, is it alright if we move your new concern on separate thread with new ticket number since this is now Firmware related issue? A separate thread will help other customers in searching solutions similar to your concerns.

Additionally, kindly confirm if you already tried our latest driver release and if its okay to proceed closing this specific thread.

Hoping to hear from you soon.

Should there be no response, we will follow up after 3 business days.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

How are you doing?

This is just a follow up to check if you read our previous message. If yes, kindly provide the information requested for us to continue checking your query. 

Looking forward to your reply.

Should there be no response, we will follow up after 3 business days.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

Good day!

We found a similar thread about this issue. Same issue or error was resolved on thread below and we recommend to follow the instructions provided. Customer in this thread also encountered the same error "Tool execution completed with the following status: The configuration file could not be opened/read, or a syntax error was discovered in the file" during NVM update.

https://community.intel.com/t5/Ethernet-Products/Intel-X710-T2L-NVM-Update-to-7-3-Failing/td-p/664667

Feel free to let us know if this was helpful on resolving the issue.

Awaiting to your reply.

We will follow up after 3 business days in case we don't hear from you.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

How are you doing?

This is just a follow up to check if you received our previous message. If yes, kindly confirm and let us know if the link we shared helped on this query. Feel free to let us know if you have additional questions or clarifications.

Hoping to hear from you soon.

Should there be no response from you, I’ll make sure to reach out after 3 business days.

Best regards,

Crisselle C.

Intel® Customer Support

[Caguicla_Intel]

Hello Stefan,

Good day!

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,

Crisselle C.

Intel® Customer Support