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 and configuration data related to gateway clusters. Specifically, the Get Cluster Capacity Trend operation fetches historical capacity usage trends for a specified gateway cluster over a given time range. This is useful for network administrators who want to analyze how cluster resources are utilized over time, identify peak usage periods, and plan capacity upgrades or troubleshooting.

Practical examples:

  • Monitoring bandwidth or resource consumption trends of a gateway cluster to optimize network performance.
  • Analyzing cluster capacity during specific events or time windows to detect anomalies or bottlenecks.
  • Generating reports on cluster utilization for management or auditing purposes.

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).
Cluster Name Gateway cluster name to query capacity trend data for.
Time Range Optional timestamp range for data retrieval. Contains:
- Start Time: ISO 8601 start time.
- End Time: ISO 8601 end time.
If omitted, defaults to last 3 hours.

Output

The node outputs JSON data representing the capacity trend metrics of the specified gateway cluster over the requested time range. The structure typically includes timestamps and corresponding capacity values (e.g., CPU, memory, bandwidth usage) that show how cluster capacity changes over time.

If binary data were involved (not indicated here), it would represent raw files or media related to the cluster metrics, but this operation focuses on JSON metric data only.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key credential configured in n8n.
  • The node depends on proper OAuth2 authentication credentials set up in n8n to access the Aruba Central API.
  • Network connectivity to Aruba Central services is necessary.
  • No additional external libraries beyond those bundled with the node are required.

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.
    • Providing an invalid time range format may cause request rejection.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "Unknown error in node execution": Generic catch-all; check detailed logs if debug mode is enabled.
    • Authentication errors: Verify API credentials and refresh tokens if needed.
    • Validation errors: Ensure required fields like cluster name and domain are correctly set.

Enabling Debug Mode helps by providing detailed logs to diagnose issues.

Links and References

Discussion