Description |
This article describes how to use the TAC debug script to collect debug from FortiGate in case it has a high CPU, high memory, packet drop, or misbehaving. |
||||||||||||||||||||||||||||
Scope |
FortiGate. |
||||||||||||||||||||||||||||
Solution |
The following script is crafted to collect required debug commands depending on what issue is troubleshooting and is useful to collect that information beforehand before raising a ticket with TAC.
Below is the current supported list of debug which will update from time to time:
Make the following changes to the script according to the environment and it will prompt the password when begin running the script for debug collection.
Version 1.4 script, supports collecting 2 different sets of debugs in a single Teraterm macro. The option is separated by ',' and the second digit shall remain ZERO if does not need to collect additional debug. Refer to the below article to run the script and to download the TeraTerm installer:
Note: This script is now compatible with TeraTerm version 5.3 onward or version 4.108:Tera Term 4.108 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.