F5 BIG-IP Local Traffic Manager (LTM) vs. VMware NSX

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.

Incentivized

Our high-security environments require end to end encryption, but also tend to have larger budgets. Since beginning utilization of VMware NSX, we've been able to meet the unique requirements for our high-security clients, but it does have a large price tag that goes along with it. This isn't a particularly well-suited solution for environments with tighter budgets, but it definitely provides security where we need it and are willing to pay for this solution

Incentivized

• 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.

Incentivized

• Broadcast Suppression: By suppressing broadcast traffic, we have been able to deploy a single VDI network in a /18 network space, allowing for rapid growth and proper DHCP lease timing for a VDI instant clone environment.
• Networking HA: Leveraging internal mechanisms for high availability, it provides disaster resiliency to a virtual networking environment.
• Cost Savings: All available features of NSX are licensed simultaneously. Load balancers, firewalls, and routers are all licensed as features, not per object, allowing for the deployment of as many of these objects as are needed.

Incentivized

• 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.

Incentivized

• Our biggest challenge is gaining acceptance from network engineers who are used to working with other technologies.

Incentivized

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.

Incentivized

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.

Incentivized

Good after sales support if one purchased direct support from F5.

Incentivized

Easy to implement if one had attended F5 Training for Local Traffic Manager (LTM).

Incentivized

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.

Incentivized

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.

Incentivized

• 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.

Incentivized

• Easy to manage networking and security
• Better visibility into the environments

Incentivized