Debug

When requesting support from FortiCare, it can be useful to attach one of the debug files described below to the TAC ticket:

• For configuration issues, please attach the system_customer_debug_file.

• For bug and operational issues, the system_full_debug_file (which already contains the customer archive file above) may be necessary. Please note the system_full_debug_file may be large, exceeding 1GB.

• Instructions for uploading large files to a FortiCare ticket are found here.

Creating a system debug file

The Save Debug File feature creates two archives of various configuration files, logs and other details used to help in diagnosing any issues that may arise. The archive files are saved on the appliance/VM (maximum of 3 sets of 2 files, with newest files possibly prompting a warning before overwriting the oldest) and can be downloaded to the logged-in admin PC or uploaded to an FTP or SFTP server.

The "system_customer_debug_file" and "system_full_debug_file" contain:

Debug File	Contents
CUSTOMER	CUSTOMER folder with: System configuration CSV format list of the last 100,000 Attack event logs MySQL format list of the last 25,000 Event logs CSV format list of all Protection Subnets CSV format list of all Service Protection Policy (SPP) Thresholds CSV format list of all SPPs with all associated, assigned Profiles and Service Ports
DEBUG	CUSTOMER folder with the same files as above DEBUG folder with 11 subfolders containing various files of debug information for use by Fortinet developers only.

To create a system debug file:

1. Go to System > Debug.
2. Click Save Debug File.
   The save debug will run, which may take several seconds. The GUI will indicate when the new files are ready.
3. Download the desired file via GUI or upload it to an FTP or SFTP server.
   If uploading, use one of the following formats:

• ftp://user:password@server{IP or FQDN}/path/

• sftp://user:password@server{IP or FQDN}//path/