Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP AAM
Known Affected Versions:
11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 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.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3, 13.0.1
Fixed In:
13.1.0, 11.6.4
Opened: Jan 25, 2017 Severity: 1-Blocking Related Article:
K00216423
After upgrading, BIG-IP fails to load the configuration and reports that a monitor failed to load.
The monitor fails to load.
-- Specific backslash escaping in LTM monitors. -- Upgrading from 11.5.x, 11.6.0, 11.6.1, 11.6.2, or 11.6.3 to 12.0.0, 12.1.0, 12.1.1, 12.1.2, or 13.0.0. Note: This issue is specific to LTM monitors. It does not occur in BIG-IP DNS/GTM monitors. For example, to have two backslashes in the value, you specify three backslashes. The first backslash is the 'escape' character. ltm monitor https /Common/my_https { adaptive disabled cipherlist DEFAULT:+SHA:+3DES:+kEDH compatibility enabled defaults-from /Common/https destination *:* interval 5 ip-dscp 0 recv "Test string" recv-disable \\\"Test\\\"me\\\" <-- pertinent string value (can be in recv, send or username attributes too). send Test time-until-up 0 timeout 16 username test\\\"me }
Manually correct the string to be the way it was before upgrade, then the configuration will load.
Upgrade no longer results in incorrectly removing backslashes for some LTM monitor attributes.