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, the "Get Gateway CPU Utilization Trend" operation fetches historical CPU usage metrics for a specified gateway device identified by its serial number. This is useful for network administrators and IT professionals who want to monitor the performance and health of their gateway devices over time.

Typical use cases include:

  • Tracking CPU load trends to anticipate potential overloads or failures.
  • Integrating CPU utilization data into dashboards or alerting systems.
  • Correlating CPU usage with other network events or performance metrics.

For example, an administrator could schedule this node to run periodically to collect CPU utilization data for a gateway and then trigger alerts if CPU usage exceeds certain thresholds.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, and sites), "Configuration" (configure devices, groups, and profiles). For this operation, "Monitoring" is used.
Serial Number The unique serial number identifying the gateway device whose CPU utilization trend is requested.
Time Range Optional timestamp range for data retrieval. Consists of:
- Start Time: ISO 8601 start timestamp.
- End Time: ISO 8601 end timestamp.
If omitted, defaults to the last 3 hours.

Output

The node outputs JSON data containing the CPU utilization trend for the specified gateway over the requested time range. The structure typically includes timestamps and corresponding CPU usage percentages or metrics that represent CPU load over time.

If binary data were involved (e.g., files or images), it would be summarized here, but this operation returns only 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 (an OAuth2 or similar API key credential).
  • Network access to Aruba Central services must be available from the n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number: Ensure the serial number corresponds exactly to a registered gateway device.
    • Incorrect time range format: Use valid ISO 8601 date-time strings for start and end times.
    • API authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
    • Network connectivity problems: Confirm that n8n can reach Aruba Central endpoints.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check debug logs if enabled.
    • Authentication failures: Usually indicate invalid or expired API tokens.
    • Data not found or empty response: Could mean the gateway serial number is incorrect or no data exists for the given time range.

Enabling "Debug Mode" property helps provide detailed logs to diagnose issues.

Links and References

Discussion