My main use cases for using F5 BIG-IP Virtual Edition are mainly WAF. That's the main purpose.

We use F5 BIG-IP Virtual Edition mostly for the login functionality with our Salesforce and for security login purposes.

The features I appreciate the most about F5 BIG-IP Virtual Edition are the WAF capabilities.

The advanced web application firewall protection and SSL offloading capabilities of F5 BIG-IP Virtual Edition have been utilized in my organization. These features are contributing to our application security and compliance posture.

I find it too complex to assess the impact of F5 BIG-IP Virtual Edition's automated deployment and integration with container orchestration platforms, such as Kubernetes and OpenShift, on my applications delivery speed and reliability.

I don't use F5 BIG-IP Virtual Edition's automated deployment and integration with container orchestration platforms such as Kubernetes and OpenShift.

I have been using F5 BIG-IP Virtual Edition for about five to six years, possibly longer.

F5 BIG-IP Virtual Edition is stable and reliable. I have not experienced any stability or reliability issues with the solution.

F5 BIG-IP Virtual Edition scales with us as we are continuously expanding the deals of the product.

The solution is performing well and keeping up with our needs as we continue to increase our usage.

I do not use customer service and technical support directly with F5 BIG-IP Virtual Edition. We have an integrator called Spider. They are satisfactory and whenever they encounter issues, they open a case with F5 and assist us.

I would rate the customer success and technical support for F5 BIG-IP Virtual Edition an eight out of ten.

I have no idea about the ROI from using F5 BIG-IP Virtual Edition. We use the technology on the technical side, not on the financial aspects.

I don't have information about the pricing, setup costs, or licensing for F5 BIG-IP Virtual Edition.

I do not use the load balancing and traffic management features of F5 BIG-IP Virtual Edition.

I use other container orchestration platforms, but they are not relevant to F5 BIG-IP Virtual Edition.

I have utilized F5 BIG-IP Virtual Edition's ability to integrate with cloud platforms including AWS, Azure, GCP, and Salesforce.

I have no idea how this integration has helped my organization manage hybrid or multi-cloud environments.

The seamless integration of F5 BIG-IP Virtual Edition with existing F5 technologies is not important to me as I do not use other technologies from F5.

Financially, we require F5 BIG-IP Virtual Edition because we need the product. We don't have anything else that performs the same functions, so we use it without trying alternatives.

I just use and manage F5 BIG-IP Virtual Edition, though I didn't handle its deployment.

I would recommend F5 BIG-IP Virtual Edition as a solution to others.

I would rate F5 BIG-IP Virtual Edition an eight out of ten overall.

I use the solution in my company to meet the virtualization needs of our customers. In the case of a payment gateway, according to the application, every VirtualBox gets segregated. Every VirtualBox will have multiple banks connected to one particular vCMP for a specific application.

The solution's most valuable feature is its good virtualization concepts. My company is very happy with all the basic features of the product.

On-the-go upgrades are an option that the tool currently lacks, making it an area where improvements are required. If you have an instance where you have a specific configuration of CPU memory when you want to increase it, you have to parallelly create a new instance, and you have to export and import the configurations. On the go, if you could give any option to shut down VirtualBox, increase CPUs, and start it again, that would be a good option.

I have been using F5 BIG-IP Virtual Edition for more than four to five years.

It is a scalable solution.

In F5 BIG-IP i5800, if you have assigned a single CPU and memory for a virtual instance and if it increases, you can just add a CPU and memory to the existing vCMP. What you have to do is spin one more virtual instance with the two CPUs and double the memory, like eight GB memory, for example. You can't just increase the existing VirtualBox. You have to create another VirtualBox parallel, download the configurations, and import it.

My company provides one banking application to around ten customers. My company has around seven virtual instances and seven applications, each application having around 70 customers running on one F5 BIG-IP i5800. My company has created seven VirtualBox.

The solution's technical support was good. Whenever my company reached out to the product's support team, we got solutions to our issue. In case an issue doesn't get solved, then it gets escalated, and the product's support team provides our company with an engineer to deal with the problem.

The product's initial setup phase is straightforward.

The solution is deployed on an on-premises model and the cloud model. For the on-premises version, my company deployed it on something like F5 BIG-IP i5800, and for the cloud deployment, we have installed the virtualizations on Cisco CSP kind of tools. My company ensures that VirtualBox is deployed on CSP. In both the aforementioned scenarios, we have tested the tool, after which we started to use the product in the past two to three years.

My company's customers need to make payments for the licensing charges attached to the product. It is an expensive product. As per the requirements of our company's customers, we opt for it if it is the only hosting option available. My company also needs to see which box from F5 matches the requirements of our customers.

Speaking about the impact of the tool on the application delivery process, I can say that static routes are limited. For every vCMP, there are some limitations of VLAN IDs and static routes, like the number of routes that can be added. There are some limitations in the product that are likely to impact our company's applications.

In terms of performance and scalability features, according to the application limit, my company can add a single CPU per vCMP or two CPUs per vCMP, which is dependent on the load requirements that we plan. The company also needs to plan according to the application requirements. My company didn't face any issues following the aforementioned process.

My company provisions vCMPs based on the concurrent session support and SSL support criteria. Based on the data sheets, my company checks the total concurrent connections, SSL connections, and throughput limit. Even when my company plans to do segregations, we plan to do them according to the specifications described in the data sheets.

You need ten pieces of the tool for load balancing. If my company's customers' requirements only consist of a product that offers five features, then they can adopt a basic OEM tool. If some customers need more features in a product, my company recommends F5 BIG-IP Virtual Edition. Mostly our company's customers do accept our suggestions and choose F5 BIG-IP Virtual Edition.

I recommend the product to others who plan to use it since it is a user-friendly and not-so-complex tool.

The integration capabilities of the product are easy to use, and there is no complexity involved in it.

I rate the tool an eight out of ten.

We use it for two applications.

I've also used the Virtual Edition in the network core alongside the hardware appliances. I don't think there's any issue with either. Both seem to be working well simultaneously.

It's easy to integrate with others. I've integrated it with McAfee Solutions, Aruba NAC, and the EMS tool from Micro Focus.

It's easily manageable with various solutions.

I like the virtualization aspect, similar to what you get with cloud services or VMware.

I have a specific issue with the network interface connector, the NIC.

We're limited to a maximum of two NICs in a virtualized environment. It's a limitation of the tool.

So, Network Interface Connectors (NICs) need to be improved. More NICs would be helpful.

I have been using it for three months. I use the latest version. 

I would rate the stability a seven out of ten. 

No issues with scalability. Virtual Edition handles traffic spikes.

The main difference between the Virtual Edition and the hardware is that you run the F5 image on VMware or any other cloud platform. In my experience, I haven't faced any issues with scalability or manageability due to virtualization. It's been good.

In our IT department, no one uses the Virtual Edition for F5. However, our customers use the Virtual Edition.

I would rate the scalability an eight out of ten. 

We were using the hardware initially because it was too expensive for our client. That's why they wanted to go with the BIG-IP Virtual Edition.

There weren't any major issues with the deployment, but it wasn't completely seamless. 

Virtual Edition required some additional work compared to hardware, like provisioning and sizing tasks. 

However, once configured, it's easy to scale by increasing the VM size.

VM size adjustments weren't difficult, but it's not as straightforward as hardware deployment. 

The deployment time depends on the configuration. It might take one day or one hour, depending on the number of applications that need to be configured. 

My company is a system integrator.

It is a yearly-based license. I would rate the pricing a three out of ten, with ten being expensive. 

We had Redware and Palo Alto. 

We had limitations in Redware with the number of virtual servers and tools. F5 doesn't have those limitations. 

Plus, for security, we can configure policy profiles across layers 3, 4, 7, and even 2. F5 also has persistence and separate mechanisms for things like server acceleration.  

I would recommend using this solution. Overall, I would rate the solution an eight out of ten.