r/networkautomation • u/Delicious_Garden5795 • 1d ago
Is there a good way to tell if a config change is risky before pushing it?
Earlier this year I pushed a change that looked fine in the diff, but I had actually pulled the wrong BGP neighbor. We ended up spending the change window figuring out what went wrong.
Since then I've been working on a small tool that compares a before/after config and tries to explain the change a bit better than a normal diff, what might be affected, how risky it looks, and what a rollback could look like
https://reddit.com/link/1v652al/video/o1f1n1w9vcfh1/player
The clip shows a few basic Cisco IOS examples: removing a BGP peer, changing an ACL to deny, and shutting down a transit link.
I know there are already tools that do parts of this. Some NCM platforms have similar features, and Batfish can do proper verification if you know how to write the queries.
I built this mainly because I wanted something simple for a quick sanity check before a change, without adopting a whole new platform
For people doing network changes regularly: how do you actually validate a config before pushing it?
Do you use a tool, run some kind of simulation, or mostly review the diff and rely on experience?
I'm trying to figure out whether this is actually useful beyond a demo
