Aruba Access Points (via Aruba Central)
ThirdEye provides support for managing Aruba Access Points (AP) via Aruba Central as a Cloud Device. Before beginning, ensure that there is a valid Aruba Central account with the necessary permissions to access the API. To monitor Aruba Access Points, you will need to configure a Cloud Account Credential for Aruba Central, and then use that credential in a Discovery job to find the Access Points.
Credentials
When configuring a Cloud Account Credential for Aruba Central, first make sure to generate the access token from the Aruba Central portal. With the access token details available, navigate to the Credentials page and create a new Cloud Account Credential.
The Aruba Central api provider has token validity time for both access and refresh tokens, due to this ThirdEye will periodically refresh the tokens. Starting with initial configuration of the credential.
When configuring the credential, use the information from the access token generated in the Aruba Central portal.
| Field | Required | Description |
|---|---|---|
| Credential Display Name | Y | The display name of this credential. |
| Cloud Account Provider | Y | The service provider of the cloud account (Aruba Central). |
| API Region | Y | The API Gateway region (According to the geographical cluster where the account is registered). |
| Client ID | Y | The client id to be used when requesting a new refresh token. |
| Client Secret | Y | The client secret to be used for token refresh. |
| Refresh Token | Y | The refresh token to be used. |
| Address Filter | N | The set of IPs or CIDR that will use this credential. |
Once the credential is configured, ThirdEye will do an initial token refresh to get the access token details. Thereafter, the tokens will be refreshed periodically, once 90% of the token’s expiry time has elapsed.
Telemetry (Neighbor Collection)
Any device discovered via Aruba Central will have support for Telemetry jobs, and can collect interface, OSPF and BGP neighbor data.
