BugZero | F5 BugID 1128429 - Rebooting one or more blades at different times ma...

F5 - Defect ID: 1128429

Rebooting one or more blades at different times may cause traffic imbalance results High CPU

F5 - Defect ID: 1128429

Rebooting one or more blades at different times may cause traffic imbalance results High CPU

Last updated on December 31st, 2025

BugZero Risk Score
6.0 Medium

Overall: 6.0

Severity: 6.4

Community: 4.2

Lifecycle: 8.7

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Priority: 4-Minor
Status: Resolved
Impact Category: Carrier-Grade NAT
Views: 2

Description

Symptoms

One or more TMMs are consuming more CPU cycles than the other TMMs. The increased CPU usage is caused by a significant number of internal TMM traffic redirections.

Impact

Increased TMM CPU usage on one or more TMMs.

Conditions

- LSN pools enabled. - The sp-dag configured on the client-side and server-side VLANs (cmp-hash src-ip and cmp-hash dst-ip respectively).

Workaround

- Set up an High Availability (HA) pair of VIPRIONs and make an active VIPRION cluster standby before doing any operation that involves the rebooting, insertion, or removal of one or more blades. Or if the VIPRION is a stand-alone cluster: - Stop all external traffic to the VIPRION before rebooting, inserting, or removing one or more blades. - Restart or reboot all the blades at the same time from the primary, using the following "clsh" command: "clsh reboot volume <NEW_VOLUME>" or "clsh bigstart restart".

Fix Information

None

Change history

2025-12-31 Added: 15.1.10.7, 15.1.10.8, 16.1.6.1, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

2025-11-15 Added: 15.1.10.7, 15.1.10.8, 16.1.6.1, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

2025-11-08 Added: 15.1.10.7, 15.1.10.8, 16.1.6.1, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

2025-10-19 Added: 15.1.10.7, 15.1.10.8, 16.1.6.1, 17.1.3

2025-10-15 Added: 17.1.3

2025-06-28 Added: 13.1.5, 13.1.5.1, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2

Relevant Products

Click on a version to see all relevant bugs

Affected versions:13.1.5, 13.1.5.1, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top F5 Defects

9.4Defect ID: 1691489
Traffic does not pass through rSereis FIPS system
9.4Defect ID: 970269
Install fails as lind keeps failing due to "Fatal error: block id new probe failed - device file:/dev/cdrom"
9.4Defect ID: 1429717
APM as oAuth AS intermittently returning HTTP/1.1 400 Bad Request
9.4Defect ID: 2141205
Tpm-status returns: "System Integrity: Invalid" on BIG-IP versions released since October 2025
9.4Defect ID: 1032405
TMUI XSS vulnerability CVE-2021-23037

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 1128429

Rebooting one or more blades at different times may cause traffic imbalance results High CPU

F5 - Defect ID: 1128429

Rebooting one or more blades at different times may cause traffic imbalance results High CPU

Last updated on December 31st, 2025

BugZero Risk Score6.0 Medium

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Top F5 Defects

Ready to prevent the next vendor outage?

Links

BugZero Risk Score
6.0 Medium