Now with virtual server details and some bug fixes. Please note that you must update your config file too (or add the irules section added in the latest version).
Since devcentral is broken I’m posting an update here instead.
Setting up a secure VPN is easier than you might think. With F5 APM and Google authenticator you’re up and running soon.
There is an article on devcentral doing this but I thought it could be a bit simpler so I wrote my own. Tested on version 12 but should be more or less applicable to version 11 as well. Please let me know if there’s any differences and I’ll update the article.
Since we rely so heavily on the load balancers to handle part of the application logic the line between application servers and network equipment is blurred out. URIs and headers may change, and pools might be chosen depending on many different factors.
To add some transparence here I would recommend using the loadbalancer to give the users of your company additional information if they need it.
Taking care of the CDN can be a hassle sometimes. Unless you implement the perfect system with unique keys for every item update you will need to purge content once in a while.
We asked for some guiding from Limelight but they did not have any example for Powershell themselves so I had to translate the existing one from Perl. Hardest part was the authentication and getting the hash right but with some help from the nice people at stackoverflow it worked out in the end.
Kudos also to Limelight for having a good API documentation.
As always, if you improve it then please share it.
Contributions is always appreciated!
The F5 Web UI usability has not improved that much in a long time. Version 12 is starting to do things about it, but it’s too early to adopt unless you absolutely need some of its features.
The script is using Tampermonkey, a client side script engine, to add functionality to the F5 UI.