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 WAN compression trend data for a specific gateway uplink interface. It is designed to monitor WAN link performance by analyzing compression trends over time, which can help network administrators optimize bandwidth usage and troubleshoot WAN-related issues.

Typical use cases include:

  • Monitoring WAN uplink efficiency by tracking compression ratios.
  • Diagnosing WAN performance degradation or anomalies.
  • Generating historical reports on WAN compression trends for capacity planning.

For example, a network engineer could use this node to fetch WAN compression trends for a particular gateway's uplink interface over the last 3 hours (default) or a custom time range, enabling detailed analysis of WAN traffic behavior.

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

Output

The node outputs JSON data containing the WAN compression trend metrics for the specified gateway uplink interface. The structure typically includes timestamps and corresponding compression statistics over the requested time range.

If binary data were involved (not indicated here), it would represent raw or processed telemetry data related to WAN compression.

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).
  • Network connectivity to Aruba Central services.
  • Proper permissions to access monitoring data for gateways.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number or link tag will cause the API call to fail.
    • Incorrect time range formats may result in errors or empty data sets.
    • Insufficient API permissions or expired tokens will lead to authentication 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 refresh tokens as needed.
    • Data not found or empty response: Confirm that the gateway serial number and link tag are correct and that data exists for the specified time range.

Enabling Debug Mode helps capture detailed logs to diagnose issues.

Links and References

Discussion