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 performance trend data related to gateway uplinks. Specifically, the "List Gateway Uplink Performance Trends" operation fetches detailed metrics about the uplink performance of a specified gateway device over a configurable time range.

Use cases include monitoring network health and performance for gateways in enterprise environments, troubleshooting connectivity issues, and analyzing historical uplink trends to optimize network configurations.

For example, a network administrator can use this node to pull uplink throughput and error trends for a particular gateway identified by its serial number, optionally filtered by a specific probe ID and time range, enabling proactive network management.

Properties

Name Meaning
Debug Mode Enable or disable detailed debug logs to assist with troubleshooting node execution.
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 whose uplink performance trends are to be retrieved. This is required.
Probe ID Optional identifier for a specific probe to filter the performance trend data.
Time Range Optional collection specifying start and end timestamps (in ISO 8601 format) to limit the data retrieval period. Defaults to the last 3 hours if not set.

Output

The node outputs JSON data containing the gateway uplink performance trends. This typically includes time-series metrics such as throughput, latency, packet loss, errors, and other relevant uplink statistics collected by probes on the gateway.

If binary data were involved (e.g., logs or files), it would be summarized accordingly, but this operation focuses on structured JSON metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 or similar API key credential).
  • Network access to Aruba Central endpoints must be available from the n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number will cause the API call to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Specifying an invalid time range (e.g., start time after end time) may lead to empty results or errors.
    • Network connectivity problems to Aruba Central API endpoints can cause request failures.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • Authentication errors: Verify API credentials and permissions.
    • Validation errors: Ensure all required fields like serial number are correctly provided.

Enabling Debug Mode property helps capture detailed logs for diagnosing issues.

Links and References

  • Aruba Central Next Gen API Documentation (official Aruba Networks site)
  • n8n Documentation on creating custom nodes and using credentials
  • General REST API best practices for authentication and error handling

Discussion