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, the "Get AP Radio Throughput Trend" operation fetches throughput trend metrics for a particular radio on an access point over a specified time range. This is useful for network administrators who want to analyze wireless performance trends, troubleshoot throughput issues, or optimize radio configurations.

Practical examples:

  • Monitoring how the throughput of a specific radio changes during peak hours.
  • Comparing throughput trends between different radios or access points.
  • Detecting performance degradation or interference affecting radio throughput.

Properties

Name Meaning
Debug Mode Enable detailed debug logs for troubleshooting purposes.
Domain API domain to interact with; options are:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Serial Number The serial number of the access point to query.
Radio Number The specific radio number within the access point for which throughput trend data is requested.
Time Range Defines the start and end times for data retrieval in ISO 8601 format:
- Start Time: Beginning of the time window.
- End Time: End of the time window.

Output

The node outputs JSON data containing the throughput trend information for the specified radio on the access point. The structure typically includes timestamps and corresponding throughput values (e.g., bytes per second or Mbps) over the selected time range. This allows users to visualize or further process the throughput trend data.

If binary data were involved (not indicated here), it would represent raw files or media, but this node focuses on JSON metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 API key credential).
  • Proper permissions to access monitoring data for the specified access point and radio.
  • The node uses internal helper modules for executing operations and logging, bundled within the node's codebase.

Troubleshooting

  • Common issues:

    • Invalid or missing serial number or radio number will cause the API call to fail.
    • Incorrect time range format or missing start/end times may result in no data returned or errors.
    • Insufficient API permissions or expired authentication tokens can lead to authorization errors.
    • Network connectivity problems to Aruba Central API endpoints.
  • Error messages:

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • Authorization errors: Verify API credentials and permissions.
    • Validation errors: Ensure all required properties (serial number, radio number, time range) are correctly set.

Enabling "Debug Mode" helps provide detailed logs to diagnose issues.

Links and References

Discussion