12-03-2014 11:13 PM
12-07-2014 09:42 PM
On Aruba Mobility Access Switch (MAS):
* IPSec packet encryption/decryption is done in hardware.
* And further these IPSec/VPN packets are software processed for deep packet inspection & session handling.
* And to provide the control plane protection (to CPU), there is a rate limit of 40K PPS (packets per second). This will prevent any possibilty of CPU hogging by just one type of traffic (this way traffic is policed for control plane protection)
* Which means, coming to your question on throughput: Depending on the packet size(s), you can get varying throughput numbers:
With 64 byte packets : ~20 Mbps
With 1500 byte packets : ~480 Mbps
12-07-2014 11:18 PM
12-10-2014 06:03 PM
We are currently running new performance tests based upon recent code changes and once they are ready we can send them your way.
Mobility Controllers do have better software forwarding performance than the Mobility Access Switches given their architecture. They are actually different.
The Mobility Switches are based around a switching ASIC in which the majority of the L2/L3 is done in hardware so we get wirespeed switching and routing. Only traffic requireing stateful Firewall, NAT and VPN is directed to a multi-core processor for "session-processing".
The Mobility Controllers on the otherhand always have their traffic sent through a multi-core processor and as such have higher capactiy CPUs so they can scale from X Gbps to XX Gbps depending on the model.
Another way to look at it is that the software forwarding features of the Mobility Access Switch are designed for small branch deployements while Mobility Controllers can scale from small branch deployment up through large campus designs.