Troubleshooting Tip: How to collect logs and configuration to assist TAC in debugging issues on a FortiSwitch
| Description | This article describes how to collect the logs, provide information and configuration to assist TAC in debugging issues with FortiSwitches. Attach this data to the Fortinet Support Ticket. |
| Scope | FortiGate v7.4.x and FortiSwitches 7.4.x. and above. |
| Solution | Provide the information below while opening the TAC ticket:
Provide the following logs:
 
 
Provide the logs from the core FortiSwitches (directly connected to FortiGate) for any issue and from any problematic switch, depending on the issue. If the switch is offline, use the FortiGate CLI to check if the switch has an IP address and if it is reachable. If it is not, gain console access to the switch and provide the logs.
execute dhcp lease-list fortilink execute ping <switchIP> execute ssh admin@switchIP
  diagnose debug report diagnose sys top <----- Run this for a minute. To stop it, press Ctrl + C. diagnose debug crashlog read get switch modules status get switch modules detail get switch modules limits
For the first time, it will prompt to set a new password, and if the password is not known it can be re-reseted. Related document: Technical Tip: How to change the admin password on the FortiGate for the managed FortiSwitch.
execute switch-controller get-conn-status execute switch-controller get-sync-status all execute switch-controller diagnose-connection diagnose switch-controller switch-info stp diagnose switch-controller switch-info lldp neighbors-summary diagnose switch-controller switch-info mclag icl diagnose sys top <----- Run this for a minute. To stop it, press Ctrl + C.
Alternatively, execute the following command on the FortiGate for a smaller number of FortiSwitches:
diagnose debug fortilink-report all
![]() |






