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 listing uplink probes for a given gateway. It is useful in network management scenarios where administrators need detailed insights into the status and performance of WAN uplinks on their gateways.

Typical use cases include:

  • Monitoring WAN interface health and connectivity.
  • Troubleshooting uplink issues by analyzing probe results.
  • Collecting historical uplink probe data within a specified time range for reporting or alerting.

For example, a network engineer can use this node to fetch uplink probe data for a specific gateway's WAN interface identified by its serial number and link tag, optionally filtering the data by a custom time range.

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
- Configuration: Configure devices, groups, and profiles
Serial Number Gateway serial number (string). Required when using the "monitoring" domain and certain operations including listing uplink probes.
Link Tag WAN interface link tag (string) identifying the specific uplink interface on the gateway.
Time Range Optional timestamp range for data retrieval (defaults to last 3 hours):
- Start Time (ISO 8601 datetime)
- End Time (ISO 8601 datetime)

Output

The node outputs JSON data representing the list of uplink probes for the specified gateway and WAN interface. The structure typically includes details such as timestamps, probe results, latency, packet loss, and other relevant metrics collected from the uplink probes.

If binary data were involved, it would represent raw probe data or logs, but in this case, the output is purely JSON structured data summarizing uplink probe information.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • The node depends on proper configuration of the API domain ("monitoring") and valid gateway identifiers (serial number and link tag).
  • No additional external services are required beyond Aruba Central Next Gen API access.

Troubleshooting

  • Common Issues:

    • Missing or incorrect serial number or link tag will result in errors or empty results.
    • Invalid or expired API authentication tokens will cause authentication failures.
    • Incorrect domain selection may lead to unsupported operation errors.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check detailed debug logs if enabled.
    • Authentication errors: Verify API credentials and permissions.
    • Validation errors: Ensure all required properties (serial number, link tag) are provided and correctly formatted.

Enabling "Debug Mode" helps capture detailed logs that can assist in diagnosing issues.

Links and References

  • Aruba Central Next Gen API Documentation (for monitoring gateways and uplink probes)
  • n8n Documentation on creating and configuring API credential nodes
  • Network monitoring best practices for WAN uplinks

Discussion