HPE Aruba Central, AP and CX Field Runbook
Aruba equipment can be physically healthy while appearing in the wrong Central group, inheriting unintended configuration or failing to provide usable client service. TechRunz aligns inventory, subscriptions, group architecture, switch and AP prerequisites, field installation and measured acceptance before the site is handed to operations.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Account, group and configuration readiness
Confirm device serials, customer account, subscriptions, Central group and site before shipping or installation. Identify whether the group uses UI configuration, templates or other approved orchestration, and determine which settings are inherited versus site-specific.
Review the AOS-CX and AP software plan, management addressing, DNS, NTP, certificates, VLANs, trunks, spanning tree, link aggregation, authentication and firewall dependencies. Record the approved startup or replacement path rather than allowing a factory-default device to join an uncertain group.
Before a device ships, agree on which Central group it lands in when it first calls home, who holds the account rights to move it, and what the technician does if a switch or AP arrives unprovisioned. Naming that decision early reduces onsite guesswork about template inheritance and subscription state.
- Authorized Central account
- Inventory, subscription and group
- Software and configuration baseline
- Network-service prerequisites
Switch and AP field installation
Rack and cable switches with clear member, uplink and power labels. For VSF or VSX designs, verify model support, member order, links and remote change sequence before joining production. Confirm transceivers, link speed, errors and PoE budget after the physical build.
Install APs at the scheduled coordinates using the approved mount and orientation. Reconcile each AP serial to room, cable and switch port. Confirm it receives the intended VLAN and power and appears in the correct Central site before moving to the next area.
VSF member insertion and VSX pairing steps deserve their own hold points, with a remote engineer watching Central events as each link comes up. Leave the prior uplink patching intact until the new member reports healthy, and log any mount or port substitution while you are still standing at that location.
- Switch member and uplink labels
- VSF or VSX verification
- AP serial, mount and cable mapping
- PoE and transceiver health
| Component | Field acceptance | Evidence |
|---|---|---|
| Central | Account, group, site and subscription | Inventory and health record |
| AOS-CX | Members, uplinks, VLANs, PoE and management | Port and topology checks |
| Access points | Location, cable, RF and client service | Annotated plan and tests |
| Operations | Alerts, software, recovery and ownership | Closeout package |
Client, RF and resilience validation
Test management reachability, gateway and routing behavior, DHCP, DNS, authentication and required application paths. Use representative wired and wireless clients and verify the intended SSID, role or policy rather than accepting association alone.
Review radio state, channel and power behavior after the network has stabilized. Test roaming on defined paths and approved switch, uplink or power recovery scenarios. Capture Central alerts and event timelines when results differ from the design so remote engineers can reproduce the condition.
Evidence carries further when a client-side observation sits beside the matching Central record: the authentication or role result, the switch port state and the timestamp of the event. Save those together for each area tested so a remote engineer can separate an RF question from a policy or upstream routing question.
- Identity, DHCP and DNS
- Representative client workflows
- RF and roaming checks
- Approved failure and recovery tests
Central records and operational handoff
Reconcile Central inventory, group, site, labels and subscription status with installed serials and annotated plans. Record AOS-CX switch names, member positions, management addresses, uplinks, AP ports, software versions and outstanding alerts.
Deliver protected configuration and recovery records to the client-controlled repository. Name the team responsible for Central administration, software policy, certificate lifecycle, alert response and support entitlement. Temporary credentials and private configuration output should not appear in general field reports.
The record read during a later replacement is the one worth building now: which serial sat on which mount, the AOS-CX or AP version it carried, the group it belonged to and the port that fed it. File that with the annotated plans, and point readers to HPE Aruba documentation for firmware guidance.
- Central inventory reconciliation
- Software and topology records
- Alerts, exceptions and ownership
- Protected recovery information
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Confirm Central group
Reconcile device inventory, subscriptions and target group so each AP and switch inherits the intended configuration.
Stage switch uplinks
Prepare CX switch roles, uplinks and PoE budget before an access point ever draws power onsite.
Install and label
Mount APs to the plan, land them on labeled CX PoE ports and confirm each checks into its Central group.
Measure client service
Validate association, roaming, DHCP and application reach with representative clients rather than accepting an online status.
Information to gather before design
Aruba devices can appear online while sitting in the wrong group, so the field team needs account, subscription and design detail before the first dispatch.
- Central group and site structure
- Device serials and subscription assignments
- CX uplink and VLAN design
- AP mounting locations and heights
- Central label and naming conventions
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Why verify the Central group before an AP or switch connects?
Group assignment can control inherited configuration; an incorrect group can produce an avoidable outage or rework.
Is an AP healthy when Central shows it online?
Online status is necessary but not sufficient. Validate switch port, power, RF, authentication, addressing and representative applications.
Should VSF or VSX changes be improvised onsite?
No. Member order, supported topology and recovery should be reviewed in an approved method before production changes.
What should operations receive?
Central and device inventory, topology, ports, software, tests, alerts, exceptions, recovery records and named ownership.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Start an Aruba Central site deployment
Send the site list, the Central group structure you expect devices to land in, and the CX and AP models being installed. Photos of existing racks and uplink paths help scope the dispatch.