Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.6.2 HF1, 11.2.1, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.6.0, 11.5.1 HF5, 11.4.1 HF4, 11.4.0 HF8
Opened: Dec 23, 2013 Severity: 3-Major Related Article:
K15687
BIG-IP APM user sessions may fail to reconnect after multiple failover events between peer systems. As a result of this issue, you may encounter the following symptoms: The system logs messages for each user attempt to reestablish the session after the failover events. For example: notice apd[5421]: 01490102:5: 63db9fd4: Access policy result: Network_Access notice tmm1[8742]: 01490505:5: 63db9fd4: No leasepool assigned notice tmm[8742]: 01490501:5: 63db9fd4: Session deleted due to user logout request.
Network access sessions fail to reestablish.
This issue occurs when all of the following conditions are met: -- The active BIG-IP APM system experiences a failover event, causing the peer standby BIG-IP APM system to become active. -- The newly active BIG-IP APM system also experiences a failover event, causing the initial active BIG-IP APM system now in standby to become active. -- Users have established network access sessions with either of the BIG-IP APM systems prior or between failover events.
No workaround. Failovers triggered because of tmm crash or reboots do not have this problem.
The Active device now syncs snapshots to standby so applications like network access work as expected after multiple failovers.