rwest at zyedge
May 1, 2012, 1:25 AM
I have tested on v11 and v10..x boxes and the tmsh commands work on both. I don't have anymore 9.x to work with, so I think just having a working tmsh example should do the trick. Not sure if you caught my email to John Heasley, but it seems the last function before the commandtable is broken. Just clearing that up should be enough to do a little testing. Let me know if you need anymore information.
From: Colin Stubbs [mailto:cstubbs [at] gmail]
Sent: Tuesday, May 01, 2012 3:59 AM
To: Dale Shaw
Cc: Ryan West; rancid-discuss [at] shrubbery
Subject: Re: [rancid] F5 BIG-IP devices - any tricks?
Hmm, looks like gmail is spam dropping some of this list for me. This is the first email that came thru re: this subject :-(
Given I wrote the first patch I'm happy to get cracking on updating it. I have actually already been doing various things related to that due to working with BIGIP v11.
There's a bit that needs to change for v11 - anyone else on the list using it yet and need to monitor devices with it ? bigpipe command will no longer work and TMSH command syntax is sufficiently different to bigpipe that they're basically different device types. Would need fork f5rancid into two different types, provide a configuration option to specify version, or auto-detect v11 or < v11 and use a different command set based on that.
cstubbs @ gmail . com [smtp, g+, fb, msn]
Phone: +61 468 311 061
Pub Key ID: 0xC857AC24
On 1 May 2012 15:31, Dale Shaw <dale.shaw+rancid-discuss [at] gmail> wrote:
> On Sat, Apr 28, 2012 at 10:30 PM, Ryan West <rwest [at] zyedge> wrote:
>> The link that was provided earlier by Matthew seems promising. I was able to run all commands on both v10 and v11 devices. > The patch, however, did not apply properly against a 2.3.8 build and my attempts to manually input the lines worked except for this routine, where it fails at the end:
>> Here is the link to the full changes. If anyone can tell me how to fix the last line, I should be able to quickly test it against v11 and v10 devices that we monitor.
> Concur; patch as displayed in blog post seems broken. Link to .diff
> 404's. Cc'ing the blog owner.
> Happy to help test this in our small environment (4 x LTMs running
> BIG-IP 10.1.0 3341.0).
Rancid-discuss mailing list
Rancid-discuss [at] shrubbery