One OAuth2 app in Aruba Central's API Gateway lets SmartTile read every switch, access point and gateway Central manages — status every three minutes, clients, SSIDs, subscriptions and firmware compliance — and turn an Aruba device going offline into the same alert and ticket as any other outage.
Aruba Central already knows which switch, access point and gateway is online. What it does not do is put that next to your circuits, firewalls and cameras, or open the ticket in the IT Service Management (ITSM) system your team works from. SmartTile reads Central through its own REST API — reads only, apart from one firmware call that is off by default — so an Aruba device that goes dark is handled exactly like any other outage.
Groups, sites (with address), the device inventory, and every switch, AP and gateway: serial, MAC, model, part number, firmware, IP and public IP, uptime, clients, CPU, memory, temperature, PoE draw, fan and power supply, stack role and config-sync state.
Online / offline per device from Central's monitoring lists — three calls a check, paced for Central's ~5,000 calls-a-day allowance. Adjustable 60–3,600 s under Admin → Uptime Analytics → API check frequency.
A device that disappears from a list that otherwise came back fine for 3 two-minute periods is marked offline. Central omitting a dead device never leaves it green. Adjustable 0–30 periods.
Map an Aruba device to a SmartTile device with ping off and Central owns its up/down: DOWN with state history (source Aruba API), then the normal alert and auto-ticket after 14 min offline. Ping-monitored devices stay with ping.
Connected wireless and wired clients (SSID, VLAN, RSSI, SNR, band, OS, the AP or switch they are on), SSIDs with client counts, and every subscription with quantity, used and end date.
Central's current vs recommended build per device on the Firmware tab. On mapped devices an upgrade-available build becomes a FirmwareAutomate advisory: ticket, window, verify. SmartTile pushes the upgrade only if you switch that on.
| Field | Where it comes from |
|---|---|
| Client ID / Secret | Central → API Gateway → My Apps & Tokens |
| Access + Refresh Token | Generated for that app in API Gateway |
| Customer ID (CID) | Central account-home page header |
| Region / gateway URL | Your Central cluster; custom URL for “Other” |
| Auto-refresh | On by default — SmartTile renews the pair before expiry |
/oauth2/tokenrefresh the token pair (Central rotates the refresh token — both are re-saved encrypted)/central/v2/sitessites and addresses; also the Test call/configuration/v2/groupsconfiguration groups/platform/device_inventory/v1/devicesinventory: serial, MAC, model, part number/monitoring/v1/switchesswitch status and health/monitoring/v2/apsAP status, radios, clients (v1 fallback)/monitoring/v1/gatewaysgateway status (mobility controllers as fallback)/monitoring/v2/networks · /v2/clientsSSIDs, connected wireless + wired clients/platform/licensing/v1/subscriptionssubscriptions, seats, end dates/firmware/v1/devicesrunning vs recommended firmware/firmware/v1/upgradeonly when “Execute upgrades” is on — off by defaultClient secret, access and refresh tokens are encrypted AES-256-GCM before they are stored. The API returns only “token stored / expires at” — never the value.
Seven requests a second per credential, backoff on 429 and 5xx, and the credential pauses itself after 50 failures in a row rather than hammering a dead account.
Every request is scoped to your organization and company. A mapping to a device, location or company outside your account is refused. Changes need an admin.
Credentials added, tested, mapped, firmware scheduled, sync switched — each lands in the Aruba audit log. Background sync has an on/off switch and a server kill switch.
| Objection | Answer |
|---|---|
| “Will SmartTile change our Aruba configuration?” | No. Every call is a read. The only write is the firmware upgrade request, and it stays off unless you turn on Execute upgrades. |
| “We already have Central's own alerts.” | Keep them. SmartTile adds the same outage alert, state history and ticket your other devices get, next to your circuits and firewalls. |
| “Our API allowance is tight.” | Status runs every 3 minutes at three calls a check by default; full discovery once a night. |