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 devices. Specifically, the "Get Gateway Port Frames Trend" operation fetches time-series trend data about frames on a specified port of a gateway device. This is useful for network administrators who want to analyze traffic patterns, detect anomalies, or monitor performance metrics over time on specific gateway ports.

Practical examples include:

  • Monitoring frame counts on a gateway port to identify unusual spikes or drops in traffic.
  • Correlating port frame trends with network events or outages.
  • Generating reports or dashboards showing historical port utilization.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting (true/false).
Domain API domain to interact with: "Monitoring" (monitor devices, clients, and sites) or "Configuration" (configure devices, groups, and profiles). For this operation, "Monitoring" is used.
Serial Number The serial number of the gateway device to query.
Port Number The specific port number on the gateway for which to retrieve frame trend data.
Time Range Optional start and end timestamps (ISO 8601 format) defining the period for data retrieval. Defaults to the last 3 hours if not set. Includes:
- Start Time
- End Time

Output

The node outputs JSON data representing the trend of port frames over the specified time range. The structure typically includes timestamped entries with frame counts or related metrics for the given port on the gateway. This allows downstream nodes or workflows to process, visualize, or analyze the time series data.

If binary data were involved (not indicated here), it would represent raw data streams or files, but this operation focuses on JSON-formatted monitoring metrics.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • Network access to Aruba Central services.
  • Proper permissions to query gateway monitoring data.
  • No additional external dependencies beyond the API and n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number will cause the API call to fail.
    • Incorrect port number may result in empty or error responses.
    • Time range outside available data window may return no results.
    • Network connectivity issues or expired API tokens can cause authentication failures.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check node parameters and API connectivity.
    • Authentication errors: Verify API credentials and permissions.
    • Validation errors: Ensure required fields like serial number and port number are correctly set.
  • Resolution Tips:

    • Enable Debug Mode to get detailed logs for troubleshooting.
    • Confirm that the gateway serial number and port number exist and are correct.
    • Adjust time range to valid intervals.
    • Refresh or reconfigure API credentials if authentication fails.

Links and References

Discussion