Aruba Central Automation
Connect an Aruba Central environment with your own API credentials.
Connect Classic Central
Connected — Classic Central
Device status isn't available for this API client.
Webhook key whk_… active. Add the webhook URL shown when it was
generated to Aruba Central if you haven't already.
Connect New Central
Connected — New Central
Device status isn't available for this API client.
Webhook key whk_… active. Add the webhook URL and API key shown
when it was generated to New Central if you haven't already.
Connect Classic Central from the Connect Central tab to see its dashboard.
Connect New Central from the Connect Central tab to see your account overview.
Account Overview
Configuration
Query server status (RFC 5997)
Blank → edits each group's default radio profile (the “default” Central shows).
Named → creates/edits a named profile (
rf …-radio-profile <name> + zone <name>)
in each selected group; it applies to APs whose zone is set to that name (assign the zone in Central).
The 5 GHz settings are also written to the secondary 5 GHz radio.Only the fields you set below are changed — other radio settings are left alone.
Clear a field to fall back to Central's regulatory default.
| Option | 2.4 GHz | 5 GHz | 6 GHz |
|---|---|---|---|
| Configure this band | |||
| Allowed channels | |||
| Min transmit power (dBm) | |||
| Max transmit power (dBm) | |||
| Channel width | |||
| CSA count | |||
| High-noise backoff (s) | |||
| Advertise 802.11d & 802.11h | |||
| Spectrum monitor | |||
| Channel quality aware | |||
| Disable ARM/WIDS functions |
Off: only the options you set are added or changed. On: any of the managed options
(channels, TX power, width, CSA count, backoff, 802.11d/h, spectrum monitor, channel-quality-aware, ARM/WIDS) left blank here is
removed from the group. Use “Load from” first so the form matches the group.
Rules — evaluated top to bottom, first match wins
Service = Application / App category / Web category / Web reputation allows or denies by AppRF classification (applied on supported APs only). Values are CLI tokens — the suggestion lists aren't exhaustive, type any token your platform accepts. Use ↑ ↓ to reorder (first match wins); other rule options (time-range, throttle, …) on a loaded rule are preserved as-is.
Generated CLI
Creates a blank ArubaOS 10 group.
Add SSIDs / RF profiles / access rules with the configuration cards afterwards.
AOS-10 APs also carry their own regulatory domain — the group country here is a
default; the AP may already have one set at device level.
Device types in this group
Switch types
AOS-8 / Instant CLI. Indent sub-commands two spaces. Each top-level block
(e.g.
wlan ssid-profile …) is spliced into every selected group's live config —
a block with the same header is replaced, everything else is untouched.Generated CLI to be deployed
·
Load from
Deploy to AP groups *
Existing backups
| Name | Created | By | Protected |
|---|
Create a backup
Restore configuration
This overwrites 's entire configuration with the backup and pushes it to every device in the group. This cannot be undone. Type the group name to confirm.
Runs on this server, not in the cloud. This SSHes directly into
every AP, switch and gateway's management IP to pull its running config — it only
works if you're running Aruba Central Automation yourself (for example as a Docker
container) on a host that actually has network/SSH access to your devices. It will
not work on a shared or hosted instance that can't reach your LAN.
Central connection
Classic Central only — External Backup discovers devices via the Classic API, then SSHes to them directly.
Device SSH login
One admin username/password, tried over SSH against every discovered AP, switch and gateway.
Destination server
Schedule
History
Configuration
Note: creating/deleting AP groups isn't supported when your account has both Classic and New Central — Central rejects it; use the Central UI. It works on standalone / on-prem New Central.
HPE Aruba's API only allows creating device groups on standalone / on-prem New Central.
If your account also has Classic Central (the toggle at the top-right of the Central UI), Central will
reject this — create the group in the Central UI instead. Try Create below to check.
Set the radios you want; leave a field blank to keep the Central default.
| Option | 2.4 GHz | 5 GHz | 6 GHz |
|---|---|---|---|
| Include this radio | |||
| Min TX power (dBm) | |||
| Max TX power (dBm) | |||
| Min channel width | |||
| Max channel width | |||
| Allowed channels | |||
| 802.11h |
Creates a New Central policy (the rules) plus a matching role, evaluated top to bottom. Source is Any; set the service and destination per rule.
Policy JSON
Assign to AP groups (optional)
The profile is always created in the library. Assigning it to a group also attaches it there
(device function: Campus AP) — this can fail if the group already has a profile of that kind, or (for SSIDs)
needs a matching role; the create still succeeds and you can finish the assignment in the Central UI.
| Setting | 2.4 GHz | 5 GHz | 6 GHz |
|---|---|---|---|
| Change this band | |||
| Allowed channels | |||
| Min TX power (dBm) | |||
| Max TX power (dBm) |
Blank fields are left unchanged. Untick a band to skip it entirely.
AP groups *
| Radio | 2.4 GHz | 5 GHz | 6 GHz · AOS-10 |
|---|---|---|---|
| Assignment | |||
| Channel | |||
| TX power (dBm) |
Automatic hands that radio back to ARM / AirMatch.
Manual pins it — enter a channel (AOS-10 also takes a TX power; leave power blank for auto power).
AOS-8 / Instant APs have 2.4 & 5 GHz only.
Access points *
| Setting | 2.4 GHz | 5 GHz | 6 GHz |
|---|---|---|---|
| Allowed channels | |||
| Min TX power (dBm) | |||
| Max TX power (dBm) |
Creates a per-AP radio profile (constrained channels + power) assigned to that AP. A single channel pins it; several let AirMatch choose among them. Type
auto in a channel field to remove the per-AP profile. AirMatch applies changes on its next run — allow a few minutes.Access points *
Topology
100%
© Aruba Central Automation