Aruba EdgeConnect
ThirdEye’s provides cloud device support for HPE Aruba EdgeConnect (EC) devices (formally known as SilverPeak). You can manage EdgeConnect devices locally via deployed Orchestrator or Aruba Central cloud portal.
Credential Handling
For EdgeConnect devices, you must configure the API key and API URL to access Orchestrator or the cloud portal.
| Field | Required | Description |
|---|---|---|
| Cloud Account Provider | Y | The service provider of the cloud account (Aruba EdgeConnect) |
| Account User | Y | The username of the cloud credential |
| API URL | Y | The API provider url |
| API Key | Y | Password or the access token for the account |
| Address Set | N | The set of IPs or CIDR to use this credential |
Discovery
Discovery for EdgeConnect devices is similar to that of other cloud devices. You can configure multiple cloud account credentials.
Once you select the required cloud accounts, they will be used in the discovery process to fetch the devices within the discovery boundary from the Orchestrator API. Any issues will be displayed in same fashion as with any other discovery errors. Discovery will add the following information to the device’s metaJson with the key cloudData.
| Field | Description |
|---|---|
| cloudAccount | The name of the cloud account which was used |
| organizationalId | The Id used for the device in Orchestrator |
Discovered devices will appear in the [General] tab as shown below:
Telemetry (Neighbor Collection)
Any device discovered via an EdgeConnect provider will have support for Telemetry jobs, and can collect interface, OSPF and BGP neighbor data.
