Aggregation servers, or Aggregators, are a key component in the Multapplied SD-WAN architecture. Aggregators split outbound traffic bound for customers into multiple streams for each leg and recombine inbound traffic from each leg before sending it on to its final destination on the internet. This is what enables Multapplied SD-WAN to combine the speed of bonded connections, even for a single download or upload, and to offer instant, transparent failover when a leg goes down.
Aggregators can be considered a type of router, since they route traffic between the partner’s core network and the CPEs. In fact, they are typically integrated into the dynamic routing configuration of the partner network.
System Requirements for Aggregators
Environment : bare metal (strongly recommended for performance), ESX, Xen (PV-GRUB or HVM), or KVM
see virtualization considerations on provisioning Aggregators.
CPU : Intel Xeon CPU Ivy Bridge (2013) or newer with at least 4 cores
if encryption is enabled for the tunnel or private WAN, AES acceleration instruction set is recommended for faster speeds
RAM : minimum 2 GB (supports 50 bonds/1 GB memory)
add 50 MB for every bond running TCP proxy (when TCP proxy is enabled on at least 1 bond, Aggregator needs more memory and this can vary depending on the speeds set on the bond)
Disk : minimum 16 GB
Ethernet : One gigabit interface
IP address : One static public IP
Internet uplink : Sufficient bandwidth for all bonds assigned to the Aggregator, considering your oversubscription ratio if applicable.
For example, with two bonds, each with two 10/10 Mbps legs, the Aggregator would need 40/40 Mbps bandwidth to Internet, assuming no oversubscription. Using an oversubscription ratio of 4:1, the Aggregator could be given 10/10 Mbps bandwidth.
Recommended – remote KVM ability such as IPMI or ILO