Operational Defect Database
BugZero found this defect 614 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1128429
Rebooting one or more blades at different times may cause traffic imbalance results High CPU
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
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
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1128429: Rebooting one or more blades at different times may cause traffic imbalance results High CPU ... Last Modified: Apr 26, 2024 ... 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. ... 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
