Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API

Actions82

Overview

This node interacts with Aruba Central Next Gen API to retrieve monitoring data related to Access Points (APs), specifically focusing on tunnel throughput trends. The "Get AP Tunnel Throughput Trend" operation fetches historical throughput metrics for a specified tunnel on an access point over a given time range.

Typical use cases include:

  • Network administrators monitoring the performance and bandwidth usage of specific tunnels on access points.
  • Troubleshooting network bottlenecks or verifying tunnel capacity over time.
  • Generating reports or dashboards that visualize tunnel throughput trends for operational insights.

For example, a user can specify an AP by its serial number and a tunnel ID, then request throughput data between two timestamps to analyze traffic patterns or detect anomalies.

Properties

Name Meaning
Debug Mode Enable detailed debug logs for troubleshooting purposes.
Domain API domain to interact with; options are: "Monitoring" (for device/client/site monitoring) or "Configuration" (for device/group/profile configuration). For this operation, "Monitoring" is used.
Serial Number The unique serial number identifying the access point whose tunnel throughput trend is being queried.
Tunnel ID Identifier of the specific tunnel on the access point for which throughput data is requested.
Time Range Optional collection specifying the start and end times (in ISO 8601 format) to define the period for data retrieval.

Output

The node outputs JSON data containing the throughput trend information for the specified AP tunnel. This typically includes timestamped throughput values representing the tunnel's bandwidth usage over the selected time range.

The exact structure depends on the API response but generally includes fields such as:

  • Timestamps or time intervals
  • Throughput measurements (e.g., in Mbps)
  • Possibly metadata about the tunnel or AP

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 or similar API key credential).
  • Proper permissions to access monitoring data for the specified AP and tunnel.

Troubleshooting

  • Common issues:

    • Invalid or missing serial number or tunnel ID will cause the API call to fail.
    • Incorrect time range formats or invalid date values may result in errors or empty data.
    • Insufficient API permissions or expired credentials can lead to authentication errors.
    • Network connectivity problems to Aruba Central API endpoints.
  • Error messages:

    • Errors from the API will be caught and reported with descriptive messages.
    • If debug mode is enabled, detailed logs will help identify the failure point.
    • Typical error resolution involves verifying input parameters, refreshing credentials, and ensuring network access.

Links and References

Discussion