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 WAN availability trends for a specific gateway uplink. It is designed to monitor the uptime and availability metrics of WAN interfaces on gateways, which is crucial for network administrators who want to track connectivity performance over time.

Typical use cases include:

  • Monitoring WAN link stability and availability for troubleshooting or SLA verification.
  • Collecting historical WAN availability data to analyze trends and detect intermittent outages.
  • Integrating WAN availability metrics into broader network monitoring dashboards or alerting systems.

For example, a network engineer could use this node to automatically fetch WAN availability trends every few hours and trigger alerts if availability drops below a threshold.

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 identifying the target gateway device.
Link Tag WAN interface link tag specifying which WAN uplink interface to query.
Time Range Optional timestamp range for data retrieval (defaults to last 3 hours):
- Start Time (ISO 8601 format)
- End Time (ISO 8601 format)

Output

The node outputs JSON data containing the WAN availability trend information for the specified gateway uplink. The structure typically includes timestamps and corresponding availability metrics that represent the WAN interface's uptime or downtime over the requested period.

If binary data were output, it would represent raw or processed telemetry related to WAN availability, but in this case, the output is purely JSON-based metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key credential configured in n8n.
  • The node depends on proper configuration of the "Domain" property to select the correct API domain ("monitoring" for this operation).
  • Network access to Aruba Central endpoints must be available from the n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number or link tag will cause the API call to fail.
    • Incorrect domain selection may result in unsupported operation errors.
    • Network connectivity issues or expired API credentials can lead to authentication failures.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check debug logs if enabled.
    • Authentication errors: Verify API key validity and permissions.
    • Validation errors: Ensure required properties like serial number and link tag are correctly set.

Enabling "Debug Mode" helps by providing detailed logs to diagnose issues.

Links and References

  • Aruba Central Next Gen API Documentation (general reference for API endpoints and parameters)
  • n8n Documentation on Custom Nodes and Credentials
  • ISO 8601 DateTime Format Reference: https://en.wikipedia.org/wiki/ISO_8601

Discussion