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, the "Get Gateway WAN Availability Trend" operation fetches historical availability trends of the WAN interfaces on a specified gateway device. This is useful for network administrators who want to analyze WAN uptime and performance over time, identify outages or degradations, and optimize network reliability.

Practical examples include:

  • Monitoring WAN link stability for a critical gateway.
  • Generating reports on WAN availability trends for SLA compliance.
  • Troubleshooting intermittent WAN connectivity issues by reviewing historical availability data.

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, sites) or "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is used.
Serial Number The unique serial number identifying the gateway device to query.
Time Range Optional timestamp range to specify start and end times for data retrieval in ISO 8601 format. Defaults to last 3 hours if not set. Contains:
- Start Time
- End Time

Output

The node outputs JSON data representing the WAN availability trend for the specified gateway. The structure typically includes timestamps and corresponding availability metrics (e.g., percentage uptime or status flags) over the requested time range.

If binary data were output, it would represent raw data files or reports, but this node focuses on JSON-formatted monitoring data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key credential configured in n8n.
  • The node depends on the arubaCentralNextGenOAuth2Api credential for authentication.
  • No additional external dependencies beyond the Aruba Central API and n8n environment.

Troubleshooting

  • Common Issues:

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

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • API-specific errors returned from Aruba Central (e.g., unauthorized, not found) will be surfaced as node errors.
  • Resolutions:

    • Verify the serial number is correct and corresponds to an existing gateway.
    • Ensure the time range dates are valid ISO 8601 strings.
    • Confirm API credentials are valid and have necessary permissions.
    • Enable Debug Mode to get detailed logs for troubleshooting.

Links and References

Discussion