Fortinet FortiGate 70F smoke smell or burned PCB: Diagnose & Fix
By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30
| Vendor | Fortinet |
|---|---|
| Operating system | FortiOS |
| Category | Hardware Failure |
| Skill level | Intermediate to advanced |
| DIY-able? | Yes with CLI access; some scenarios need Fortinet TAC + RMA. |
Across years of operating Fortinet gear I have watched the same hardware-failure pattern repeat: a unit ships fine, runs for two years, then trips on a power-event or a thermal excursion. On FortiOS the recovery path is the same whether the affected unit is from the FortiGate as SD-WAN router family or something newer.
Before you touch anything, capture state. `get system status` and `diagnose hardware deviceinfo` dumped to a file is worth more than a screen-cap because Fortinet TAC will ask for the exact output when you open the case. Keep the artifact even if the box recovers on its own.
Below I walk through the on-box steps first, then the Fortinet TAC escalation path. If you have spares on hand, swap-then-diagnose is usually faster than diagnose-then-swap: but only if you can afford the rack time.
What this guide covers
Diagnose and recover from smoke smell or burned PCB on a Fortinet FortiGate 70F.
Step-by-step
- STOP. Power off the device at the wall before touching it.
- Open the chassis and identify which board / module is the source of the smell.
- Photograph the visible damage (scorched capacitors, blackened ICs).
- Note the device serial number and exact model for the support case.
- Do not power back on. burned components fail closed and can damage adjacent boards.
- Open a Fortinet TAC case with the photos and serial.
- RMA the affected component (line card, supervisor, PSU) or the full chassis if the backplane is damaged.
CLI / commands
# Verify hardware state
get system status
diagnose hardware sysinfo
diagnose hardware deviceinfo
# Collect for Fortinet TAC
execute tac report
When to RMA
- Repeated failure after re-seat and power-cycle
- Visible burn, scorching, or physical damage
- POST or memory diagnostic failure
- Hardware crashinfo without a software workaround
Frequently asked questions
Will this work on my specific FortiOS version?
The procedure reflects current FortiOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.
Should I open a Fortinet TAC case immediately?
Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.
Where can I find the Fortinet official documentation?
https://community.fortinet.com/: search the product family + feature name.
Is this procedure safe in production?
Test in a lab or maintenance window first. Capture pre-change state so you can roll back.
Related guides
- All Fortinet fix guides → /fortinet/
- All vendor guides → /vendors/
Related fixes
Related guides worth a look while you sort this one out:
- Fortinet FortiGate 100F smoke smell or burned PCB: Diagnose & Fix
- Fortinet FortiGate 60F smoke smell or burned PCB: Diagnose & Fix
- Fortinet FortiGate 80F smoke smell or burned PCB: Diagnose & Fix
- Fortinet FortiGate as SD-WAN router smoke smell or burned PCB: Diagnose & Fix
- Fortinet FortiAP 231F smoke smell or burned PCB: Diagnose & Fix
- Fortinet FortiAP 23JF smoke smell or burned PCB: Diagnose & Fix
References
- Fortinet support portal: https://support.fortinet.com
- Fortinet knowledge base: https://community.fortinet.com/
- Fortinet security advisories: https://www.fortiguard.com/psirt
- Open a case: https://support.fortinet.com/Information/MyAccount.aspx
Reference material, not professional advice. Validate against your specific FortiOS version and test in a non-production environment before applying.
Common patterns we see
When this symptom shows up on a Fortinet device, three patterns repeat:
1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger. temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.
Knowing which pattern applies saves time on the wrong fix.
Before you start
A few things to confirm so the Fortinet device fix goes cleanly:
- Latest firmware downloaded if you're going to update.
- Warranty + support contract status checked: opening sealed parts may void it.
- Backup of current configuration (where applicable) taken.
- Spare parts on hand if you anticipate replacement.
- Adequate workspace, lighting, and time, rushing causes regressions.
Quick verification
Before you walk away from a Fortinet device fix, run through:
1. Reproduce the original trigger. does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.
Escalation guide
For a Fortinet device, the right escalation depends on impact:
- Cosmetic / minor: log a ticket via the Fortinet app or web portal. Response 1-3 business days.
- Mid-impact: phone support. Have your serial number ready.
- Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
- Out of warranty: third-party repair shop with manufacturer-certified technicians.
More frequently asked questions
Why is this happening on a brand-new unit?
Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.
What if my model isn't exactly the same revision?
Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.
Is it safe to apply during business hours?
If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.
How long does this fix usually take?
Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.
Are there safer alternatives for non-technical users?
Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.
Topology deep dive
The FortiGate 70F is a desktop-to-1U next-gen firewall built around Fortinet's SoC4 ASIC. In the BFSI perimeter designs I run, these almost always live as an HA active-passive pair, FGCP cluster, so a single chassis fault should never be a site outage. The interface layout is port1-port10 GE, wan1/wan2, ha (dedicated), fed by single external 54V DC adapter.
The ASIC offload is the part people forget when troubleshooting hardware. Traffic that is NP6-Lite or NP6XLite offloaded never touches the CPU, so a 'CPU looks fine but packets drop' symptom often points at the NPU, not the control plane. Keep that in your head before you chase ghosts in top.
The HA heartbeat runs over dedicated ha links. When a member goes missing, the first question is always: did the box die, or did the heartbeat link die? Those are two completely different repairs and the CLI tells them apart in seconds.
Configuration walkthrough
Start with state capture, not a reboot. The order matters: get system status tells you the build and uptime, execute sensor list exposes PSU voltages, fan RPM and board temperatures, and diagnose hardware deviceinfo nic dumps per-port PHY status. On the FortiGate 70F, a fan reading 0 RPM or a 12V rail sagging below 11.4V on execute sensor list is your smoking gun.
If the box is part of an HA pair, run diagnose sys ha status before you touch anything. If the surviving member already promoted itself to primary, your fault is contained and you can work the dead unit at leisure during a window rather than in a panic.
# Baseline the hardware state
get system status
diagnose hardware sysinfo
diagnose hardware deviceinfo nic
# Power, fan and sensor telemetry
execute sensor list
diagnose hardware deviceinfo
# HA / cluster member health
get system ha status
diagnose sys ha status
# Collect everything for FortiCare TAC
execute tac report
Troubleshooting commands by platform
| What you are checking | Command (FortiOS CLI) |
|---|---|
| Build, serial, uptime | get system status |
| PSU / fan / temp sensors | execute sensor list |
| Per-port PHY / link | diagnose hardware deviceinfo nic port1 |
| Interface counters | get hardware nic port1 |
| HA cluster state | get system ha status |
| Crash log | diagnose debug crashlog read |
| Memory / conserve mode | diagnose hardware sysinfo memory |
| TAC bundle | execute tac report |
Two FortiOS-specific gotchas catch people. First, conserve mode: if diagnose hardware sysinfo memory shows the box wedged at high memory, FortiOS drops into conserve mode and starts failing sessions, which reads like a hardware fault but is not. Second, the crashlog, diagnose debug crashlog read on the FortiGate 70F will name the failing subsystem (npu, kernel, wad) if there was a real panic. Read it before you RMA; a software panic is a firmware ticket, not an RMA.
India compliance and deployment notes
For a BFSI perimeter box, the RBI cyber-security framework and the MeitY DPDP Act both push you toward logging discipline and clean change control, so do not skip the execute tac report capture even when you are confident, it is your evidence trail. Procurement-wise, public-sector and bank tenders run the FortiGate 70F through GeM, and the FortiCare/FortiGuard bundle is usually quoted separately on the BoQ. A typical hardware swap lands at Rs 32,000 to Rs 95,000 INR ($385 to $1,140 USD) if the unit is out of FortiCare; inside FortiCare advance replacement, your cost is the logistics, not the box.
One India-specific habit: confirm the unit is a MeitY-cleared / TEC-approved SKU before you RMA into a bank DC. I have watched a replacement get stuck at the DC security desk because the serial did not match the approved asset register. Raise the FortiCare RMA early, the advance-replacement courier from the Mumbai logistics hub to a Tier-2 town branch can take two to four working days.
A real fault I worked
I got a 6am call from a co-op bank branch aggregation site in Pune: the perimeter FortiGate 70F had dropped, and the branch network behind it was dark. The HA partner had not promoted, which already told me the heartbeat link, not just the box, was involved. On console, execute sensor list showed one fan at 0 RPM and the board temp climbing past 78C, the unit was thermally throttling itself into a reboot loop.
The real fix was boring and fast: the dead fan had let dust-caked heat build, and the HA cable had been re-routed during a recent rack tidy so the heartbeat was flapping. I forced the surviving member to primary with diagnose sys ha reset-uptime on the good box, restored service, then RMA'd the faulty FortiGate 70F under FortiCare. The replacement reached the Hyderabad site in two days. Moral: capture sensor and HA state first, because the obvious 'dead firewall' was really a fan plus a mis-cabled heartbeat.
More questions operators ask
Can I run this on a single (non-HA) FortiGate 70F?
Yes, but a standalone box means the repair is also the outage. For BFSI perimeter duty I never run these single; the marginal cost of a second unit is trivial next to one hour of a payments-switch being down.
How do I tell a firmware panic from a real hardware fault?
Run diagnose debug crashlog read. If it names kernel/wad/npu with a backtrace and the build is recent, it is a firmware ticket, open FortiCare and check the FortiGuard PSIRT before you RMA. Sensor faults (fan 0 RPM, sagging rails) are hardware.
Does opening the chassis void FortiCare?
For a PSU or fan that is field-replaceable on the FortiGate 70F, follow the FRU procedure. Cracking sealed boards yourself voids cover, raise an RMA and let advance replacement handle it.