HPE Aruba outdoor campus Wi-Fi for yards, walkways and loading areas

This reference design is a starting point for project discovery, not a completed customer case. Final quantities and settings require site measurements, endpoint compatibility checks and a release-specific implementation design.

1. Requirements analysis

Workload and capacity example

Illustrative zone: a plaza and two loading entrances with 150 phones and 20 operational clients at peak. Model gathering locations, client uplink and actual applications, and test indoor/outdoor transitions. Survey placement, antenna angles and power paths; a maximum advertised range is not usable business coverage.

Deliverables at this stage: a measured floor plan, client/application inventory, current topology and dependencies, agreed test objectives and constraints. Keep associated-client counts, active-client counts and concurrent application demand as separate inputs.

2. Solution design

Outdoor clients → appropriately rated Aruba outdoor APs → protected wired or fiber backhaul → campus services. Assess wired backhaul first; any mesh design requires its own support and capacity review.

Survey the operating area

Map walkways, vehicle routes, loading work and actual client heights, including trees, metal structures and moving obstructions. Measure interference and candidate antenna directions. Derive coverage boundaries from required work locations rather than a nominal advertised radius.

Review installation and backhaul

Evaluate candidates such as AP-565 or AP-675 against regional, environmental, power and mounting requirements. Qualified installers must follow the selected model guide for grounding, surge protection, sealing and cable restraint. Check power reach and switch environment; assess fiber and local power where the copper design is unsuitable.

Treat mesh as a separate design

Verify model, software, regional and backhaul-band support before considering mesh. Measure the target workload over the intended hop count and failure path. Deliver a location plan, antenna directions, port records and installation acceptance evidence, with obstruction and seasonal retest requirements.

3. Network topology and forwarding

Prefer reliable wired backhaul and separate outdoor guest and operational policies. A mesh alternative needs its own line-of-sight, airtime, hop, channel, failure and capacity assessment. Lightning protection and grounding require qualified installation following the device guide and local requirements.

Dashed paths denote logical management or authentication dependencies, not physical direct cables. Central is the management service, not the client data-plane transit point. If tunneling is chosen, redraw and validate the AP-to-gateway path and the authenticator location for that mode.

SSID, segment and access-policy example

Names and VLAN IDs above are illustrative and must be mapped to the customer address plan. A VLAN is not a complete security boundary: enforce the approved ACL/firewall/role policy at the selected forwarding points and verify both allow and deny behavior. Publish only the minimum necessary SSIDs and verify legacy-client exceptions separately.

4. Implementation plan

1. Site walk：Confirm service boundaries, poles, obstacles, foliage, grounding and backhaul resources.
2. Placement trial：Test bidirectional client use at proposed height/orientation and indoor/outdoor transitions.
3. Engineering design：Document mounts, transport, PoE, sealing, grounding and safe access against installation guidance.
4. Configuration and transport：Verify destination channels/power, roles, management and uplink headroom; test mesh separately if selected.
5. Peak/environment validation：Test gathering peaks, loading operations and entrances; retain weather, client and location data.
6. Handover and inspection：Deliver placement, orientation, grounding and rollback records and post-weather/foliage inspection rules.

Change control and rollback gate

Before each batch, name the change owner, business approver and recovery operator. Preserve the approved pre-change configuration and verify that the hardware/software supports the intended recovery. Stop or roll back if critical transactions fail, identity rules are wrong or agreed recovery limits are exceeded. Capture timestamps and logs before altering the next variable.

5. Configuration and procurement checklist

6. Acceptance and operational handover

1. Test work-height clients along walkways and loading points, recording obstructions and application success.
2. Inspect mounting, grounding, sealing, power and uplinks with installation evidence.
3. For mesh, measure workload and failure behavior over the planned hop count.
4. Exercise a power or uplink alarm and confirm safe maintenance access.

Agree numeric coverage, SNR, packet-loss, latency and recovery thresholds with the application owner before the pilot. Record locations, representative clients, load and software so results can be reproduced.

7. Prepare a project request

Send scaled plans, device and application schedules, current software and topology, power and cabling records, destination and rollout constraints. We use these inputs to discuss a project-specific configuration and quotation.

Prepare the network BOM

8. Regional and architecture checks

Product families above are candidates for evaluation. Confirm exact destination SKUs, certifications, permitted channels and software support before ordering. For mainland China, global 6 GHz capability does not establish local permission to enable it. AOS 8, AOS 10 and Central features require version-specific verification.