Bug ID 641390: Backslash removal in LTM monitors after upgrade

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP AAM(all modules)

Known Affected Versions:
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, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 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, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.2 HF1, 11.6.4

Opened: Jan 25, 2017

Severity: 1-Blocking

Related Article: K00216423

Symptoms

After upgrading, BIG-IP fails to load the configuration and reports that a monitor failed to load.

Impact

The monitor fails to load.

Conditions

-- 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 }

Workaround

Manually correct the string to be the way it was before upgrade, then the configuration will load.

Fix Information

Upgrade no longer results in incorrectly removing backslashes for some LTM monitor attributes.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips