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 information about Access Points (APs), specifically radios associated with APs, under the "Access Points" resource and the "Get All Radios" operation. It is designed to fetch radio details from the monitoring domain of the API, allowing users to monitor wireless infrastructure status and configurations.

Common scenarios where this node is beneficial include:

  • Network administrators wanting to audit or monitor all radios on their access points.
  • Automated workflows that gather radio status for reporting or alerting.
  • Filtering radios by site or operational status to focus on specific network segments or troubleshoot connectivity issues.

For example, a user can configure the node to return all radios currently online at a particular site, enabling targeted monitoring and maintenance.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, sites) or "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is used.
Return All Whether to return all results or only up to a given limit. Applies when Domain is "Monitoring".
Limit Maximum number of results to return if "Return All" is false. Range: 1 to 100.
Filters Collection of filters to narrow down results:
- Site ID: Filter radios by a specific site identifier.
- Status: Filter radios by status; options are "Online" or "Offline".

Output

The node outputs an array of JSON objects representing radios associated with access points. Each object contains details about a radio, such as its status, site association, and other relevant metadata provided by the Aruba Central API.

If binary data were involved (e.g., firmware files or images), it would be summarized here, but this operation focuses on JSON data output only.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured in n8n credentials (an OAuth2 or API key credential).
  • The node depends on internal helper modules for executing operations and logging, bundled within the node's codebase.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired API tokens.
    • Network connectivity problems preventing API calls.
    • Incorrect filter values leading to empty results.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check API credentials and network.
    • Detailed debug logs can be enabled via the "Debug Mode" property to get more insight into failures.
  • Resolutions:

    • Verify and refresh API credentials.
    • Ensure correct domain and resource selections.
    • Use filters carefully; confirm site IDs and status values exist in your environment.
    • Enable debug mode to trace request and response details.

Links and References

  • Aruba Central Next Gen API Documentation (for Monitoring domain): Aruba Central API Docs
  • n8n Documentation on creating custom nodes: n8n Custom Nodes
  • General best practices for API authentication and error handling in n8n workflows.

Discussion