F5 BIG-IP software from Seattle-based F5 Networks is a load balancing and application protection solution suite available on cloud or via virtual editions, on a subscription or perpetual licensing basis.
N/A
F5 BIG-IP Local Traffic Manager (LTM)
Score 9.7 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.
N/A
VMware NSX
Score 8.7 out of 10
N/A
VMware NSX is network virtualization technology. VMware NSX is no longer sold as a standalone product and is now available as a part of VMware Cloud Foundation.
F5 BIG-IP Vs Netscaler Traffic Manager by Citrix I would say there is no comparison. Netscaler was difficult to use and no one easily understood the configurations. It led to many times where our engineers would need to reverse engineer the configuration before they could …
We combine the AWAF and F5 BIG-IP Local Traffic Manager to not only deliver high performance apps but also secure the apps against so many kinds of threats.
The F5 LTMs integrate great with the F5 DNS appliances and makes on the fly decisions using iquery. We have two HA data centers that the F5 LTMs are used in and integrate great with teh F5 DNS servers.
We use both ACI & NSX. They both provide a programmable network and in future releases of ACI they will allow you to stretch fabrics into the cloud like you can do with NSX. ACI, when compared to NSX, turned out to be significantly cheaper, but it also was lacking certain …
Application delivery of both simple and advanced applications. It's easy to handle certificate management that do require individual certificates to be installed on each backend server, you can just install the certificate on the F5 BIG-IP and use for multiple backends. Also adding WAF is as simple as adding a generic policy and you will cover 80% of the scenarios.
I mean the only reason we changed away from it was price and it just simply had to do with the licensing that Citrix was offering on the NetScalers. They had basically an all you can eat consumption license that we were easily inside of with all of our VDI usage, whereas with F5 we had to buy the hardware and we had to license the software. Any place you need to actually do traffic balancing at scale, it's a fantastic product. I couldn't recommend it highly enough. There's just some things that hardware SSL offload and hardware load balancing just simply can't be equal that I don't know if there's a better product on the market for that.
With proper design, VMware NSX can and should be deployed to virtually any VMware virtualization environment, but the deployment should be tailored to the needs of that environment. There isn't really a one size fits all deployment design for all environments. That versatility is what provides its greatest strength to a business.
It's reliable. We've had very little problems with the technology. Performance is always right on. Metrics are great. They come out of it. We'd like to do more probably with it in the future as we start to grow a lot more.
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.
Recently we have been deploying F5 web application firewall and we have started the deployment. We have already moved applications out there, but we are not yet to the point wherein I could comment any positive feedback or any negative feedback because we are still going through it, right. But as far as I'm concerned, I don't see any drawbacks or any shortcomings on the F5 product lineup.
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.
Stability of product and easy way to have account manager contact. F5 support team is also always available to help with major issues. Last year during the major OS upgrade F5 team and F5 leadership always shared clear information and F5 team was dedicated to help us to have it closed in record time
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.
It actually satisfies the use cases, but I would like to know what it can do more than just the use cases, which is what I'm looking for, to talk at some point with somebody and figure out what to do next. We probably maybe could be able to do more that we don't know yet.
I am very comfortable with this product not only configuring it but automating it as well. There are not many configurations or situations where I do not know how to implement it on the device. I find it straightforward and easy to use.
I've supported F5 for three different companies. Our F5 support has been very consistent, regardless who the customer is. F5 technicians are very experienced and provide good support, even when issues are more related to knowledge than they are with the ability of the product to do what you need it to do.
That's the one thing that really stood out. It was a lot easier to use from an administrator standpoint, so I think that's the one thing that really made our team decide to go with this product versus another competitor. Just ease of use.
F5 is doing its specialized function. There is no other product that can beat them. We are extremely happy with the product. Especially on load balancing, traffic redirecting TLS encryption, and SNI modification. We will continue to explore F5's product, especially on the public cloud side. e.g. NGINX.
We use both Cisco ACI and VMware NSX, and while they have different strengths and capabilities, I would recommend VMware NSX, as it can be used in all VMware environments, without costly physical infrastructure changes. Cisco ACI provides some of the same capabilities, but not all. It's focus relies on physical networking changes.
The F5 BIG-IP has improved all our load balancing needs, we have over 400 LTM VIPs in our environment this all use to be done with DNS round Robin configurations.
we have created unique APM solutions to support our external customer base
It has allowed us to let application developers know that the issues are with their application and not due to the network, because of where it sits. This has been invaluable when troubleshooting issues when they arise. Knowing whether or not traffic is even hitting the F5 BIG-IP Local Traffic Manager (LTM), either ingress or outgoing. If the Dev's information is not even making it to the F5 BIG-IP Local Traffic Manager (LTM), we can quickly tell them and let them figure the issue out on their own, saving the rest of the Network Team from getting that 2am call.
