ARUBA CONTROLLER LICENSING
Aruba JW472AAE AP Capacity License Guide
What the JW472AAE electronic license enables, how AP capacity is consumed, and which adjacent Aruba controller licenses must remain separate in a bill of materials.
JW472AAE is capacity, not a controller appliance
HPE Aruba Networking identifies JW472AAE as the LIC-AP Controller per AP Capacity License E-LTU. The part number represents an electronic license-to-use item. It does not include a physical access point, Mobility Controller, Mobility Conductor, gateway, power supply, support contract or installation service.
This distinction matters when a quote is built from search results. A product title containing “controller” can be mistaken for controller hardware, while the official description places the SKU in the Mobility Controller license table. The purchase record should therefore state the controller or gateway environment that will receive the entitlement and the number of operational APs to be covered.
Count the APs that consume capacity
The ArubaOS license guide defines AP licensing on a per-AP basis. An AP license is required for each operational LAN-connected, mesh or remote AP that is advertising at least one BSSID. Aruba's 7200 controller product reference also states that the minimum configuration for each AP attached to the controller is one LIC-AP per AP.
| Deployment input | Count for JW472AAE planning | Evidence to retain |
|---|---|---|
| Campus AP | One capacity license for each operational AP. | AP inventory, controller association and active status. |
| Remote AP | Include operational remote APs in the required pool. | RAP inventory and target licensing pool. |
| Mesh AP | Include mesh APs that meet the documented consumption condition. | Mesh role and controller assignment. |
| Growth reserve | Add only the approved expansion quantity; do not hide it in the current count. | Current total, reserve total and deployment date. |
The controller CLI commands show ap license-usage and show license-usage expose available, used and remaining AP capacity. Export the real output before ordering instead of deriving quantity from an old asset list.
AP capacity does not replace feature licenses
Aruba lists JW472AAE separately from JW473AAE Policy Enforcement Firewall, JW474AAE RFProtect and Q9B90AAE Advanced Cryptography licensing. Those part numbers are not aliases. A design that needs policy enforcement or RF protection must validate those functions and their consumption rules independently.
JW472AAE
Controller per-AP capacity. Use it to satisfy the AP capacity requirement documented for operational APs.
JW473AAE / JW474AAE
Separate PEF and RFProtect entitlements. Include them only when the design requires their features and the controller architecture supports them.
Central subscriptions
Aruba Central device subscriptions follow a different licensing model. Do not substitute a Central AP subscription for this controller capacity SKU.
ArubaOS documentation also distinguishes sharable licenses in a licensing pool from controller-specific licenses. Confirm the deployed ArubaOS architecture, Mobility Conductor use and license-pool placement before assigning purchased keys.
Build the quantity from live state
Start with the current operational AP count, then reconcile APs staged for commissioning, decommissioning and disaster recovery. Record whether capacity is held in a centralized pool and whether managed devices can draw from that pool. If a controller reports a lower overall AP limit than the license count, investigate platform capacity or another entitlement boundary instead of assuming that additional JW472AAE units alone will remove the limit.
- Export the AP license-usage and license server tables.
- Separate active campus, remote and mesh APs from retired inventory.
- Map every managed device to its licensing pool or controller-specific entitlement.
- Add approved near-term AP growth as a visible reserve line.
- Check PEF, RFProtect and other feature requirements independently.
JW472AAE order checklist
- Match the exact SKU: require JW472AAE on the quote and purchase order.
- Describe the item correctly: label it as an electronic per-AP capacity license, not controller hardware.
- Capture the platform: record controller, gateway, Mobility Conductor and ArubaOS release.
- Confirm the pool: document where the license will be installed and which devices consume it.
- Reconcile quantities: compare ordered capacity with live AP usage and approved growth.
- Separate services: list support, feature licenses and Central subscriptions on distinct lines.
- Validate after activation: retain license-usage output and entitlement records.
Related product record
Review the exact product page when requesting stock, delivery and license registration details.
Official manufacturer sources
- HPE Aruba 7200 individual AP license reference
- HPE Aruba Networking ArubaOS data sheet
- ArubaOS license types and usage
- ArubaOS show ap license-usage command reference
This independent procurement guide is not an HPE Aruba Networking publication and does not claim partner authorization. Confirm current platform support, entitlement rules and registration requirements with HPE Aruba Networking before purchase.