What this article covers

Standardizes the required CLI diagnostic output logs to collect before submitting a Hardware Return Merchandise Authorization (RMA) ticket to Fortinet TAC.

ScopeNetwork engineers requesting hardware replacement (RMA) for failing FortiGate components.

Before using the CLI

PhotographsPreserve clear photos of LEDs, labels and visibly failed components where useful.
Swap resultsRecord known-good cable, optic, PSU or port comparison results.
Impact statementDocument service impact, redundancy loss and occurrence time.

On-site workflow

01

Capture system identity and performance

Record serial, model, firmware and overall system state.

get system status
get system performance status
02

Capture sensor and PSU health

Run the full hardware sensor output and PSU status command.

execute sensor list
diagnose hardware deviceinfo psu
03

Capture crash history

Include kernel and process crash information.

diagnose debug crashlog read
04

Capture physical interface hardware status

Record the available NIC hardware list.

diagnose hardware nic list
05

Save the complete terminal session

Save the CLI output as a text log and attach it to the Fortinet Support Portal RMA ticket. Include the failed component, troubleshooting already performed and the customer impact.

Operational caution

Review before applying: Diagnostic output can contain serial numbers, hostnames, addresses and internal topology. Apply the organisation's data-handling and redaction policy before sharing.
Next step

Preserve the hardware evidence

Attach the evidence package to the support ticket and state which component is believed to have failed, how it was isolated and whether redundancy or production service is affected.