Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API

Actions408

Access Points → Get AP Tunnel Jitter Trend

AI-generated

Overview

This node operation retrieves the jitter trend data for a specific access point tunnel in Aruba Central's monitoring domain. It is useful for network administrators who want to monitor the quality and performance of tunnels between access points, particularly focusing on jitter metrics over a specified time range. For example, it can help in diagnosing network issues related to voice or video traffic that are sensitive to jitter.

Use Case Examples

  1. Monitoring the jitter trend of a tunnel identified by its tunnel ID on a specific access point identified by its serial number over a custom time range to ensure network performance meets quality standards.
  2. Using the node to fetch jitter trend data for troubleshooting intermittent connectivity or performance degradation in wireless tunnels.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with, set to 'monitoring' for this operation.
Serial Number Access point serial number to identify the specific AP for which the tunnel jitter trend is retrieved.
Tunnel ID Tunnel identifier to specify which tunnel's jitter trend data to retrieve.
Time Range Optional start and end times to define the period for which jitter trend data is retrieved.

Output

JSON

  • timestamp - Timestamp of the jitter data point.
  • jitterValue - Measured jitter value at the given timestamp.
  • tunnelId - Identifier of the tunnel for which jitter data is reported.
  • serialNumber - Serial number of the access point associated with the tunnel.

Dependencies

  • Aruba Central Next Gen API with OAuth2 authentication

Troubleshooting

  • Ensure the serial number and tunnel ID are correctly specified and exist in the Aruba Central system.
  • Verify that the API domain is set to 'monitoring' as this operation is domain-specific.
  • Check that the OAuth2 credentials are valid and have the necessary permissions to access monitoring data.
  • If the time range is specified, ensure the start time is before the end time and both are in ISO 8601 format.
  • Enable debug mode to get detailed logs if the node execution fails for better troubleshooting.

Discussion