Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
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
Fixed In:
13.0.0
Opened: Feb 12, 2016 Severity: 3-Major
The object property values containing spaces are prefixed by the /Common partition name. The object property values not containing spaces are not prefixed by /Common partition. Example: post fix: (tmos)# list security dos bot-signature one-line ... security dos bot-signature "Nmap web server probe (nice ports Trinity)" { category "Network Scanner" rule "uricontent:\"nice ports,/Trinity.txt.bak\"; nocase;" } ... prior to fix: (tmos)# list security dos bot-signature one-line ... security dos bot-signature "Nmap web server probe (nice ports Trinity)" { category "/Common/Network Scanner" rule "uricontent:\"nice ports,/Trinity.txt.bak\"; nocase;" } security::dos::bot-signature is one example of this behavior. However, this may impact all property values that contain spaces in them.
The tmsh list action or save config action will save the partition name /Common for property value of objects in /Common partition that contain spaces in them.
Object property-values contain spaces in them.
None, but this is a cosmetic issue. It does not lead to any incorrect configuration behavior. It is just a inconsistent listing depending upon whether the value contains the space character or not.
The property values with or without spaces exhibit identical behavior. The listing of the property does not contain the /Common as a prefix.