Bug ID 421332: Configuration of unbundled 40GbE interface applied to first 10GbE interface in bundle

Last Modified: Mar 02, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1, 11.6.1, 11.5.4, 11.4.1 HF10, 11.2.1 HF16

Opened: May 16, 2013
Severity: 3-Major
Related Article:


If a 40GbE interface is configured with bundling disabled, its attributes (including Enabled/Disabled state and media-sfp configuration) are inherited by the first corresponding 10GbE interface. This can result in the 10GbE interface being disabled or failing to establish a link, and reporting a status of DOWN. For example, on a B4300 blade: 40GbE interface 10GbE interfaces 2.1 bundle disabled, disabled 1.1 DOWN, 1.2-1.4 UP 2.2 bundle disabled, disabled 1.5 DOWN, 1.6-1.8 UP 2.3 bundle disabled, disabled 1.9 DOWN, 1.10-1.12 UP 2.4 bundle disabled, disabled 1.13 DOWN, 1.14-1.16 UP


The first of four unbundled 10GbE interfaces that correspond to the unbundled 40GbE interface may not behave as expected. In many situations, it may fail to establish a link successfully, and remain in a DOWN state.


F5 hardware platforms that allow bundling/unbundling of 40GbE/10GbE interfaces: - VIPRION B4300 blades (A108, A110) - VIPRION B2250 blades (A113) - BIG-IP 10000-series appliances (D111, D112, D113) With the following interface configurations: - 1.x (10GbE) interfaces populated with 10Gb SFP+ modules and properly connected to switch. - 2.x (40GbE) interfaces configured as 'bundle disabled'.


To recover after booting: Manually Disable and re-Enable affected (10GbE) 1.x interfaces after the BIG-IP system boots and initial configuration is applied. To prevent this issue from repeating: Restore the configuration of the corresponding bundled 2.x interface to its default state. For instance, ensure it is configured for auto negotiation, and is not disabled.

Fix Information


Behavior Change