Notes from real deployments
The configs, the gotchas, the upgrade that went sideways at 2 a.m. People describing what they actually run, including the part where it broke and what they'd do differently now.
The DiagDebug network
A Fortinet community run by the people who get paged.
Local chapters for engineers who run this gear for a living. Each one is led by a practitioner, signs up to the same three trust rules, and answers to the people in the room instead of to somebody's pipeline number.
The name is diag debug, the first thing you type when something's on fire. If you know, you know. If you don't, come anyway.
What this is
What you actually get out of it.
Access to Fortinet product teams
Chapters that want it get a line to Fortinet product and engineering. Roadmap context, early looks, and somewhere to put feedback so it reaches the people building the thing instead of a support queue.
Practitioner-run agenda
Practitioners pick the topics and the speakers at every chapter. Talks are technical. If one starts drifting into a pitch, members say so and the chair handles it. Who runs it →
Who it's for
Practitioners.
If you touch a FortiGate, a FortiAnalyzer, or a support ticket about one, you're in the right place.
Titles matter less than whether you've had to fix this stuff at an inconvenient hour.
- Network engineersRunning FortiGate at the edge, in the data center, or across a sprawl of branch sites.
- Security architectsDesigning segmentation, SD-WAN, and Fabric integrations that have to survive an audit.
- MSP and MSSP engineersManaging dozens of tenants and every firmware version that ever shipped.
- Cert candidatesWorking the NSE and Fortinet Certified tracks, looking for study partners who've actually done the labs.
- IT directors and managersRunning Fortinet environments and the teams that keep them up. Here for roadmap, staffing, and what's coming.
Chapters
Find your metro.
Pulled straight from the directory. Active chapters are holding events. The forming ones are still looking for a chair and a few founding members.
DiagDebug is an independent, practitioner-led community and is not affiliated with, sponsored by, or endorsed by Fortinet, Inc. Fortinet and FortiGate are trademarks of Fortinet, Inc., used here only to describe the community's shared area of practice.
No chapter in your metro yet?
If you run Fortinet and you'd show up to this, you're probably the person to start it. Here's what that takes.
Start a chapter