iControl Ruby Library Updated to v10.2.0.2

Our Ruby iControl Library has been cooking here on DevCentral for six months now. We’ve received a lot of feedback on our first release from the DevCentral community. We’ve taken what we’ve learned from the alpha release, made a few improvements, and are now releasing our first stable version:

Here are a few of the fixes and enhancements we made with this release:

  • annoying SSL cert-depth message is now gone for good; you should no longer see the ‘at depth 0 - 18: self signed certificate’  error
  • fixed installation issues associated with letters in the 'verson' section of gemspec
  • updated iControl WSDLs

The new version should take precedence within Ruby Gems, but you probably want to remove the previous version just to prevent confusion. Here are the steps to update your version:

  1. Download the iControl Ruby Library Gem
  2. Uninstall the previous version
    gem uninstall f5-icontrol
  3. Install the new version
    gem install f5-icontrol-
  4. Verify the installed version
    % gem list -d | grep f5
    => f5-icontrol (
          Homepage: http://devcentral.f5.com/s
  5. Test your new installation by running the example code
    cd /var/lib/gems/1.8/gems/f5-icontrol- (location may vary based on system)
    ./get-version.rb admin admin
       => BIG-IP_v10.2.1

If everything went as planned, you should see your BIG-IP version without any SSL certificate errors. Another good test is to run the SSL certificate report (ssl-certificate-report.rb) against your BIG-IP. It is non-invasive and will test a number of compatibilities. Until next time, happy coding.

Published Jun 21, 2011
Version 1.0

Was this article helpful?


  • George_Watkins_'s avatar
    Historic F5 Account
    Hi Paul,



    That was a piece of code I was working on that shouldn't have been checked into SVN. My apologies. I will remove it for the time being and add it back in when it is finished.






  • Where has the ruby icontrol gem download moved to? All the links I can find on here are 404'ing. :-/