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 Packet Loss Trend" operation fetches packet loss 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 health and performance of AP tunnels, identify packet loss issues, and troubleshoot connectivity problems.

Practical examples include:

  • Tracking packet loss trends on a specific AP tunnel to detect intermittent connectivity issues.
  • Correlating packet loss data with other performance metrics to optimize wireless network reliability.
  • Automating alerts or reports based on packet loss thresholds in monitored AP tunnels.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, sites), "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is used.
Serial Number Access point serial number identifying the specific AP to query.
Tunnel ID Identifier of the tunnel on the AP for which packet loss trend data is requested.
Time Range Optional collection specifying the start and end times (in ISO 8601 format) for data retrieval.

Output

The node outputs JSON data containing the packet loss trend information for the specified AP tunnel within the requested time range. The structure typically includes timestamps and corresponding packet loss values, allowing visualization or further processing of packet loss over time.

If binary data were output, it would represent raw or encoded telemetry data, but this node focuses on JSON metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • The node depends on internal helper modules for executing operations and logging, bundled within the node's source.
  • No additional external services beyond Aruba Central API are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or tunnel ID will cause the API call to fail.
    • Incorrect time range formats or invalid date values may result in no data returned or errors.
    • Network connectivity issues or expired API tokens can cause authentication failures.
  • Error Messages:

    • Errors from the API are caught and rethrown as node execution errors with descriptive messages.
    • Typical error message: "Unknown error in node execution" indicates an unhandled exception; enabling Debug Mode can provide more detailed logs.
  • Resolutions:

    • Verify that the serial number and tunnel ID correspond to existing resources in Aruba Central.
    • Ensure time range dates are valid ISO 8601 strings.
    • Check API credentials and renew tokens if necessary.
    • Enable Debug Mode to get detailed logs for troubleshooting.

Links and References

  • Aruba Central Next Gen API Documentation (general reference for API endpoints and data models)
  • n8n Documentation on creating custom nodes and handling API integrations
  • ISO 8601 Date and Time Format Specification

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion