Last Modified: Oct 16, 2023
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 11.6.4, 11.6.5, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
12.0.0, 11.6.0 HF6, 11.5.4, 11.5.3 HF2
Opened: Feb 04, 2014 Severity: 3-Major
Persistence entry aging is not performed immediately after receiving traffic from the client. Because of that, age of the persistence entry might not be accurate. When viewing persistence table ages, the age may appear as zero (0) even when there is no traffic. Further, ages may climb to around 30 then suddenly drop back to zero when there has been no traffic for several seconds. These behaviors are by design: persistence ages are not immediately updated, but are updated periodically. For certain types of persistence entries with associated traffic, the age is always reported as zero since the associated flow is still active.
The persistence entry might be removed after the expected time. This timing-related issue affects how the age of the persistence entry is calculated. Its time varies depending on its position in the persistence table.
Persistence is configured on the virtual server.