{"id":776,"date":"2011-08-15T11:20:27","date_gmt":"2011-08-15T16:20:27","guid":{"rendered":"http:\/\/it.thelibrarie.com\/weblog\/?p=776"},"modified":"2013-05-21T08:15:39","modified_gmt":"2013-05-21T13:15:39","slug":"rancid-ubuntu-10-04","status":"publish","type":"post","link":"https:\/\/it.thelibrarie.com\/weblog\/2011\/08\/rancid-ubuntu-10-04\/","title":{"rendered":"Rancid Ubuntu 10.04"},"content":{"rendered":"

Rancid stands for R<\/strong>eally A<\/strong>wesome N<\/strong>ew C<\/strong>isco confI<\/strong>g D<\/strong>iffer. It’s produced by Shrubbery Networks (http:\/\/www.shrubbery.net\/rancid\/<\/a>). Basically it’s sole purpose is to make backups of your networking gear. And it can email you of any changes as well. This documentation is a work in progress – I had attempted to setup a rancid server one other time, but ran out of courage shortly after the beginning. And I’m compiling based on a few other internet sources.<\/p>\n

Started with a 10.04.3 LTS server with LAMP\/Mail(postfix) installed. x86 for those who care. For those who don’t care, it’s still on an x86 system.<\/p>\n

I started installation, like all of my other projects, by switching to root:<\/p>\n

su<\/code><\/p><\/blockquote>\n

I also created the rancid user with a password:<\/p>\n

adduser rancid<\/code><\/p><\/blockquote>\n

Install the Rancid Base:<\/p>\n

apt-get install rancid<\/code>
\ny<\/code>\n<\/p><\/blockquote>\n

Edit the Rancid Configuration by adding groups:<\/p>\n

nano \/etc\/rancid\/rancid.conf<\/code>
\nLIST_OF_GROUPS=\"Group1 Group2 ... Group18\"<\/code>
\nSave and Quit<\/p><\/blockquote>\n

Edit the Mail Aliases:<\/p>\n

nano \/etc\/aliases<\/code>
\nrancid-Group1: root<\/code>
\nrancid-admin-Group1: root<\/code>
\nrancid-Group18: root<\/code>
\nrancid-admin-Group18: root<\/code>
\nSave and Quit<\/p><\/blockquote>\n

Restart Your Mail Services:<\/p>\n

\/etc\/init.d\/postfix restart<\/code><\/p><\/blockquote>\n

Run rancid CVS Groups:<\/p>\n

sudo su -c \/var\/lib\/rancid\/bin\/rancid-cvs -s \/bin\/bash -l rancid<\/code>
\nYou should now see a few new directories created in \/var\/lib\/rancid:
\n\/Group1
\n\/Group2
\n…
\n\/Group18<\/p><\/blockquote>\n

We want to edit the configuration files in each of these groups to reflect the devices. We’ll start with \/Group1:<\/p>\n

cd \/var\/lib\/rancid\/Group1<\/code>
\nnano router.db<\/code>
\nIPADDRESS_OR_HOSTNAME:brand:up_or_down<\/code>
\nIf you select down, rancid will not actively check this device.
\nExample:
\n10.10.0.1:cisco:up
\n10.15.0.1:cisco:up
\n10.20.0.20:cisco:up<\/p><\/blockquote>\n

At one time, whilst setting this up for the first time, I thought that you could only have one login\/enable for the entire system. I found that quite “uncool”. Luckily for everyone reading this, I found out that I was incorrect with my assumption. It’s actually quite easy now that I look back on the configuration.<\/p>\n

Create A Password File:<\/p>\n

The installation of rancid on ubuntu will attempt to create a user called “rancid” with a home directory of \/var\/lib\/rancid, but a login point of \/dev\/null. But, since we already created the “rancid” user, we must create a cloginrc file to house the passwords for your cisco gear in this user’s home directory. If you run this as root, it’ll be in \/root\/.clogin.rc<\/u>
\nnano \/home\/rancid\/.cloginrc<\/code>
\nadd method * telnet<\/code>
\nadd password IPADDRESS_OR_HOSTNAME LOGINPASSWORD ENABLEPASSWORD<\/code>
\nadd password OTHERIP_OR_HOSTNAME LOGINPASSWORD ENABLEPASSWORD<\/code>
\nSave and exit<\/p><\/blockquote>\n

For SSH:<\/p>\n

add autoenable * 1<\/code>
\nadd method IPADDRESS ssh<\/code>
\nadd user IPADDRESS USERNAME<\/code>
\nadd userpassword IPADDRESS PASSWORD
\nadd password IPADDRESS PASSWORD ENABLEPASSWORD<\/code><\/p><\/blockquote>\n

Change permissions of the password file (isn't necessary now that I created the user to begin with):<\/p>\n

chmod 640 \/var\/lib\/rancid\/.cloginrc<\/code>
\nchown rancid \/home\/rancid\/cloginrc<\/code><\/p><\/blockquote>\n

Run the rancid server:<\/p>\n

sudo su -c \/var\/lib\/rancid\/bin\/rancid-run -s \/bin\/bash -l rancid<\/code><\/p><\/blockquote>\n

View the Log Files:<\/p>\n

nano \/var\/log\/rancid\/GROUPNAME.DATE.TIME<\/code>
\n\"\"<\/a>\n<\/p><\/blockquote>\n

Where Are The Configuration Files?<\/p>\n

\/var\/lib\/rancid\/CVS\/GROUPNAME\/configs\/IP_OR_HOSTNAME,v<\/code><\/p><\/blockquote>\n

Too Much Information:<\/p>\n

If you feel like you only want to have the configuration files and not the proc info\/mem info etc, just edit the following file:
\nnano \/var\/lib\/rancid\/bin\/rancid<\/code>
\nSearch for \"# Mail\"
\nComment out lines you no longer wish to document
\nSave and Quit\n<\/p><\/blockquote>\n

Add the Web GUI:<\/p>\n

apt-get install cvsweb<\/code>
\nnano \/etc\/cvsweb\/cvsweb.conf<\/code>
\nFind \"@CVSrepositories\"
\nAdd:
\n'rancid' => ['Rancid', '\/var\/lib\/rancid\/CVS'],<\/code>
\nSave and Quit
\nRestart apache
\napache2ctl restart<\/code>
\nsudo ~rancid\/bin\/rancid-run<\/code> (or, if in as root, rancid-run<\/code>)
\nYou can now open a web browser to http:\/\/IPOFSERVER\/cgi-bin\/cvsweb<\/p><\/blockquote>\n

EMail testing
\nI am having a few issues with email aliases - you're supposed to be able to utilize \"rancid-NAMEOFDEVICE: real email\" or the like for it to forward. I was getting NDRs as it was trying to send locally. So I temporarily changed the NDR to all send to the email address I wanted to send anyway.<\/p>\n

Cron job
\nI cron this for every 10 minutes - but it takes longer and longer to check all the devices on the network when I keep adding more and more to the configuration. <\/p>\n

Sample Configuration (\/home\/rancid\/.cloginrc):<\/p>\n

add method 10.15.1.245 telnet
\nadd method 10.15.1.246 telnet
\nadd method 10.11.0.2 ssh
\nadd user 10.11.0.2 rancid
\nadd userpassword 10.5.0.2 P@SSw0rd
\nadd password 10.15.1.246 P@55 3n@bL3
\nadd password 10.15.1.245 P@55 3n@bL3
\nadd password 10.11.0.2 P@SSw0rd 3n@bL3<\/p><\/blockquote>\n

***EDIT***
\nSometimes I'm a little slow when it comes to problems with workarounds - I mean, why fix something when it's only halfway broken?
\nI forgot that when you edit the \/etc\/aliases file that you have to run the command newaliases to update the \/etc\/aliases.db file. Otherwise you'll see \"warning: database \/etc\/aliases.db is older than source file \/etc\/aliases\" in your \/var\/log\/mail.info file. And away we go!<\/p>\n

***EDIT 2***
\nIf you put in hostnames instead of IP addresses (preferred method as it makes it easier to find in the list later), it's recommended to add static address aliases instead of relying on DNS.
\nnano \/etc\/hosts
\nIPADDRESSOFDEVICE NAMEOFDEVICE NAMEOFDEVICE.DOMAIN.TLD
\nPing the name of the device and verify you have resolution.<\/p>\n

Also, I found that rancid HATES capital letters. Recommended that everything be lowercase. ESPECIALLY in your .clogin file!!! I found this out with tail -45 \/var\/log\/rancid\/LATESTFILEHERE<\/p>\n

And, if you follow my above installation procedure, you will find the main page loads without any icons. I sorted this out by the following:
\nmkdir \/var\/www\/icons<\/code>
\nnano \/etc\/apache\/sites-enabled\/000-default<\/code>
\nFind Alias \/doc\/ \"\/usr\/share\/doc\/\"
\nAdd the following below it
\nAlias \/cvsweb\/icons\/ \"\/var\/www\/icons\/\"<\/code>
\nSave and quit
\napache2ctl restart<\/code>
\nLoad the dir.gif, back.gif, and text.gif files of your choosing into the \/var\/www\/icons directory
\n