What Neo can do with Aruba Central
- Read the alerts behind a ticket, and acknowledge or clear them once the issue is handled
- Read the status and stats of access points, switches and gateways: ports, PoE, radios, uplinks and tunnels
- Read site health and find a user’s wireless or wired client
- Move a device into the right group, and add it to or remove it from a site
- Reboot an access point, switch or gateway, bounce a port or its PoE, and run ping or show commands from a device
Each call acts in one customer tenant
An MSP account in Aruba Central holds each customer as a tenant. Neo names the tenant on every call: on Classic Central with the tenant’s customer ID, and on Central with a token HPE GreenLake issues for that tenant only. On a ticket, Neo acts only in the tenant the ticket’s company is mapped to. A customer that runs its own Aruba Central account can connect it as that customer’s own key on the card; Neo then uses it for that customer’s tickets.Your tenants are mapped to companies
Neo matches your Aruba Central tenants to the companies in your PSA and keeps the mapping on the card’s Organization Mapping tab, refreshed on each PSA metadata sync. An exact name that matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents. Every other match waits for you on the Organization Mapping tab: a match after stripping a legal-form suffix, a name two of your PSA companies share, two tenants on one company, and an AI match. A mapping you set by hand survives every later sync. See HPE Aruba Networking Central API for the permission groups.Next steps
Connect Aruba Central
Create an API client and save it in Neo.