Last Modified: Dec 07, 2023
Affected Product(s):
BIG-IP TMOS
Known 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, 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, 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
Opened: Jul 22, 2022 Severity: 4-Minor
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.
Increased TMM CPU usage on one or more TMMs.
- 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).
- 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".
None