Bug ID 459211: Use of data-group record string hash (#) causes a tmsh config load error

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 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.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

Fixed In:
11.6.0

Opened: Apr 26, 2014
Severity: 3-Major
Related AskF5 Article:
K15527

Symptoms

On the command line interface, if you specify a data-group record string with the hash ('#') character, then after saving, tmsh encounters a config load error.

Impact

tmsh fails on load.

Conditions

Using the command line interface.

Workaround

To allow the configuration to load add double quotes around # in bigip.conf for data-group string records that include the '#' symbol. For an example ltm data-group internal vf-test { records { # { ----------------> "#" data test2 } } type string } After the configuration has successfully loaded modify the affected data-group replacing the (#) with an alternate string or character combination that does not include the use of "#".

Fix Information

Specify a data-group record string with the hash ('#') character no longer results in a config load error.

Behavior Change