|
The troubleshooting, for various process, can generate lot of debug outputs and sometimes can cause high FortiGate resource utilization or can be unresponsive.
Check the duration first which is at default 30 seconds:
# diag debug duration <----- Current duration is 30 minutes, the timer is not started yet.
Change duration to 1 minute which is lowest:
# diag debug duration 1 <----- The 1 minute count-down starts and it is possible to track this.
# diag debug duration <----- Output shows as per below:
Current duration is 1 minutes and 0 minutes 29 seconds have passed.
Once it says 30 seconds elapsed, it is possible to run the debug of any process which will be active for only 30 more seconds.
Example:
'# diag deb app ike 255' and flush the particular tunnel name from other terminal and it will show logs of the same VPN setup.
After a 1 minute passed, the debug will stop, and then it will reset to 30 minutes which is default value and show output as below:
Fortigate # diag deb duration <----- Current duration is 30 minutes, the timer is not started yet.
|
