BigIP Report Old
Problem this snippet solves:
This codeshare has been deprecated due to a hosting platform corruption. I have moved code and conversation to a new record (on the same original URL) https://devcentral.f5.com/s/articles/bigip-report
can be Overview
This is a script which will generate a report of the BigIP 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 our 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 guest permissions on your devices.
Demo/Preview
Please note that it takes time to make these so sometimes they're a bit outdated and they only cover one HA pair. However, they still serve the purpose of showing what you can expect from the report.
Interactive demo
http://loadbalancing.se/bigipreportdemo/
Screen shots
The main report:
The device overview:
Certificate details:
How to use this snippet:
This codeshare has been deprecated due to a hosting platform corruption. I have moved code and conversation to a new record (on the same original URL) https://devcentral.f5.com/s/articles/bigip-report
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).
Download: https://loadbalancing.se/downloads/bigipreport-v5.5.4.zip
Documentation, installation instructions and troubleshooting: https://loadbalancing.se/bigipreport-rest/
Docker support
This will be the recommended way of running bigipreport in the near future. It's still undergoing testing but it's looking really good so far.
https://loadbalancing.se/2021/01/05/running-bigipreport-on-docker/
BigipReport (Legacy)
Older version of the report that only runs on Windows and is depending on a Powershell plugin originally written by Joe Pruitt (F5).
BigipReport (Stable):
https://loadbalancing.se/downloads/bigipreport-5.3.1.zip
BigipReport (BETA): https://loadbalancing.se/downloads/bigipreport-5.4.0-beta.zip
iControl Snapin: https://loadbalancing.se/downloads/f5-icontrol.zip
Documentation and installation instructions:
https://loadbalancing.se/bigip-report/
Upgrade instructions
Protect the report using APM and active directory
Written by DevCentral member Shann_P:
https://loadbalancing.se/2018/04/08/protecting-bigip-report-behind-an-apm-by-shannon-poole/
Got issues/problems/feedback?
Still have issues? Drop a comment below. We usually reply quite fast. Any bugs found, issues detected or ideas contributed makes the report better for everyone, so it's always appreciated.
---
Also trying out a Discord channel now. You're welcome to hang out with us there:
Code :
85931,86647,90730
Tested this on version:
13.0
Hi!
- If you open the javascript console of your browser do you see any errors?
- Have you copied over the files from the web files directory (included in the zip file)?
- Do you get any error message from IIS?
Also could be worth double checking the security permissions on the web directory to ensure that the user has access to it.
/Patrik
- leo_graellsNimbostratus
Hello, Your script seems to be awesome. I have a problem when executing it with 1826 line :
PS E:\wamp64\www> .\bigipreport-4.6.9.ps1 Vous devez fournir une expression de valeur à droite de l'opérateur « - ».Au niveau de E:\wamp64\www\bigipreport-4.6.9.ps1 : 1826 Caractère : 57+ $ruleScope = $Global:irules | Where-Object { $_.name - <<<< in $Bigipreportconfig.Settings.iRules.iRule.iRuleName -and $_.loadbalancer -in $Bigipreportconfig.Settings.iRules.iRule.loadbalancer } + CategoryInfo : ParserError: (:) [], ParseException + FullyQualifiedErrorId : ExpectedValueExpression
Thanks for your help !
- Munawar_Khan_34Nimbostratus
Hi Patrik, I cannot able to see the complete report. Attached error snapshot.
@Leo - Thanks for reporting. I don't believe that I have tested without iRule links in a while. Will get back to you.
@Munawar, the error you see is probably not the cause. Could you please do the following?
- Start up a command prompt and go to the web root of your IIS server. Default is C:\inetpub\wwwroot (to enter that directory, issue the command "cd C:\inetpub\wwwroot").
- When you're in that directory, issue this command "dir /s".
- Paste the output here.
/Patrik
Leo, I tried to disable the iRule links and it worked as expected. Which version of TMOS are you running?
Try following the set-up guide (https://loadbalancing.se/bigip-report/) and minimize the configuration file changes?
Please report back when done? :)
- leo_graellsNimbostratus
@Patrik,I've already followed your set-up guide, I'm running with BIG-IP 11.6.1 Build 2.0.338 Hotfix HF2 TMOS version.
What do you expect with "I tried to disable the iRule links and it worked as expected" ?
Thanks you
- Munawar_Khan_34Nimbostratus
Hi, Patrik, Attached is the results
@Leo, what I meant was that I figured that you'd configured the report to now show iRule links since the section you referred to is activated when you do. But if you didn't the issue must be somewhere else. What's your powershell version (enter $PSversiontable in the powershell window)?
@Munawar, it's almost as if you don't have anything configured in your BigIP. Are you running the LTM module on it? Is the powershell script really finishing without any errors?
@Munawar, sorry but I have to ask this as well. Double check that you've configured any load balancer IP's in the config file?
@Leo, I would also like to ask, is the script failing straight away? As in refusing to load at all, or do you get the pre-execution checks?
I tested the script against an 11.6.1 device just now and it worked fine.
/Patrik