Bug 1623904

Summary: lldpad is not compatible to NICs with internal LLDP processing
Product: Red Hat Enterprise Linux 7 Reporter: Dominik Holler <dholler>
Component: lldpadAssignee: Aaron Conole <aconole>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: cleech, danken, dholler, klaas, loberman, mburman, mkalinin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 21:42:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1636254    

Description Dominik Holler 2018-08-30 12:18:36 UTC
Description of problem:

lldpad might cause trouble on NICs with internal LLDP processing.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Use lldpad on a
  QLogic Corp. QLogic 2x1GE+2x10GE QL41162HMRJ CNA network card and a
  Broadcom Limited NetXtreme II BCM57800 1/10 Gigabit Ethernet (BCM57800 1-Gigabit Ethernet)
2.
3.

Actual results:

QLogic Corp. QLogic 2x1GE+2x10GE QL41162HMRJ CNA network card:

> and last but not least a problem with lldp which is my main reason for writing this e-mail:
> - there seems to be an issue with the RHEL 7.5 driver or with the network card, not sure yet) that creates spam in our cisco switch logs with messages like this
> %LLDP-FEX105-3-DETECT_MULTIPLE_PEERS: Multiple peers detected on Eth105/1/7
>
> from client side I can see that the AckNo of CEE DCBX TLV is increasing steadily:
> lldptool -t -n -i em2
> [...]
> CEE DCBX TLV
>          Control TLV:
>            SeqNo: 1, AckNo: 91685
>          Application TLV:
>            Enabled, Not Willing, No Error
>            Ethertype: 0x8906, Priority Map: 0x08
>          Priority Groups TLV:
>            Enabled, Not Willing, No Error
>            PGID Priorities:  0:[0,1,2,3,4,5,6,7]
>            PGID Percentages: 0:100% 1:0% 2:0% 3:0% 4:0% 5:0% 6:0% 7:0%
>            Number of TC's supported: 1
> [...]

Broadcom Limited NetXtreme II BCM57800 1/10 Gigabit Ethernet (BCM57800 1-Gigabit Ethernet):

> bnx2x_dcbnl_set_dcbx Requested DCBX mode is beyond advertised capabilities

Expected results:
no error messages

Additional info:

https://www.mail-archive.com/users@ovirt.org/msg50754.html

Comment 3 Dominik Holler 2018-12-17 15:53:43 UTC
On the long run, I think someone with expert knowledge should have a look at this issue, because other LLDP consumers like network manager, skydive and even Open vSwitch might be affected, too.

Comment 5 Dominik Holler 2019-01-24 08:04:16 UTC
Yes, if you want to use FCoE, lldpad cannot be disabled, but disabling lldp receiving on the interface via

lldptool set-lldp –i $ifname adminStatus=disabled

should do the trick, see
https://www.kernel.org/doc/Documentation/scsi/bnx2fc.txt
and attachment 1521303 [details]  .

What is the difference to the past prior to 7.6?

Comment 6 loberman 2019-01-24 08:16:09 UTC
The fcoe setup with bcm57810 seems to function fine with 
systemctl disable lldpad in my lab.
Note that lldp will still function in the switch and HBA firmware but using software lldpad was breaking my configuration.

Having said that it's configuration specific. Using a system from QA with bcm57740 interfaces required lldpad get enabled likely because of what the switch was unable to provide.

Comment 9 Klaas Demter 2020-02-18 16:49:27 UTC
I see a similar problem with Broadcom Inc. and subsidiaries NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) that leads to a problem with links occasionally going down. On the cisco router we see log entries like this:

%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 10 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 20 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 30 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 40 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 50 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 60 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 70 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 80 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 90 DCBX PDUs
%LLDP-FEX104-1-NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs: No Acks have been received on Interface Eth104/1/5 for last 100 DCBX PDUs
%LLDP-FEX104-5-SERVER_REMOVED: Server with Chassis ID nnn Port ID nnn on local port Eth104/1/5 has been removed

and then it'll just turn off the link

kernel 3.10.0-1062.9.1.el7.x86_64
lldpad-1.0.1-5.git036e314.el7.x86_64

Comment 11 Chris Williams 2020-11-11 21:42:08 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7