Bug ID 646440: TMSH allows mirror for persistence even when no mirroring configuration exists

Last Modified: Jul 02, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 13.1.3,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,,, 14.1.2,,,,,,, 15.0.0, 15.0.1,,,, 15.1.0,,,

Opened: Feb 17, 2017
Severity: 3-Major
Related AskF5 Article:


When Mirroring is not configured in a high-availability (HA) configuration, the Configuration Utility (GUI) correctly hides the 'mirror' option for Persistence profile. However, Persistence Mirroring can still be enabled via TMSH.


A memory leak and degraded performance can occur when: -- The Mirroring option of a Persistence profile is enabled. -- Mirroring in the HA environment is not configured.


-- Mirroring is configured in an HA configuration. -- Persistence profile. -- Using TMSH.


Always use the Configuration Utility (GUI) to configure Persistence profiles. If you encounter this issue, complete the following procedure to locate Persistence profiles with Mirroring enabled, and then disable Mirroring for those profiles: 1. Access the BIG-IP Bash prompt. 2. List the Persistence profiles with the following command: tmsh list ltm persistence 3. Examine the Persistence profiles to identify the ones with 'mirror enabled'. 4. Disable Mirroring for each Persistence profile, using a command similar to the following: tmsh modify ltm persistence <persistence_type> <profile_name> mirror disabled 5. Save the changes to the Persistence profiles: tmsh save sys config

Fix Information


Behavior Change