Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API
Join our community

Actions82

Overview

This node interacts with Aruba Central Next Gen API to retrieve throughput trend data for a specific Access Point (AP). It is designed to fetch historical throughput metrics over a specified time range, segmented by interface type such as wireless, wired, or LTE. This functionality is useful for network administrators and engineers who want to monitor the performance and bandwidth usage trends of individual APs in their network.

Typical use cases include:

  • Analyzing traffic patterns on an AP to identify peak usage times.
  • Troubleshooting network performance issues by correlating throughput trends with other metrics.
  • Capacity planning by understanding how throughput evolves over time on different interfaces.

For example, a user can specify an AP's serial number and request wireless throughput trends between two timestamps to visualize how the wireless traffic load changes throughout the day.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, sites), "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is used.
Serial Number Access point serial number to identify which AP's throughput trends to retrieve.
Time Range Optional collection specifying start and end times (in ISO 8601 format) for data retrieval.
Interface Type Type of interface for which to retrieve throughput data. Options: "Wireless", "Wired", "LTE".

Output

The node outputs JSON data representing the throughput trends of the specified AP interface over the requested time range. The structure typically includes timestamped throughput values, allowing users to analyze how throughput varies over time.

If binary data were output, it would represent raw or processed throughput metrics, but this node focuses on JSON-formatted metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key or OAuth2 token configured in n8n credentials.
  • The node depends on the executeOperation helper function to perform the actual API call.
  • No additional external services are required beyond Aruba Central API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number will cause the API call to fail or return no data.
    • Incorrect time range formats or invalid date values may result in errors or empty responses.
    • Network connectivity issues or expired API tokens will prevent successful data retrieval.

  • Error Messages:

    • Errors during execution are caught and rethrown as node operation errors with descriptive messages.
    • Enabling Debug Mode provides detailed logs that help identify where failures occur.

  • Resolutions:

    • Verify the serial number is correct and corresponds to an existing AP.
    • Ensure time range dates are valid ISO 8601 strings.
    • Confirm API credentials are valid and have necessary permissions.
    • Use Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion