F5 BIG-IP DNS (formerly BIG-IP Global Traffic Manager) secures DNS infrastructure.
N/A
F5 BIG-IP Local Traffic Manager (LTM)
Score 8.9 out of 10
N/A
F5 states that the "brain" of the BIG-IP platform, Local Traffic Manager (LTM) intelligently manages network traffic so applications are always fast, available, and secure.
It's well suited. Like I said, it provides us, it provides the clients and the business environments throughout an Internal Revenue Service. The network visibility needed for them to provide their application and the use of their applications throughout the Internal Revenue Service and the enterprise, as far as IRS.
There was a need to have the DR environment to be available actively but not to send the traffic unless the production is down The F5 BIG-IP Local Traffic Manager (LTM) priority feature helped achieving it. It was well suited in handling the HTTP headers using polices and iRules. It was less appropriate from the application security perspective in the current version. But after attending the AppWorld 2024, I see a lot of ways to protect the network and the application with several features.
Sure. It does load balancing fantastically. I mean, it's an industry standard product for that. We also use it for TLS offload for applications. Those are the two main use cases for that. We do also use some of the I rules for traffic filtering. We've used that in some of the external facing services. It does a really nice job with that. It's a little bit complicated sometimes and some of the Cipher Suite stuff is interesting.
I'd like to see better reporting capabilities on the decision-making process for DNS resolutions. Currently there are plenty of log messages for that, but I'd like to see tighter integration into the GUI.
It could be an improvement to better discriminate features intended for AA vs LDNS functionality within the GUI.
Some of the stuff you have to dive into the CLI to really use, I'm going to reach back to the previous employer for this. So I had a much greater degree of involvement with it at that point in time for, I was the crypto guy at the company and I had to design all the cipher suites that we actually implemented on our front end banking products. So in order to do that, I had to dive into it, download all the Cipher suites, figure out the actual order of operation for them, how they were selected because I wanted to design the Cipher Suites to actually provide a specific customer experience for the types of connections that our customers were likely to initiate. Getting at that information was a giant PITA. It was poorly documented at the time. I'm not sure if it's documented any better now. Every time the software changed or got upgraded, made your version, I'd have to do it all over again because the upgrades to the stack, which looked like it was based on open SSL, but it was heavily modified with a different syntax. Oh yay. That's fun too. So I had to write giant documents describing all of the ciphers that I was designing for this because it just kept changing all the time. So I didn't care for that aspect of it. Traffic management does a great job for that.
We use this heavily and it is one of the best products out there for this type of use case. We already have LTMs and to leverage GTM on top of that is just a piece of cake. Everything is so well integrated its amazing
F5 has always been one of the best products we have in the data center. We had few issues with the BUG and Code upgrades but the main use cases for F5 was always top notch. From High availability to Globally load balancing applications across multiple data centers and muti cloud environments.
F5 BIG-IP Local Traffic Manager is a very good product. It is used in our company widely. So far we are very happy with the product. Esspecially on the load balancing and TLS encryption and Traffic redirecting based on HTTP path and http query. iRules is very easy to use as well.
As I mentioned, the GSLB capability, being able to do intelligent DNS by having access to monitor specific endpoints associated to my current BIG-IP infrastructure, I believe that brings a huge value, then combine fast responses and security.
Obviously NetScaler, because we had that functionality, we just turned it on. We were only using it for our Citrix farms and we migrated all of our F5 uses over to the NetScalers. So simply because that was, other than buying the product, which the actual NetScaler themselves were cheap. I mean it cost us like $60,000 for all of them for the hardware. We were already licensed for it, so it was a no-brainer. We didn't have a choice. Definitely a superior product. A lot more functionality, particularly in corner cases where you might need to make some specific traffic tweaks. I would say that the NetScaler doesn't do nearly as good a job with that traffic filtering. You only really get URI filtering with NetScaler. You don't have the flexibility, the eye rolls or the complexity of the eye rolls, so that's a negative too.
We use these for 600+ applications and we are able to manage all of them remotely and provide security across every application in one single platform.
We are able to provide an amazing customer experience load balancing across multiple nodes and this increases traffic on our websites and ultimately increases orders and traffic.
