Bug ID 1572493: LAG Trunk Configuration is Missing Inside of Tenant

Last Modified: Oct 21, 2024

Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C, Velos(all modules)

Known Affected Versions:
F5OS-A 1.7.0, F5OS-C 1.6.2

Fixed In:
F5OS-A 1.8.0

Opened: Mar 27, 2024

Severity: 1-Blocking

Symptoms

When creating a LACP LAG or Static LAG, the lag and its members will show as up on the F5OS and switch side (Arista and Cisco). However, on the tenant, tmsh will show that neither the trunk nor trunk members are present: root@(localhost)(cfg-sync Standalone)(Active)(/Common)(tmos)# list net trunk root@(localhost)(cfg-sync Standalone)(Active)(/Common)(tmos)#

Impact

The trunk information will not be visible in the tenant. - On high-end rSeries appliances (r5000, r10000, and r12000-series systems) and VELOS tenants, traffic will still work. - On low-end rSeries appliances (r2000 and r4000-series systems), traffic will not flow.

Conditions

BIG-IP tenant on F5OS system

Workaround

NA

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips