HPE Aruba hotel Wi-Fi with room APs, guest isolation and shared-area coverage

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 inputs: 120 rooms × 85% occupancy × 3 connected devices gives about 306 associated clients; busy-hour activity still needs measurement. A separate 180-person event needs its own airtime, portal and Internet model. Do not average room and event peaks. Survey room types before fixing hospitality AP quantities.

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

Room clients and wired endpoints → Aruba hospitality APs → floor PoE switching → hotel services and Internet. Lobby and event spaces use their own campus AP design. Central, ClearPass and business integrations are selected by requirement.

Validate the room, not just the corridor

Survey representative room types with doors closed and real client positions at the bed and desk. Measure adjacent-floor interference. Lobby, restaurant and ballroom demand requires a separate capacity model. Select hospitality AP candidates such as AP-505H or AP-605H only after checking the destination SKU, software and lifecycle.

Check room services and access lifecycle

Document AP input power and any downstream PoE requirement separately, including wired VLANs and switch-wide power budget. Define voucher issuance, expiry and checkout revocation. PMS integration requires a supported interface, software and commercial scope. Verify room-scoped discovery with same-room and adjacent-room devices rather than assuming discovery visibility follows physical room boundaries.

Pilot with hotel operations

Test a representative floor before a phased rollout. Include reception staff in credential recovery and incident workflows. Record room-to-AP-to-switch mappings, management ownership and rollback steps. Validate busy-hour access and restore service during agreed maintenance periods.

3. Network topology and forwarding

Room and shared-area APs use a manageable access foundation while guest, hotel-office, in-room service and management traffic have distinct policies. Decide whether wired room ports share a guest isolation boundary. Discovery alone does not authorize casting traffic: verify visibility, authorization, ACLs and checkout cleanup together.

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 inventory：Collect room/floor plans, cable records, switches and PMS versions; agree room closure and night-work windows.
2. Representative-room pilot：Trial candidate room APs in corner, thick-wall and standard rooms; test bidirectional bed/desk use with doors closed.
3. Floor power and access：Verify AP input and room-device output power per port; size the floor switch and uplink for peak load.
4. Guest and room policy：Validate guest credentials, staff roles and supported room discovery; test PMS integration in a limited environment first.
5. Operational pilot：Exercise check-in, extension, room change, checkout and credential recovery on one floor.
6. Floor-by-floor rollout：Avoid arrival peaks; hand over room/port mappings, reception instructions, escalation and rollback records.

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 bed and desk locations with doors closed and document coverage and application throughput.
2. Verify room-service VLANs, downstream PoE and the switch power budget at peak load.
3. Use adjacent-room clients to test isolation, discovery scope and credential expiry.
4. Measure busy-hour authentication and Internet access, including reception recovery workflows.

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.