Fortinet black logo

Handbook

Debug

Copy Link
Copy Doc ID 603e8323-b78c-11ec-9fd1-fa163e15d75b:981474
Download PDF

Debug

When requesting support from FortiCare, it can be useful to include a Debug file to the TAC ticket from FortiDDoS.

Creating a system debug file

The Save Debug File feature creates an archive of various configuration files, logs and other details used to help in diagnosing any issues that may arise. The file is saved locally (maximum of 3 files) and can be downloaded to the logged-in admin PC or uploaded to an FTP server (no security credentials).

The debug compressed file includes a CUSTOMER folder and DEBUG folder containing the following:

Folder

Contents

CUSTOMER
  • System configuration

  • CSV format list of the last 20,000 Attack event logs

  • CSV format list of all Protection Subnets

  • CSV format list of all Service Protection Profile (SPP) Thresholds

  • MySQL format list of the last 20,000 Event logs

DEBUG 10 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 file is complete.
  3. When the file is ready, download it via GUI or upload it to an FTP server.
    If uploading to FTP, a dialog will display. Enter the following FTP parameters:
    Settings Guidelines

    Name

    system_debug_file_<date>_<time>.zip

    Running Status

    Running status indicates the final download status.

    Running — The system is still collecting and compressing the debug file to generate a download file.

    Ready — The file is ready to download via the GUI/upload to FTP.

    Upload Status

    The upload FTP status.

    Running — The File is uploading. Error messages will appear in the Upload Status column.

    Ready — The Upload is completed.

Debug

When requesting support from FortiCare, it can be useful to include a Debug file to the TAC ticket from FortiDDoS.

Creating a system debug file

The Save Debug File feature creates an archive of various configuration files, logs and other details used to help in diagnosing any issues that may arise. The file is saved locally (maximum of 3 files) and can be downloaded to the logged-in admin PC or uploaded to an FTP server (no security credentials).

The debug compressed file includes a CUSTOMER folder and DEBUG folder containing the following:

Folder

Contents

CUSTOMER
  • System configuration

  • CSV format list of the last 20,000 Attack event logs

  • CSV format list of all Protection Subnets

  • CSV format list of all Service Protection Profile (SPP) Thresholds

  • MySQL format list of the last 20,000 Event logs

DEBUG 10 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 file is complete.
  3. When the file is ready, download it via GUI or upload it to an FTP server.
    If uploading to FTP, a dialog will display. Enter the following FTP parameters:
    Settings Guidelines

    Name

    system_debug_file_<date>_<time>.zip

    Running Status

    Running status indicates the final download status.

    Running — The system is still collecting and compressing the debug file to generate a download file.

    Ready — The file is ready to download via the GUI/upload to FTP.

    Upload Status

    The upload FTP status.

    Running — The File is uploading. Error messages will appear in the Upload Status column.

    Ready — The Upload is completed.