README
1Rancid patch to collect server network configuration
2
3* How it works
4
5 This is completely based on the idea and the code of Michael Stefaniuc :
6
7 http://www.shrubbery.net/pipermail/rancid-discuss/2005-November/001276.html
8
9 This patch creates a new type of network equipement called "server"
10 in Rancid. To use it, you need to declare your server in rancid
11 as any other equipements, and choose "server" as equipement type.
12
13 Rancid calls wrancid (a wrapper) to fetch the configuration on
14 the server. The wrapper starts another program (serverscript)
15 which :
16 - connects via ssh to the server
17 - starts a script on the server (called "parsenet")
18 Parsenet outputs the network configuration in an IOS-like format
19 Rancid records the output and versions it, as it woukd do with
20 any other equipement.
21
22 NB : you need to setup a trust relationship between the rancid
23 host and the server. We advise you to user a user with the least
24 priviledges on the server (ie. not root) and to only grant him
25 the rights to execute "parsenet" (via sudo for example).
26
27* Installation
28
29 * patch the rancid front-end script (rancid-fe) in the
30 rancid binary directory on your system : /usr/lib/rancid/bin
31 on Debian/Ubuntu, /usr/local/libexec/rancid on FreeBSD
32 (the patch is against Rancid 2.3.6) :
33
34 cd "your rancid binary directory"
35 patch -p1 < ~/netmagis/topo/rancid/rancid-server.patch
36
37 * copy the generic wrapper and the script called by the wrapper
38 in the same directory :
39
40 cp topo/rancid/wrancid topo/rancid/serverscript \
41 "you rancid binary directory"
42
43 * On each server you want to poll with rancid, install the
44 "parsenet" script in /usr/local/bin
45