Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API

Actions82

Overview

This node interacts with Aruba Central Next Gen API to retrieve detailed monitoring data about Access Points (APs), specifically focusing on power consumption metrics for a given AP. It is useful in network management scenarios where administrators need to monitor the energy usage of their wireless infrastructure to optimize power efficiency, detect anomalies, or plan capacity.

Typical use cases include:

  • Tracking power consumption trends of specific access points over time.
  • Integrating power usage data into broader network health dashboards.
  • Automating alerts or actions based on unusual power consumption patterns.

For example, a network operator can input an AP's serial number and a time range to fetch its power consumption data, helping identify if an AP is consuming more power than expected during certain periods.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting (true/false).
Domain API domain to interact with. Options:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Serial Number Access point serial number (string). Required when Domain is "monitoring" and Resource is "Access Points".
Time Range Optional collection specifying the time window for data retrieval:
- Start Time: ISO 8601 formatted start datetime
- End Time: ISO 8601 formatted end datetime

Output

The node outputs JSON data containing the power consumption details of the specified access point within the requested time range. The structure typically includes timestamps and corresponding power consumption values, enabling trend analysis.

If binary data were involved (not indicated here), it would represent raw or processed files related to the AP metrics, but this node focuses on JSON metric data only.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API authentication token configured in n8n credentials.
  • The node depends on the arubaCentralNextGenOAuth2Api credential for authorization.
  • No additional external services are required beyond Aruba Central API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number: Ensure the serial number corresponds exactly to an existing AP in Aruba Central.
    • Incorrect time range format: Use valid ISO 8601 date-time strings for start and end times.
    • API authentication errors: Verify that the API key or OAuth token is correctly configured and has 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 credentials.
    • Validation errors: Indicate missing or malformed input parameters like serial number or time range.

Enabling Debug Mode helps provide detailed logs to diagnose issues.

Links and References

Discussion