BIG-IP Report

Problem this snippet solves:

Overview

This is a script which will generate a report of the BIG-IP LTM configuration on all your load balancers making it easy to find information and get a comprehensive overview of virtual servers and pools connected to them.

This information is used to relay information to NOC and developers to give them insight in where things are located and to be able to plan patching and deploys. I also use it myself as a quick way get information or gather data used as a foundation for RFC's, ie get a list of all external virtual servers without compression profiles.

The script has been running on 13 pairs of load balancers, indexing over 1200 virtual servers for several years now and the report is widely used across the company and by many companies and governments across the world.

It's easy to setup and use and only requires auditor (read-only) permissions on your devices.

Demo/Preview

Interactive demo

http://loadbalancing.se/bigipreportdemo/

Screen shots

The main report:

The device overview:

Certificate details:

How to use this snippet:

Installation instructions

BigipReport REST

This is the only branch we're updating since middle of 2020 and it supports 12.x and upwards (maybe even 11.6).

Updated Oct 16, 2024
Version 11.0
application delivery
devops
iControl
LTM
microsoft powershell with icontrol
  • LiefZimmerman's avatar
    LiefZimmerman
    Icon for Admin rankAdmin
    Apr 22, 2021

    Due to a platform corruption during the 2019 migration I have worked with   team to move his original legacy codeshare to this new record (same URL).

    The legacy codeshare is temporarily available at https://devcentral.f5.com/s/articles/bigip-report-old

     

    The negative repercussions of this change are:

    • the nearly 1000 historical comments appear that they must will have to remain on the legacy record.
    • the numerous *likes* stayed with the legacy record (smash that like at the top right of this page!! if you like it)
    • anyone bookmarking that legacy record will not be notified of changes made here (click that bookmark icon)

     

    The positive repercussions of this are:

    • Patrik can now make edits to the entry - making updates more likely and timely. (a deep in the weeds corruption I couldn't ferret out)
    • You all only have to deal with one set of comments here - making conversation easier. (another part of the corruption)
    • And, looking on the bright side of a negative, I don't have to find out (yet) what happens when the comment counter rolls over to 1000.😩

     

    Thank you for your patience and persistence with Patrik's awesome contribution and thank you for your dedication to our community.