Bug ID 659648: LTM Policy rule name migration doesn't properly handle whitespace

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.2, 12.1.3,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Apr 20, 2017

Severity: 3-Major


LTM Policy validation does not allow rule names to begin or end with whitespace characters. When migrating configuration to the next version, the migration process attempts to trim off any leading and trailing whitespace. However, this process does not handle leading and trailing whitespace when such characters occur within a double quoted string.


Policy rules are migrated incorrectly, then fail validation because there of remaining leading and/or trailing whitespace characters.


LTM policy with a rule name that contains leading and/or trailing whitespace characters. These will typically occur within a double-quoted string. Here is an example that one might find in bigip.conf: ltm policy example1 { rules { " leading and trailing spaces " { ... } ... }


Prior to migration, LTM Policy rule name can be renamed to remove leading and trailing whitespace. After a failed migration, bigip.conf can be manually edited to remove offending characters and then the configuration can be manually loaded.

Fix Information

LTM Policy migration properly handles whitespace in rule names in a quoted string.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips