F5 BIG-IP Local Traffic Manager (LTM) Reviews

All the cyber security vendors and their products need improvement, including F5 and this product. No one is 100% secured, because attacks are more sophisticated now, and the hackers have become more advanced.

Recently, I've seen one of the attacks on this particular network, where they managed to bypass its multi-factor authentication. They were able to bypass that level of security, and they managed to get into the network.

Every cyber security vendor needs to be proactive. No one is perfect, so even the rank one cyber security vendors should also keep their eyes open all the time.

It would also be better if F5 provided free product training for F5 BIG-IP Local Traffic Manager (LTM), so end customers could have more awareness and understanding of the product, so they'll know how to use it.

Our level of requirements, usage, and scalability are being met by this product. If we needed additional features, or if we needed additional licenses, all we need to do is just buy the additional features or licenses, so we currently don't have any additional features we'd like to be included in the next version of F5 BIG-IP Local Traffic Manager (LTM).

My experience with F5 BIG-IP Local Traffic Manager (LTM) is a total of four years now. We have customers, e.g. from the government, who prefer this solution. We also propose it to them because they have a bigger environment, compared to the environment size of private companies. We have customers from the government, e.g. from the Department of Communication.

F5 BIG-IP Local Traffic Manager (LTM) is scalable and secure, so we propose this solution to customers with bigger environments, e.g. those in the government.

I'm rating F5 technical support a nine out of ten.

We used Fortinet, but what we were getting from F5 BIG-IP Local Traffic Manager (LTM) was always more than what we got from Fortinet, even when using FortiWeb and Forti WAF cloud as a service, and even when considering the functionality of each product.

F5 BIG-IP Local Traffic Manager (LTM) is more complex to implement. Implementation of this product would be much easier if you have the right service, e.g. consultation services included, support from the distributor or directly from the vendor itself, or a certified partner. Having consultation and support will help make it much easier for the end customer during implementation, but the implementation process for this product is more complex than Fortinet.

The cost is high for this product, so small customers, e.g. those in a private bank, won't be able to afford F5 BIG-IP Local Traffic Manager (LTM), and they also don't really need the kind of support and functionality that this product gives.

For customers who are in the government, we propose F5 BIG-IP Local Traffic Manager (LTM) despite its cost being high, because they'll really need it. They host their applications in the cloud, and in private data centers, e.g. private cloud services, so they'll need the kind of protection that this product provides.

It depends on customer. Whenever we see that customers can't afford, or the environment is smaller, we propose Fortinet, or some other solution that's cheaper than Fortinet. We don't propose F5 BIG-IP Local Traffic Manager (LTM) to them.

I was able to evaluate Fortinet.

We have a partnership with Fortinet, as a reseller of F5 BIG-IP Local Traffic Manager (LTM) and other F5 products. We are also a reseller of Cisco and Forcepoint products, though we just started with Forcepoint, so we haven't been doing much with their products currently.

My advice to users of F5 BIG-IP Local Traffic Manager (LTM), including people who are thinking of implementing this product, is that they need to have product awareness. What we are seeing in our government customers is that they don't have awareness, in particular, they don't know what they're using, which is why they're having issues. They need to understand the product first, and they need to go and get the training first, but they are hesitant to pay for the training.

Unlike Fortinet who provides free training, F5 doesn't. Ever since the pandemic, Fortinet has provided free training, but certification is not free. If F5 can provide free training for F5 BIG-IP Local Traffic Manager (LTM), that would be better.

My rating for F5 BIG-IP Local Traffic Manager (LTM) is eight out of ten.

I mainly use LTM to protect applications.

LTM's most valuable features include application security, data collection, and parameter-level rules. 

LTM would be improved with the inclusion of signature-based blocking. In the next release, LTM should include the ability to configure account details and access user logs.

I've been using LTM for six years.

LTM is a stable product.

LTM is scalable.

The initial setup is straightforward, so long as you have some understanding of the solution, and it should take around forty-five minutes. However, if you're unfamiliar with LTM, it will take longer.

I would recommend LTM to other users and give it a rating of nine out of ten.

The solution is used for deploying applications.

The most valuable feature of F5 BIG-IP LTM is the operating system. It is nicely designed and orchestrated. The solution has all the features that are necessary for medium to large-sized enterprises would need to ensure their application are available throughout the globe. The LTM and DTM features combined provide a great service to organizations for presenting around the world which includes load balancing. 

If there are any problems with the applications during integration they can be managed well with the solutions' ability to provide visibility.

The solution could improve the ease of use, the management could be simplified. Other solutions are easier to use.

I have been using F5 BIG-IP Local Traffic Manager (LTM) for approximately 15 years.

The stability of F5 BIG-IP LTM is great.

50 percent of my customers are using this solution.

F5 BIG-IP LTM is a scalable solution.

I have not needed technical support from F5 BIG-IP LTM.

If you are an expert in F5 BIG-IP LTM then the solution is simple to implement. If someone is new to implementing the solution it is difficult.

The length of time it takes to do the deployment depends on the size of the network it is being deployed in.

We do the implementation of the solution.

This solution comes with a standard license, and there are also extra licenses that can be obtained. The licenses are purchasable for durations of one, two, three, and five years. The hardware is something to consider when purchasing

I recommend this solution to my customers.

I rate F5 BIG-IP Local Traffic Manager a nine out of ten.

We use it for server management and application traffic, that is, to load balance between traffic for applications coming from their service. Users coming in are then able to have their traffic go to the service that has the suitable resources or adequate resources.

F5 BIG-IP Local Traffic Manager (LTM) improves the resilience and quality of the application itself, the speed and the user experience for the application. The data that the users need from the application is actually acquired faster. So, it provides faster data acquisition.

It also provides lower latency.

It would be good to have better traffic and better data. It would be nice to have more granularity to see packets in terms of the header details, the analytics, etc. It would be nice if that was also part of it and to have analytics added to the traffic.

I've been using it for two years.

F5 BIG-IP Local Traffic Manager (LTM) is pretty stable. It's one of the most stable products that I know, when it comes to load balancing and traffic.

It is very scalable. We have thousands of users.

The technical support is top notch.

It is pretty easy to set up.

Because there were other parties involved, the deployment took us about a week. Normally, it takes a couple of hours.

We did it in-house.

I would advise you to go for it because it's one of the top three solutions in my opinion. I would rate it at seven on a scale from one to ten.

We primarily use the solution for security purposes.

The security on offer from the solution is very good.

The stability is excellent.

The pricing of the product is a bit too high. They should work to make it more affordable. It needs to be more cost-efficient. 

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance has been good.

I've never used technical support. I can't speak to how helpful or responsive they are when it comes to servicing their customers, having never used them personally.

I also have experience with Check Point. 

We did not install the solution ourselves. We used an integrator that handled the process and helped us set everything up. 

We used an integrator to assist with the installation. We were pleased with the results. There was nothing to complain about the results.

The pricing is pretty high. It's not the least expensive option.

That said, we're willing to pay for the premium security on offer.

I'm a customer and an end-user.

We are using the 12th version of the solution. 

I'd rate the solution at a nine out of ten. We've been quite satisfied with the capabilities of the product.

I'd recommend the solution to other users and companies. 

We are primarily using it for load balancing, and with BIG-IQ managing Layer 7 security policies.

We did get good flexibility as well as the capabilities to accept declarative API and create per app dashboard and create a better view on the telemetry dashboard.

• Cloud templates 
• Declarative onboarding
• API service gateway
• Policy-based security management.

Services to be improved: 

• Multi-cloud consistency, like to simplify administration with centralized policies with multi-cloud vendors
• F5 lateral scalability within the container is still restricted.
• Web application firewalls and service mesh would be a nice-to-have feature.
• Drive programmable application with 100% restful API
• Cover deployment
• Monitoring
• Policy-based control. 

We have around 12 data centers. On average, in every data center, we have 14 to 15 F5 load balancers. We manage everything from a central location, then we deploy policy for use, giving us a place for our control managers.

I have Big-IP change and control manager, which give me the roll back option. Therefore, I can view the last things which happened on the device.

In future, I would like there to be more device security. I would like the tool to support SSL links, along with SSL and TLS. It also needs to disable the old cipher suite, which is a very old. There are ciphers, like D5, still available on the device.

We have faced security stability issues, but we work around it.

It is very scalable.

F5 tech support is helpful. I would rate the technical support with an eight out of 10.

We used to have Cisco, then we have Citrix NetScaler. The Citrix NetScaler is just a load balancer. It did not me the complete ADC features. That is why F5 is the king of load balancing.

The initial setup was pretty straightforward; not complex.

Security should be involved in any base license. When you bring on F5, you only have default license. Then, the ASM product license has to be purchased. It would be great if F5 could include the ASM in the base license. 

Central solution to control traffic or web applications (besides NG Firewall).

• Easy administration
• A lot of features
• Scriptable (iRules and REST API)

I have some experience with other load balancing providers. The BIG-IP’s interface is more intuitive than other GUIs. It is well structured, not overloaded, and does not have too many gimmicks.

The ASM administration is quite complex. I am a technical GUI expert (not UI). They did improve the ASM administration in each version, but added new features, too. The topic itself is pretty complex, so it is not easy to provide a nice, clean interface. There are a lot of references and dependencies in-between the different subareas.

I have not yet encountered any stability issues.

I have not yet encountered any scalability issues.

Technical support is good. I have had nothing to complain about up until now.

I previously used a different solution. We switched because the hardware was too old, and the other vendor did not have the same set of features.

Initial setup was straightforward. We were up and running in three hours.

Take a look at the modules that you are going to use. Look into the best bundles for them.

Before choosing this product, I compared it with Radware. Cisco was already off the market, and Citrix was not as big as it is today.

Use the community and DevCentral.