Skip to main content
The common use is a device-down or alert ticket: the agent finds the device in the customer’s Aruba Central tenant, reads its status, its site’s health and the alerts around it, writes what it found on the ticket, and acknowledges or clears the alert once the issue is handled.
Automatically enabled when you configure HPE Aruba Networking Central permissions in your agent workflow.

What It Does

  • Work in the ticket company’s own Aruba Central tenant, from the company mapping
  • Read alerts and notifications, events, insights and audit logs; acknowledge, clear, defer or reprioritize alerts
  • Read access points, switches, gateways, stacks and swarms: status, ports, PoE, radios, uplinks, tunnels and trends
  • Read site and network health, topology and routing tables
  • Find a user’s wireless or wired client, its connection and its roaming history
  • Move devices between configuration groups or device groups, and add devices to or remove them from sites
  • Reboot a device, blink its LEDs, bounce a port or its PoE, run a cable test, disconnect clients
  • Run ping, traceroute, show commands and other troubleshooting tests from a device
  • Read and change configuration, firmware, inventory, subscriptions, security and guest settings, users and alert rules
Neo works with both platforms: Central, the current platform managed from HPE GreenLake, and Classic Central. Their paths differ, and the agent’s skill uses the ones for your platform.

Permission Groups

Access Profiles

Safety Controls