[c-nsp] Tracking config changes

[Phou-Ngan Vannaxay]

Yes.
in your rancid.conf file, set FILTER_PWDS and NOCOMMSTR to YES or NO.

# FILTER_PWDS determines which passwords are filtered from configs by the
# value set (NO | YES | ALL).  see rancid.conf(5).
#FILTER_PWDS=YES; export FILTER_PWDS
#
# if NOCOMMSTR is set, snmp community strings will be stripped from the configs
#NOCOMMSTR=YES; export NOCOMMSTR



Le 28 mai 2010 à 13:53, Lee a écrit :

> On 5/24/10, Clayton Zekelman <clayton at mnsi.net> wrote:
>> 
>> 
>> We use RANCID on our network.  All changes are made through the CLI on the
>> routers/switches, and RANCID just tracks them.
>> 
>> If we have an outage where we have to re-build the router's config, we have
>> the versions and changes all stored nicely in the CVS.
>> 
>> All changes are e-mailed to our NOC list to make sure everyone knows what is
>> going on.
> 
> Does RANCID blank out SNMP community strings & Cisco type 5|7
> passwords before mailing out the diffs?
> 
> Work bought a product that grabs the configs after a change, does
> diffs, etc. but it apparently does NOT have the ability to blank out
> sensitive information before e-mailing the info so I'm looking for
> something else.
> 
> Thanks,
> Lee
> _______________________________________________
> 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/
>