Forum Discussion
Yann_Desmarest
Aug 21, 2014Cirrus
This is a known issue still unresolved in the latest BIG-IP release.
You can use tmsh to workaround your issue :
To use the CLI, You can use the "tmsh modify sys db value " to change the setting of "Logs / Configuration / Options".
Example
tmsh modify sys db log.http.level value Warning.
You can also list the various log level variables by using the list command. So, from the CLI:
- Type 'tmsh'
- list sys db log (and then hit the tab key twice)
Please note that there are quite a few log level variables so it might want to list quite a few, so knowing what one you want to modify is a better.
Some common ones are:-
Local Traffic Logging
sys db log.arp.level value-range "Debug Error Informational Notice Warning"
sys db log.http.level value-range "Debug Error Informational Notice Warning"
sys db log.ip.level value-range "Debug Informational Notice Warning"
......
Global Traffic Logging
sys db log.gtm.level value-range "alert crit debug emerg err error info notice panic warn warning"
sys db log.big3d.level value-range "alert crit debug emerg err error info notice panic warn warning"
sys db log.big3dshim.level value-range "alert crit debug emerg err error info notice panic warn warning"
Audit Logging
sys db config.auditin value-range "all disable enable verbose"