Catégorie
Operations & Fieldcraft
Tous les outils et articles de cette catégorie, rassemblés au même endroit.
Outils
Before/After Health Snapshot Comparator
You declare the states, the tool gates the conclusion: seven selections produce a tiered comparison report - baseline quality, a churn-classed dimension catalog, delta-interpretation guidance, and the continue / observe / investigate / hold-rollback-ready gate. Never labels a change successful on green components alone.
Change Blast-Radius Mapper
Describe what you are changing and its structure; a fixed rule set maps the blast radius as concentric tiers (target, co-located, downstream, human) populated with what could be affected, plus severity-tagged risks and containment measures. It maps what could be affected, never asserts what will break.
Change Window Runbook Builder
Describe a planned change in six structured fields; a fixed rule set assembles an ordered runbook across six phases - with the risks the plan carries and readiness cautions about the input. Advisory structure to review and adapt, never an approval.
Digital transformation tracker
Thirty milestones across seven domains, sorted by how much you should trust them: what shipped, what is already law, what is scheduled, what is scheduled but actively moving, and what is only somebody's forecast.
Fault Hypothesis Builder
Describe a fault in six structured fields; a fixed rule set ranks hypotheses to test - with the evidence to collect, what would support each, and what would weaken it. Advisory structure, never a diagnosis.
Flow Path Reasoner
The senior skill is refusing to troubleshoot until the path is understood. Seven selections build a canonical hop map with side-flows, TLS segments, rewrite points, and ranked failure-domain candidates - and unknowns stay visibly unknown.
Incident Timeline & RCA Builder
RCA stands for root cause analysis - the disciplined walk from an incident's symptoms back to the conditions that allowed it. Enter an incident's events as a small timeline and mark the contributing-factor domains you observed; a fixed rule set orders the timeline, derives the milestone spans, and structures candidate contributing factors with the evidence for each. It never names a root cause - candidates to investigate, not a verdict.
Network operating system comparer
Fourteen network operating systems — IOS, IOS XE, IOS XR, NX-OS, Junos, Junos Evolved, EOS, TMOS, F5OS, EXOS, VOSS, FortiOS, PAN-OS and Gaia — with lineage, what each runs on, how components share state, where the planes divide, and what an upgrade costs. Pick one for a full profile or two to see them axis by axis. Every entry lists weaknesses as well as strengths.
Packet Capture Plan Builder
Command builders answer how to capture; this answers where, why, and what it would mean. Describe the path and the symptom; a 35-rule original registry designs a phased capture plan: ranked points on named boundaries, expected observations, an interpretation matrix with supports and weakens decided before collection, and sync/authorization discipline. It plans captures - it never ingests them.
TAC Escalation Packet Builder
Describe the issue you are about to escalate; a fixed rule set assembles a complete vendor-support packet and a checklist of the artifacts still to collect before opening the case, dropping what you already have. It structures the hand-off; it does not open a case or contact any vendor.
Terminal, shell, TTY and console explainer
Paste what `tty` printed — /dev/pts/3, /dev/tty2, /dev/ttyS0, /dev/tty, /dev/console, or “not a tty” — and see which layer you are actually looking at, what is holding the other end, and what that implies for signals, job control and what happens when the window closes. Local and offline.
Articles
Terminal, shell, TTY, console
Four words used interchangeably by almost everyone, including the documentation. They name four different things, and the distinction explains why Ctrl+C kills your command but not your shell.
LireWhat a Channel Systems Engineer Actually Does
Inside a distributor there is a role almost nobody outside the channel can describe: the systems engineer who supports resellers rather than customers. Bill of materials work on every project that passes through, proofs of concept, presentations, enablement, bootcamps, trade shows. Some of the resellers being supported have no technical staff at all, which is the fact that explains the rest of the job.
LireWhat a network operating system actually is
IOS, Junos, EOS, TMOS, FortiOS, PAN-OS and the rest, compared on the axes that matter: what they run on, how components share state, where the planes divide, and what happens when one part fails.
LireThe path a product takes, and the jobs along it
Between the company that builds a thing and the person who depends on it, a product passes through many hands. Each pair belongs to a job with its own clients, suppliers, accountability and measurement — and the measurement is rarely the same as the accountability.
Lire