Multi-vendor path tracing: the hard parts
Tracing a packet across IOS, NX-OS, and PAN-OS means reconciling three different ACL syntaxes, two route table formats, and zero shared conventions.
Practical writeups on multi-vendor networks, fabric design, change detection, and the engineering behind running 13,000+ endpoints through one pipeline.
How stripping volatile fields and hashing the rest eliminates false-positive diffs — and why timestamp-based comparisons fail at scale.
Tracing a packet across IOS, NX-OS, and PAN-OS means reconciling three different ACL syntaxes, two route table formats, and zero shared conventions.
MAC tables, ARP, DHCP snooping, CDP/LLDP, 802.1X, and APIC hosts — stitched together in the right order, they replace a stale spreadsheet.
Configurable thresholds, cooldown windows, and atomic database operations keep your ACI fabric monitored even when controllers go down.
The operational pain that started SAMURAI — and the design decisions that let a single pane of glass replace Cisco Prime, Panorama, FMC, and SSH terminals.
Docker image pull, offline IEEE OUI database, and TLS certificate pinning — everything you need to run SAMURAI without internet access.
Deep dives on multi-vendor architecture, fabric design, change-detection algorithms, and the engineering behind SAMURAI.
~2 emails / month. Unsubscribe any time. No marketing nonsense.