$BASEDIR/<group>/router.db
Configuration file described here, where <group> is a device group name defined in the variable LIST_OF_GROUPS within $BASEDIR/etc/rancid.conf.
Rancid group configuration file
One device is listed per-line, where the syntax is:
<device_name>;<device_type>;<state>[;comments]
For example:
scooby.shrubbery.net;cisco;up
The fields are as follows:
<device_name>The name of the device, which must resolve via gethostbyname , used as the argument to telnet(1), rsh(1), or ssh(1), to connect to the device. Once converted to lower-case, this also becomes the name of the file used to store the configuration under $BASEDIR/<group>/configs.
Experience has shown that using the device's FQDN (Fully Qualified Domain Name) works best, as in the example above.
<device_type>The type of device from the set:
agmA Cisco Anomaly Guard Module (aka Riverhead). Suspect that at some point the UI will become more cisco-like and it can be merged with the IOS rancid module.
alteonAn Alteon WebOS switches.
arcosAn Arrcus router.
aristaAn Arista Networks device.
baynetA Bay Networks router.
bigipA F5 device running BIG-IP >= v11.
cat5A Cisco catalyst series 5000 and 4000 switches (i.e.: running the catalyst OS, not IOS).
ciena-wsA Ciena Waveserver.
ciscoA Cisco router, PIX, or switch such as the 3500XL or 6000 running IOS (or IOS-like) OS, but not IOS-XR, NX-OS or Cisco small business devices.
cisco-sbA Cisco small business devices.
cisco-nxA Cisco Nexus switch/router.
cisco-xrA Cisco device running IOS-XR.
cisco-wlc4A Cisco Wireless Controller versions up to 4.
cisco-wlc5A Cisco Wireless Controller versions 5 and above.
cssA Cisco content services switch.
enterasysAn enterasys NAS. This is currently an alias for the riverstone device type.
erxA Juniper E-series edge router.
fss2A Fujitsu FSS2/1finity device.
dellA Dell switch. Known working models are DES-3010F, DES-3052P, DES-3526, and DES-3550. Note that Dell OEMs some equipment and has purchased some companies, so a Dell product may not work with the dell rancid module but may work with smc or force10.
extremeAn Extreme switch.
ezt3An ADC-Kentrox EZ-T3 mux.
f5A F5 BigIP switch.
force10A Force10 router.
fortigateA Fortinet firewall.
fortigate-fullA Fortinet firewall with all defaults shown.
foundryA Foundry router, switch, or router-switch. This includes HP Procurve switches that are OEMs of Foundry products, such as the HP9304M.
hitachiA Hitachi router.
hpA HP Procurve switch such as the 2524, 4108 or J9086A (aka. 2610) procurve switches, J9091A, and J8698A. Also see the foundry type.
juniperA Juniper router.
mrtdA host running the (Merit) MRTd daemon.
mrvA MRV optical device; including NC316, OptiSwitch 904, OptiSwitch 906G, OptiSwitch 912C, OptiSwitch 940.
netscalerA Netscaler load balancer.
netscreenA Netscreen firewall.
paloaltoA Palo Alto Networks device.
redbackA Redback router, NAS, etc.
riverstoneA Riverstone NAS or Cabletron (starting with version ~9.0.3) router.
routerosA Mikrotik RouterOS router.
smcA SMC switch, which also account for some Dell OEMs. Including Dell PowerConnect 35xx (3524, 3524P, 3548, 3548P) and 7048.
srosA Nokia (Alcatel-Lucent) router, such as the 7750 SR.
xirrusA Xirrus array.
zebraZebra routing software.
<state>The state is either "up", or some other arbitrary value, e.g. "down". If the device is not marked "up" the device's configuration will not be collected. It is highly recommended that comments are made for any router not listed as up, so as to indicate the reason a router is not to be polled, e.g.:
dial1.paris;cisco;up;
core1.paris;cisco;down;in testing until 5/5/2001.
core2.paris;cisco;ticketed;Ticket 6054234, 5/3/2001
border1.paris;juniper;up;
The script "downreport" in util/ can be used to produce a report of routers in router.db that are not marked "up".
[comments]Freeform string to describe the current state of the router.
A ``#'' at the beginning of a line is a comment; the entire line is ignored.
If a device is deleted from the router.db file, then rancid will clean up by removing the device's config file from $BASEDIR/<group>/configs. The device will be removed from the revision control system. It is possible, in most cases, to resurrect or check-out copies of deleted device configurations.
router.db contains information for devices which are members of a rancid group. control_rancid(1) reads this file to compile a list of devices which it should collect.
$BASEDIR/<group>/router.db
Configuration file described here, where <group> is a device group name defined in the variable LIST_OF_GROUPS within $BASEDIR/etc/rancid.conf.
9 releases since Debian 5.0 (Lenny); the text changed 5 times.