Last Modified: Sep 13, 2023
Known Affected Versions:
11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 11.6.4, 11.6.5, 22.214.171.124, 126.96.36.199, 188.8.131.52, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 184.108.40.206, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
13.1.0, 13.0.1, 220.127.116.11
Opened: Jun 10, 2016 Severity: 2-Critical
Memory hold/leak in SessionDB due to poor HA connection. Active device cannot tell the Standby device that an entry has been deleted because of poor HA connection. These entries accumulate on the Standby device, consuming extra memory which is not released.
Eventual out-of-memory errors on standby device.
A poor HA or insufficient connection exists, one that is not capable of handling the required HA traffic between devices.
The mitigation steps in ID 555465 apply to this as well: You can mitigate by temporarily disabling HA: - Disable session mirroring: tmsh modify sys db statemirror.mirrorsessions value disable - Wait a minute for HA connections to stabilize - Sync the config changes - Reboot the standby - Re-enable session mirroring: tmsh modify sys db statemirror.mirrorsessions value enable
On the Next Active ("Standby") device, SessionDB will remove all Subkey entries that the Next Active did not receive HA (re)mirror messages for during the HA sync that occurs after an HA (re)connect; the Next Active not receiving a (re)mirror for an entry generally indicates that the entry no longer exists on the Active.