No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


This set of scripts connect to F5 devices using the SOAP iControl API to extract and store information about the virtual servers, pools, nodes, and iRules.


This requires Python 2.6 / 2.7. I don’t think the bigsuds library is compatible with Python 3.x. It also requires SQLite 3. That works with Python out of the box on RHEL 6 based distros for me.

Install the F5 bigsuds library (and it's requirements) with pip: pip install -r requirements.txt

On the F5 side, this should work with 11.x F5’s. Interacting with version 10 requires using different methods in bigsuds. There’s no reason it couldn’t be modified to work with 10.x, but I don’t use 10.x devices enough myself for it to be worthwhile.


./ <db_filename>
./ <db_filename> 	
./ <db_filename>
./ <db_filename>

The ltm_list variable in will need to be modified to include the FQDN's or IP addresses of the F5's you are wanting to scan. For example:

ltm_list = [ "", "", ""]

When the script is ran, it prompts for credentials, and then connects to each of the F5’s specified in the ltm_list array. By default, the admin user account is able to connect via iControl. The root account is not.

The load_ltm_data script rebuilds the database, and stores all of the partitions / virtuals / pools / etc that it finds. The search_by* scripts search the specified database and display each of the VIP’s that match, along with the related pools / etc. will display all of the VIP’s that the specified node is a part of. Here is an example output from one of the search scripts:

        VIP Name: /Common/READINGLIST-DEV
                Pool: /Common/VOYAGER-INTERNAL
                        - Member: /Common/VOYAGER-INTERNAL : 443
                                Node IP:
                        - Rule Name: /Common/READINGLIST-DEV-IRULE
                        - Rule Name: /Common/TEST2

You can search by either the full IP address, or a partial name (for instance "eading" would match the READINGLIST-DEV VIP in the output above). displays output similar to the output above, but for all objects in the database.