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
Real configs, real upgrades, and real fixes from engineers running the same gear you are. Free to attend, technical by default, and no sales pitches.
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
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.
Chapters can bring in Fortinet product and engineering people for roadmap context, early looks, and a place to put feedback so it reaches the people building the thing instead of a support queue.
The engineer two exits up the freeway who already fixed the thing you're fighting. Local leaders pick the topics and speakers, and every session stays technical. Who runs it →
Who it's for
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.
House rules
Sessions are technical. Pricing, pitches, and recruiting stay out of the room, whoever is presenting.
Attendee lists are never handed to sales teams, sponsors, or recruiters, Fortinet's included.
The rest is in the network policies and the code of conduct.
Chapters
Pulled straight from the directory. Active chapters are holding events. Forming ones are looking for local leaders.
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