Managing IOS Configuration Snippets

Keegan Holley no.spam at comcast.net
Sat Mar 1 03:20:11 UTC 2014


On Feb 28, 2014, at 9:35 PM, Dale W. Carder <dwcarder at wisc.edu> wrote:

> Thus spake Keegan Holley (no.spam at comcast.net) on Fri, Feb 28, 2014 at 09:49:19AM -0500:
>> I wasn’t saying just fix it.  I was saying that router configs don’t lend well to versioning.  
> 
> Um, what?
> 
> $> rlog r-cssc-b280c-1-core.conf | grep 'total revision'
> total revisions: 2009;	selected revisions: 2009

I wish you were here to see my eyes rolling.. 2009 versions of something are no more grok-able than one current version.  Congrats, you have a config backup system.
> 
>> When it’s a router config chances are someone fat-fingered something.  Most of the time the best thing to do is to fix or at least alert on the error, not to record it as a valid config version. 
> 
> We have our operators manually check in revisions (think in rcs terms:
> co -l router, go do work, verify it, ci -u router) rather than
> unsolicited / cron-triggered checkins.  Then the check-in message
> contains the operator's description text of the change and often a
> ticket number.  So there slightly fewer fat-finger configs checked in.

That’s not what the OP was looking for AFAIK.  This is just change management.

> 
> Dale




More information about the NANOG mailing list