BigIP Report Old

I'm ashamed to admit, but this has helped us ID 163 orphaned pools across the enterprise, so we have found it useful. Ideally we shouldn't have scenarios this extreme; however it has helped us quickly ID loads of clean up work. Keep up the good work and please feel free to share how we can help support you guys.

Wanted to add a side note: Only issue we found with the feature was it did ID our High Availability -> Fail-Safe -> Gateway Pools as Orphaned and to some extent it's fair as they are not attached to a virtual, but are in use.

Regards,

Jeff

163? Wow. (runs and hides under his 3000+ reported orphan pools)

I don't think the script is catching all pools. For example if a pool is selected through a data group lookup, I don't think that pool is associated with the virtual host. I'll do some more testing on this.

@TimRiker LOL!! :)

Ah that makes sense. Interestingly enough it does pickup our pool members that are associated by an iRule that does pool selection.

Thank you Tim for all your hard work. I recently wrote a plugin to BigIPReport at work that displays Orphan pools, monitors and iRules. What if we moved all this to a separate section in the console?

I think what Tim was after was to reduce logic in the table generation in terms of the orphan pools and keep the virtual servers json file clean and this could accomplish that.

What do you think?

Jeff, could you share that iRule with me?

/Patrik

Thank you Patrik for all your hard work! I've packaged up my changes into a release called 5.1.0. Download available from my git repo here:

https://github.com/timriker/BigIPReport/raw/master/Releases/BigipReport-5.1.0.zip

This release greatly reduces the loading time in the browser. Our giant setup used to take over 5 minutes to load in the browser, and with these changes, loads in about 10 seconds. Re-copy all resource files when you upgrade or your table will be empty.

More info on the pull request here:

https://github.com/epacke/BigIPReport/pull/93

Diff, if anyone is interested using w=1 to ignore whitespace:

https://github.com/epacke/BigIPReport/pull/93/files?w=1

Changes:

• uses datatables in memory data source to render in client
• "orphan pools" are exported in

  virtualservers.json

• "orphan pools" show with pool name in virtual server field
• ASM types are in

  asmpolicies.json

• made the logo transparent (unrelated)
• relative paths for resource loading from javascript
• use Map() for pool lookups to speed up loading
• bumped to 5.1.0 version and made a release package
• disabled console resizing

The only thing I've found not working is the NATFile support. Are people using this? If so, what should happen with the browser side rendering? I could export the NAT table and use it on the client, or just mangle the IPs in the existing json files. I'm not using that feature, so asking for some feedback.

Thanks Tim. I use the NATFile support and it is being heavily used while we go through our Data Center consolidation projects. Let me see how it acts in the new 5.1.0 version. Will get back to you with results. Will also work a deployment with w=1 to check results.

NAT entries should look like this. Example with and without Public IP

I think we'll have to re-do the NAT file support to use Json format. Maybe convert the nat file to json during report generation. Or ask the user to write the NAT file as Json directly to the json folder of the report.

/Patrik

Patrik, I hope my comment was clear. I was actually complimenting the fact that while there is only one pool attached to the VIP, the report shows both associated and selected via the iRule.

iRule when HTTP_REQUEST { if { [HTTP::uri] starts_with "/insight" } { pool Insight-UAT-8050 } else { pool Tableau-UAT-8054 } }

pool Tableau-UAT-8054

The cool part is both the 8054 and 8050 pools are displayed!