[f-nsp] using

[joshua sahala]

On (02/10/04 22:08), Niels Bakker wrote:
> 
> * Bruce.Rodger at strath.ac.uk (Bruce Rodger) [Fri 01 Oct 2004, 11:15 CEST]:
> [about rancid]
> > The only real problem I've found is that occasionally when retrieving
> > the config from a BigIron, the module serial number (as reported by
> > "show version") gets corrupted, so you occasionally get emails from
> > rancid saying the config has changed, with a corresponding email an
> > hour later saying it has changed back....
> 
> You get that too?

 i see it too, mostly on our ni1500's
 
> I can wholeheartedly recommend rancid.  Hook it up to a user with
> lowered privilege levels (one that can only execute "show" command),
> optionally write a script to watch syslog and tell rancid to get the
> config whenever a box logs that it's been changed.  You can't upload
> configs with it but it forms a good audit trail along with cvsweb.

 i too will add a recomendation for rancid :)

 you can push config changes with rancid, you just have to pre-write
 them (which could work with automated scripting), and then use the
 '-s' flag on flogin

/joshua
--