Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API

Actions82

Overview

This node interacts with Aruba Central Next Gen API to retrieve monitoring data related to Access Points (APs). Specifically, the "Get AP Tunnel Jitter Trend" operation fetches jitter trend metrics for a specified tunnel on an access point over a given time range. This is useful for network administrators who want to monitor the quality and stability of tunnels between access points and controllers or other network elements.

Typical use cases include:

  • Monitoring network performance issues related to jitter in AP tunnels.
  • Analyzing trends over time to detect degradation or improvements in tunnel quality.
  • Integrating jitter trend data into dashboards or alerting systems for proactive network management.

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 Access point serial number (string). Identifies the specific AP to query.
Tunnel ID Tunnel identifier (string). Specifies which tunnel's jitter trend to retrieve.
Time Range Optional collection specifying:
- Start Time: ISO 8601 start time for data retrieval.
- End Time: ISO 8601 end time for data retrieval.

Output

The node outputs JSON data containing the jitter trend metrics for the specified AP tunnel within the requested time range. The structure typically includes timestamps and corresponding jitter values, allowing users to analyze how jitter changes over time.

If binary data were involved (not indicated here), it would represent raw or processed telemetry data, but this operation focuses on 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 API key credential).
  • Proper permissions to access monitoring data for APs and tunnels.
  • Network connectivity to Aruba Central services.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or tunnel ID will cause the API call to fail.
    • Incorrect time range format or invalid dates may result in no data returned or errors.
    • Insufficient API permissions can lead to authorization errors.
    • Network connectivity problems can cause request timeouts or failures.
  • Error Messages:

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

Enabling Debug Mode helps capture detailed logs to diagnose issues.

Links and References

Discussion