Last Modified: Oct 16, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10
Opened: Apr 15, 2026 Severity: 3-Major
When an LTM statistics profile is deleted and recreated using the same name, counters can retain previous values. This behavior is inconsistent with expected lifecycle semantics and differs from HTTP profile behavior (which resets on recreate). Recreated statistics profile shows prior counter value (example: resp_counter stays at 1) instead of 0. Manual tmsh reset-stat ltm profile statistics resets it to 0.
Operational and troubleshooting confusion due to stale statistics after object recreation. Users expect recreated statistics profile counters to start from zero, but old values may persist unless a manual reset is run.
Create statistics profile with custom field (example: field1 resp_counter). Attach profile and iRule to a virutal server. Generate traffic to increment counter. Detach/remove profile, delete profile, and recreate profile with same name. Show profile statistics.
Run tmsh reset-stat ltm profile statistics after recreating profile (or avoid reusing same name until reset).
None