A configuration standard for a router estate
Every customer router audited against a standard the operator chose setting by setting, and a rollout in batches with a record of what changed where.
What we built
Three tools, and none of them changes anything. A health check for each router. An audit that reads 115 settings from each router, strips the secrets, and takes the most common value as the baseline, so the outliers show up as differences. And a generator that writes a change file for each site and a batch plan, without connecting to anything.
The operator chose the standard, setting by setting. We added one setting of our own, a keepalive on the management network, and said so.
How it holds up
The pilot site was changed and checked first. The next batch waits while any site is down for an unrelated reason, so a change window never overlaps an outage. Each applied batch drops out of the next audit, so the work left shrinks towards zero and every remaining difference has an owner.
Need something like this?
Tell us what you’re working on. You’ll get a straight answer on whether we’re the right firm for it.
Start a conversation