[rancid] wrangling configs with RANCID (right for non-Cisco vendors?)

[Jethro R Binks]

On Thu, 19 Aug 2010, john heasley wrote:

> Wed, Aug 18, 2010 at 05:47:31PM -0700, Rogelio:
> > On Wed, Aug 18, 2010 at 5:36 PM, Ryan West <rwest at zyedge.com> wrote:
> > > A lot of non cisco devices are supported, what type of device are you trying to backup?
> > 
> > D-Link and BelAir wireless devices are some of what we have to
> > monitor.  Many more weird ones are on the Horizon.
> > 
> > Does RANCID allow you to monitor devices that don't easily output
> > their config?  (Some of these devices make you go into each directory
> > and type out a command that gives the status, but not in a format that
> > is copy/pastable)
> 
> none are currently supported.  as mentioned in a recent thread, its 
> possible that a script could, for example, tftp a config from a device, 
> copy that config to (or compile multiple tftp'd files int) 
> router.db_devicename.raw, then treat the like rancid does for the NOPIPE 
> option (see rancid.conf(5)).

Michael Stefaniuc wrote "wrancid" which allowed you to use an arbitrary 
script to obtain "a config", for rancid to work against.  I updated and 
tweaked it a bit, see the following for more details:

  http://sites.google.com/site/jrbinks/code/rancid/wraprancid

but beware: I haven't tested this in a long time, don't actually use it 
day to day currently, and don't remember that much about it :).

Jethro.

.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
Jethro R Binks, Computing Officer
Information Services, The University Of Strathclyde, Glasgow, UK

The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.