Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API

Actions82

Overview

This node interacts with the Aruba Central Next Gen API to retrieve wireless LAN (WLAN) throughput trend data for access points. It is designed to fetch performance metrics over a specified time range, helping network administrators monitor WLAN traffic and bandwidth usage trends.

Common scenarios where this node is beneficial include:

  • Monitoring WLAN performance to identify peak usage times.
  • Analyzing throughput trends to detect potential network bottlenecks.
  • Generating reports on WLAN traffic patterns for capacity planning.

For example, a user can specify a WLAN name and a time range to obtain throughput data that helps in understanding how the wireless network performs during business hours versus off-hours.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, and sites), "Configuration" (configure devices, groups, and profiles). For this operation, "Monitoring" is used.
WLAN Name Name of the wireless LAN for which throughput trend data is requested.
Time Range Collection specifying the start and end times for data retrieval in ISO 8601 format. Includes:
- Start Time: Beginning of the data interval.
- End Time: End of the data interval.

Output

The node outputs JSON data containing the WLAN throughput trend information over the specified time range. The structure typically includes timestamps and corresponding throughput values, allowing users to analyze how throughput changes over time.

If binary data were output, it would represent raw or processed data files related to the throughput metrics, but this node focuses on JSON metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • The node depends on the monitoring domain of the Aruba Central API.
  • No additional external services are required beyond the Aruba Central API.

Troubleshooting

  • Common Issues:

    • Incorrect WLAN name may result in no data returned or errors.
    • Invalid or missing time range parameters can cause API request failures.
    • Network connectivity issues or expired API tokens will prevent successful data retrieval.
  • Error Messages:

    • Errors indicating "Unknown error in node execution" usually mean the API call failed; enabling Debug Mode can provide more detailed logs.
    • Authentication errors suggest checking the API key or OAuth2 token validity.
    • Validation errors about missing required fields indicate that mandatory properties like WLAN Name or Domain are not set.

To resolve these, verify all input parameters, ensure valid credentials, and enable Debug Mode to get detailed logs for diagnosis.

Links and References

Discussion