[enhacement] Disable Intel firmware embedded LLDP agent before collecting LLDP data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Andre Ruiz |
Bug Description
I hit a hardware specific case. I see LLDP info was collected on one NIC, but not on the other NIC with MAAS commissioning process.
In the end, some Intel cards including X710 have an embedded LLDP agent in their hardware, which was blocking forwarding LLDP packet to Linux kernel. It would be nice if MAAS disables the firmware embedded agent before running LLDP phase. Otherwise, LLDP info won't be collected.
Workaround would be to run the command below as a custom commissioning script.
i40e_path=
for dev in $i40e_path/*; do
[ -e "$dev" ] || break
echo lldp stop > "${dev}/command"
done
See:
https:/
https:/
https:/
https:/
Related branches
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 140 lines (+75/-26)2 files modifiedsrc/metadataserver/builtin_scripts/commissioning_scripts/install_lldpd.py (+55/-26)
src/metadataserver/builtin_scripts/commissioning_scripts/tests/test_lldp.py (+20/-0)
tags: | added: cpe-onsite |
description: | updated |
description: | updated |
Changed in maas: | |
milestone: | 2.5.0alpha2 → 2.5.0beta1 |
Changed in maas: | |
milestone: | 2.5.0beta1 → 2.5.0beta2 |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.5.0beta2 → 2.5.0rc1 |
Changed in maas: | |
milestone: | 2.5.0rc1 → 2.5.x |
Changed in maas: | |
milestone: | 2.5.x → next |
Changed in maas: | |
status: | Invalid → New |
Changed in maas: | |
milestone: | next → none |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Andre Ruiz (andre-ruiz) |
Changed in maas: | |
milestone: | none → next |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | next → 2.9.0b4 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
bus info: pci@0000:01:00.0