Bug ID 554993: Profile Stats Not Updated After Standby Upgrade Followed By Failover

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8

Fixed In:
12.1.0, 11.6.1, 11.5.4 HF2

Opened: Oct 29, 2015
Severity: 3-Major
Related AskF5 Article:
K23856891

Symptoms

1. The current active sessions, current pending sessions, and current established sessions counts shown in commands 'tmsh show /apm profile access' and 'tmctl profile_access_stat' become zero after failover. 2. The system posts an error message to /var/log/apm: 01490559:3: 00000000: Access stats encountered error: SessionDB operation failed (ERR_NOT_FOUND).

Impact

The current active sessions, current pending sessions, and current established sessions counts of profile access stats remain zero after failover.

Conditions

This issue happens when the following conditions are met: 1. The HA configuration is running a release prior to 11.5.3 HF2, 11.6.0 HF6, or 12.0.0. 2. A standby unit is upgraded to version 11.5.3 HF2, 11.6.0 HF6, or 12.0.0. 3. Failover is triggered.

Workaround

Upgrade all devices in the HA configuration to the same release and reboot them simultaneously.

Fix Information

The current active sessions, current pending sessions, and current established sessions counts of profile access stats now report correctly after failover.

Behavior Change