Agenda: exercises-rancid-2.txt

Advanced Registry Operations Curriculum
Using RANCID Part II

Notes:
------
* Commands preceded with "$" imply that you should execute the command as
  a general user - not as root.
* Commands preceded with "#" imply that you should be working as root.
* Commands with more specific command lines (e.g. "RTR-GW>" or "mysql>") 
  imply that you are executing commands on remote equipment, or within 
  another program.

Exercises
---------

0.      Become the RANCID user

        - Make sure you are the root user first. If not, then do:
        
        $ su -
        
        - To become the RANCID user do:

        # su -s /bin/bash rancid

1. Note the IP addresses for the routers

        192.168.5.129 for group 1 or 192.168.5.161 for group 2

2. Update /var/lib/rancid/.cloginrc

        Change the file to look like this:

        $ vi /var/lib/rancid/.cloginrc

        add user 192.168.5.* admin
        add password 192.168.5.* GTcctld! GTcctld!

        (This tells RANCID that all hosts called "192.168.5.*" use the
        same password and user -- no need to add every router by hand!)

3. Update the router.db

    $ vi /var/lib/rancid/all/router.db

        Add our other classroom router to the file. You should end up with:

        192.168.5.129:cisco:up
        192.168.5.161:cisco:up

        (Note that "cisco" means this is Cisco equipment -- it tells Rancid
        that we are expecting to talk to a Cisco device here.  You can also
        talk to Juniper, HP, ...)

4. Run rancid again:

        $ /usr/lib/rancid/bin/rancid-run

        (Should take a few seconds)

5. Check out the logs:

        $ cd /var/lib/rancid/logs
        $ ls -l

        ... View the contents of the file:

        $ more all.*

6. Look at the configs

        $ cd /var/lib/rancid/all/configs
        $ more 192.168.5.1*

        - If all went well, you can see the configs of ALL routers

7. Change the configuration on the router (change the description on
    an interface, for example)

8. Run rancid again

        $ /usr/lib/rancid/bin/rancid-run

9. Play with clogin:

        $  /usr/lib/rancid/bin/clogin -c "show clock" 192.168.5.129 192.168.5.161

- What do you notice ?


10. Add the RANCID CVS repository in to CVSweb

        - First we install CVSweb:

        # apt-get install cvsweb

11. Edit the file /etc/cvsweb/cvsweb.conf

        # vi /etc/cvsweb/cvsweb.conf

        - Change the line:

'local'   => ['Local Repository', '/var/lib/cvs'],

        to

'nagios3' => ['AROC Nagios', '/home/sysadmin/cvs'],

        - Save and exit

12. Fix a link:

        # cd /var/www
        # ln -s /usr/share/cvsweb .
        
        - Edit the file /etc/cvsweb/cvsweb.conf:

        # vi /etc/cvsweb/cvsweb.conf

        - Either above or below the line:

'nagios3' => ['AROC Nagios', '/home/tldadmin/cvs'],

        add a new line that reads:

'rancid'   => ['Rancid Repository', '/var/lib/rancid/CVS'],

        - Save and exit

        - Open a web browser to the link:

        http://MyMachine/cgi-bin/cvsweb/

          and select between the RANCID and the AROC Nagios3 configuration files CVS
          repositories in the CVS Root drop-down list.