guides
Instructions that have to actually work
For us a guide means a reproducible procedure with commands, verification and a rollback — not a general overview. That is why the first ones are validated in the lab before they are published.
format
A guide and an article do different jobs
- A guideAnswers "how"
- A reproducible procedure: starting state and prerequisites, commands exactly as they must be run, the output you should see, a verification step and a rollback. If you cannot reproduce it in a lab, that is our defect.
- A knowledge-base articleAnswers "why"
- Architectural context: which decision is taken, at what trade-off, where the approach breaks and why we work this way. It does not replace commands — it explains why those commands are the right ones.
If what you need right now is context rather than commands, go to the knowledge base.
catalogue
Published guides
first guides in preparation
The catalogue is empty because we do not publish half-checked procedures: until a procedure has been run end to end in the lab and its rollback verified, it does not appear here.
In the meantime, technical articles on the same subjects are already published in the knowledge base.
planned
What the first guides will cover
This is a working plan, not published material. The order may change — a topic reaches the catalogue only once its procedure has been verified.
01
A BGP session with RPKI validation
From publishing the ROA to standing up a validator and verifying the prefix filter — with commands and the output you should see.
02
Flow export from an edge router
Enabling sFlow/NetFlow export, standing up the collector and getting the first genuinely useful view of traffic.
03
An EVE-NG lab for a migration test
Rebuilding the topology, running failure scenarios and rehearsing a repeatable rollback before production.
04
An alert that means something
From choosing the metric to thresholds and escalation: how to write an alert that is worth being woken up for.