diff options
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 48 |
1 files changed, 30 insertions, 18 deletions
@@ -1,31 +1,31 @@ -Frequently Asked Questions about rancid - last updated 20010926 +Frequently Asked Questions about rancid - last updated 20011121. 1) Platform specific Q. I have a Cisco Catalyst 6500 series switch running the IOS (NOT catOS) software, is the router.db device type cisco or cat5? -A. A catalyst running IOS is type "cisco". see the router.db(5) manual page. +A. A catalyst running IOS is type "cisco". See the router.db(5) manual page. Q. I have a Cisco ??? on which collection stopped working, but clogin works as expected. -A. Check if 'write term' produces output. Some IOS combinated with large - configs and low free memory produce zero 'write term' output. The device - will have to be rebooted. +A. Check if 'write term' produces output. Some IOS combined with large + configs and low free memory produce zero 'write term' output, esp. combined + with a memory leak. The device will have to be rebooted or upgraded. 2) CVS and filesystem permissions -Q. I am new to cvs, where can i find additional information? -A. The manual page for cvs is quite complete, but can be be overwhelming even - for someone familiar with rcs. There are some excellent resources on the - pages http://www.loria.fr/~molli/cvs-index.html +Q. I am new to CVS, where can I find additional information? +A. The manual page for CVS is quite complete, but can be be overwhelming even + for someone familiar with RCS. There are some excellent resources on the + web. See http://www.loria.fr/~molli/cvs-index.html Q. Errors are showing up in the logs like: cvs [diff aborted]: there is no version here; run 'cvs checkout' first A. The directory was not imported into CVS properly or was not properly checked out afterward, so CVS control files or directories do not exist. create_cvs should always be used to create the directories and perform the CVS work. - If it is just the directories have been created manually, save a copy of + If it is just the directories that have been created manually, save a copy of the router.db file, then remove the group's directory, use create_cvs, and replace the router.db file. If the CVS import was also performed manually, cd to <BASEDIR> and use 'cvs co <rancid group>' to create all the CVS @@ -33,14 +33,15 @@ A. The directory was not imported into CVS properly or was not properly checked Q. I keep receiving the same diff for a (or set of) devices, but I know the data is not changing repeatedly. Why? -A. This is most likely either a cvs or filesystem permissions problem. Check +A. This is most likely either a CVS or filesystem permissions problem. Check the log file from the last run for that group first; it may provide the exact cause. - note: it is very important the following be done as the user who normally + Note: It is very important the following be done as the user who normally runs the rancid collection from cron. Check the cvs status of the device's file. eg: + guelah [2704] cvs status rtr.shrubbery.net =================================================================== File: yogi.shrubbery.net Status: Up-to-date @@ -50,6 +51,7 @@ A. This is most likely either a cvs or filesystem permissions problem. Check Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) + The Status: should be Up-to-date. If the status is "Unknown", then somehow the file has been created without being cvs add'ed. This should be corrected by removing that device's entry from the group's router.db file, @@ -70,13 +72,14 @@ A. This is most likely either a cvs or filesystem permissions problem. Check 3) General -Q. I have a (set of) device(s) on which collection fails. How can i debug +Q. I have a (set of) device(s) on which collection fails. How can I debug this? A. Our usual diagnostic procedure for this is: - Make sure that the appropriate *login (eg: clogin for cisco) works. This tests to make sure you don't have routing or firewall issues, DNS - or hostname errors, that your .cloginrc is correct, and that the *login - script doesnt have a bug of some sort. For example: + or hostname errors, that your .cloginrc is correct, your banner does + not have some character that *login does not like, and that the *login + script doesn't have a bug of some sort. For example: clogin cisco_router @@ -106,9 +109,18 @@ A. Our usual diagnostic procedure for this is: If all of these work, make sure that the device's entry in the group's router.db file is correct and check the group's last log file for errors. -Q. I'm still stuck on this problem. Where can i get more help? +Q. Are there any characters in the banner that rancid has problems with OR + I changed the device's command prompt? +A. The trickest part about clogin (et al) is recognizing the prompt + correctly. clogin looks for '>' and '#' to figure out if it is logged + in or in enable mode. So if you have a '>' or '#' in your login banner + (other other motd), then clogin gets all confused and will not be + able to log in correctly, and thus rancid will fail. + + Don't use '>' or '#' in your prompt or in your banner or other motd. + +Q. I'm still stuck on this problem. Where can I get more help? A. A discussion list is available, rancid-discuss@shrubbery.net. You must - be a subscriber to post. subscribe like this: + be a subscriber to post. Subscribe like this: shell% echo "subscribe" | mail rancid-discuss-request@shrubbery.net - |