Bug ID 1672269: Blades missing L2 entries causing excessive DLFs.

Last Modified: Jan 30, 2025

Affected Product(s):
F5OS F5OS-C(all modules)

Fixed In:
F5OS-C 1.8.0

Opened: Sep 18, 2024

Severity: 2-Critical

Symptoms

Excessive DLFs from certain blades due to missing L2 entries. The 'l2fs_stat' tmstat table shows the IDs of the blades to which L2 entries will be forwarded to: [root@blade-1 ~]# docker exec -i partition_fpga tmctl -d blade -w 180 l2fs_stat -s svc_ids svc_ids --------------------------------- [ 0x2c 0x4c 0x6c 0x8c 0xac 0xcc ] [root@blade-1 ~]# In this example, blade-1 will forward to blades 3, 5,7,9,11 and 13. A blade should have an entry for all other blades in the partition.

Impact

L2 entries learned on the affected blade are not forwarded to other blades causing missing L2 entries on those blades.

Conditions

Reboot of a tenant or changing the tenant from deployed to configured back to deployed.

Workaround

Reboot the blade that's missing the entries for other blades. For example, blade-1 is missing IDs for all blades in the partition: [root@blade-1 ~]# docker exec -i partition_fpga tmctl -d blade -w 180 l2fs_stat -s svc_ids svc_ids --------------------------------- [ ] [root@blade-1 ~]#

Fix Information

On tenant deletion, don't remove service IDs belonging to the L2FwdSvc.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips