Loading...
Loading...
If jitterentropy-read from CPU jitter is used in all cases, a big performance problem is seen for most cases where BIG-IP works in non-FIPS mode. This can be encountered after upgrading to version 17.x from an earlier BIG-IP version.
Very high CPU utilization is seen when BIG-IP handles traffic while in non-FIPS mode.
The issues occur when BIG-IP operates in non-FIPS or FIPS mode and use jitterentropy to generate seed.
None
Jitterentropy-read of CPU jitter is now invoked in any one of these situations, - Either BIG-IP operates in FIPS mode, - TMM is processing traffic in non-FIPS and FIPS modes. In this case, none of the other components perform the stated jitter read operations and improves performance.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.