[rancid] F5 BIG-IP devices - any tricks?

[Colin Stubbs]

Patch attached for 2.3.8.

It uses `bigpipe version`'s response to determine if it should use
tmsh or not, and switches command table as appropriate.

So it will only use tmsh on a BIGIP v11 F5, as they respond like this,

[root at localhost:] ~ # bp version
/usr/bin/bp: bigpipe is no longer supported; please use tmsh.
[root at localhost:] ~ #

This should keep things the same for existing users and avoid
unexpected config diff after upgrade.

Tested against,

bigip1.f5.routedlogic.net:#Sys::Version
bigip1.f5.routedlogic.net-#	Main Package
bigip1.f5.routedlogic.net-#	  Product  BIG-IP
bigip1.f5.routedlogic.net-#	  Version  10.2.3
bigip1.f5.routedlogic.net-#	  Build    112.0
bigip1.f5.routedlogic.net-#	  Edition  Final
--
bigip2.f5.routedlogic.net:#Sys::Version
bigip2.f5.routedlogic.net-#	Main Package
bigip2.f5.routedlogic.net-#	  Product  BIG-IP
bigip2.f5.routedlogic.net-#	  Version  11.1.0
bigip2.f5.routedlogic.net-#	  Build    1943.0
bigip2.f5.routedlogic.net-#	  Edition  Final
--
bigip3.f5.routedlogic.net:#Sys::Version
bigip3.f5.routedlogic.net-#	Main Package
bigip3.f5.routedlogic.net-#	  Product  BIG-IP
bigip3.f5.routedlogic.net-#	  Version  10.1.0
bigip3.f5.routedlogic.net-#	  Build    3341.1084
bigip3.f5.routedlogic.net-#	  Edition  Final


-Colin


On 2 May 2012 00:05, Lance Vermilion <rancid at gheek.net> wrote:
> A new device type setting would be the static method otherwise a version
> check would be needed for dynamic.
>
> Simply run a bigpipe command  and if the response is not what we expect run
> tmsh and if that fails exit with a failure for that node.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rancid-2.3.8-f5rancid.in.patch
Type: application/octet-stream
Size: 7324 bytes
Desc: not available
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20120506/5cce567f/attachment.obj>