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 focusing on LAN tunnel status trends. It is useful for network administrators who want to track the health and performance of gateway LAN tunnels over time. For example, it can be used to monitor connectivity issues or performance degradation in specific tunnels by analyzing their status trends within a given time range.

Typical scenarios include:

  • Monitoring the status trend of a particular LAN tunnel on a gateway to detect intermittent connectivity problems.
  • Collecting historical status data for reporting or alerting purposes.
  • Troubleshooting network issues by correlating tunnel status changes with other network events.

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) or "Configuration" (configure devices, groups, and profiles). Only "Monitoring" applies here.
Serial Number Gateway serial number identifying the specific gateway device to query.
Tunnel Name The name of the LAN tunnel for which to retrieve the status trend details.
Time Range Optional timestamp range for data retrieval, defaults to the last 3 hours if not specified. Includes:
- Start Time (ISO 8601 format)
- End Time (ISO 8601 format)

Output

The node outputs JSON data representing the LAN tunnel status trend over the specified time range. This typically includes timestamps and corresponding status values indicating the operational state of the tunnel at those times. The exact structure depends on the API response but generally provides a time series suitable for visualization or further analysis.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node uses the "monitoring" domain of the API.
  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • Common Issues:

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

    • Errors during execution will be caught and reported with descriptive messages.
    • If debug mode is enabled, detailed logs will help identify the failure point.
    • Typical error messages might include authentication failures, resource not found, or invalid parameters.
  • Resolution Tips:

    • Verify that the gateway serial number and tunnel name are correct and exist in Aruba Central.
    • Ensure the API credentials are valid and have sufficient permissions.
    • Use ISO 8601 format for start and end times when specifying a time range.
    • Enable debug mode to get detailed logs for troubleshooting.

Links and References

Discussion