Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
10.2.4, 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.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF4, 11.5.3, 11.4.1 HF9
Opened: Oct 14, 2014 Severity: 2-Critical Related Article:
K16669
Users fail the access policy check after failover happens. The command 'configdump -allkeys' does not display any entry for the access profile.
Users cannot log on
The issue will show up after the following events: 1. The TMM on the active node restarts or crashes, the node become standby. 2. TMM and APD restart. APD re-creates config snapshots in the SessionDB. 3. The snapshots just created get deleted. 4. Failover happens again and the node becomes active. 5. Users fail to log on
Run 'bigstart restart apd' to re-create config snapshots.
APM checks config snapshots periodically and recreates them if any are missing.