Product

FortiSwitch

Secure Ethernet switching with standalone and FortiLink-managed deployment models.

Data Sheets

100–200 Series → 300–600 Series → 1000–3000 Series → Rugged Series →

Quick referencesOfficial documents and operational shortcuts

Data Sheets

All 4 series

Secure Access Series →Verified Oct 2026
Secure Campus Series →Verified Oct 2026
Campus Core & Data Center Series →Verified Oct 2026
Rugged Series →Verified Oct 2026

QSGQuick Start Guides →InManDis

DocumentationFortiSwitch Docs →Verified Sep 2026

MatricesFortiSwitch Matrix →FortiSwitch Transceiver Matrix →

ToolsFortiSwitch Finder →Compare FortiSwitch models →FortiLink Compatibility Tool →

CLICLI Cheat Sheet →InManDis

Ordering GuideFortiSwitch Ordering Guide →Verified Sep 2026

CLI quick reference

Extended CLI Reference

FortiSwitch CLI Cheat Sheet →

Common FortiSwitch operational and troubleshooting starting points. Availability varies by FortiSwitchOS release and standalone versus FortiLink-managed operation.

Health & status

get system status
get switch lldp neighbors-summary
diagnose switch physical-ports list
diagnose switch trunk list
get switch modules status

Troubleshooting CLI

get switch lldp neighbors-summary
diagnose switch physical-ports list
diagnose switch trunk list
get switch modules status

execute ping <IP>
execute traceroute <IP>

diagnose sniffer packet any 'host <IP>' 4 0 l

get system performance status
diagnose sys top 1 20

FortiLink-managed switches: Also verify switch authorization, FortiLink status, VLAN assignment, trunk state and the controller view from the managing FortiGate.

Troubleshooting framework

Step	What to do
1. Symptoms	Write down exactly what is failing, affected scope, start time and last known-good state.
2. Health	Check CPU, memory, interfaces, HA/control-plane status and recent configuration changes.
3. Path	Validate L1/L2/L3, routing, policy, session state and dependencies in that order.
4. Logs	Correlate system/event/traffic logs with packet captures and targeted debugs.
5. Version	Check release notes, known issues, compatibility and lifecycle before assuming configuration error.