Question: How does licensing work on the Mobility Access Switch platforms?
Licenses are only required if the Mobility Access Switch is using Tunneled Node. The licenses actually reside on the Mobility Controller, not the Mobility Access Switch. A single Mobility Access Switch or ArubaStack of up to eight MAS devices will appear as a single logical switch with the following licenses applied on the Mobility Controller. Each logical grouping of between one and eight Mobility Access Switches will consume one AP license on a Mobility Controller.
A Mobility Access Switch deployed as a single device or as an ArubaStack will consume a single AP license on an Aruba controller
Provides connectivity to controller for config
Centralized Authentication etc
A Mobility Access Switch deployed as a single device or as an Arubastack will consume a single PEFNG license on an Aruba controller
Provides wired policy enforcement for tunneled traffic
A Mobility Access Switch deployed as a single device or as an Arubastack will consume a single RFProtect license on an Aruba controller
Enables RFProtect/WIP feature on the Mobility Access Switch for shutting down port on which rouge AP is detected
Note that the number of AP licenses must be equivalent to the number of PEF and RFP licenses supported by the Mobility Controller. As an example, in a customer environment with 100 wireless APs and four ArubaStacks (logical groups of between one and eight physical MAS), the Mobility Controller would need 104 AP (required), 104 PEF (for firewall) and 104 RFP (for RFP/WIP) licenses.