Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 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.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, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Mar 11, 2015
Severity: 3-Major
Related Article:
K45762521
In the GUI it is possible to set the value 'none' for certain string parameters on LTM policy actions/operands. Once persisted to bigip.conf, this produces a configuration that, when loaded, is different from what was intended, which might cause a validation error.
tmsh load sys config fails.
Several operands require a string parameter (e.g., both http-cookie and http-header require a name string), as do several actions (e.g., tcl set-variable requires an expression). Using the GUI to set the value 'none' to these parameters produces a config, that when loaded from tmsh, causes a validation error.
None
The GUI no longer allows 'none' as a value for LTM policy operand and action parameters, which avoids an issue where a configuration is created that cannot be loaded.
