Skip to main content
pprince
Staff
Staff
October 14, 2024

Troubleshooting Tip: How to collect logs and configuration to assist TAC in debugging issues on a FortiSwitch

  • October 14, 2024
  • 0 replies
  • 7399 views
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:

  • Timeline of when the issue was first observed.

  • Details of any recent changes in the network, configuration, or user traffic patterns.

  • Information about network traffic, types of users, and any third-party switches connected to the FortiSwitches

  • Detailed description of user impact or functionality impact.

  • Troubleshooting steps already performed to isolate or narrow down the issue.

  • Frequency and pattern of occurrence of the issue.

  • References to relevant KB articles and release notes for any known or fixed issues related to FortiSwitch.

  • Any available workaround identified or implemented.

 

Provide the following logs:

 

  1. Provide FortiGate configuration and debug report under FortiGate GUI -> Administrator -> Configuration -> Backup. Related document: Technical Tip: Download Debug Logs and 'execute tac report'.

 

fgt.png

 

  1. Provide FortiSwitch event logs for the time of the issue or of the last 24 hours, depending on a case-by-case basis under FortiGate GUI -> Logs & Report -> System Events -> Logs -> Select FortiSwitch Events. Related document: Viewing event logs.

 

fgtfsw.png

 

  1. Capture a snippet of the topology view of the Managed Fortiswitches under FortiGate GUI -> WiFi & Switch Controller -> Managed FortiSwitches -> Topology.

 

top.png

 

  1. Connect to the CLI or gain SSH access to the FortiSwitch under WiFi & Switch Controller -> Managed FortiSwitches -> 'Right-Click' -> Connect to CLI.

 

swcl.png

 

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 


dddd.png

 

diagnose debug report
show full-config

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.

 

  1. Connect to the CLI or gain SSH access to the FortiGate and collect the following log output (note: FortiGate will list the output for online FortiSwitches):

 

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 trunk config
diagnose switch-controller switch-info trunk status

diagnose switch-controller switch-info lldp neighbors-summary

diagnose switch-controller switch-info mclag icl
diagnose switch-controller switch-info mclag peer-consistency-check
diagnose switch-controller switch-info mclag list

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

 

logfgt.png