Bug ID 510588: Cross blade trunk with balanced trunk.cluster.distribution has issues with re-enabling the only local trunk working member

Last Modified: Sep 28, 2023

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

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6

Opened: Mar 04, 2015

Severity: 3-Major


When using the non-default trunk.cluster.distribution mode, with a cross blade trunk and the only remaining trunk member for the slot disabled, results in trunk errors when re-enabling this (non favor local) trunk member interface.


Re-enabled local trunk member interface of a balanced cross blade trunk (i.e. using non favor local members) may not function correctly.


trunk.cluster.distribution mode has been configured for multi-blade trunking in a VIPRION. See https://support.f5.com/kb/en-us/solutions/public/1000/600/sol1689


A restart of the bcm56xxd daemon may be required to re-add all the trunk members of a balanced cross blade trunk.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips