“Carolina West Wireless needed to deploy a load balancer solution with Metaswitch’s EAS product. Through the help of Loadbalancer.org’s product and product support, we were able to do so within record time. We had several unique configuration requirements and they were very prompt in responding. Each answer was spot on and very easy to understand and deploy! I can’t stress enough how important this level of support was for us in our time of need. Thank you for being so easy to do business with!”
Jason HodgesCarolina West Wireless
Metaswitch and Loadbalancer.org have a long-standing partnership for the implementation of EAS SSS. Whether deployed as hardware or virtualized, the Loadbalancer.org solution ensures EAS SSS is highly available and highly secure.
In this environment, the EAS servers may also be connected to separate signalling and media networks. These additional networks carry SIP and RTP traffic respectively. It is not necessary to connect the load balancer to them as the load balancer is not responsible for load balancing SIP or RTP traffic.
Please see the below, WAF Gateway with Metaswitch EAS DSS/SSS Deployment Guide, for further details.
For deployments up to 250,000 subscribers, your virtual host should be allocated a minimum of 8 vCPU's, 16GB RAM and 8GB disk storage.
This specification will support the following bandwidth and connection thresholds:
|Internet||EAS||100 Mbit/s||70,000 pkts/s||380,000|
|EAS||Internet||700 Mbit/s||55,000 pkts/s||380,000|
For larger deployments, your Metaswitch support representative will give you details of the expected load on your load balancers based on your predicted usage profile.
There are two ways that Metaswitch Virtual EAS SSS can be deployed. The deployment type used determines how the load balancer must be configured. It is essential to know which type of deployment is in place or being planned before attempting to set up a load balancer. If the deployment type is not clear, please contact Metaswitch support for further information. Some of the virtual services needed to load balance Metaswitch Virtual EAS SSS require source IP persistence. The EAS servers include a file named pools.txt which describes the virtual services that need to be set up, whether or not they require persistence, and if so what persistence timeout value should be used.
In a virtualized environment, the Virtual EAS SSS deployment type used determines how the load balancer must be configured. It is essential to know which type of deployment is in place or being planned before attempting to set up a load balancer. In this scenario, the Loadbalancer.org solution should be used to provide both load balancing and protection against security vulnerabilities.
Hardware installs follow a significantly different deployment architecture, so it's best to contact your Metaswitch support representative for assistance. In this scenario, a separate pair of dedicated Loadbalancer.org appliances should be installed to provide protection against security vulnerabilities.
For other modes of implementation and additional details, please refer to the below Deployment Guide.
Metaswitch recommend using some specific tests which make use of the EAS Craft menu and the CommPortal web portal. These include Pool Configuration, Health Checking, Persistence & Failover / High-Availability. The System Overview in the Loadbalancer.org appliance can also be viewed in the WebUI. It shows a graphical view of all VIPs & RIPs (i.e. the EAS servers) and shows the state/health of each server as well as the state of each cluster as a whole. Please refer to the below Deployment Guide for full details.
Eliminate stress in large environments with the totally unrestricted Enterprise VA MAX. This virtual load balancer offers unrestricted throughput and bandwidth, allowing you to manage unlimited load balanced services and back-end servers. You will never have to worry about scalability again.More Information Free Trial
Surely you must have a question?