Who rated this post

I often observe that debugging on firewalls is not disabled after a debug session. From a performance point of view, this is usually a problem. Therefore some tips  how to disable the debug if necessary and what should be enabled again after the debug.

                           -> fw ctl debug 0

CPM                   -> ./cpm_debug.sh -t crud -s INFO
                                ./cpm_debug.sh -r
FWM                   -> fw debug fwm off
FWD                   -> fw debug fwd off
CPD                    -> unset TMOUT
                                 cpd_admin debug on TDERROR_ALL_ALL=5
                                 tail –f $CPDIR/log/cpd.elg>&cpd_debug.txt
                                 cpd_admin debug off
                                 kill%
CPCA                   -> fw debug cpca off

VPN                     -> vpn debug off
                                 vpn debug ikeoff

RAD                     -> rad_admin rad debug off

DLPU                   -> fw_debug dlpu off

cp_file                 -> fw_debug cp_file_convertd off TDERROR_ALL_ALL=0

WSTLSD  (https)-> for PROC in $(pidof wstlsd); do fw debug $PROC off TDERROR-_ALL_ALL=0; done

For all other user space processes, see the following article: sk97638

                           -> env | grep TDERROR | awk -F= '{print $1}'

                            -> fwaccel on

                             > vpn accel on      (All VPN tunnels will be reset!)

                            -> SCConfigManager.exe 
                                 LogLevel = Error
                                 CommLogLevel = Off