[c-nsp] Tracking config changes

[Mark Wheadon]

If you have less than 20 devices. Cat Tools Freeware Edition is pretty 
good and it comes with a nice GUI that runs on Windows, you can schedule 
copy run starts and also get a report e-mailed to you of the differences 
in configuration.


On 25/05/2010 11:30, Youssef Bengelloun-Zahr wrote:
> Hello Mike,
>
> +1 for RANCID + SVN + DIFFED MAILS.
>
> Y.
>
>
>
> 2010/5/25 Frederic LOUI<frederic.loui at renater.fr>
>
>    
>> Hi Mike,
>>
>> RANCID +1
>> Besides what has been said so far...
>> Other alternatives to circumvent the problem. (If you still want to make
>> sure that you did not forget to save your config ...)
>> * On recent IOS, you can use EEM (Embedded Event Manager to trigger a
>> "write mem" when running-config is different than startup-config.
>> * On older platform, maybe the kron feature can be used to "write mem"
>>
>> Hope this help
>> Cheers/ Fred
>>
>> Mike a écrit :
>>
>>   Hi Gang,
>>      
>>> In my smallish network I am guilty sometimes of using cli to make cisco
>>> switch and router config changes, and sometimes I have been known to forget
>>> to 'wr mem' when I'm sure it's what I want. The reasons for this vary, but I
>>> want to be better than this disaster waiting for a power outage or other
>>> event to force a reset, losing something that could potentially be important
>>> that I may forget about later. I know there are approaches to this in larger
>>> envionments using config version control systems and such, but I think I
>>> want something simpler to at least notify me when/if I have a 'running
>>> config' that has been modified from the 'startup config' and not committed
>>> to nvram.
>>>
>>> One approach I might think of would be to poll the devices on my normal
>>> snmp schedule and include a check for the last date of configuration change.
>>> I could easilly throw an alert if it's been more than an hour since the last
>>> config change/write to memory, but I don't know which variables I would poll
>>> for that. A secondary idea might also be to download the configs and commit
>>> them to cvs anytime a change is detected, but some here might think this is
>>> backwards and that configs should only be uploaded? What do you other
>>> service provider folks do?
>>>
>>> Mike-
>>> _______________________________________________
>>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>>        
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>>      
>
>
>