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 gateway clusters. Specifically, the Get Cluster Member Capacity Trend operation fetches capacity trend metrics for members of a specified gateway cluster over a given time range. This is useful for network administrators who want to analyze resource usage trends (such as bandwidth or processing capacity) across cluster members to optimize performance and plan capacity upgrades.

Practical examples include:

  • Monitoring how individual gateways in a cluster handle traffic load over time.
  • Detecting unusual spikes or drops in capacity that might indicate issues.
  • Comparing capacity trends between cluster members to balance loads.

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. Required when querying specific gateway details under the monitoring domain. Not directly used in this operation but part of the gateway-related properties.
Cluster Name Gateway cluster name. Identifies which cluster's member capacity trend to retrieve.
Time Range Optional timestamp range for data retrieval. Includes Start Time and End Time in ISO 8601 format. Defaults to last 3 hours if not specified.

Output

The node outputs JSON data representing the capacity trend metrics for each member of the specified gateway cluster within the requested time range. The structure typically includes timestamps and corresponding capacity values per cluster member, allowing visualization or further analysis of capacity changes over time.

If binary data were output, it would represent raw metric files or reports, but this operation focuses on JSON-formatted trend data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 or API key credential).
  • Network access to Aruba Central endpoints.
  • Proper permissions to query monitoring data for the specified cluster.

Troubleshooting

  • Common Issues:

    • Invalid or missing cluster name will cause the API call to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Specifying an invalid time range (e.g., start time after end time) may cause no data to be returned or errors.
    • Network connectivity problems can prevent successful API calls.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • Authentication failures: Verify API credentials and permissions.
    • Validation errors: Ensure required fields like cluster name are provided and correctly formatted.

Enabling Debug Mode helps capture detailed logs to diagnose issues.

Links and References

  • Aruba Central Next Gen API Documentation (for monitoring domain and cluster metrics)
  • n8n documentation on creating and configuring API credential nodes
  • ISO 8601 date/time format specification for time range inputs

Discussion