Last Modified: Sep 13, 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.6.2 HF1, 11.2.1, 11.3.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 11.6.4, 11.6.5, 188.8.131.52, 184.108.40.206, 220.127.116.11
11.6.0 HF6, 11.5.2, 11.5.1 HF7, 11.4.1 HF7
Opened: Dec 02, 2014 Severity: 2-Critical Related Article:
Related Article: K15914
On a standby unit, TMM dumps core files when it is starting up and continues to do so when the active unit is handling traffic in the APM module.
TMM on the standby device crashes with SEGV, which causes existing sessions not stored on the standby device and users have to re-login should failover occur.
The issue happens on APM systems when high availability is configured and the following conditions are met: 1. The active device is busy processing traffic. 2. Some sessions on the active device are terminated. 3. The TMM in standby device is starting up.
In APM HA environments, the system now prevents global status from being updated before the initialization is completed on a standby device. TMM on the standby no longer dumps core files on startup.