Api Reference Guide
Api Reference Guide
Contents
Contents 3
About this Guide 4
Related Documents 4
Conventions 4
Terminology Change 5
Contacting Support 5
API Gateway 6
Accessing API Gateway 7
Viewing Swagger Interface 7
List of Supported APIs 8
Domain URL 10
Creating Application and Token 10
Using OAuth 2.0 for Authentication 12
Access and Refresh Tokens 12
Obtaining Token Using Offline Token Mechanism 16
Obtaining Token Using OAuth Grant Mechanism 16
Step 1: Authenticate a User and Create a User Session 17
Step 2: [Optional] Generating Client Credentials 18
Step 3: Generate Authorization Code 19
Step 4: Exchange Auth Code for a Token 20
Step 5: Refreshing a Token 21
Step 6: Deleting a Token 22
Viewing Usage Statistics 23
Changes to Aruba Central APIs 24
New APIs 25
Modified API 29
Deprecated APIs 31
Removed APIs 34
Webhooks 37
Creating and Updating Webhooks Through the UI 38
Viewing Webhooks 40
Refreshing Webhooks Token Through the UI 41
Creating and Updating Webhooks Through the API Gateway 41
List of Webhooks APIs 42
Sample Webhooks Payload Format for Alerts 44
Access Point Alerts—Sample JSON 44
AOS-Switch Alerts—Sample JSON 55
AOS-CX Switch Alerts—Sample JSON 62
Gateway Alerts—Sample JSON 69
Miscellaneous Alerts—Sample JSON 87
Related Documents
For more information on Aruba Central, see Aruba Central Help Center —To access help center, click the help
Conventions
The following conventions are used throughout this guide to emphasize important concepts:
Italics This style is used to emphasize important terms and to mark the titles of books.
Contacting Support
Table 2: Contact Information
API Gateway
The API Gateway feature in Aruba Central supports the REST API for all Aruba Central services. This feature
allows Aruba Central users to write custom applications, embed, or integrate the APIs with their own
applications. The REST APIs support HTTP GET and POST operations by providing a specific URL for each
query. The output for these operations is returned in the JSON format.
For secure access to the APIs, the Aruba Central API Framework plug-in supports OAuth protocol for
authentication and authorization. The access tokens provide a temporary and secure access to the APIs. The
access tokens have a limited lifetime for security reasons and the applications should use the refresh API to
obtain new tokens periodically (every 2 hours).
The API call volume is rate-limited to seven (7) calls per second, per customer.
The following figure illustrates the API gateway workflow for the users:
1. In the Account Home page, under Global Settings, click API Gateway.
The API Gateway page is displayed. You can get new tokens and refresh old tokens. To obtain a new token
application, you must set authentication parameters for a user session.
1. In the Account Home page, under Global Settings, click API Gateway.
The API Gateway page with the list of published APIs is displayed.
2. To view the Swagger interface, click the link in the Documentation column next to the specific
published API name. The documentation is displayed in a new window.
API Gateway | 7
Figure 2 API Gateway Dashboard
Monitoring Gets network, client, and event details. It also allows you to manage labels and switches.
n Devices
Aruba has enforced a request limit for the following APIs:
n GET /msp_api/v1/customers
n GET /msp_api/v1/customers/{customer_id}/devices
n GET /msp_api/v1/devices
n PUT /msp_api/v1/customers/{customer_id}/devices
The maximum limit is set to 50 per API call. If you exceed this limit, the API call returns the
HTTP error code 400 and the following error message: LIMIT_REQUEST_EXCEEDED.
User Allows you to manage users and also allows you to configure various types of users with a
Management specific level of access control.
Audit Event Logs Gets a list of audit events and the details of an audit event.
Presence Allows you to configure the Presence Analytics application. It also retrieves site and loyalty
Analytics data.
Notification Gets notification alerts generated for events pertaining to device provisioning,
configuration, and user management.
Unified Retrieves data for all sessions for a specific period of time. It also retrieves the total
Communications number of clients who made calls in the given time range and gets the Lync/Skype for
Business URL for the Aruba Central cluster that you are using.
Reporting Gets the list of configured reports for the given customer ID.
Network Health Allows you to get data for all the labels and sites.
Webhook Allows you to add, or delete Webhooks, and get or refresh Webhook tokens. See Webhooks
for further details on Webhook.
VisualRF Allows you retrieve information on floor plans, location of APs, clients and rogue devices.
DPS Monitoring Gets DPS compliance and session statistics for all the links of a device belonging to a
specific policy.
For a complete list of APIs and the corresponding documentation, see https://app1-
apigw.central.arubanetworks.com/swagger/central.
This section also includes the following topics:
API Gateway | 9
n Domain URL
n Creating Application and Token
n Viewing and Revoking Tokens
n Obtaining Token Using Offline Token Mechanism
n Viewing Usage Statistics
n Changes to Aruba Central APIs
Domain URL
To access the API Gateway or generating tokens, you must use the appropriate domain URL.
The following table shows the region-specific domain URLs for accessing API Gateway:
US-1 app1-apigw.central.arubanetworks.com
US-2 apigw-prod2.central.arubanetworks.com
US-WEST-4 apigw-uswest4.central.arubanetworks.com
EU-1 eu-apigw.central.arubanetworks.com
EU-2 apigw-eucentral2.central.arubanetworks.com
EU-3 apigw-eucentral3.central.arubanetworks.com
Canada-1 apigw-ca.central.arubanetworks.com
China-1 apigw.central.arubanetworks.com.cn
APAC-1 api-ap.central.arubanetworks.com
APAC-EAST1 apigw-apaceast.central.arubanetworks.com
APAC-SOUTH1 apigw-apacsouth.central.arubanetworks.com
1. In the Account Home page, under Global Settings, click API Gateway.
The API Gateway page is displayed.
The admin user will be able to create new apps for all the non-admin user by clicking + Add Apps &
Tokens in the System Apps & Tokens tab.
API Gateway | 11
n Name—Name of the application. In non-admin user profile, the Application Name field
contains the logged-in user name and is non-editable. Any new tokens generated in non-
admin user profile is associated with the same application name.
n Client ID—Unique ID for each application.
n Client Secret—Unique secret ID for each application.
n Redirect URI—Redirect URL.
n Application—Name of the application. For example, Network Operations.
n Tokens—Token created for the application. The option is available to admin user profile only.
n Created At—Date on which the application was created.
To delete the added application, click delete icon on the row corresponding to an application and click
Yes to delete that application.
Only admin users will be able to generate tokens with multiple application names. In non-admin user profile, the
Application Name field contains the user name and is non-editable. Any new tokens generated in non- admin
user profile is associated with the same application name. However, all the multiple application names and the
associated tokens in non-admin user profiles from the earlier versions is retained in the Token List table.
Accessing APIs
To access the API, use the following URL:
https://app1-apigw.central.arubanetworks.com/.
This endpoint is accessible over SSL and the HTTP (non-SSL) connections are redirected to the SSL port.
https://app1- The API gateway URL. All APIs can be accessed from this URL by providing
apigw.central.arubanetworks.com/ a correct access token.
request_path URL URL path of an API, for example, to access monitoring APIs, use the path
Path /monitoring/v1/aps.
Example
Request Method: GET
https://app1-apigw.central.arubanetworks.com/monitoring/v1/aps
Request Header:
Authorization: Bearer ouzMaXEBbB6XqGtsWomK7MvaTuhrqDQ1
Response:
{
"aps": [
{
"firmware_version": "6.4.4.4-4.2.3.1_54637",
"group_name": "00TestVRK",
"ip_address": "10.29.18.195",
"labels": [
"Filter_242",
"Ziaomof",
"roster",
"242455",
"Diegso"
],
"macaddr": "6c:f3:7f:c3:5d:92",
"model": "AP-134",
API Gateway | 13
"name": "6c:f3:7f:c3:5d:92",
"radios": [
{
"band": 0,
"index": 1,
"macaddr": "6c:f3:7f:b5:d9:20",
"status": "Down"
},
{
"band": 1,
"index": 0,
"macaddr": "6c:f3:7f:b5:d9:30",
"status": "Down"
}
],
"serial": "AX0140586",
"status": "Down",
"swarm_id": "e3bf1ba201a6f85f4b5eaedeead5e502d85a9aef58d8e1d8a0",
"swarm_master": true
}
],
"count": 1
}
Example
Request Method: GET
https://app1-apigw.central.arubanetworks.com/central/v2/sites
Request Header:
TenantID: 267958b55d5a463e94a302c20f4a6b68
Response Code: 200
Response:
{
"count": 1,
"sites": [
{
"address": "bangalore",
1. In the Account Home page, under Global Settings, click API Gateway. The API Gateway page is
displayed.
2. Click My Apps & Tokens. The Token List table displays the following:
n Token ID—Token ID of the application.
n User Name—Name of the user to whom this token is associated to. An application can be
associated to multiple users.
n Application—Name of the application to which this token is associated to. For example, Network
Operations.
n Generated At—Date on which the token was generated.
n Revoke Token—Click Revoke Token and click Yes to revoke the token associated to a particular
user. For example, if two users are associated to an application and if you want to remove access
to a particular user, revoke the token associated to that user.
n Download Token—Click Download Token to download the token.
In MSP mode, the admin user profile has System Apps & Tokens tab which displays all the apps and tokens
generated in all non-admin user profiles in addition to the apps and tokens created in the admin user profile. To
view all the tokens of admin and non-admin user, go to Account Home > Global Settings > API Gateway >
System Apps & Tokens.
1. In the Account Home page, under Global Settings, click API Gateway. The API Gateway page is
displayed.
2. Click My Apps & Tokens.
The admin user can create new tokens for all non-admin users by clicking + Add Apps & Tokens in the System
Apps & Tokens tab.
API Gateway | 15
3. Click + Add Apps & Tokens to add a new token.
4. Enter the application name in the Application Name box and click Generate.
If you have registered a custom URI when creating a new app under System Apps and Tokens, the Redirect
URI option is disabled for you in the My Apps and Tokens tab > Add Apps and Tokens > New Token . In such
cases, the Redirect URI option in Add Apps and Tokens > New Token under My Apps and Tokens populates
your already registered URI.
1. In the Account Home page, under Global Settings, click API Gateway. The API Gateway page is
displayed.
2. Click My Apps & Tokens.
In the MSP mode, the admin user profile can view the System Apps & Tokens tab which displays all the
apps and tokens generated in all the non-admin user profiles in addition to the apps and tokens created in
the admin user profile.
3. Click + Add Apps & Tokens. The New Token pane is displayed.
4. Enter the application name and redirect URI in the Application Name and Redirect URI fields
respectively.
5. Choose the application from the Application drop-down list and click Generate to generate a new
token.
6. The Token List table displays the following:
n Token ID—Token ID of the application.
n User Name—Name of the user to whom this token is associated to. An application can be
associated to multiple users.
n Application—Name of the application to which this token is associated to. For example, Network
Operations.
n Generated At—Date on which the token was generated.
n Revoke Token—Click Revoke Token and click Yes to revoke the token associated to a particular
user. For example, if two users are associated to an application and if you want to remove access
to a particular user, revoke the token associated to that user.
n Download Token—Click Download Token to download the token.
API calls are limited to 1 API per second. This rate-limit is applicable only to the APIs in the first 3 steps mentioned
above.
Example
Request Method: POST
URL: https://app1- apigw.central.arubanetworks.com/oauth2/authorize/central/api/login?client_
id=<client_id> HTTP/1.1
Host: app1-apigw.central.arubanetworks.com
Request Header:
Accept: application/json
Content -Type: application/json
POST Request Body(JSON):
{
"username": "xxxxx",
"password": "xxxxx"
}
Error Response:
400: Bad Request
Response Body (JSON):
{
"extra": {},
API Gateway | 17
"message": "<error string>"
}
401: Auth failure
Response Body (JSON):
{
"message": "Auth failure",
"status": false
}
429: API rate limit exceeded
Response Body (JSON):
{
"message": "API rate limit exceeded"
}
Success Response:
200: OK
Response Body (JSON):
{
"status": true
}
Response Header:
Set-Cookie: csrftoken=xxxx;session=xxxx;
The csrf token value received in the successful response message must be used as a parameter for all
subsequent POST/PUT requests. The session value must also be used for all subsequent requests to maintain
the user session context.
Example
Request Method: POST
URI—https://app1-apigw.central.arubanetworks.coms/oauth2/authorize/central/api/client_
credentials?client_id=<msp_client_id>
POST Request Body(JSON):
{
"customer_id": "<tenant_id>"
}
Request Header: (Values from login API request)
Set-Cookie: csrftoken=xxxx;session=xxxx;
Response Body(JSON):
{
"client_id": "<new-client-id>",
"client_secret": <new-client-secret>"
}
Error Response
client_id client_id is a The client_id is a unique identifier that identifies the caller. Application
unique developers obtain a client ID and a client secret when they register with the
hexadecimal API gateway admin.
string
response_ code Use code as the response type to get the authorization code that can be
type exchanged for token
scope all or read Requested API permissions may be either all (for both read and write
access) or read for read-only access.
Example
Request Method: POST
URL: https://app1 - apigw.central.arubanetworks.com/oauth2/authorize/central/api/?client_id=<client_
id>&response_type=code&scope=all HTTP/1.1
Host: app1-apigw.central.arubanetworks.com
Request Header:
Accept: application/json Cookie: “session=xxxx” X-CSRF-Token: xxxx
Content -Type: application/json
POST Request Body(JSON):
{
"customer_id": "xxxxx"
}
Error Response:
400: Bad Request
Response Body (JSON):
{
"extra": {},
"message": "<error string>"
}
401: Auth failure
API Gateway | 19
Response Body (JSON):
{
"message": "Auth failure",
"status": false
}
429: API rate limit exceeded
Response Body (JSON):
{
"message": "API rate limit exceeded"
}
Success Response:
200: OK
Response Body (JSON):
{
" auth_code ": “xxxx”
}
Pass the csrf-token value you obtained in step one in the request header, otherwise the request will be rejected.
Note the auth_code value in the response, as you will use this code to obtain an OAuth token.
Response Header:
Set-Cookie: csrftoken=xxxx;session=xxxx;
client_id client_id is a The client_id is a unique identifier that identifies the caller. Application
unique developers obtain a client ID and a client secret when they register with the
hexadecimal API gateway admin.
string
client_secret client_secret is The client_secret is a unique identifier provided to each developer at the time
a unique of registration. Application developers can obtain a client ID and client secret
hexadecimal when they register with the API gateway admin.
string
grant_type authorization_ Use code to get the authorization code that can be exchanged for the token.
code
code auth_code The authorization code received from the authorization server.
received from
step 1
redirect_uri string The redirect URI must be the same as the one given at the time of
registration. This is an optional parameter.
The response to this API query is a JSON dictionary with following values:
token_type bearer Identifies the token type. Central supports only the bearer token type (See
https://tools.ietf.org/html/rfc6750)
refresh_ string Refresh tokens are credentials used to renew or refresh the access_token when it
token expires without repeating the complete authentication flow. A refresh token is a
string representing the authorization granted to the client by the resource owner.
access_ string Access tokens are credentials used to access protected resources. An access token is
token a string representing an authorization issued to the client.
Example
Request Method: POST
URL: https: //apigw-prod2.central.arubanetworks.com/oauth2/token?client_id=<Ccentral-API-app-
clientid>&client_secret=xxxx&grant_type=authorization_code&code=xxxx \
Content -Type: application/json
Response:
{
"refresh_token": "xxxx",
"token_type": "bearer",
"access_token": "xxxx",
"expires_in": 7200
}
https://app1- The endpoint is a POST call to refresh the access token using
apigw.central.arubanetworks.com/oauth2/token the refresh token obtained from the server
API Gateway | 21
Query parameters for this API are as follows:
client_id client_id is a The client_id is a unique identifier that identifies the caller. Application
unique developers obtain a client ID and a client secret when they register with the
hexadecimal API gateway admin.
string
client_secret client_secret is The client_secret is a unique identifier provided to each developer at the time
a unique of registration. Application developers obtain a client ID and a client secret
hexadecimal when they register with the API gateway admin.
string
grant_type refresh_token Specify refresh_token as the grant type to request that an authorization code
be exchanged for a token
refresh_ string A string representing the authorization granted to the client by the resource
token owner.
The response to this API query is a JSON dictionary with following values:
token_type bearer Identifies the token type. Only the bearer token type is supported. For more
information, see https://tools.ietf.org/html/rfc6750.
refresh_ string Refresh tokens are credentials used to renew or refresh the access token when it
token expires without going through the complete authorization flow. A refresh token is a
string representing the authorization granted to the client by the resource owner.
access_ string Access tokens are credentials used to access the protected resources. An access
token token is a string representing an authorization issued to the client.
Example
Method: POST
https://apigw-prod2.central.arubanetworks.com/oauth2/token?client_id=<Central-API-app-
clientid>&client_secret=xxxx&grant_type=refresh_token&refresh_token=xxxx
Response
{
"refresh_token": "xxxx",
"token_type": "bearer",
"access_token": "xxxx",
"expires_in": 7200
}
Example
Method : DELETE
URL:https://app1-apigw.central.arubanetworks.com/oauth2/api/tokens
JSON Body:
{
"access_token": "<access_token_to_be_deleted>"
}
Headers:
Content-Type: application/json
X-CSRF-Token: <CSRF_token_obatained_from_login_API>
Cookie: "session=<session_obatained_from_login_API>"
n Current Usage
n Last one week API usage data
n Per user usage
n MSP and tenant usage if you are in MSP mode
To view the usage statistics for users of API Gateway, complete the following steps:
1. In the Account Home page, under Global Settings, click API Gateway. The API Gateway page is
displayed.
API Gateway | 23
2. Click Usage. The following details are displayed:
a. Current usage—Current usage of API calls assigned for a day along with the reset time in local
time zone.
b. Last one week API usage data:
n Date—The date of usage.
n Usage Per Day—The total usage by the user per day. This is derived based on the total
number of API calls made on a per day basis. This is an aggregate across all customers.
d. If you are in MSP mode, the MSP & Tenant Usage table is displayed:
n Tenant ID: ID of the tenant account.
n Usage Per Day: The total usage by the tenant account per day. This is derived based on the
total number of API calls made on a per day basis.
3. To download the API gateway usage statistics, click Download CSV.
The Usage tab is only available for administrators and the usage data is stored only for the previous 30 days.
n New APIs
n Modified API
New APIs
The following table lists the new APIs:
n [GET] /monitoring/v2/clients This API is introduced to get a list of unified clients and it is
backward compatible with the version 1 APIs (GET
/monitoring/v1/clients/wired and GET
/monitoring/v1/clients/wireless). This API version is introduced
with the following parameter inclusions:
n last_client_mac—Use this parameter to fetch the next set of
clients beyond set limit. This is used to fetch the clients details
beyond 10000 clients.
n timerange— Use this to filter the unified client information
based on the time range. By default, 3 hours is selected.
n client_type—Use this to select the client type as WIRELESS or
WIRED. By default, client type is selected as WIRELESS.
n client_status—Use this to select either CONNECTED for a list
of connected clients or FAILED_TO_CONNECT for a list failed
clients. By default, the client status is selected as
CONNECTED.
n [GET] /monitoring/v2/clients/ This API is introduced to get the client details (wired and wireless).
{macaddr}
n [GET] /client_policy This API is introduced to fetch a policy that allows network access
for registered clients, based on their MAC address and client
profile tag.
n [PUT] /client_policy This API is introduced to configure or update a policy that allows
network access for registered clients, based on their MAC address
and client profile tag.
n [GET] /client_registration This API is introduced to fetch the list of registered clients that are
allowed to access the network.
n [DELETE] /client_registration/{mac_ This API is introduced to delete the registered client and to
remove network access.
address}
API Gateway | 25
Table 19: New APIs
New API Description
n [POST] /client_registration This API is introduced to add a registered client to allow network
access.
n [PATCH] /client_registration/{mac_ This API is introduced to update Client Name for the registered
clients.
address}
n [GET] /user_policy This API is introduced to fetch a policy that allows wireless network
access for users, based on their user groups.
n [DELETE] /user_policy This API is introduced to delete existing policy to remove wireless
network access for all users.
NOTE: For all AI Ops APIs, AI Insights will get triggered only when there are failure events in the user network,
so all Insights might not be present all the time. Therefore, providing an empty API response for a selected time
period.
n [GET] /aiops/v2/insights/global/list This APIs are introduced to get the list of insights for a given time
duration
n [GET] /aiops/v2/insights/site/{site_
id}/list
n [GET] /aiops/v2/insights/ap/{ap_
serial}/list
n [GET] /aiops/v2/insights/client/{sta_
mac}/list
n [GET] /aiops/v2/insights/gateway/
{gw_serial}/list
n [GET] /aiops/v2/insights/switch/{sw_
serial}/list
n [GET] /aiops/v2/insights/global/id/ This APIs are introduced to get details of single insight for a given
time duration.
{insight_id}/export
n [GET] /aiops/v2/insights/site/{site_
id}/id/{insight_id}/export
n [GET] /aiops/v2/insights/ap/{ap_
serial}/id/{insight_id}/export
n [GET] /aiops/v2/insights/client/{sta_
mac}/id/{insight_id}/export
n [GET] /aiops/v2/insights/gateway/
{gw_serial}/id/{insight_id}/export
n [GET] /aiops/v2/insights/switch/{sw_
serial}/id/{insight_id}/export
n [GET] /msp_api/v1/groups/{group_ This API is introduced to get the list of customers mapped to MSP
group based on limit and offset.
name}/customers
Troubleshooting APIs
n [GET] /troubleshooting/v1/running- This API is introduced to get list of backups associated with the
device serial.
config-backup/serial/{serial}
n [GET] /troubleshooting/v1/running- This API is introduced to filter/list the backups associated with the
device serial and starting with the prefix.
config-backup/serial/{serial}/prefix/
{prefix}
n [GET] /troubleshooting/v1/running- This API is introduced to fetch the backup stored against the given
name.
config-backup/name/{name}
n [POST] This API is introduced to initiate backup of running config for the
switch with the given serial and store output against a name
/troubleshooting/v1/running-config-
starting with the given prefix.
backup/serial/{serial}/prefix/
{prefix}
n [GET] /configuration/full_hotspot/ This API is introduced to get the WLAN list of an UI group.
{group_name_or_guid}
n [GET] /configuration/full_hotspot/ This API is introduced to get the hotspot list of an UI group or swarm
{group_name_or_guid}/{mode_ with mode name.
name}
n [GET] /configuration/full_hotspot/ This API is introduced to get the WLAN default configuration.
API Gateway | 27
Table 19: New APIs
New API Description
{group_name_or_guid}/template
n [GET] /configuration/full_hotspot/ This API is introduced to initiate backup of running config for the
switch with the given serial and store output against a name
{group_name_or_guid}/{hotspot_
starting with the given prefix.
name}/{mode_name}
NOTE: In the API parameter, make sure that the node_type and node_id fields are set to Global.
n [GET] /ipms-config/v1/node_list/ This API is introduced to retrieve an address pool by identifier pool
name.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/
n [POST] /ipms-config/v1/node_list/ This API is introduced to create an address pool by identifier pool
name.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/
n [PUT] /ipms-config/v1/node_list/ This API is introduced to create or update the address pool by
identifier pool name.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/
n [DELETE] /ipms-config/v1/node_list/ This API is introduced to delete the IP range by identifier range id.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/ip_range/{range_id}/
n [GET] /ipms-config/v1/node_list/ This API is introduced to retrieve the IP range by identifier range
id.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/ip_range/{range_id}/
n [POST] /ipms-config/v1/node_list/ This API is introduced to create IP range by identifier range id.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/ip_range/{range_id}/
n [PUT] /ipms-config/v1/node_list/ This API is introduced to create or update the IP range by identifier
range id.
{node_type}/{node_
id}/config/address_pool/{pool_
name}/ip_range/{range_id}/
n [GET] /ipms-config/v1/node_list/ This API is introduced to have global level config for IPMS service.
{node_type}/{node_id}/
Modified API
The following table lists the modified APIs:
n [GET] /monitoring/v1/switch_ Following fields are added in the response to ensure that the API call
gets a list of ports, which includes:
stacks/{stack-id}/ports
n [GET] /monitoring/v1/switches/ n out_errors per port
n in_errors per port
{serial}/ports
API Gateway | 29
Table 20: Modified APIs
Modified API Description
n [GET] /monitoring/v1/switches/ The switch_type field is added to select the type of switch in the API
endpoints. Following are the supported values:
{serial}
n [GET] /monitoring/v1/switch_ n ArubaCX
n ArubaSwitch
stacks/{stack_id}
n MAAS
n GET /monitoring/v1/switches n site parameter is introduced to filter the switches by site name.
n site and stack_id fields are added to the response to get the site
name and stack id details for the switches.
n The switch_type field is added in the response to select the type of
switch in the API endpoints. Following are the supported values:
o AOS-CX
o AOS-S
n GET /monitoring/v1/switches/ n site and stack_id fields are added to the response to get the site
{serial} name and stack id details for the switches.
n nae_aggr_status field is added to the response that informs about
the switch status either as Critical, Major, Minor, Normal, and
Warning. This field is only applicable for CX switches.
n [GET] /auditlogs/v1/events n The limit parameter has been enhanced to return 100 audit
n [GET] events.
/platform/auditlogs/v1/logs n Following new parameters are introduced to filter audit events by
time range:
o start_time—Start time in epoch seconds. If start time is not
n [GET] /monitoring/v1/gateways site parameter is introduced to filter the APIs by site name.
n [GET] /monitoring/v1/aps/ Following fields are added in the response to get the site and swarm
name of the AP :
{serial}
n site_name
n swarm_name
n [GET] /monitoring/v1/swarms swarm_name parameter is introduced to filter the API by swarm name.
Topology
n [GET] /devices/{device_serial} n In alignment with the redesign of HPE engineering terminology, the
term Master in the API response changed to Conductor.
Deprecated APIs
The following table lists the APIs that have been deprecated. These APIs will continue to function but could
be removed in a future release. Aruba strongly discourages the use of these APIs and recommends that you
use the alternative API.
User Management
API Gateway | 31
Table 21: Deprecated APIs
Deprecated API Alternative API
Presence Analytics
[GET] /presence/v2/analytics/aggregates NA
[GET] /presence/v2/insights/top_sites NA
[GET] /presence/v2/insights/bottom_sites NA
[GET] /presence/v2/loyalty/aggregates NA
n [GET] NA
/presence/v2/loyalty/aggregates/top_
sites
n [GET]
[/presence/v2/loyalty/aggregates/botto
m_sites
n [GET] /presence/v2/loyalty/trends/top_
sites
n [GET]
/presence/v2/loyalty/trends/bottom_
sites
[GET] /monitoring/v1/aps/{serial}/uplink_ NA
history
[GET] /monitoring/v1/aps/ NA
{serial}/neighbouring_clients
API Gateway | 33
Table 21: Deprecated APIs
Deprecated API Alternative API
Deprecated Licensing
[DELETE] [DELETE]
/msp/customer/settings/autolicense /platform/licensing/v1/msp/customer/settings/autolicen
se
Removed APIs
The following table lists the APIs that have been removed and the alternative APIs:
User Management
Device Management
WIDS
Configuration
The following table lists the APIs that have been removed:
API Gateway | 35
Table 23: Removed APIs
Removed APIs
ACP MSP
n [GET] /platform/msp_api/v1/customers/{customer_id}
n [PUT] /platform/msp_api/v1/customers/{customer_
id}
n [DELETE] /platform/msp_api/v1/customers/
{customer_id}
n [GET] /platform/msp_api/v1/customers
n [POST] /platform/msp_api/v1/customers
Clarity
n [GET] /clarity/v1/overview/healthscore
n [GET] /clarity/v1/overview/healthscore/dns
n [GET] /clarity/v1/overview/network_stats
n [GET] /clarity/v1/ssid/names
n [GET] /clarity/v1/overview/reasons
n [GET] /clarity/v1/overview/attempts
n [GET] /clarity/v1/overview/device_attempts
n [GET] /clarity/v1/trend/healthscore
n [GET] /clarity/v1/trend/healthscore/dns
n [GET] /clarity/v1/trend/network_stats
n [GET] /clarity/v1/clients/search/partial
n [GET] /clarity/v1/clients/search/absolute
n [GET] /clarity/v1/clients/details
n [GET] /clarity/v1/clients/stats
n [GET] /clarity/v1/insights
n [GET] /clarity/v1/insights/details
n [GET] /clarity/v1/insights/distribution
n [GET] /clarity/v1/license
Attributes
n [GET] /monitoring/v1/attribute_values
Presence Analytics
n [POST] /presence/v1/config/thresholds
n [GET] /presence/v1/config/thresholds
n [GET] /presence/v1/analytics/aggregates
n [GET] /presence/v1/analytics/trends
n [GET] /presence/v1/insights/top_sites
n [GET] /presence/v1/insights/bottom_sites
n [GET] /presence/v1/insights/sites/aggregates
Webhooks
Webhooks allow you to implement event reactions by providing real-time information or notifications to
other applications. Aruba Central allows you to create Webhooks and select Webhooks as the notification
delivery option for all alerts.
Using Aruba Central, you can integrate Webhooks with other third-party applications such as ServiceNow,
Zapier, IFTTT, and so on.
You can access the Webhooks service either through the Aruba Central UI or API Gateway. Aruba Central
supports creating up to 10 Webhooks. To enable redundancy, Aruba Central allows you to add up to three
URLs per Webhook.
From Aruba Central, you can add, list, or delete Webhooks; get or refresh Webhooks token; get or update
Webhooks settings for a specific item; and test Webhooks notification.
This section includes the following topics:
In the Alerts & Events page, click the Configuration icon to configure and enable an alert. In the
Notification Options, select Webhooks as the notification delivery option.
The following figure illustrates how Aruba Central integrates with third-party applications using Webhooks.
1. In the Account Home page, under Global Settings, click Webhooks. The Webhooks page is
displayed.
Webhooks | 38
2. In the Webhook tab, click + sign. The Add Webhook pop-up window is displayed.
c. URLs—Enter the URL. Click + to enter another URL. You can add up to three URLs.
4. Click Save. The Webhooks is created and listed in the Webhook table.
n Number of URL Entries—Number of URLs in Webhooks. Click the number to view the list of
URLs.
n Updated At—Date and time at which Webhooks was updated.
n Webhook ID—Webhooks ID.
n Token—Webhooks token. Webhooks token enables header authentication and the third-party
receiving service must validate the token to ensure authenticity.
n Edit—Select the Webhook from the list and click the Edit icon to edit the Webhook. You can
refresh the token and add URLs. Click Save to save the changes.
n Delete—Select the Webhook from the list and click the Delete icon and click Yes to delete the
Webhook.
n Test Webhooks—Select the Webhook from the list and click the Test Webhooks icon to test the
Webhook by posting sample webhook payload to the configured URL. The Test Webhooks table
provides the URL and Status of the selected Webhook.
n View Dispatch Logs—Select the Webhook from the list and click the View Dispatch Log icon to
view the Dispatch Logs for the selected Webhook. The Dispatch Logs table provides the URL,
Status, and Dispatched Time. Click the arrow against each row to view the Log Details and
Attempts in the drop-down for the respective URL.
Webhooks | 40
Figure 9 Dispatch Logs Details Page
n GET
n POST
n PUT
n DELETE
You can perform CRUD operation on the Webhooks URL configuration. The key configuration elements that
are required to use API Webhooks service are Webhooks URL and a shared secret.
A shared secret token is generated for the Webhooks URL when you register for Webhooks. A hash key is
generated using SHA256 algorithm by using the payload and the shared secret token. The API required to
1. In the Account Home page, under Global Settings, click API Gateway. The API Gateway page is
displayed.
2. In the APIs tab, click the Swagger link under the Documentation header. The Swagger website
opens.
3. In the Swagger website, from the URL drop-down list, select Webhook. All available Webhooks APIs
are listed under API Reference.
{
"count": 1,
"settings": [
{
"wid": "e26450be-4dac-435b-ac01-15d8f9667eb8",
"name": "AAA",
"updated_ts": 1523956927,
"urls": [
"https://example.org/webhook1",
"https://example.org/webhook1"
],
"secure_token": "KEu5ZPTi44UO4MnMiOqz"
}
]
}
{
"name": "AAA",
"wid": "e829a0f6-1e36-42fe-bafd-631443cbd581"
}
Webhooks | 42
{
"wid": "e26450be-4dac-435b-ac01-15d8f9667eb8"
}
{
"wid": "e26450be-4dac-435b-ac01-15d8f9667eb8",
"name": "AAA",
"updated_ts": 1523956927,
"urls": [
"https://example.org/webhook1",
"https://example.org/webhook1"
],
"secure_token": "KEu5ZPTi44UO4MnMiOqz"
}
{
"name": "AAA",
"wid": "e829a0f6-1e36-42fe-bafd-631443cbd581"
}
{
"name": "AAA",
"secure_token": "[{\"token\": \"zSMrzuYrblgBfByy2JrM\", \"ts\": 1523957233}]"
}
{
"name": "AAA",
"secure_token": "[{\"token\": \"zSMrzuYrblgBfByy2JrM\", \"ts\": 1523957233}]"
}
Webhooks | 44
"device_id": "CNDSHN74L6",
"description": "CPU utilization for AP 20:a6:cd:cc:17:58 with serial CNDSHN74L6 has been
above 1% for about 5 minutes since 2021-02-02 06:11:00 UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612246560,
"details": {
"name": "20:a6:cd:cc:17:58",
"unit": "%",
"serial": "CNDSHN74L6",
"group": "1",
"labels": "3",
"_rule_number": "0",
"ds_key": "55ef4ae129a24c2180e010708202b502.CNDSHN74L6.cpu_utilization.5m",
"duration": "5",
"threshold": "1",
"time": "2021-02-02 06:11:00 UTC"
},
"webhook": "110576c0-59fb-4295-b53b-fdbafbc95dee",
"text": "CPU utilization for AP 20:a6:cd:cc:17:58 with serial CNDSHN74L6 has been
above 1% for about 5 minutes since 2021-02-02 06:11:00 UTC"
}
AP Disconnected
{
"id": "AXdhbSf7o68tULajRFQy",
"nid": 4,
"alert_type": "AP disconnected",
"setting_id": "55ef4ae129a24c2180e010708202b502-4",
"device_id": "DZ0001581",
"description": "AP f0:5c:19:c9:f7:6a with MAC address f0:5c:19:c9:f7:6a disconnected,
Group:unprovisioned",
"state": "Open",
"severity": "Major",
"operation": "create",
"timestamp": 1612247279,
"details": {
"params": [
"DZ0001581",
"f0:5c:19:c9:f7:6a",
"10.29.6.170",
"f0:5c:19:c9:f7:6a",
"",
""
],
"group": "1",
"ts": "1612246960735",
"labels": "",
"serial": "DZ0001581",
"conn_status": "disconnected",
"time": "2021-02-02 06:27:59 UTC",
"group_name": "unprovisioned"
},
"webhook": "110576c0-59fb-4295-b53b-fdbafbc95dee",
"text": "AP f0:5c:19:c9:f7:6a with MAC address f0:5c:19:c9:f7:6a disconnected,
Group:unprovisioned"
}
Webhooks | 46
"id": "AXdhYFm6o68tULajREe4",
"nid": 1252,
"alert_type": "AP_RADIO_OVER_UTILIZATION",
"setting_id": "55ef4ae129a24c2180e010708202b502-1252",
"device_id": "DZ0001581",
"description": "Radio utilization on AP f0:5c:19:c9:f7:6a operating on channel 132E and
serving 0 clients has been above 5% for about 5 minutes since 2021-02-02 06:09:00 UTC",
"state": "Open",
"severity": "Major",
"operation": "create",
"timestamp": 1612246440,
"details": {
"name": "f0:5c:19:c9:f7:6a",
"_band": "1",
"_radio_num": "0",
"channel": "132E",
"client_count": "0",
"unit": "%",
"serial": "DZ0001581",
"group": "1",
"_rule_number": "0",
"ds_key": "55ef4ae129a24c2180e010708202b502.DZ0001581.radio.busy64",
"duration": "5",
"threshold": "5",
"time": "2021-02-02 06:09:00 UTC"
}
AP_Radio_Non_Wifi_Over_Utilization
{
"id": "AXdhYFnIo68tULajREe5",
"nid": 1259,
"alert_type": "AP_RADIO_NON_WIFI_OVER_UTILIZATION",
"setting_id": "55ef4ae129a24c2180e010708202b502-1259",
"device_id": "DZ0001581",
"description": "Radio Non-Wifi utilization on AP f0:5c:19:c9:f7:6a operating on channel 6
and serving 0 clients has been above 1% for about 5 minutes since 2021-02-02 06:09:00
UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612246440,
"details": {
"name": "f0:5c:19:c9:f7:6a",
"_band": "0",
"_radio_num": "1",
"channel": "6",
"client_count": "0",
"unit": "%",
"serial": "DZ0001581",
"group": "1",
"_rule_number": "0",
"ds_key": "55ef4ae129a24c2180e010708202b502.DZ0001581.radio.interference",
"duration": "5",
"threshold": "1",
"time": "2021-02-02 06:09:00 UTC"
},
"webhook": "110576c0-59fb-4295-b53b-fdbafbc95dee",
"text": "Radio Non-Wifi utilization on AP f0:5c:19:c9:f7:6a operating on channel 6
and serving 0 clients has been above 1% for about 5 minutes since 2021-02-02 06:09:00
UTC"
}
AP_Tunnel_Down
Webhooks | 48
"alert_type": "Client attack detected",
"description": "An AP (NAME iap-303-iphone456-o and MAC 90:4c:81:cf:27:74 on RADIO 1)
detected an unencrypted frame
between a valid client (88:63:df:bb:2a:9d) and access point (BSSID 90:4c:81:72:77:55)
with source 88:63:df:bb:2a:9d
and receiver ff:ff:ff:ff:ff:ff SNR value is 55",
"timestamp": 1564392710,
"webhook": "780c65a0-10b6-4eb1-b725-21b0d52aa432",
"setting_id": "201804170291-13",
"state": "Open",
"nid": 13,
"details": {
"group": "3",
"labels": "3,142,141",
"params": "None",
"_rule_number": "0",
"time": "2019-07-29 09:31:50 UTC"
},
"operation": "create",
"device_id": "CNGHKGX004",
"id": "AWw9EmBxVQO1ZtiGO1Q8",
"severity": "Critical"
}
Connected Clients
{
"id": "AXdhWQbro68tULajREA9",
"nid": 1254,
"alert_type": "CONNECTED_CLIENTS",
"setting_id": "55ef4ae129a24c2180e010708202b502-1254",
"device_id": "cf62d07c019cd6bca90e6079e351251070d9e286f310c87541",
"description": "Number of clients connected to VC SetMeUp-C9:F7:6A has been
above 1 for about 5 minutes since 2021-02-02 06:01:00 UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612245960,
"details": {
"customer_id": "55ef4ae129a24c2180e010708202b502",
"name": "SetMeUp-C9:F7:6A",
"serial": "cf62d07c019cd6bca90e6079e351251070d9e286f310c87541",
"group": "1",
"_rule_number": "0",
"ds_key": "55ef4ae129a24c2180e010708202b502.cluster.363.device.clients.5m",
"duration": "5",
"threshold": "1",
"time": "2021-02-02 06:01:00 UTC"
},
"webhook": "110576c0-59fb-4295-b53b-fdbafbc95dee",
"text": "Number of clients connected to VC SetMeUp-C9:F7:6A has been above 1 for
about 5 minutes since 2021-02-02 06:01:00 UTC"
}
Webhooks | 50
"time": "2021-02-02 06:25:05 UTC"
},
"webhook": "110576c0-59fb-4295-b53b-fdbafbc95dee",
"text": "Insufficient inline power supplied to AP-325 with name 20:a6:cd:cc:17:58"
}
Modem Plugged
{
"id": "AXdhmYueo68tULajRH6n",
"nid": 18,
"alert_type": "Modem Plugged",
"setting_id": "b8be21720dc04a8e9f0028374b6a9bbd-18",
"device_id": "GRUT000002",
"description": "Modem plugged to AP GRUT000002 with MAC address 4a:36:66:b8:50:00",
"state": "Open",
"severity": "Major",
"operation": "create",
"timestamp": 1612250188,
"details": {
"group": "0",
"labels": "",
"_rule_number": "0",
"params": [
"GRUT000002",
"4a:36:66:b8:50:00"
],
"serial": "GRUT000002",
"time": "2021-02-02 07:16:28 UTC"
},
"webhook": "31a75d0a-dfd4-4c22-a32b-09d7b033d41e",
"text": "Modem plugged to AP GRUT000002 with MAC address 4a:36:66:b8:50:00"
}
Modem Unplugged
{
"id": "AXdhp2Uwo68tULajRIVC",
"nid": 19,
"alert_type": "Modem Unplugged",
"setting_id": "b8be21720dc04a8e9f0028374b6a9bbd-19",
"device_id": "GRUT000001",
"description": "Modem unplugged from AP GRUT000001 with MAC address 64:2a:90:97:f0:00",
"state": "Open",
"severity": "Major",
"operation": "create",
"timestamp": 1612251096,
"details": {
"group": "0",
"labels": "",
"_rule_number": "0",
"params": [
"GRUT000001",
"64:2a:90:97:f0:00"
],
"serial": "GRUT000001",
"time": "2021-02-02 07:31:36 UTC"
},
"webhook": "31a75d0a-dfd4-4c22-a32b-09d7b033d41e",
"text": "Modem unplugged from AP GRUT000001 with MAC address 64:2a:90:97:f0:00"
}
New AP Detected
{
"id": "AXdhcXF1o68tULajRFld",
Rogue AP Detected
{
"alert_type": "Rogue AP detected",
"description": "An AP (NAME 84:d4:7e:c5:c8:8c and MAC address 84:d4:7e:c5:c8:8con RADIO
Webhooks | 52
1)
detected an access point
(BSSID 0c:00:01:34:69:62 and SSID ssid1 on CHANNEL 52) as rogue",
"timestamp": 1564326128,
"webhook": "780c65a0-10b6-4eb1-b725-21b0d52aa432",
"setting_id": "201804170291-10",
"state": "Open",
"nid": 10,
"details": {
"_rule_number": "0",
"group": "1",
"labels": "",
"params": [
"84:d4:7e:c5:c8:8c",
"84:d4:7e:c5:c8:8c",
"1",
"0c:00:01:34:69:62",
"ssid1",
"52"
],
"time": "2019-07-28 15:02:08 UTC"
},
"operation": "create",
"device_id": "CT0779239",
"id": "AWw5Gm1zVQO1ZtiJK89l",
"severity": "Critical"
}
Uplink Changed
Webhooks | 54
AOS-Switch Alerts—Sample JSON
This section includes sample JSON content for the following alerts:
Switch Disconnected
{
"id": "AXbhjMPpKHBn24BIWnGc",
"nid": 203,
"alert_type": "Switch Disconnected",
"setting_id": "f1ae23ba9025490cb53efb0993e05f17-203",
"device_id": "CN80HKW2Z6",
"description": "Switch with serial CN80HKW2Z6, MAC address 54:80:28:61:b3:20 IP address
10.21.20.231
and Hostname Aruba-2930F-24G-PoEP-4SFPP reconnected",
"state": "Close",
"severity": "Major",
"operation": "update",
"timestamp": 1612383547,
"details": {
"params": [
"CN80HKW2Z6",
"54:80:28:61:b3:20",
"10.21.20.231",
"Aruba-2930F-24G-PoEP-4SFPP",
"",
""
],
"serial": "CN80HKW2Z6",
"time": "2021-01-08 10:31:07 UTC",
"conn_status": "reconnected"
},
"webhook": "8077a55e-f8d3-43af-a67f-12263f5b778e",
"text": "Switch with serial CN80HKW2Z6, MAC address 54:80:28:61:b3:20 IP address
10.21.20.231
and Hostname Aruba-2930F-24G-PoEP-4SFPP reconnected"
}
Webhooks | 56
"threshold": "1",
"time": "2021-02-04 04:35:00 UTC"
},
"webhook": "8077a55e-f8d3-43af-a67f-12263f5b778e",
"text": "CPU utilization for Switch HP-2920-48G-POEP with serial SG53FLZ0RX has been
above 1% for about 5 minutes since 2021-02-04 04:35:00 UTC."
}
Webhooks | 58
"webhook": "4d588353-3355-487d-81af-c97f62b0abb0",
"setting_id": "e344d961bccd411dbd279bf92f61b989-1307",
"state": "Open",
"nid": 1305,
"details": {
"group": "0",
"name": "Aruba-2930F-24G-PoEP-4SFPP",
"ip": "10.22.182.78",
"labels": [],
"mac": "e0:07:1b:c4:8d:80",
"time": "2019-09-26 13:52:00 UTC",
"threshold": "1",
"serial": "CN69HKW05T"
},
"operation": "create",
"device_id": "CN69HKW05T",
"id": "AW1t18ccYu0OgJ2aoDYw",
"severity": "Critical"
}
Webhooks | 60
{
"id": "AXt4qBL_fvwY_x8ol-sJ",
"nid": 1308,
"alert_type": "SWITCH_STP_ROOT_CHANGE",
"setting_id": "417fc95887044bcba9b3e2ce3830aecb-1308",
"device_id": "QXRF011180",
"description": "CST Root changed on Sep 24 10:57:09 from Switch QXRF011180.
dummy with Serial: QXRF011180, IP Address: 75.200.87.30 and Priority: 24576 to
Switch 70:10:6f:84:0c:80 with Serial: QXRF011180, IP Address: 75.200.87.30 and Priority
20480",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1629816886,
"details": {
"ts": "Sep 24 10:57:09",
"pr1": "24576",
"pr2": "20480",
"host1": "QXRF011180.dummy",
"host2": "70:10:6f:84:0c:80",
"ip1": "75.200.87.30",
"ip2": " ",
"serial1": "QXRF011180",
"serial2": " ",
"type": "CST",
"group": "16336",
"labels": "5844",
"serial": "QXRF011180",
"time": "2021-08-24 14:54:46 UTC"
},
"webhook": "34000e8a-475c-46e3-9bec-79c5f281e868",
"text": "CST Root changed on Sep 24 10:57:09 from Switch QXRF011180.dummy with
Serial: QXRF011180, IP Address: 75.200.87.30 and Priority: 24576 to Switch
70:10:6f:84:0c:80
with Serial: QXRF011180, IP Address: 75.200.87.30 and Priority 20480
}
Switch Disconnected
{
"id": "AXbhjMPpKHBn24BIWnGc",
"nid": 203,
"alert_type": "Switch Disconnected",
"setting_id": "f1ae23ba9025490cb53efb0993e05f17-203",
"device_id": "CN80HKW2Z6",
"description": "Switch with serial CN80HKW2Z6, MAC address 54:80:28:61:b3:20 IP address
10.21.20.231
and Hostname Aruba-2930F-24G-PoEP-4SFPP reconnected",
"state": "Close",
"severity": "Major",
"operation": "update",
"timestamp": 1612383547,
"details": {
"params": [
"CN80HKW2Z6",
"54:80:28:61:b3:20",
"10.21.20.231",
"Aruba-2930F-24G-PoEP-4SFPP",
Webhooks | 62
"",
""
],
"serial": "CN80HKW2Z6",
"time": "2021-01-08 10:31:07 UTC",
"conn_status": "reconnected"
},
"webhook": "8077a55e-f8d3-43af-a67f-12263f5b778e",
"text": "Switch with serial CN80HKW2Z6, MAC address 54:80:28:61:b3:20 IP address
10.21.20.231
and Hostname Aruba-2930F-24G-PoEP-4SFPP reconnected"
}
Webhooks | 64
"severity": "Critical"
}
Webhooks | 66
"name": "6300",
"site": "",
"device_id": "SG9ZKN7078",
"hostname": "6300",
"description": "eMMC storage reached critical utilization level.Please contact
HPE Aruba support for further assistance.",
"event_id": "9104",
"time": "2021-09-09 07:03:38 UTC"
},
"webhook": "5ef178b6-4916-46e6-bed2-ab61a8cd7271",
"text": "Switch with serial SG9ZKN7078 : eMMC storage reached critical utilization
level.Please contact HPE Aruba support for further assistance.",
"cluster_hostname": "app-yoda.arubathena.com"
}
Webhooks | 68
"operation": "create",
"timestamp": 1631118901,
"details": {
"serial": "SG9ZKN702T",
"mac": "",
"mem_id": "4",
"role": [
"Member"
],
"action": "Removed From",
"host": "6300",
"stack_id": "6a9cb0fb-2346-48df-a0c4-90237ea71afa",
"group": "326",
"time": "2021-09-08 16:35:01 UTC"
},
"webhook": "374b4438-dff9-464c-a03e-a781c6c9a68f",
"text": "Stack Member with Serial ID: SG9ZKN702T,
MAC Address: , Member ID: 4 and Role: ['Member'] Removed From stack with
Hostname: 6300, Stack ID: 6a9cb0fb-2346-48df-a0c4-90237ea71afa"
}
CFG_Set_Advertisement_Failure
{
"id": "AXdnqE9jo68tULajSR8X",
"nid": 1554,
"alert_type": "CFG_SET_ADVERTISEMENT_FAILURE",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1554",
"device_id": "BIM0010001",
"description": "CFG-Set advertisement failure for Gateway BIM0010001 with serial
BIM0010001 on tunnel default-local-vpnip-data-ipsecmap-00:1a:1e:04:27:48-link6 from
10.1.1.1 to 200.1.1.6",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612351819,
"details": {
"src_ip": "10.1.1.1",
"dst_ip": "200.1.1.6",
"alias_map_name": "default-local-vpnip-data-ipsecmap-00:1a:1e:04:27:48-link6",
"map_name": "default-local-vpnip-data-ipsecmap-00:1a:1e:04:27:48-link6",
"hostname": "BIM0010001",
"serial": "BIM0010001",
"group": "0",
"labels": [],
"time": "2021-02-03 11:30:19 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "CFG-Set advertisement failure for Gateway BIM0010001 with serial
BIM0010001 on tunnel default-local-vpnip-data-ipsecmap-00:1a:1e:04:27:48-link6 from
10.1.1.1 to 200.1.1.6"
}
Webhooks | 70
"operation": "create",
"timestamp": 1612802016,
"details": {
"serial": "DL0002986",
"nbr_addr": "103.1.1.2",
"nbr_as": "103",
"nbr_id": "197.0.0.3",
"group": "57",
"time": "2021-02-08 16:33:36 UTC"
},
"webhook": "5cbc87e4-9eb5-45d2-b890-b21db89ca5b4",
"text": "BGP neighbor 103.1.1.2 is down (router-id=197.0.0.3, ASN=103, serial=DL0002986)"
}
Controller_CPU_Over_Utilization
{
"id": "AXdi7ppYo68tULajRVeA",
"nid": 1351,
"alert_type": "CONTROLLER_CPU_OVER_UTILIZATION",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1351",
"device_id": "CNJJKLB0HB",
"description": "CPU utilization for Gateway WTH_9004-2 with serial CNJJKLB0HB has been
above 10% for about 5 minutes since 2021-02-02 13:24:00 UTC.",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612272540,
"details": {
"name": "WTH_9004-2",
"unit": "%",
"serial": "CNJJKLB0HB",
"group": "36",
"labels": "8",
"_rule_number": "0",
"ds_key": "6039f9543bac449291bfcd19eb10d1eb.CNJJKLB0HB.cpu_utilization.5m",
"duration": "5",
"threshold": "10",
"time": "2021-02-02 13:24:00 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "CPU utilization for Gateway WTH_9004-2 with serial CNJJKLB0HB has been
above 10% for about 5 minutes since 2021-02-02 13:24:00 UTC."
}
Controller_Emergency_Up_Link_Mode
{
"id": "AXdjJsYpo68tULajRXTU",
"nid": 1353,
"alert_type": "CONTROLLER_EMERGENCY_UP_LINK_MODE",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1353",
"device_id": "BIM0010002",
"description": "Gateway BIM0010002 with serial BIM0010002 is operating on emergency mode
at 2021-02-02 14:30:21 UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612276221,
"details": {
"name": "BIM0010002",
"serial": "BIM0010002",
"group": "0",
"labels": [],
"time": "2021-02-02 14:30:21 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
Controller_Memory_Over_Utilization
{
"id": "AXdiyfwQo68tULajRTiG",
"nid": 1352,
"alert_type": "CONTROLLER_MEMORY_OVER_UTILIZATION",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1352",
"device_id": "CNJJKLB0G6",
"description": "Memory utilization for Gateway WTH_9004-1 with serial CNJJKLB0G6 has been
above 30% for about 30 minutes since 2021-02-02 12:19:00 UTC.",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612270140,
"details": {
"name": "WTH_9004-1",
"unit": "%",
"serial": "CNJJKLB0G6",
"group": "36",
"labels": "8",
"_rule_number": "0",
"ds_key": "6039f9543bac449291bfcd19eb10d1eb.CNJJKLB0G6.memory_utilization.5m",
"duration": "30",
"threshold": "30",
"time": "2021-02-02 12:19:00 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "Memory utilization for Gateway WTH_9004-1 with serial CNJJKLB0G6 has been
above 30% for about 30 minutes since 2021-02-02 12:19:00 UTC."
}
Webhooks | 72
},
"operation": "create",
"device_id": "CW0003307",
"id": "AWws60Yxon2R5PyMmUU4",
"severity": "Major"
}
DPS_Compliance_Alert
{
"ack_by": null,
"ack_ts": 1579828824000,
"acknowledge": 0,
"cid": "201804172180",
"description": "SLA DPS Compliance Violations for Customer : aruba, Device Hostname :
bg2-ha2, Policy : all,
Uplink : 400_lte, Probe Ip: 52.52.253.87, Threshold Profile : {u'dps_threshold_profile_
name': u'BestForInternet',
u'dps_threshold_profile_packet_loss_value': 1, u'dps_threshold_profile_bw_util_value':
80,
u'dps_threshold_profile_latency_value': 1}, Violation Reason: Latency, Violation Value:
1.363ms",
"group_name": "",
"id": "AW_VItEnenGOhQ4XrMp_",
"labels": [],
"nid": 20,
"severity": 5,
"sites": [
{
"id": 38,
"name": "site_2"
}
],
"ts": 1579828824000,
"type": "DPS_COMPLIANCE_ALERT",
"type_desc": "SLA DPS Compliance Violations"
}
Gateway_Connected_to_Cluster
Gateway_Disconnected_From_Cluster
{
"id": "AXd9vPKro68tULajWxzi",
"nid": 1803,
"alert_type": "GATEWAY_DISCONNECTED_FROM_CLUSTER",
"setting_id": "abce082bef4a428bb31366f6d6ff223f-1803",
"device_id": "54",
"description": "Gateway with name: c2c-7010-4-1 and serial: CG0020729 left
cluster: C2C-253-YODA.",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612722270,
"details": {
"group": "278",
"labels": [],
"name": "c2c-7010-4-1",
"serial": "54",
"gateway": "CG0020729",
"cluster_name": "C2C-253-YODA",
"alert_key": "CG0020729",
"time": "2021-02-07 18:24:30 UTC"
},
"webhook": "52e0abbd-cdda-45f2-bd68-3107fef43841",
"text": "Gateway with name: c2c-7010-4-1 and serial: CG0020729 left
cluster: C2C-253-YODA."
}
Webhooks | 74
"state": "Open",
"severity": "Minor",
"operation": "create",
"timestamp": 1612722604,
"details": {
"group": "278",
"labels": [],
"name": "c2c-7010-3",
"serial": "54",
"gateway": "CG0021234",
"cluster_name": "C2C-253-YODA",
"alert_key": "CG0021234",
"time": "2021-02-07 18:30:04 UTC"
},
"webhook": "52e0abbd-cdda-45f2-bd68-3107fef43841",
"text": "Gateway with name: c2c-7010-3 and serial: CG0021234 became the leader of
cluster: C2C-253-YODA."
}
Gateway_Base_License_Capacity_Exceeded
{
"id": "AXdr-dsfo68tULajS0bj",
"nid": 1356,
"alert_type": "GATEWAY_BASE_LICENSE_CAPACITY_EXCEEDED",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1356",
"device_id": "SCA0000073",
"description": "Base license capacity limit exceeded for Gateway with
name: CSIM_SCA0000073, serial: SCA0000073",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612424272,
"details": {
"group": "0",
"labels": [],
"name": "CSIM_SCA0000073",
"serial": "SCA0000073",
"time": "2021-02-04 07:37:52 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "Base license capacity limit exceeded for Gateway with
name: CSIM_SCA0000073, serial: SCA0000073"
}
Gateway_Disconnected
{
"id": "AXdmLPpwo68tULajSCh_",
"nid": 303,
"alert_type": "GATEWAY_DISCONNECTED",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-303",
"device_id": "CNJJKLB0NZ",
"description": "Gateway WTH-9004-3 with serial CNJJKLB0NZ, MAC address 20:4c:03:b1:e0:22
and
IP address 192.168.142.2 disconnected. , Group:UTM, Site:UTM",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612326959,
"details": {
"params": [
"CNJJKLB0NZ",
"20:4c:03:b1:e0:22",
"192.168.142.2",
"WTH-9004-3",
"",
""
],
"group": "36",
"ts": "1612326547369",
"labels": "8",
"serial": "CNJJKLB0NZ",
"conn_status": "disconnected",
"time": "2021-02-03 04:35:59 UTC",
"group_name": "UTM",
"site_name": "UTM"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "Gateway WTH-9004-3 with serial CNJJKLB0NZ, MAC address 20:4c:03:b1:e0:22 and
IP address 192.168.142.2 disconnected. , Group:UTM, Site:UTM"
}
Webhooks | 76
{
"id": "AXdr6Yf3o68tULajSz4Y",
"nid": 2306,
"alert_type": "GW_IDS_IPS_ALERT_THREAT_SID_OVER_A_PERIOD",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-2306",
"device_id": "2821300",
"description": "Dear Incident Manager,<br/>Your <b>Aruba Central Portal</b> admin
configured
an email alert notification to be sent to this email address <br/><br/><b>Why
this alert?</b><br/>Threat events of signature id <b>2821300</b> exceeded the
threshold <b>50</b> in last <b>30</b> minutes, triggering this <b>CRITICAL</b> Alert
notification. <br/><br/><b>What is next? </b><br/>Reach out to your <b>Aruba Central
Portal</b> admin to address this incident.<br/>If not addressed or if the situation
escalates,
you may continue to receive similar alert notifications. <br/><br/><b>More
Information</b> <br/>Go to \"https://app-yoda.arubathena.com/frontend/#/IDPS_DASHBOARD\"
<br/><br/><i>System Generated Email from Aruba Central based on alert configuration;
do not reply.</i> <br/><br/>Thanks,<br/><br/>Aruba Central",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612423202,
"details": {
"threshold": "50",
"agg_field_name": "signature",
"duration": "30",
"signature": "2821300",
"severity": "CRITICAL",
"rule_id": "0",
"serial": "2821300",
"time": "2021-02-04 06:50:02 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "Dear Incident Manager,<br/>Your <b>Aruba Central Portal</b> admin configured an
email alert notification to be sent to this email address <br/><br/><b>Why
this alert?</b><br/>Threat events of signature id <b>2821300</b> exceeded the
threshold <b>50</b> in last <b>30</b> minutes, triggering this <b>CRITICAL</b> Alert
notification.
<br/><br/><b>What is next? </b><br/>Reach out to your <b>Aruba Central Portal</b> admin
to
address this incident.<br/>If not addressed or if the situation escalates, you may
continue to
receive similar alert notifications. <br/><br/><b>More Information</b> <br/>Go
to \"https://app-yoda.arubathena.com/frontend/#/IDPS_DASHBOARD\" <br/><br/><i>System
Generated
Email from Aruba Central based on alert configuration; do not reply.</i>
<br/><br/>Thanks,<br/><br/>Aruba
Central"
}
Webhooks | 78
"text": "Memory utilization for IDS/IPS engine on Gateway WTH_9004-2 with serial
CNJJKLB0HB has been above 2% for about 5 minutes since 2021-02-04 02:49:00 UTC."
}
GW_Cluster_VLAN_Mismatch
{
"id": "AXd9rMzXo68tULajWxbZ",
"nid": 1801,
"alert_type": "GW_CLUSTER_VLAN_MISMATCH",
"setting_id": "abce082bef4a428bb31366f6d6ff223f-1801",
"device_id": "54",
"description": "There is a VLAN mismatch in cluster C2C-253-YODA between Gateway with
serial: CG0020729 and Gateway with serial: CG0021234.",
"state": "Close",
"severity": "Minor",
"operation": "update",
"timestamp": 1612722281,
"details": {
"gateway2": "CG0021234",
"gateway1": "CG0020729",
"serial": "54",
"alert_key": "CG0020729-CG0021234",
"time": "2021-02-07 18:06:52 UTC",
"cluster-name": "C2C-253-YODA",
"group": "278",
"labels": []
},
"webhook": "52e0abbd-cdda-45f2-bd68-3107fef43841",
"text": "There is a VLAN mismatch in cluster C2C-253-YODA between Gateway with
serial: CG0020729 and Gateway with serial: CG0021234."
}
New_Gateway_Connected
{
"id": "AXd96oFqo68tULajWy28",
"nid": 301,
"alert_type": "NEW_GATEWAY_DETECTED",
"setting_id": "abce082bef4a428bb31366f6d6ff223f-301",
OAP_Channel_Connected
{
"id": "AXeC5dlWo68tULajXiwK",
"nid": 1359,
"alert_type": "CONTROLLER OAP CONNECTION",
"setting_id": "a847a3aea73d4ba7b34c00323fb9ee7a-1359",
"device_id": "CP0048220",
"description": "Overlay Route Orchestrator control connection is down for
Legacy2.0-BGW1-A7005-39_82_AC (serial=CP0048220)",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612808837,
"details": {
"hostname": "Legacy2.0-BGW1-A7005-39_82_AC",
"serial": "CP0048220",
"group": "22",
"time": "2021-02-08 18:27:17 UTC"
},
"webhook": "f6f2b19a-31d5-445c-b340-eb1ca8a6fdd8",
"text": "Overlay Route Orchestrator control connection is down for
Legacy2.0-BGW1-A7005-39_82_AC (serial=CP0048220)"
}
OAP_Channel_Disconnect
{
"id": "AXeC5dlWo68tULajXiwK",
"nid": 1359,
"alert_type": "CONTROLLER OAP CONNECTION",
"setting_id": "a847a3aea73d4ba7b34c00323fb9ee7a-1359",
"device_id": "CP0048220",
"description": "Overlay Route Orchestrator control connection is down for
Legacy2.0-BGW1-A7005-39_82_AC (serial=CP0048220)",
"state": "Close",
"severity": "Critical",
Webhooks | 80
"operation": "update",
"timestamp": 1612808838,
"details": {
"hostname": "Legacy2.0-BGW1-A7005-39_82_AC",
"serial": "CP0048220",
"group": "22",
"time": "2021-02-08 18:27:17 UTC"
},
"webhook": "f6f2b19a-31d5-445c-b340-eb1ca8a6fdd8",
"text": "Overlay Route Orchestrator control connection is down for
Legacy2.0-BGW1-A7005-39_82_AC (serial=CP0048220)"
}
WAN_Auto_Negotiation
{
"id": "AXdnjuvwo68tULajSQyc",
"nid": 1506,
"alert_type": "WAN_UPLINK_AUTONEGOTIATION_STATE_CHANGE",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1506",
"device_id": "CNJJKLB0NZ",
"description": "WAN ports autonegotiaton speed changed from 1000 Mbps to Auto Mbps
for device WTH-9004-3 with serial CNJJKLB0NZ for uplink GE0/0/1 at 2021-02-03 11:02:35
UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612350155,
"details": {
"intf_name": "GE0/0/1",
"speed": "1000",
"new_speed": "Auto",
"hostname": "WTH-9004-3",
"serial": "CNJJKLB0NZ",
"group": "36",
"labels": [
"8"
],
"time": "2021-02-03 11:02:35 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "WAN ports autonegotiaton speed changed from 1000 Mbps to Auto Mbps for
device WTH-9004-3 with serial CNJJKLB0NZ for uplink GE0/0/1 at 2021-02-03 11:02:35 UTC"
}
Webhooks | 82
{
"id": "AXdncVpfo68tULajSPzi",
"nid": 1502,
"alert_type": "WAN_UPLINK_REACHABILITY_VPN_PEER_FAILED",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1502",
"device_id": "CNJJKLB0HB",
"description": "WAN reachability check failed for Gateway WTH_9004-2 with serial
CNJJKLB0HB
to VPN peer 192.168.103.99 on uplink inet2_inet. Default-gateway is unreachable.",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612348217,
"details": {
"ip": "192.168.103.99",
"intf_name": "inet2_inet",
"default_gw_status": "unreachable",
"hostname": "WTH_9004-2",
"serial": "CNJJKLB0HB",
"group": "36",
"labels": [
"8"
],
"time": "2021-02-03 10:30:17 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "WAN reachability check failed for Gateway WTH_9004-2 with serial CNJJKLB0HB to
VPN peer 192.168.103.99 on uplink inet2_inet. Default-gateway is unreachable."
}
WAN_Uplink_Flap
{
WAN_Tunnel_Flap
{
"id": "AXe2H5oGo68tULajexfD",
"nid": 1601,
"alert_type": "WAN_TUNNEL_FLAP",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1601",
"device_id": "CNJJKLB0G6",
"description": "Tunnel WTH_9004-1:inet_inet::GSK_VPNC2:vlan103 status flapped 1% on
device
WTH_9004-1 with serial CNJJKLB0G6 for about 15 minutes since 2021-02-18 16:56:00 UTC.",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1613668260,
"details": {
"src_ip": "192.168.32.10",
"dst_ip": "192.168.103.99",
"alias_map_name": "WTH_9004-1:inet_inet::GSK_VPNC2:vlan103",
"uplink_tag": "inet_inet",
"hostname": "WTH_9004-1",
"unit": "%",
"serial": "CNJJKLB0G6",
"group": "36",
"labels": "8",
"_rule_number": "0",
"ds_key": "6039f9543bac449291bfcd19eb10d1eb.CNJJKLB0G6.uplink.tunnel.flap.5m",
"duration": "15",
"threshold": "1",
"time": "2021-02-18 16:56:00 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
Webhooks | 84
"text": "Tunnel WTH_9004-1:inet_inet::GSK_VPNC2:vlan103 status flapped 1% on device
WTH_9004-1 with serial CNJJKLB0G6 for about 15 minutes since 2021-02-18 16:56:00 UTC."
}
WAN_Auto_Negotiation_Flap
{
"alert_type": "WAN_AUTO_NEGOTIATION_FLAP",
"description": "Uplink GE0/0/1 speed flapped 1% on device CNHHKLB031 for about
15 minutes since 2019-07-25 12:32:00 UTC.",
"timestamp": 1564058820,
"webhook": "394c7a3c-ca41-4476-8afc-857e54aa4b3b",
"setting_id": "abce082bef4a428bb31366f6d6ff223f-1602",
"state": "Open",z
"nid": 1602,
"details": {
"new_speed": "Auto",
"group": "77",
"labels": "8,661",
"duration": "15",
"_rule_number": "0",
"intf_name": "GE0/0/1",
"time": "2019-07-25 12:32:00 UTC",
"threshold": "1",
"ds_key": "abce082bef4a428bb31366f6d6ff223f.CNHHKLB031.uplink.speed.flap.5m",
"serial": "CNHHKLB031",
"speed": "1000",
"unit": "%"
},
"operation": "create",
"device_id": "CNHHKLB031",
"id": "AWwpK55sVQO1ZtiGh8zr",
"severity": "Minor"
}
WAN_IPsec_SA_Establishment_Failed
{
"id": "AXdi4-5Bo68tULajRU_R",
"nid": 1550,
"alert_type": "WAN_IPSEC_SA_ESTABILSHMENT_FAILED",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1550",
"device_id": "CNJJKLB0NZ",
"description": "IPSec Tunnel Establishment from 192.168.36.10 to 192.168.103.99 failed on
device WTH-9004-3 with serial CNJJKLB0NZ at 2021-02-02 13:17:20 UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612271840,
"details": {
"src_ip": "192.168.36.10",
"dst_ip": "192.168.103.99",
"alias_map_name": "WTH-9004-3:inet_inet::GSK_VPNC2:vlan103",
"link_tag": "inet_inet",
"hostname": "WTH-9004-3",
"serial": "CNJJKLB0NZ",
"group": "36",
"labels": [
"8"
],
"time": "2021-02-02 13:17:20 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "IPSec Tunnel Establishment from 192.168.36.10 to 192.168.103.99 failed on
device WTH-9004-3 with serial CNJJKLB0NZ at 2021-02-02 13:17:20 UTC"
}
WAN_IPsec_SA_Down
WAN_IPsec_SA_All_Down
{
"id": "AXdi4Qoyo68tULajRUzs",
"nid": 1552,
"alert_type": "WAN_IPSEC_SA_ALL_DOWN",
"setting_id": "6039f9543bac449291bfcd19eb10d1eb-1552",
"device_id": "CNJJKLB0G6",
"description": "All IPSec SAs down for device WTH_9004-1 with serial CNJJKLB0G6 at
2021-02-02 13:14:11 UTC",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1612271651,
"details": {
"hostname": "WTH_9004-1",
"serial": "CNJJKLB0G6",
"group": "36",
"labels": [
"8"
],
"time": "2021-02-02 13:14:11 UTC"
},
"webhook": "a82456c8-1402-4fe1-a195-0131e6b392ee",
"text": "All IPSec SAs down for device WTH_9004-1 with serial CNJJKLB0G6 at
2021-02-02 13:14:11 UTC"
}
Webhooks | 86
{
"id": "AXuqDamDKFHq3kj2qihO",
"nid": 1511,
"alert_type": "CELLULAR_DATA_USAGE",
"setting_id": "082445a5b8264597bce334f932c9a3a4-1511",
"device_id": "TWJCKSP01C",
"description": "Cellular data usage 11 MB has exceeded the configured limit 1 MB
for Gateway Aruba9004-LTE with serial TWJCKSP01C",
"state": "Open",
"severity": "Critical",
"operation": "create",
"timestamp": 1630645627,
"details": {
"usage": "11 MB",
"limit": "1 MB",
"name": "Aruba9004-LTE",
"serial": "TWJCKSP01C",
"group": "6",
"labels": [],
"time": "2021-09-03 05:07:07 UTC"
},
"webhook": "a7b7f0de-2465-4340-b491-d9ea676326f3",
"text": "Cellular data usage 11 MB has exceeded the configured limit 1 MB
for Gateway Aruba9004-LTE with serial TWJCKSP01C"
}
Webhooks | 88
"webhook": "057b0a95-9f06-4a0f-b4bf-149a28d749b3",
"setting_id": "573b0412517a41c8a73a80f3e74ff0d2-14",
"state": "Open",
"nid": 14,
"details": {
"group": "-1",
"labels": "None",
"params": [],
"_rule_number": "0",
"time": "2019-09-23 10:28:54 UTC"
},
"operation": "create",
"device_id": "",
"id": "AW1dqr6nYu0OgJ2alX1l",
"severity": "Major"
}