What is our primary use case?
We primarily use it to create WAFs and wide IP (virtual server) configurations. Additionally, we leverage Global Server Load Balancing (GSLB) when we need to define access policies or create web application firewalls (WAFs). In those scenarios, F5 is our go-to solution.
Let's say we have servers in the DMZ or back-end that shouldn't communicate directly with the outside world or receive unwanted traffic. F5 comes in with virtual IPs to act as a middleman. Daily traffic gets routed according to our policies, like round robin. With four servers, F5 sends queries one by one to each, checking if they're healthy and ready to serve clients. That's a typical use case.
Additionally, if we need to inspect or modify packets (e.g., for SSL decryption), we can install tools on F5 to handle that offloading and send the traffic onward transparently to the back-end. These are some of the key features I use regularly.
And if we need to modify packets on the fly, like the certificates within the traffic, we can install them on the F5, perform traffic manipulation and offloading, and then send the traffic decrypted or encrypted to the backend in plain text. These are all capabilities we're quite familiar with.
How has it helped my organization?
If we need to patch servers before they go into production. This is where the F5's protection side, specifically certificate management, comes in handy.
We can use the F5 to send traffic and analyze if the patched servers are functioning correctly before they're exposed to production users.
What is most valuable?
The most valuable feature is the virtual IP creation. It's our most frequently used feature. It allows us to take a server out of the pool if it's acting strangely on the backend without impacting client traffic. The client remains connected to the virtual IP, and the F5 automatically routes them to a healthy server.
What needs improvement?
In my opinion, the GUI side needs some improvement based on my usage. Sometimes, it doesn't work as efficiently as the CLI side.
Feature-wise, sometimes when I log in to the GUI and want to see the pool members, and I click on that, it sometimes goes and shows me some traffic details for that specific node, inside, outside, page traffic, everything. But when I click the back arrow to go back, it takes me to a different page, not the page I was on before.
So those are some of the things I think could be improved upon.
For how long have I used the solution?
I have been using it for several years. While I've been using it less in the last few months due to workload, overall, I've been using it for about five years or more.
What do I think about the stability of the solution?
It is a stable solution. I would rate the stability a ten out of ten.
What do I think about the scalability of the solution?
From my perspective, the work I do benefits from good visibility before anything goes to production. We can generate traffic with F5's load generators to see how it behaves, exposing any packet errors and other issues. This is valuable for me, as it allows for troubleshooting without involving server personnel.
Additionally, we can capture traffic directly on the F5, analyzing it using F5's traffic analytics feature. This independence from network engineers is good, eliminating the need to constantly ask them to check server issues. In essence, using F5 allows us to verify its health and traffic handling independently. Overall, this has been very helpful.
Overall, I would rate the scalability a nine out of ten.
How are customer service and support?
My experience with customer service and support has been good.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I did use a different solution.
However, we opted for F5 because it's a really scalable solution. It's easy to deploy and a stable solution. Moreover, it offers good support.
How was the initial setup?
The initial setup was straightforward.
What was our ROI?
It's definitely good to have it. It definitely saves time and money.
What other advice do I have?
It's a really scalable solution, stable solution, one of the best products in the market in that segment, widely used as well as a lot of good support documentation online and call support available.
Overall, I would rate the solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises