F5 BIG-IP Local Traffic Manager (LTM) Reviews

As an IT developer, mostly I use load balancing for the traffic. Currently, it's distributing the load perfectly, as per my understanding of our requirements.

It's definitely scalable and is stable as well.

The initial setup is not complex, and the technical support is fine.

I'm not very sure about the security with F5 BIG-IP Local Traffic Manager (LTM). We have our own private data center, but we are going to migrate our private data center into the Azure cloud environment. Security will then be a major concern when we migrate our own whole infrastructure to the public cloud.

So, I think they should improve in terms of security because nowadays, most organizations try to build their infrastructure on public cloud.

More documentation should be uploaded because very limited documentation is available on the internet. It will also help us to understand the system before purchasing the product.

I've been using this solution for two years.

It's a stable solution.

It's definitely scalable. It's a distributed architecture and micro services, so it's scalable. In fact, we are planning to increase usage and scale horizontally.

I don't have any issues with respect to technical support; it has been fine.

The initial setup is not complex. 

If you have your own data center, then you can use F5 BIG-IP Local Traffic Manager (LTM). I don't see any issues because they have been in the industry for a long time, and F5 BIG-IP Local Traffic Manager (LTM) is very stable.

I would rate this solution at eight on a scale from one to ten.

We use it for low balancing.

It has been in our environment for four to five years, but I have only been using it for a little over a year.

• The detail that you have available when setting up iRules. 
• How the traffic routing works in F5.

The management process seems a bit difficult. 

The management interface is unclear, complex, and not concise. I would like a better user interface.

For integration with other AWS environments, we do some tie-ins with some autoscaling groups. This has been challenging for us. We have had issues, where when autoscaling groups scale up, there are some instances which are not showing up in the proper size. Then, those IPs would get registered with F5, but never get released. Therefore, we are ending up with a whole bunch of ghosted IPs. However, this is more an implementation detail than an F5 detail.

It is very stable. I have no concerns regarding stability for F5.

We are seasonal, so we go from low to high volumes. F5 has never been a concern of ours for stability.

We run an Active-Active version of two instances, so scalability between the on-premise and AWS versions hasn't been a huge issue for us. Where we are finding the AWS version helpful is when we are trying to scale up new environments. AWS Marketplace helps here a lot.

We have support agreements in place, but they are managed by the infrastructure team. I do not contact the technical support, they do.

The integration and configuration into the AWS environment was pretty good.

The product was already in place when I came onboard.

My preference is to use AWS natively, but there are some issues around session management and so on, which have prevented us from using it. While a lot of these issues have been solved, a lot of our applications are tied to the F5 infrastructure.

Always use the Automatic Synching between F5. Don't try to use the API to do the synching. This is where we went wrong. We were trying to push the nodes to F5 individually instead of letting F5 handle the synchronization process, and it doesn't work.

We were previously using the on-premise version, but now we are using the AWS version. They are about the same as far as functionality.

We use F5 BIG-IP Local Traffic Manager for our applications. We have six applications and 16 servers currently. We make all our applications and utilize this tool. Some applications are published on LSM.

The price for F5 BIG-IP Local Traffic Manager is very high. This aspect could be improved.

I've used F5 BIG-IP Local Traffic Manager (LTM) for one year, within the last year.

We find this tool stable. We are sensitive to changes, and for us, F5 BIG-IP Local Traffic Manager is stable.

F5 BIG-IP Local Traffic Manager is scalable.

We had a good setup experience with this tool, but we had to raise a ticket with support for assistance.

We implemented F5 BIG-IP Local Traffic Manager ourselves. We didn't use a consultant or integrator for implementation, but we contacted their support team.

F5 BIG-IP Local Traffic Manager is a high-priced tool. We pay for its license yearly.

F5 BIG-IP Local Traffic Manager has good performance.

Your success with F5 BIG-IP Local Traffic Manager will depend on how much you understand how the application is working.

Deployment of this tool took two hours.

We have 600 users of this tool, and currently, there's no requirement for increasing its usage.

We have one manager and two technical staff who takes care of the deployment and maintenance of this tool. They're building applications, and they're using this tool.

I'm recommending F5 BIG-IP Local Traffic Manager to others who want to start using it.

On a scale from one to ten, with one being the worst and ten being the best, I'm rating F5 BIG-IP Local Traffic Manager (LTM) an eight.

We use F5 BIG-IP Local Traffic Manager (LTM) as a load balancing solution. We use many of the features associated with the solution, such as the Local Traffic Manager and Access Analytics that are associated with the SSL.

F5 BIG-IP Local Traffic Manager (LTM) is very easy to use, from SSL Management to enabling, disabling loads, applications, systems, and monitoring. Overall the solution keeps our application functional from a client's perspective 24 hours a day, seven days a week. We have rules that are set up to detect if any part of the application in one of the nodes is not functioning correctly, having a problem, or is experiencing any sort of error, it will automatically pull it out of the load balance bundle and alerts somebody to go take action and at the address. This means our clients are happy because they are not receiving strange errors because somebody's typed something somewhere incorrectly and we are happy because our uptime is reliable.

The solution could improve the documentation.

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

The stability is very good. We have to power off a system to reboot it after firmware or other updates, but I have not had a problem with the stability of the units at all. We had a system cluster go down but that was a physical issue with the hard drive. They shipped us out a new one, plugged it back in, and it almost self-configures. We had to put some details in the hard drive, but it takes the configuration from the other units and runs well. We have had zero downtime over the last five years.

F5 BIG-IP Local Traffic Manager (LTM) is very scalable. We have recently expanded the cluster to five nodes and I am running in an active scenario. I did the upgrade live and it did not require any downtime.

The technical support is good. I have not had any problem asking questions that a support person can not answer. Technical support is not engineering and that was something that I had to learn. If you have something that is already functional and you need to figure out why it stopped working, why it is now broken, or you did an upgrade and something is wrong, the technical support can help with that. I have called them a dozen times over the five years and they have had my issue resolved within approximately one hour.

Setting up the solution on the systems is not difficult but enabling applications and configuration can be complex. The difficulty level can also depend on the environment, we have a more complex environment. You have to have some base knowledge of the solution for what you are doing before you can go do it. Configuring the solution is not something that a layperson is going to be able to do. You have to know what you are looking for before you will be able to find it.

My advice to those wanting to implement this solution is they need to do their research ahead of time and know what problems you are trying to solve. In our case, our solutions engineer from F5 directly has been amazing. If you receive a good team in account management, they can point you in the right direction, and in a lot of cases, they can get you moving along. The support from him has been tremendous, it has been extremely valuable.

Our configuration is not simple. There is some custom code that is written in our system, but everything works as they say it should, it is a great solution.

I rate F5 BIG-IP Local Traffic Manager (LTM) an eight out of ten.

The product can be used for many applications including load balancing and GLB's overload balancing. It depends on the module. If there's a public APM you can use it for WAF and many other use-cases. 

The performance of the product is great. 

We enjoy its overall ease of use.

It's relatively easy to configure. There's a certain level of fine-grain configurations that you can perform.

The solution is very stable.

We've found the product to be quite scalable.

The initial setup is very straightforward. 

The pricing could always be better. It's a bit expensive.

It would be ideal if they offered integration with NGINX. They purchased NGINX as well. Therefore, if it's got integration with NGINX, then you kind of have one single pane of a console for all the F5/NGINX portions of your work. 

I've been using the solution for six years. It's been a while.

The stability is very good. The performance is reliable. It doesn't crash or freeze. We don't find there are a lot of bugs or glitches. 

The scalability is great. If a company needs to expand it, it can do so easily.

We have about 2,500 users on it currently.

We do plan to increase usage in the near future.

We've used technical support in the past and have been satisfied with the level of attention we receive. They are helpful and responsive. 

The installation process is not overly complex or difficult. It's very straightforward and pretty simple. 

The deployment is fast as well. It takes maybe an hour to an hour and a half to set everything up. 

We have two people on staff that can handle deployment and maintenance. They are admins.

I handled the installation myself. I did not need the assistance of any integrator or consultant. It was all handled in-house. 

The solution could work at lowering its prices a bit.

The licensing needs to be a bit more flexible.

We pay our licensing fees on a yearly basis. 

We did evaluate other solutions before choosing this product. However, it was a long time ago. I can't recall the products we looked at. One might have been Barracuda.

We're a customer and a partner of F5.

The product is an on-premise virtual edition solution.

I'd rate the solution at a nine out of ten. We've been mostly quite happy with it so far.

I'd recommend the solution to other users and organizations. Our experience has been a positive one. 

The F5 is something we purchased for another project that has not been turned on just yet.

The solution is very powerful.

The product is quite flexible. 

The horizontal scalability that is on offer is very good as well.

I would like to see some better documentation focused on our website and better search criteria. That's probably the best way to say that there needs to help with research.

The cost of the solution is pretty high. It would be ideal if it was more reasonable.

We were originally supposed to launch this project for a client, however, that hasn't materialized yet.

While we never really got around to scaling the solution just yet, there is horizontal scalability that is on offer that seems very good.

This is being deployed in a service provider environment. Therefore, it'll be impactful to all of our customers. However, I would say as far as internal support users, we have a team of probably ten that'll be supporting this product once it's launched in production.

In terms of technical support, so far it has been pretty good. That said, it's more to set up the solution versus actual production support. They're not helping us deal with bugs or glitches, they've just been helping us with a rather complex implementation. We've been satisfied with their assistance in that sense. They seem knowledgeable and responsive.

The initial setup is largely complex. However, we had a lot of help from their internal sales team or support team has been important in terms of working around the difficulties.

We have a staff of ten that are handling deployment and maintenance. They're not dedicated just to this product, however. They support our overall service provider architecture.

The cost is quite high. The long-term support in particular is quite high.

Customers need to be aware that each feature is licensable, which allows costs to accrue.

We're just a customer. We don't have a business relationship with F5.

The F5 is something we purchased for another project that has not yet been turned up. That said, the experience I've had with F5 has been very positive, specifically working directly with their corporate sales engineering team. 

Overall, I'd rate the solution eight out of ten. If it wasn't for the high cost of the product, I might rate it a bit higher.

I would advise those considering the solution to explore all options. Specifically, the total cost of ownership. It can be lower with some other vendors. A10 is oftentimes a lower cost of ownership. One challenge with F5 is everything is a licensable feature. Whereas something like an A10 is not. You see the same challenges with a Cisco type of device as well, however, it's in a different arena, with different products.

This is for remote access to an internal network of the organization to do all types of work. The requirement for VPN is secure with high performance.

Two issues found in using BIG-IP VPN compared with Cisco VPN:

1. Performance: Two applications are being used: remote desktop (RDP or rdesktop) and VNC viewer. Comparisons are done on the same client machines (Windows 10 and Linux 16.04) over the same network. When using Cisco VPN, applications are working smoothly while occasionally jittery. When using F5 VPN, applications are quite jittery. Sometimes applications are useless (too slow to refresh the screen).
2. Client support: Cisco VPN has more Clients supported than BIG-IP, e.g., BSD.

Still not clear why our IT decided to switch to F5 BIG-IP after two years experience. It appears as if there may be some advantage (possibly) related to security concerns (more secure?).

Performance is the first thing and most critical issue that needs improvement.

Supporting more Clients would be nice, but without improving performance, F5 will not widely be used for critical work. It killed an international meeting the first time that we used BIG-IP VPN.

Performance: Using the product, applications are jittery.

No issues.

We used Cisco VPN. I am not sure why our IT forced us to switch to F5 without our feedback.

Initial setup is easy and pretty standard. Setup is not much different from all other VPNs.

In-house.

Unless the price difference is large, this is not the primary concern for the product. The performance and product-related issues (secure for VPN, multi-function for network device, etc.) are the keys.

No.

F5 BIG-IP LTM is used for delivering applications and protecting the application from web attacks.

F5 BIG-IP LTM can improve on the SSL loading which includes the authentication of certificates. Although, most of these issues have been solved there are still some issue that persists.

In a feature release, it would be helpful to have real-time packet features in the GUI.

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

I have clients that have approximately 5,000 users using the solutions and others with 40,000 users.

When we increase the services we have to then increase the usage of the solution, we put more virtual F5 devices in the cloud.

The support from F5 BIG-IP LTM is good.

The initial setup of F5 BIG-IP LTM is straightforward. The full deployment took approximately two to three days.

I used one person for the deployment of F5 BIG-IP LTM because it is easy to do.

There are a few licensing options available for F5 BIG-IP LTM. You can have a perpetual license which is a lifetime license. You then only need to renew the support, if you choose to open a ticket with the support.

The second option is a subscription model on the cloud. When I have a project that will only one year. I purchase a subscription for one year only. It would work for the whole year and after we can shut it down because there is no need for it.

My advice to others is to have a good staff who understand the technology. If someone understands the technology, that will make life easy for them or their organization. I cannot say that technology is difficult, but technology is very critical when you put it in your environment. Having good staff who can manage that solution makes life a lot easier.

I rate F5 BIG-IP LTM a nine out of ten.