Aruba AP-515 vs AP-535: Wi-Fi 6 Access Point Guide

Aruba AP-515 and AP-535 are dual-band Wi-Fi 6 campus access points. Both serve 2.4 GHz and 5 GHz clients, but their radio configuration, wired interfaces and power requirements differ. Compare those differences against the site's client mix and switching infrastructure before choosing the full regional ordering code.

AP-515 vs AP-535: differences that affect the installation

Selection pointAP-515AP-535
2.4 GHz radio2x2 MIMO4x4 MIMO
5 GHz radio4x4 MIMO4x4 MIMO
Ethernet E0Up to 2.5 GbpsUp to 5 Gbps
Ethernet E1Up to 1 GbpsUp to 5 Gbps
PoE inputE0E0 and/or E1; configurable power-source handling

Radio references: 510 Series radio configuration and 530 Series radio configuration. Ethernet values are negotiated port limits from the QuickSpecs below, not guaranteed application throughput.

Choose from the RF plan, not the model number

For an AP-515 proposal, check that the planned client population and traffic fit its radio and uplink arrangement. For an AP-535 proposal, identify a concrete reason for the additional 2.4 GHz radio capability or faster wired interfaces. A higher model number alone does not establish better performance in a particular room.

Ask the designer to document client capabilities, concurrent usage, channel planning and measured coverage. Separate the access point decision from any switch upgrade: list the required port speed, cabling and power budget together so that the quotation covers the complete installation.

Check the power source before accepting the quote

The 510 Series QuickSpecs lists unrestricted operation with DC or 802.3at/802.3bt power. For 802.3af, AP-515 behavior depends on Intelligent Power Monitoring (IPM); with IPM disabled, normal radio operation is not supported. Do not accept a generic “PoE compatible” statement as the power design.

The 530 Series QuickSpecs distinguishes single and combined supplies. With one 802.3at supply and IPM disabled, the USB port and the other Ethernet port are disabled. Unrestricted operation is listed for DC, 802.3bt class 5, or two 802.3at class 4 supplies. AP-535 does not support operation from 802.3af. Verify the exact supply and IPM configuration during acceptance.

Keep radio hardware and deployment compatibility separate

Confirm the complete regional part number, antenna variant, software release and intended management platform before ordering. Record the support-matrix entry used for the design; a matching brand name is not proof that an AP can join an existing controller or that a subscription transfers with a used unit. Check current lifecycle and support notices for the exact offer before purchase.

If the project specifically requires 6 GHz, assess a suitable Wi-Fi 6E or later model separately. The 2.4/5 GHz comparison above does not establish a 6 GHz upgrade path or a drop-in replacement.

Acceptance checklist for the delivered equipment

  1. Match the unit label and full regional SKU to the approved quotation; record serial numbers and supplied condition.
  2. Check the agreed mounting kit, power accessories and package contents against the delivery list.
  3. Connect the planned power source and record the reported PoE class, IPM setting and any restricted functions.
  4. Verify negotiated Ethernet speed on each interface required by the design; test failover or aggregation only if explicitly included in the configuration.
  5. Confirm adoption into the approved software environment, then test the required SSIDs, authentication and client traffic against the site's acceptance criteria.
  6. Document warranty provider, return terms, support eligibility and any outstanding configuration work before accepting the order.

Use the Aruba catalog and procurement information to identify available listings, then request confirmation of the exact model, condition and package. A catalog entry does not confirm current stock or compatibility with your deployment.

Document/Firmware Download

The linked 510 and 530 Series QuickSpecs provide interface and power details. Use the appropriate official documentation and supported software release for the supplied unit; firmware access and support entitlement must be verified separately.