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 monitoring data related to gateways, specifically focusing on uplink throughput trends for a given gateway device. It is useful in network management scenarios where administrators want to analyze WAN interface performance over time, detect bottlenecks, or verify link stability.

A practical example use case is fetching the uplink throughput trend of a specific gateway's WAN interface (identified by serial number and link tag) over a custom time range to monitor bandwidth usage patterns or troubleshoot connectivity issues.

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 Gateway serial number identifying the target device.
Link Tag WAN interface link tag specifying which uplink interface's throughput trend to retrieve.
Time Range Optional timestamp range for data retrieval. Contains:
- Start Time (ISO 8601 format)
- End Time (ISO 8601 format)
Defaults to last 3 hours if not specified.

Output

The node outputs JSON data representing the uplink throughput trend for the specified gateway WAN interface. This typically includes time-series data points showing throughput metrics (e.g., bytes per second) over the requested time range.

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 OAuth2 or similar API key credential).
  • The node depends on internal helper modules for executing operations and logging, but these are bundled internally and do not require external installation.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or link tag will cause the API call to fail or return no data.
    • Incorrect time range formats may lead to errors or empty results.
    • Network connectivity or authentication failures can prevent successful API calls.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check detailed debug logs if enabled.
    • Authentication errors: Verify that the API key or OAuth2 credentials are correctly set up.
    • Data not found or empty response: Confirm that the serial number and link tag correspond to existing devices/interfaces in Aruba Central.

Enabling Debug Mode helps provide detailed logs to diagnose issues.

Links and References

  • Aruba Central Next Gen API Documentation (for monitoring gateways and uplink throughput trends)
  • n8n Documentation on creating and using custom nodes
  • General API authentication setup guides for Aruba Central

Discussion