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 Packets Trend" operation fetches time-series data about packet trends on a specified port of a gateway device identified by its serial number.

Use cases include:

  • Monitoring network traffic patterns on specific gateway ports.
  • Analyzing packet flow trends over time for troubleshooting or capacity planning.
  • Integrating gateway port metrics into broader network monitoring workflows.

For example, a network administrator can use this node to pull packet trend data from a particular gateway port over the last few hours to identify unusual spikes or drops in traffic.

Properties

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

Output

The node outputs JSON data representing the packet trend metrics for the specified gateway port over the requested time range. This typically includes timestamped values showing packet counts or rates, allowing visualization or further processing of traffic trends.

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

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • The node depends on internal helper modules for executing operations and logging, but these are bundled internally.
  • No additional external services beyond Aruba Central API are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or port number will cause the API call to fail.
    • Incorrect time range formats may result in errors or empty data sets.
    • Network connectivity issues or expired API tokens will prevent successful data retrieval.
  • Error Messages:

    • Errors are caught and rethrown as node operation errors with descriptive messages.
    • Typical error messages might include "Invalid serial number", "Port number not found", or generic API errors.
  • Resolution Tips:

    • Verify that the serial number and port number correspond to existing gateway hardware.
    • Ensure the time range is correctly formatted in ISO 8601 and logically consistent (start before end).
    • Confirm that the API authentication token is valid and has necessary permissions.
    • Enable Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion