My main use case for F5 BIG-IP Virtual Edition is for LTM and GTM. For LTM, I use it for load balancing, and GTM is for global load balancing, which functions as intelligent DNS. Let's suppose we have one application abc.com. We create an alias on abc.gslb.com and forward that traffic to a CNAME, which in turn forwards the traffic to the GTM. The GTM does the load balancing between the data centers. Sometimes it is active-active, and sometimes it is an active-standby setup similar to DCDR, depending on the requirement and application team requests. After that, if there is a disaster at some data center, such as power issues, the standby data center will serve that purpose. This really increases our availability and performance of the application, and we are receiving fewer complaints, almost none. My use case is known mainly for the GTM and LTM.
I am currently using F5 BIG-IP Virtual Edition for LTM and GTM purposes across two data centers. For load balancing between the data centers, I use GTM, and within a data center, load balancing is handled by LTM. For a critical application, we have created an active standby setup using GTM. If something happens with DC1, traffic will automatically be transferred to DC2. For the LTM use case, we have an application such as abc.com with 50 servers behind it, and we perform load balancing between those servers.
My main use case for F5 BIG-IP Virtual Edition is for load balancer creation, VIP creation, iRules, and all of our on-premises related networking management. A specific example of how I use F5 BIG-IP Virtual Edition for load balancer creation and iRules is when I write a simple iRule, and a script detects if the server is in the pool or down. If they are down, it automatically redirects the user to a friendly 'we'll be back soon' hosted page. If the pool doesn't have the target endpoints added, then traffic could fail. I need to ensure that iRules are pointing to the right pool for the hosted zones. I use F5 BIG-IP Virtual Edition to handle SSL/TLS decryption instead of having web servers struggle to encrypt and decrypt traffic. F5 BIG-IP Virtual Edition does all the heavy lifting at the front door, which keeps my backend server fast and dedicated strictly to running the application code. I also use it to manage the application health check, and every few seconds, F5 BIG-IP Virtual Edition pings my on-premises servers to ensure they are healthy. If the servers are frozen or crash, F5 BIG-IP Virtual Edition automatically pulls them out of the rotation, so the user never hits a dead link.
network engineer at a tech vendor with 1,001-5,000 employees
MSP
Top 20
Feb 10, 2026
My main use case for F5 BIG-IP Virtual Edition is that it provides load balancers, and we have multiple pieces in our organization. In my daily work, we generally have multiple customers, and I have set up partitions for customers, manage their URLs, and keep their servers under their VIP.
My main use case for F5 BIG-IP Virtual Edition is to facilitate site-to-user communication and to enable access to site services. In my environment, we have an internal DMZ zone, which includes an HTTP server and Telnet services. When an external remote user wants to connect with our services, we need to use F5 BIG-IP Virtual Edition for the round-robin method to ensure that the services have 24/7 reachability without any interruption.
Our main use case for F5 BIG-IP Virtual Edition is for virtual VIP configuration and SSL offload. We use F5 BIG-IP Virtual Edition for SSL offload by utilizing a particular VIP with a specific SSL certificate saved and served by F5 BIG-IP Virtual Edition for that particular VIP.
Network Architect at a pharma/biotech company with 1,001-5,000 employees
Real User
Top 10
Jan 31, 2026
My main use case for F5 BIG-IP Virtual Edition is to load balance the incoming traffic in our environment. When users want to access our internal infrastructure or web applications located in our internal infrastructure or DMZ environment, their traffic is load balanced into the internal environment. Users arrive from the internet and either land into our DMZ web application, from which we redirect the same application via F5 BIG-IP Virtual Edition to our internal environment. We are using the LTM edition in our environment for this purpose. Apart from that, we are also using F5 BIG-IP Virtual Edition as BIG-IP DNS, which was previously known as GTM. We use F5 products for DNS traffic as well. We have two data centers, one on the west side and one on the east side in the Azure environment. BIG-IP DNS edition load balances the traffic into different data centers. In some cases, for disaster recovery scenarios, we use this virtual IP DNS capability. Additionally, we are also using F5 BIG-IP Virtual Edition with ASM tools and WAF, which provides Web Application Layer 7 firewall capabilities.
Cybersecurity Engineer at a tech vendor with 10,001+ employees
Real User
Top 10
Jan 30, 2026
In F5 BIG-IP Virtual Edition, we are using the LTM and ASM module. We use F5 BIG-IP Virtual Edition for L7 load balancing and SSL offloading. In our case, we are totally working on a cloud environment, and we are using different cloud-native solutions across AWS, GCP, and Azure. Behind that, we are using F5 BIG-IP Virtual Edition's LTM and ASM module, so any traffic that lands on our cloud-native will first load balance from our cloud-native load balancers. Apart from this, we are using firewalls as well. Layer 4 traffic inspection is done on that. Post that, for Layer 7 traffic inspection and application-level load balancing, we are using F5 BIG-IP Virtual Edition's LTM and ASM module. LTM is especially used to load balance the application traffic to the real-time application servers or application load balancers. We have applied some profiles, policies, pools, and nodes. Apart from that, we are also applying an ASM policy on that virtual server so that Layer 7, which means OWASP Top 10 inspection, could be done for that application. With the help of F5 BIG-IP Virtual Edition, we can deploy that virtual edition in any kind of virtual machine. We can use cloud-native virtual VMs, or we can also deploy that on VMs. Those are the main use cases of that.
Network Security Engineer at a tech vendor with 11-50 employees
Real User
Top 5
Jan 16, 2026
My main use case for F5 BIG-IP Virtual Edition is application delivery and security, primarily for load balancing and Layer 7 (application-layer) protection of web applications. We use it to distribute traffic across multiple backend servers to ensure high availability, performance optimization, and zero single point of failure. On the security side, we use it to protect applications from common web threats such as SQL Injection, Cross-Site Scripting (XSS), CSRF, brute-force and credential-stuffing attacks, bot traffic, malicious scanners, and Layer 7 DDoS floods. Additionally, we leverage BIG-IP VE for: * SSL/TLS offloading and inspection to reduce server load * Persistence/session management (cookie / source IP) for stable user sessions * Health monitoring to automatically detect failures and route traffic to healthy nodes * Traffic visibility and logging for troubleshooting, compliance, and faster incident response Overall, it has been a reliable solution for improving application uptime, security posture, and user experience in production environments.
My main use case for F5 BIG-IP Virtual Edition, which is mostly requested by our customers, is using it as a load balancer, functioning as an LTM (Local Traffic Manager).Recently, we had a requirement from a customer who hosts a web application on a web server and needed to increase the availability of the website. We suggested and implemented a solution where we placed F5 BIG-IP Virtual Edition in front of the server and deployed three servers behind it, all hosting the same application. Using this approach, we have increased both the performance and availability of the application.
Cloud Engineer at a outsourcing company with 11-50 employees
MSP
Dec 5, 2025
My main use case for F5 BIG-IP Virtual Edition is for security. I use F5 BIG-IP Virtual Edition for security by utilizing the IP Intelligence to check the reputation of IPs.
System Administrator at a non-tech company with 501-1,000 employees
Real User
Top 10
Jun 5, 2025
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.
IT Specialist at a manufacturing company with 10,001+ employees
Real User
Top 5
Jan 14, 2025
In my company, we use NGINX. I don't work with NGINX. For us, it is better to have the virtual solution because we have more virtual VJPs on fewer machines. This is the reason we are using it today.
Manager | Engineering | Cloud Managed Services at Sify Technologies
Real User
Apr 15, 2024
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.
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.
F5 BIG-IP Virtual Edition provides SSL offloading, load balancing, and high availability, enhancing security and performance. It supports advanced traffic management and monitoring tools, integrating easily and cost-effectively for flexible deployments across data centers.F5 BIG-IP Virtual Edition is renowned for its security and performance integration. The platform's customization capabilities via iRules, combined with comprehensive traffic management tools, enable organizations to...
My main use case for F5 BIG-IP Virtual Edition is for LTM and GTM. For LTM, I use it for load balancing, and GTM is for global load balancing, which functions as intelligent DNS. Let's suppose we have one application abc.com. We create an alias on abc.gslb.com and forward that traffic to a CNAME, which in turn forwards the traffic to the GTM. The GTM does the load balancing between the data centers. Sometimes it is active-active, and sometimes it is an active-standby setup similar to DCDR, depending on the requirement and application team requests. After that, if there is a disaster at some data center, such as power issues, the standby data center will serve that purpose. This really increases our availability and performance of the application, and we are receiving fewer complaints, almost none. My use case is known mainly for the GTM and LTM.
I am currently using F5 BIG-IP Virtual Edition for LTM and GTM purposes across two data centers. For load balancing between the data centers, I use GTM, and within a data center, load balancing is handled by LTM. For a critical application, we have created an active standby setup using GTM. If something happens with DC1, traffic will automatically be transferred to DC2. For the LTM use case, we have an application such as abc.com with 50 servers behind it, and we perform load balancing between those servers.
My main use case for F5 BIG-IP Virtual Edition is for load balancer creation, VIP creation, iRules, and all of our on-premises related networking management. A specific example of how I use F5 BIG-IP Virtual Edition for load balancer creation and iRules is when I write a simple iRule, and a script detects if the server is in the pool or down. If they are down, it automatically redirects the user to a friendly 'we'll be back soon' hosted page. If the pool doesn't have the target endpoints added, then traffic could fail. I need to ensure that iRules are pointing to the right pool for the hosted zones. I use F5 BIG-IP Virtual Edition to handle SSL/TLS decryption instead of having web servers struggle to encrypt and decrypt traffic. F5 BIG-IP Virtual Edition does all the heavy lifting at the front door, which keeps my backend server fast and dedicated strictly to running the application code. I also use it to manage the application health check, and every few seconds, F5 BIG-IP Virtual Edition pings my on-premises servers to ensure they are healthy. If the servers are frozen or crash, F5 BIG-IP Virtual Edition automatically pulls them out of the rotation, so the user never hits a dead link.
My main use case for F5 BIG-IP Virtual Edition is that it provides load balancers, and we have multiple pieces in our organization. In my daily work, we generally have multiple customers, and I have set up partitions for customers, manage their URLs, and keep their servers under their VIP.
My main use case for F5 BIG-IP Virtual Edition is to facilitate site-to-user communication and to enable access to site services. In my environment, we have an internal DMZ zone, which includes an HTTP server and Telnet services. When an external remote user wants to connect with our services, we need to use F5 BIG-IP Virtual Edition for the round-robin method to ensure that the services have 24/7 reachability without any interruption.
Our main use case for F5 BIG-IP Virtual Edition is for virtual VIP configuration and SSL offload. We use F5 BIG-IP Virtual Edition for SSL offload by utilizing a particular VIP with a specific SSL certificate saved and served by F5 BIG-IP Virtual Edition for that particular VIP.
My main use case for F5 BIG-IP Virtual Edition is to load balance the incoming traffic in our environment. When users want to access our internal infrastructure or web applications located in our internal infrastructure or DMZ environment, their traffic is load balanced into the internal environment. Users arrive from the internet and either land into our DMZ web application, from which we redirect the same application via F5 BIG-IP Virtual Edition to our internal environment. We are using the LTM edition in our environment for this purpose. Apart from that, we are also using F5 BIG-IP Virtual Edition as BIG-IP DNS, which was previously known as GTM. We use F5 products for DNS traffic as well. We have two data centers, one on the west side and one on the east side in the Azure environment. BIG-IP DNS edition load balances the traffic into different data centers. In some cases, for disaster recovery scenarios, we use this virtual IP DNS capability. Additionally, we are also using F5 BIG-IP Virtual Edition with ASM tools and WAF, which provides Web Application Layer 7 firewall capabilities.
In F5 BIG-IP Virtual Edition, we are using the LTM and ASM module. We use F5 BIG-IP Virtual Edition for L7 load balancing and SSL offloading. In our case, we are totally working on a cloud environment, and we are using different cloud-native solutions across AWS, GCP, and Azure. Behind that, we are using F5 BIG-IP Virtual Edition's LTM and ASM module, so any traffic that lands on our cloud-native will first load balance from our cloud-native load balancers. Apart from this, we are using firewalls as well. Layer 4 traffic inspection is done on that. Post that, for Layer 7 traffic inspection and application-level load balancing, we are using F5 BIG-IP Virtual Edition's LTM and ASM module. LTM is especially used to load balance the application traffic to the real-time application servers or application load balancers. We have applied some profiles, policies, pools, and nodes. Apart from that, we are also applying an ASM policy on that virtual server so that Layer 7, which means OWASP Top 10 inspection, could be done for that application. With the help of F5 BIG-IP Virtual Edition, we can deploy that virtual edition in any kind of virtual machine. We can use cloud-native virtual VMs, or we can also deploy that on VMs. Those are the main use cases of that.
My main use case for F5 BIG-IP Virtual Edition is application delivery and security, primarily for load balancing and Layer 7 (application-layer) protection of web applications. We use it to distribute traffic across multiple backend servers to ensure high availability, performance optimization, and zero single point of failure. On the security side, we use it to protect applications from common web threats such as SQL Injection, Cross-Site Scripting (XSS), CSRF, brute-force and credential-stuffing attacks, bot traffic, malicious scanners, and Layer 7 DDoS floods. Additionally, we leverage BIG-IP VE for: * SSL/TLS offloading and inspection to reduce server load * Persistence/session management (cookie / source IP) for stable user sessions * Health monitoring to automatically detect failures and route traffic to healthy nodes * Traffic visibility and logging for troubleshooting, compliance, and faster incident response Overall, it has been a reliable solution for improving application uptime, security posture, and user experience in production environments.
My main use case for F5 BIG-IP Virtual Edition, which is mostly requested by our customers, is using it as a load balancer, functioning as an LTM (Local Traffic Manager).Recently, we had a requirement from a customer who hosts a web application on a web server and needed to increase the availability of the website. We suggested and implemented a solution where we placed F5 BIG-IP Virtual Edition in front of the server and deployed three servers behind it, all hosting the same application. Using this approach, we have increased both the performance and availability of the application.
My main use case for F5 BIG-IP Virtual Edition is for security. I use F5 BIG-IP Virtual Edition for security by utilizing the IP Intelligence to check the reputation of IPs.
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.
In my company, we use NGINX. I don't work with NGINX. For us, it is better to have the virtual solution because we have more virtual VJPs on fewer machines. This is the reason we are using it today.
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.
We use the solution for web application firewalls and VPNs. It could be your VPN concentrator, intelligent DNS, and load balancing.
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.