Bug ID 1042589: Wrong trunk_id is associated in bcm56xxd.

Last Modified: Apr 24, 2024

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

Known Affected Versions:
13.1.3,,,,,,, 13.1.4,, 13.1.5,,,,, 14.1.5,,,,,, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,

Fixed In:
17.0.0, 15.1.10

Opened: Aug 24, 2021

Severity: 3-Major


When a set of interfaces are moved from one trunk to another, the now empty trunk is left with a valid association in bcm56xxd, and deleting that trunk can cause a valid trunk to be removed in the BCM hardware. 'tmsh show net trunk MY_TRUNK' shows the trunk is UP, but in fact the trunk is unconfigured in hardware.


May cause an L2 traffic loop.


Moving the interfaces across trunks. i.e. tmsh modify net trunk MY_OLD_TRUNK interfaces none tmsh modify net trunk MY_NEW_TRUNK interfaces add { 1.1 1.2 } tmsh delete net trunk MY_OLD_TRUNK



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips