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 compreh...
Updated Oct 16, 2024
Version 11.0
Mathieu_Cerfon1
Altostratus
AltostratusHi Patrik
Still have a small issue with the docker version of BigIP Report. It used to take around 5-6 minutes at each execution with a Windows VM Server.
Now it's dockerized, it can take 30 to 106 minutes to execute. Noticed that seems to block on those steps :
2023-09-20 11:19:18 <device_A:Caching nodes.5757715
2023-09-20 11:19:18 <device_B>:Caching monitors
2023-09-20 11:19:33 <device_A:Caching monitors77379
2023-09-20 11:21:35 <device_B>:Caching Pools.7717258
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 296.7917296
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 297.7953358
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 300.7993795
2023-09-20 11:21:54 <device_A:Caching Pools
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 301.8015409
2023-09-20 11:24:02 <device_A:Caching Policies00432
2023-09-20 11:24:17 <device_A:Caching datagroups965
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 463.0189142
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 464.0201473
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 465.021371
2023-09-20 11:24:49 <device_A:Caching iRules0349808
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 491.0570585
2023-09-20 11:25:06 <device_A:Caching profiles0633
2023-09-20 11:25:14 <device_B>:Caching Policies40969
2023-09-20 11:25:30 <device_B>:Caching datagroups032
2023-09-20 11:26:00 <device_B>:Caching iRules1423518
2023-09-20 11:26:16 <device_B>:Caching profiles61971
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 844.5591946
Wait: 0, Run: 2, Done: 6, Fail: 0, Time: 1010.7925092 31797
2023-09-20 11:39:16 <device_B>:Caching Virtual servers
2023-09-20 11:39:33 <device_A:Caching Virtual servers
2023-09-20 11:40:18 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:40:34 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:40:50 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:41:06 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:41:10 <device_B>:Detecting orphaned pools
2023-09-20 11:41:10 <device_B>:Stats: VS:311 P:307 R:44 POL:0 DG:5 C:10 M:199 ASM:0 T:1455.6709484
2023-09-20 11:41:23 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:41:28 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:41:43 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:41:58 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:42:00 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:42:15 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:42:33 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:42:48 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:43:07 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:43:26 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:43:41 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:44:00 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:44:10 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:44:24 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:44:42 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:44:57 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:45:15 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:45:17 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:45:36 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:45:49 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:46:08 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:46:24 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:46:40 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:46:55 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:47:14 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:47:30 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:47:46 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:48:03 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:48:16 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:48:33 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:48:48 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:49:03 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
Wait: 0, Run: 1, Done: 7, Fail: 0, Time: 1935.1637433
2023-09-20 11:49:19 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:49:22 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:49:42 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:49:55 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:50:14 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:50:33 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:50:49 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:51:05 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:51:20 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:51:36 <device_A:Polling policy reference information for /Common//<Random_ASM_Policy>
2023-09-20 11:51:54 <device_A:Detecting orphaned pools
2023-09-20 11:51:54 <device_A:Stats: VS:97 P:187 R:274 POL:16 DG:61 C:26 M:57 ASM:99 T:2099.2386718
2023-09-20 11:51:55 Checking for missing data
2023-09-20 11:51:55 <device_B> does not have any Policy data
2023-09-20 11:51:55 No missing data was detected, sending alerts and compiling the report
2023-09-20 11:51:55 No certificate alerting channel has been enabled
2023-09-20 11:51:55 Support Checks has been disabled, skipping
2023-09-20 11:51:55 No failed devices alerting channel has been enabled
And this for all devices of the same customer.
On our shared infra, which has lot more objects, that work much better :
2023-09-20 11:19:09 <device_X>:Stats: VS:699 P:623 R:204 POL:213 DG:96 C:144 M:239 ASM:87 T:134.3199104
I checked CPU and memory usage on the docker, doesn't seem really high.
Network doesn't seem to be the problem, same path used than the previous setup.
Any idea ?