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 WLAN Throughput Trend operation fetches throughput trend data for a specified wireless LAN on an access point over a given time range. This is useful for network administrators who want to analyze wireless network performance, identify bottlenecks, or monitor usage patterns of specific WLANs on APs.

Practical examples:

  • Monitoring throughput trends of a corporate Wi-Fi SSID on a particular AP to detect peak usage times.
  • Comparing throughput performance across different WLANs or APs to optimize network configuration.
  • Troubleshooting slow wireless connections by analyzing historical throughput data.

Properties

Name Meaning
Debug Mode Enable detailed debug logs for troubleshooting the node execution.
Domain API domain to interact with:
- Monitoring: Monitor devices, clients, and sites.
- Configuration: Configure devices, groups, and profiles.
Serial Number The serial number of the access point to query.
WLAN Name The name of the wireless LAN (SSID) for which throughput trend data is requested.
Time Range Optional start and end times (in ISO 8601 format) defining the period for data retrieval.

Output

The node outputs JSON data containing the throughput trend information for the specified WLAN on the access point. The structure typically includes timestamps and corresponding throughput values (e.g., Mbps) over the selected time range, allowing visualization or further processing of throughput trends.

If binary data were involved (not indicated here), it would represent raw data such as reports or logs, but this node focuses on JSON throughput metrics.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing serial number or WLAN name will cause the API call to fail.
    • Incorrect time range formats or invalid date ranges may result in empty or error responses.
    • Insufficient API permissions or expired credentials can lead to authorization errors.
    • Network connectivity problems between n8n and Aruba Central API.
  • Error messages:

    • "Unknown error in node execution": Generic catch-all; check debug logs if enabled.
    • Authorization errors: Verify API credentials and permissions.
    • Validation errors: Ensure required properties like serial number and WLAN name are correctly set.

Enabling Debug Mode helps capture detailed logs to diagnose issues.

Links and References

Discussion