Bug ID 421718: Setting the log.bcm56xxd.level variable

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1

Opened: May 22, 2013

Severity: 3-Major

Symptoms

Resetting the log.bcm56xxd.level variable in tmsh does not reset to the default variable properly.

Impact

Using the command: tmsh modify sys db log.bcm56xxd.level reset-to-default, does not reset the default value. This particular command does not work. However, the db variable is still explicitly set-able.

Conditions

Using the tmsh modify sys db log.bcm56xxd.level reset-to-default command.

Workaround

Set log.bcm56xxd.level manually. Do not reset to default.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips