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 Port Throughput Trend" operation fetches throughput trend data for a specified port on an access point over a given time range. This is useful for network administrators who want to analyze traffic patterns and performance metrics of individual AP ports to optimize network usage or troubleshoot issues.

Practical examples include:

  • Monitoring bandwidth usage trends on a specific AP port to detect unusual spikes or drops.
  • Correlating throughput trends with other network events to diagnose connectivity problems.
  • Generating reports on port utilization over time for capacity planning.

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 (required). Identifies the specific AP to query.
Port Index Port index of the access point (required). Specifies which port's throughput trend to retrieve.
Time Range Optional collection specifying start and end times (ISO 8601 format) for data retrieval. Defines the period over which throughput trends are fetched.

Output

The node outputs JSON data containing the throughput trend information for the specified AP port. The structure typically includes timestamps and corresponding throughput values (e.g., bytes per second or similar metrics) over the requested time range. This allows downstream nodes or workflows to process, visualize, or analyze the throughput trends.

If binary data were involved (not indicated here), it would represent raw data such as files or images, 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 in n8n credentials (an API key credential).
  • The node depends on internal helper modules for executing operations and logging, bundled within the node implementation.
  • No additional external dependencies beyond the Aruba Central API and n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number: Ensure the AP serial number is correct and exists in Aruba Central.
    • Incorrect port index: Verify the port index corresponds to a valid port on the AP.
    • Time range errors: Start time must be before end time; both should be in ISO 8601 format.
    • API authentication failures: Confirm that the API key credential is valid and has necessary permissions.
    • Network connectivity issues: Check that n8n can reach Aruba Central endpoints.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • Authentication errors: Indicate invalid or expired API credentials.
    • Validation errors: Usually specify which input property is incorrect or missing.

Enabling "Debug Mode" helps provide detailed logs to identify the root cause.

Links and References

  • Aruba Central Next Gen API Documentation (official Aruba Networks site)
  • n8n Documentation on creating custom nodes and using credentials
  • ISO 8601 Date and Time Format Reference: https://en.wikipedia.org/wiki/ISO_8601

Discussion