[rancid] Problem with some F5 devices
Alan McKinnon
alan.mckinnon at gmail.com
Mon Dec 2 14:43:24 UTC 2013
Your tests described below are quite sensible, but also incomplete
We know that clogin works on your f5 with a simple command
We know that clogin works on a vCMP with a simple command
We know that f5rancid works on your physical chassis
What we don't know is if clogin and f5rancid works correctly on a vCMP
using the full command set. There must be some difference between what
the physical chassis and the vCMPs sending back, otherwise both would
work. I suspect some part of the vCMP output is upsetting the f5rancid
script causing it to exit early.
You need the big troubleshooting guns (this process is almost always
what you need to do anyway if adding a device to router.db doesn't work
out):
1. Run this test in a temp directory (not the usual rancid dir) as the
rancid user
2. Pick a vCMP
3. Run "f5rancid -d <vCMP>"
4. This will give lots of screen output plus a new file with the full
text output from the device in the current directory
5. In the screen output will be the full clogin command used. Copy paste
that command and run it manually. Verify that the full command set works
as expected on a vCMP
6. Look inside the raw data file from step 3. Somewhere near the end I
expect to see error messages of some kind. Those errors will tell you
were we look next.
Note that "missed cmd(s)" and "End of run not found" messages are
useless for debugging purposes, they are catch-all output and only
indicate that something went wrong. They give no clue as to why.
On 02/12/2013 15:49, Michael Sloan wrote:
> I’m relatively new to using RANCID, although it has been in use for a
> couple of years in my (new) workplace. We have been using RANCID with
> Cisco and Juniper equipment, and I recently added some devices from
> Aruba and F5 to the list of devices being archived with RANCID.
>
>
>
> We have 4 separate F5 chasses doing load-balancing and reverse proxy,
> and these work flawlessly with RANCID (once I found an F5 script that
> supports version 11 of the F5 OS, anyway). On these chasses, we have
> several vCMPs for different clients. The vCMPs have their own IP, and
> respond to the same F5 commands that the chasses do.
>
>
>
> The files generated in the configs directory for the vCMPs are all
> zero-length files, even though the physical chasses produce 23k-47k
> files in the configs directory. I have verified that clogin works, and
> clogin –c “bigpipe version’ <F5-vCMP> does in fact produce the correct
> output. Running “f5rancid <F5-vCMP>” produces a 17k file in a test
> directory, so I know the process works for the vCMPs (see directory
> listings below).
>
>
>
> I have tried removing the entries for the vCMPs in router.db, started
> ‘run-rancid’, then added the entries back, and RANCID created
> zero-length files for the vCMPS a second time.
>
>
>
> We are using RANCID 2.3.6, on a CentOS 6 system, with Expect 5.43
>
>
>
> Has anyone encountered this problem or have any ideas how to resolve it?
>
>
>
> A typical logfile:
>
>
>
> Trying to get all of the configs.
>
> 10.255.128.146: missed cmd(s): tmsh show /net route static
>
> 10.255.128.145: missed cmd(s): tmsh show /net route static
>
> 10.255.128.147: missed cmd(s): tmsh show /net route static
>
> 10.255.128.148: missed cmd(s): tmsh show /net route static
>
> 10.255.128.152: missed cmd(s): tmsh show /net route static
>
> 10.255.128.151: missed cmd(s): tmsh show /net route static
>
> 10.255.128.153: missed cmd(s): tmsh show /net route static
>
> 10.255.128.154: missed cmd(s): tmsh show /net route static,tmsh show
> /sys hardware
>
> 10.255.128.155: missed cmd(s): tmsh show /net route static
>
> 10.255.128.157: missed cmd(s): tmsh show /net route static
>
> 10.255.128.156: missed cmd(s): tmsh show /net route static
>
> 10.255.128.158: missed cmd(s): tmsh show /net route static
>
> 10.255.128.159: missed cmd(s): tmsh show /net route static
>
> Getting missed routers: round 4.
>
> 10.255.128.148: missed cmd(s): tmsh show /net route static
>
> 10.255.128.145: missed cmd(s): tmsh show /net route static
>
> 10.255.128.147: missed cmd(s): tmsh show /net route static
>
> 10.255.128.146: missed cmd(s): tmsh show /net route static
>
> 10.255.128.151: missed cmd(s): tmsh show /net route static
>
> 10.255.128.152: missed cmd(s): tmsh show /net route static
>
> 10.255.128.153: missed cmd(s): tmsh show /net route static
>
> 10.255.128.156: missed cmd(s): tmsh show /net route static
>
> 10.255.128.154: missed cmd(s): tmsh show /net route static,tmsh show
> /sys hardware
>
> 10.255.128.155: missed cmd(s): tmsh show /net route static
>
> 10.255.128.157: missed cmd(s): tmsh show /net route static
>
> 10.255.128.158: missed cmd(s): tmsh show /net route static
>
> 10.255.128.159: missed cmd(s): tmsh show /net route static
>
>
>
> cvs diff: Diffing .
>
> cvs diff: Diffing configs
>
> cvs commit: Examining .
>
> cvs commit: Examining configs
>
> Checking in configs/10.255.128.143;
>
> /usr/local/rancid/var/CVS/other/configs/10.255.128.143,v <--
> 10.255.128.143
>
> new revision: 1.647; previous revision: 1.646
>
> done
>
> Checking in configs/10.255.128.144;
>
> /usr/local/rancid/var/CVS/other/configs/10.255.128.144,v <--
> 10.255.128.144
>
> new revision: 1.283; previous revision: 1.282
>
> done
>
>
>
>
>
> 10.255.128.145 and 10.255.128.146 are two of the physical chasses, while
> the IPs from .147 and above are vCMPs.
>
>
>
> My router.db file:
>
>
>
> 10.255.128.143:f5:up
>
> 10.255.128.144:f5:up
>
> 10.255.128.145:f5:up
>
> 10.255.128.146:f5:up
>
> 10.254.200.2:f5:up
>
> 10.255.128.147:f5:up
>
> 10.255.128.148:f5:up
>
> 10.255.128.151:f5:up
>
> 10.255.128.152:f5:up
>
> 10.255.128.153:f5:up
>
> 10.255.128.154:f5:up
>
> 10.255.128.155:f5:up
>
> 10.255.128.156:f5:up
>
> 10.255.128.157:f5:up
>
> 10.255.128.158:f5:up
>
> 10.255.128.159:f5:up
>
>
>
> And lastly, the directory listing for the configs directory:
>
>
>
> -bash-3.1$ ls -l
>
> total 592
>
> -rw-r----- 1 rancid netadm 470068 Dec 2 08:17 10.254.200.2
>
> -rw-r----- 1 rancid netadm 31335 Dec 2 08:17 10.255.128.143
>
> -rw-r----- 1 rancid netadm 27155 Dec 2 08:17 10.255.128.144
>
> -rw-r----- 1 rancid netadm 28406 Nov 5 09:33 10.255.128.145
>
> -rw-r----- 1 rancid netadm 23159 Nov 5 09:33 10.255.128.146
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.147
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.148
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.151
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.152
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.153
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.154
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.155
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.156
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.157
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.158
>
> -rw-r----- 1 rancid netadm 0 Nov 27 11:17 10.255.128.159
>
> drwxr-x--- 2 rancid netadm 4096 Dec 2 08:21 CVS
>
> -rw-r----- 1 rancid netadm 11256 Dec 2 08:18 wlc.nsrc.private
>
>
>
> And my test from ‘f5rancid 10.255.128.147’ in a temp directory:
>
>
>
> -bash-3.1$ ls -l
>
> total 20
>
> -rw-r--r-- 1 rancid netadm 17700 Dec 2 08:05 10.255.128.147.new
>
>
>
>
>
>
>
> Michael Sloan
>
> Systems Programmer Network Support
>
> Office: (850) 922-5476
>
> Northwood Shared Resource Center
>
> Michael.Sloan at nsrc.myflorida.com <mailto:Michael.Sloan at nsrc.myflorida.com>
>
>
>
>
>
>
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
>
--
Alan McKinnon
alan.mckinnon at gmail.com
More information about the Rancid-discuss
mailing list