Aruba / HPE

Purpose

The Aruba integration polls Aruba switches, controllers and Aruba Central-managed access points to collect VLAN, wireless client and configuration evidence using SNMPv3 or the Aruba Central API.

Requirements

• For on-prem: SNMPv3 enabled on AOS-CX/AOS-Switch devices and SSH for config backup
• For cloud-managed: an Aruba Central account with a read-only API token
• Network reachability from the collector to the management plane

Permissions

• SNMPv3 authPriv user for on-prem switches and controllers
• Read-only SSH account for configuration capture on AOS-CX/AOS-Switch
• Aruba Central API token scoped to a Read-Only role for cloud-managed estates

Setup

1. 1
   Choose management mode

   Identify whether the site uses on-prem controllers/switches or Aruba Central.
2. 2
   Configure SNMPv3 (on-prem)

   Create an SNMPv3 authPriv user matching the AssurIQ credential profile.
3. 3
   Create a read-only SSH account (on-prem)

   Create an account restricted to read/show commands for configuration backup.
4. 4
   Generate a Central API token (cloud-managed)

   In Aruba Central, generate an API token for a Read-Only role.
5. 5
   Add credentials to AssurIQ

   Store the relevant credential in the Credential Vault and add the device or Central account under Integrations.

Verification

• Aruba devices appear in Network Map with model and firmware
• VLAN and wireless client data populates
• Configuration backup succeeds for on-prem switches

Data collected

• Switch, controller and AP inventory and firmware
• VLAN, trunk and wireless SSID configuration
• Wireless client inventory and association history
• Configuration snapshots for on-prem devices

Security model

SNMPv3 authPriv encrypts polling traffic; the SSH account is read-only and cannot modify configuration. The Aruba Central API token is scoped to a Read-Only role and cannot push configuration changes.

Common errors

• AIQ-SNMP-002SNMP authentication failed
  The credential profile was rejected by the device (bad community string or SNMPv3 auth/priv mismatch).
• AIQ-CRD-001Credentials failing
  Stored credentials were rejected by one or more targets.

Troubleshooting

• If cloud-managed sites show no data, confirm the Central API token has not expired (tokens are time-limited by default).
• If on-prem config backup fails, confirm SSH is enabled and reachable.

Disconnect

1. Remove the device or Central account from AssurIQ Integrations.
2. Revoke the Central API token or delete the SNMPv3/SSH credentials on-prem.