Bug ID 1636229: A vCPU count change can stop traffic for up to 3 hours

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Sep 03, 2024

Severity: 2-Critical

Symptoms

After changing the number of vCPUs for a BIG-IP Next instance, traffic stops passing through the instance. The instance is running but it will not pass traffic.

Impact

Traffic disrupted until the telemetry report is sent to F5. This can take up to maximum of 3 hours.

Conditions

-- Central Manager managing one or more BIG-IP Next instances -- The BIG-IP Next instances are licensed and passing traffic -- From Central Manager, you change the number of vCPUs of a BIG-IP Next instance

Workaround

CM Admin can deactivate and activate the license again for immediate passing of traffic

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips