FAQ-Why Does Debugging Information Output Stop When the debugging all Command Is Executed (the undo debugging all Command Is Not Run)

Publication Date:  2015-07-02 Views:  132 Downloads:  0
Issue Description
Why Does Debugging Information Output Stop When the debugging all Command Is Executed (the undo debugging all Command Is Not Run)?
Solution
After the debugging all command is run, the firewall displays all debugging information, which deteriorates firewall performance. Therefore, a timer is started. You can view that there is a timeout keyword following the command:

<USG> debugging all ?
  timeout  After what time the command will be stopped
  <cr>

<USG> debugging all timeout ?
INTEGER<1-1440>  The time when the command will be stopped


If the debugging all command is run, the system uses the default timer value, that is, one minute. After one minute, the system disables the debugging all command. If you set timeout in the command, the system starts a timer based on the timeout value.

The system automatically disables the debugging all command when the timer expires. Because there is much debugging information, there may be a delay in display the debugging information. Therefore, the time for displaying debugging information may be extended and thereby is longer than the specified timeout value.

END