Bug ID 1124865: Removal of LAG member from an active LACP trunk on r2k and r4k systems requires tmm restart

Last Modified: Nov 14, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1

Fixed In:
15.1.9

Opened: Jul 07, 2022

Severity: 2-Critical

Symptoms

Removal of LAG member from an active LACP trunk stops the traffic flow to the tenant launched on R2x00/R4x00 based appliances.

Impact

Traffic flow gets impacted and the system misses the packets routed onto the LACP trunk from where the LAG member was removed.

Conditions

Removal of LAG member from an active LACP trunk on R2x00 and R4x00 appliances.

Workaround

- Remove the LAG member using the confd CLI - Restart tmm on all tenants that are associated with the trunk

Fix Information

When removing a LAG member from an Active LACP trunk stops traffic flow on an R2x00/R4x00 appliance system, restarting tmm in the tenants resolves the issue.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips