Last Modified: Sep 13, 2023
Known Affected Versions:
13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.3, 188.8.131.52, 14.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.1, 188.8.131.52, 14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.0.0, 15.0.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
15.1.0, 18.104.22.168, 22.214.171.124
Opened: Oct 25, 2018 Severity: 3-Major
Memory might leak on the active unit while the high availability (HA) mirror connection is down.
Memory leak until the high availability (HA) mirror connection is up. Once mirror connection is up, the system releases the memory. High CPU may also be observed, and may be more obvious than increased memory use.
-- The persistence configured that requires its state to be stored stored on the BIG-IP system. -- Mirroring is configured on the persistence profile or the virtual server. -- Mirror connection is down, for example, next active is down/offline/unavailable.
-- Disable persistence while high availability (HA) mirror connection is down (e.g., performing maintenance). -- Disable session mirroring for iRules. -- Use persistence that does not requires its state to be stored on the BIG-IP system. -- Restore high availability (HA) connection.
Persistence records no longer leak memory while the high availability (HA) mirror connection is down.