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 memory utilization trends of a gateway device. It is useful for network administrators and IT professionals who want to track the memory usage patterns of their gateway devices over time to ensure optimal performance and troubleshoot potential issues.

Typical use cases include:

  • Monitoring gateway memory consumption to detect leaks or spikes.
  • Analyzing historical memory usage trends to plan capacity upgrades.
  • Integrating memory utilization data into broader network monitoring dashboards.

For example, a user can specify a gateway by its serial number and optionally define a time range to fetch memory utilization data for that period, helping them understand how the gateway's memory usage changes during peak hours.

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, and sites
- Configuration: Configure devices, groups, and profiles
Serial Number Gateway serial number identifying the specific gateway device to query.
Time Range Optional timestamp range for data retrieval (defaults to last 3 hours if not set), consisting of:
- Start Time: ISO 8601 formatted start datetime
- End Time: ISO 8601 formatted end datetime

Output

The node outputs JSON data representing the memory utilization trend of the specified gateway over the requested time range. The structure typically includes timestamps and corresponding memory usage metrics, allowing users to analyze how memory consumption evolves.

If binary data were output, it would represent raw or processed data files related to the memory utilization trend, but this node focuses on JSON-formatted monitoring data.

Dependencies

  • Requires an active connection to the Aruba Central Next Gen API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node depends on internal helper modules for executing operations and logging but no external libraries beyond those bundled with n8n.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number will cause the API call to fail or return no data.
    • Incorrect time range formats may lead to errors or empty results.
    • Network connectivity problems or expired API tokens will prevent successful data retrieval.
  • Error Messages:

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

    • Verify the serial number is correct and corresponds to an existing gateway.
    • Ensure date/time inputs follow ISO 8601 format.
    • Confirm API credentials are valid and have necessary permissions.
    • Enable Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion