Solved all the problems we wanted it to and some that we didn’t know we had.
August 23, 2018

Solved all the problems we wanted it to and some that we didn’t know we had.

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with F5 BIG-IP

We work in healthcare and uptime matters; we use F5 Big-IP load balancers throughout our remote hosting environment and on some of our onsite solutions. It’s proven to be an extremely reliable and fault-tolerant load balancing solution that also provides a ton of customization that allows it to meet pretty much any need we’ve been able to throw at it.
  • Load balancing
  • Health checks
  • SSL termination
  • SNAT
  • URI & Payload Rewrites
  • Pricing - Aside from there being other cheaper alternatives out there I can’t really think of anything negative to say, we migrated to them about 4 years ago and we’ve been very happy since. Even considering the price I’d say it’s worth it.
  • Less issues with our load balancers means better availability for our clients and less penalties from our SLAs.
  • Easy for newer network engineers to learn means less time spent training them.
We use a significant number of the virtual edition F5s, and a few physicals. We also have netscalers in a few places, but the netscalers we use are pretty much only used for Citrix Traffic where the F5s give us a ton of flexibility and can handle pretty much anything we throw at them.
We use it mostly for terminating SSL, load balancing and maintaining highly available web applications. But I’ve also come up with a few weirder use cases:

  • I set up Syslog and SNMP trap VIPs that forward to multiple monitoring servers to make sure that alerts were never missed (this is important since both use UDP rather than TCP and are inherently best effort and the sending node will not be aware of whether or not the messages ever reach their destination)
  • Weighted failover for PostgreSQL servers. If the primary server is down it will send connections to the secondary server. If both the primary and secondary server is down also it will send incoming connections to the tertiary server.
  • Load balancing to read only replica sets. - IPV6 to 4 Natting