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 about Access Points (APs), specifically focusing on CPU utilization for a given AP. It is useful in network management scenarios where administrators need to monitor the performance and health of wireless access points, diagnose issues related to CPU load, or optimize resource allocation.

For example, a network engineer can use this node to fetch CPU usage trends over a specified time range for a particular AP identified by its serial number. This helps in proactive maintenance and troubleshooting of network devices.

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) or "Configuration" (configure devices, groups, and profiles). For this operation, "Monitoring" is used.
Serial Number Access point serial number to identify which AP's CPU utilization data to retrieve.
Time Range Optional collection specifying the start and end times (in ISO 8601 format) for data retrieval, allowing filtering of CPU utilization data within a specific period.

Output

The node outputs JSON data containing the CPU utilization metrics of the specified access point. The structure typically includes timestamps and corresponding CPU usage values, enabling trend analysis over the selected time range.

If binary data were involved (not indicated here), it would represent raw or processed device data, but this node focuses on JSON-formatted monitoring metrics.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 API key credential).
  • Proper permissions to access monitoring data for access points in the Aruba Central environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number: Ensure the serial number corresponds to a valid AP in your Aruba Central account.
    • Incorrect time range format: Use ISO 8601 date-time strings for start and end times.
    • Insufficient API permissions: Verify that the API key has rights to access monitoring data.
    • Network connectivity problems: Confirm that n8n can reach Aruba Central API endpoints.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check debug logs if enabled.
    • Authentication errors: Indicate invalid or expired API credentials.
    • Data not found or empty response: Could mean no data available for the given serial number or time range.

Enabling Debug Mode property can help surface detailed logs to diagnose issues.

Links and References

Discussion