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 LAN tunnel throughput trends in this context. It is useful for network administrators and engineers who want to monitor the performance and bandwidth usage of specific LAN tunnels on their gateway devices over a selected time range.

Typical use cases include:

  • Tracking bandwidth utilization on a particular LAN tunnel to identify bottlenecks.
  • Analyzing historical throughput trends to plan capacity upgrades.
  • Troubleshooting network issues by correlating throughput changes with events or alerts.

For example, a user can specify a gateway's serial number and a tunnel name to fetch throughput data for that tunnel over the last few hours or a custom time range.

Properties

Name Meaning
Debug Mode Enable detailed debug logs for troubleshooting purposes.
Domain Selects the API domain to interact with: either "Monitoring" (for device/client/site monitoring) or "Configuration" (for device/group/profile configuration). For this operation, "Monitoring" is used.
Serial Number The unique serial number identifying the gateway device from which to retrieve LAN tunnel data.
Tunnel Name The name of the LAN tunnel on the gateway for which throughput trend data will be retrieved.
Time Range Optional start and end timestamps (ISO 8601 format) defining the period for data retrieval. Defaults to the last 3 hours if not specified.

Output

The node outputs JSON data representing the LAN tunnel throughput trend over the specified time range. This typically includes timestamped throughput metrics such as bytes per second or packets per second for the given tunnel.

The exact structure depends on the API response but generally contains an array of data points with time and throughput values, enabling visualization or further processing.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an OAuth2 API key credential configured in n8n.
  • Network access to Aruba Central services must be available.
  • Proper permissions on the API key to access gateway monitoring data are necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or tunnel name will cause the API call to fail.
    • Incorrect time range formats may result in errors or empty data sets.
    • Insufficient API permissions or expired credentials will prevent data retrieval.
  • Error Messages:

    • Errors during execution will be caught and reported with messages indicating the failure reason.
    • Typical error messages might include "Gateway not found," "Tunnel name invalid," or authentication failures.
  • Resolutions:

    • Verify that the serial number and tunnel name are correct and exist in Aruba Central.
    • Ensure the time range is properly formatted in ISO 8601 and logically consistent (start before end).
    • Refresh or reconfigure API credentials if authentication errors occur.
    • Enable Debug Mode to get detailed logs for diagnosing issues.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion