Yeah, you are right here. There is tooling that is able to dump all configs from network devices and compare it to docs and generate reports. I never had to use something like this, but seems usefull to enforce state of trust from documentation.. If deviation is detected, it have to be fixed right away.. And is even easy to blame who made deviation. You can use 'svn blame' from docs and access log from devices. In my small team (5 ppl) it was solved by saying: docs is the only source of trust, if you find deviation, docs telling the true. In case of complains, 'svn blame' + logs to the rescue. ---------- Original message ---------- From: Mns Nilsson via NANOG <nanog@lists.nanog.org> To: North American Network Operators Group <nanog@lists.nanog.org> Cc: Josh Reynolds <joshr@spitwspots.com>, Mns Nilsson <mansaxel@besserwisser.org> Subject: [NANOG] Re: The Network CLI -- Love it ? Hate it? Needed? Date: Wed, 19 Mar 2025 13:37:30 +0100
A *proposed* state or maybe even a snapshot of a particular time is more likely.
Documentation that deviates from reality will get ignored, forgotten and rejected. Treating it as plans and intents will work much better. We probably do that without reflecting over it already. Officially acknowledging it will only improve the process. -- M˙˙ns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE SA0XLR +46 705 989668 Xerox your lunch and file it under "sex offenders"!