OUTDOOR WLAN PROCUREMENT

Aruba AP-577 TAA Regional Model Selection Guide

Keep the EG, IL, JP and RW AP-577 TAA order lines distinct while validating country approval, directional coverage, power, mounting and software support.

PLATFORMAP-577
ANTENNAInternal directional
COMPLIANCETAA order lines
REGIONSEG, IL, JP, RW

AP-577 is the platform; the PID selects the region

HPE Aruba Networking identifies the AP-577 as an outdoor Wi-Fi 6 access point with internal directional antennas. The four product IDs below are TAA variants for different regulatory domains. Their shared enclosure and radio platform do not make the regional PIDs interchangeable.

Use the exact PID in the bill of materials, receiving record and controller inventory. Confirm that the destination country is covered by the selected regulatory model and current software release. Never use the “RW” label as a substitute for a country-specific approval check.

Four exact TAA regional order lines

Part numberOfficial HPE identityRegional markerProcurement boundary
R4H34AAP-577 (EGF1) TAA dual-radio outdoor APEGUse only after validating the intended Egypt regulatory deployment.
R4H35AAP-577 (ILF1) TAA dual-radio outdoor APILUse only after validating the intended Israel regulatory deployment.
R4H36AAP-577 (JPF1) TAA dual-radio outdoor APJPUse only after validating the intended Japan regulatory deployment.
R4H37AAP-577 (RWF1) TAA dual-radio outdoor APRWConfirm the destination country is covered by the current rest-of-world mapping.

HPE's current QuickSpecs describes all four as AP-577 TAA dual-radio 2x2/4x4 Wi-Fi 6 outdoor access points with internal directional antennas. Region and compliance identity remain part of the order line even where the base hardware description is shared.

Directional outdoor deployment needs a site record

An internal directional antenna makes orientation part of the design. Preserve the mounting location, azimuth, elevation, intended coverage area, channel plan, transmit-power policy and survey result. Confirm the approved mounting hardware, grounding, surge protection, cable path and power source against the current installation guide.

Before rollout, verify the selected AP-577 PID against the controller or cloud-management architecture and supported software matrix. Pilot adoption, regulatory-domain behavior, client connectivity and failover on the exact regional model. A successful test on another AP-577 PID does not prove that the requested region code is correct.

AP-577 order and acceptance checklist

  1. Specify the complete PID: require R4H34A, R4H35A, R4H36A or R4H37A rather than “AP-577” alone.
  2. Confirm country approval: map the installation country to the current HPE regulatory model.
  3. Retain TAA identity: reconcile the quote and chassis label with the required TAA order line.
  4. Review RF direction: record orientation and the surveyed coverage objective for the internal directional antenna.
  5. Validate infrastructure: check power, mounting, grounding, surge protection, cabling and environmental requirements.
  6. Check management support: record the controller, gateway or cloud platform and exact software release.
  7. Test the delivered unit: preserve PID, serial, adoption, country setting, channel, power and client test evidence.

Official manufacturer sources

This independent selection guide is not an HPE Aruba Networking publication and does not claim partner authorization. Confirm the current regulatory model, software support, mounting, power and environmental requirements directly with HPE before purchase or installation.