The recommendation is for no more than 5,000 concurrent users per APM VE.ДЇigure 1: Scaling SSL VPN using BIG-IP Local Traffic Manager (LTM) Conceptual Diagram The design goal is to spread the required SSL VPN load across a larger number of APM VE instances with lower concurrent user count rather than utilizing a smaller number of higher concurrent users.В This approach is designed to maximise the throughput per-user. 2GB of RAM needs to be allocated per vCPU. The solution consists of two tiers, one being the load balancing of inbound SSL VPN traffic utilising existing BIG-IP Local Traffic Manager (LTM) to several APM VE which perform SSL VPN termination.В The High-Performance APM VEвЂ™sВ are utilising VE subscription licenses, that support up to 24 vCPUвЂ™s and have no throughput limits. This solution brief will be focused on Load Balancing via BIG-IP LTM - option (c). Note: the above mechanisms can also be utilized with existing Active-Passive cluster APM instances that choose to redeploy as Active-Active behind the LTM or GSLB. Load Balancing via BIG-IP Local Traffic Manager (LTM).Global Server Load Balancing (GSLB) via F5 DNS Load Balancer Cloud Service.Global Server Load Balancing (GSLB) via F5 DNS (Formerly known as GTM).Traffic steering across the High-Performance APM VEвЂ™s using one of the following mechanisms:.

Utilizing several High-Performance Access Policy Manager (APM) Virtual Editions (VE) to provide horizontal scaling with appropriate APM CCU licensing.While some customers are able to support this increase on their existing physical or virtual infrastructure, many are facing unprecedented demand that cannot be supported on their existing infrastructure. In response to the COVID-19 pandemic, many organisations have implemented a remote working policy, resulting in a significant increase in the number of users requiring remote access.

F5 https vpn monitor