Aruba Central icon

Aruba Central

Interact with the Aruba Central API

Actions95

Gateway → Get Errors

AI-generated

Overview

This node interacts with the Aruba Central API to retrieve error information for a specific Gateway device within the Monitoring domain. It is useful for network administrators who need to monitor and troubleshoot network issues by accessing detailed port error data from a Gateway device. For example, it can be used to fetch error statistics for a particular port on a Gateway to identify connectivity or hardware problems.

Use Case Examples

  1. Retrieve all port errors for a Gateway device with a given serial number to analyze network health.
  2. Fetch a limited number of error records for a specific port on a Gateway to troubleshoot intermittent connectivity issues.

Properties

Name Meaning
Domain Specifies the domain of the Aruba Central API to interact with, defaulting to 'monitoring' for this operation.
Return All Determines whether to return all error results or limit the number of results returned (only applicable when domain is 'monitoring').
Limit Maximum number of error results to return when 'Return All' is false.
Serial Serial number of the Gateway device to query for errors.
Port Filter errors by a specific port on the Gateway device (e.g., GE0/0/1).
Additional Fields Optional additional parameters such as 'Interval' to specify the sampling interval for port errors.

Output

JSON

  • errorCount - Number of errors recorded for the specified port and interval.
  • timestamp - Timestamp of the error data sample.
  • port - Port identifier for which errors are reported.
  • serial - Serial number of the Gateway device queried.

Dependencies

  • Aruba Central API with OAuth2 authentication

Troubleshooting

  • Ensure the serial number of the Gateway device is correct and the device is registered in Aruba Central.
  • Verify that the port identifier matches the format expected by Aruba Central (e.g., GE0/0/1).
  • Check that the OAuth2 credentials for Aruba Central API are valid and have sufficient permissions.
  • If 'Return All' is enabled and the dataset is large, the node execution might take longer or time out; consider using the 'Limit' parameter to restrict results.
  • Common error messages may include authentication failures, invalid parameters, or network connectivity issues. Verify credentials and input parameters to resolve these.

Links

Discussion