Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API
Join our community

Actions82

Overview

This node interacts with the Aruba Central Next Gen API to retrieve information about Access Points (APs) within a specified domain, particularly under the "monitoring" domain. The "Get All Access Points" operation fetches a list of APs, optionally filtered by criteria such as site ID, model, status, and deployment mode. It supports returning either all matching results or a limited subset.

Typical use cases include:

  • Monitoring network infrastructure by listing all access points and their statuses.
  • Filtering APs by site or model to focus on specific segments of a network.
  • Integrating AP data into dashboards or automated workflows for network management.

For example, a network administrator could use this node to automatically gather all online APs in a particular site to check their health or usage statistics.

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
Return All Whether to return all results or only up to a given limit (only available when Domain is "Monitoring")
Limit Max number of results to return (1-100). Only used if Return All is false and Domain is "Monitoring".
Filters Collection of filters to narrow down the access points returned:
- Site ID: Filter by site identifier
- Model: Filter by AP model
- Status: Filter by AP status ("Online" or "Offline")
- Deployment: Filter by deployment mode

Output

The node outputs an array of JSON objects representing access points. Each object contains details about an individual AP, such as its identifier, model, status, site association, and deployment mode. The exact structure depends on the API response but typically includes fields relevant to monitoring APs.

If binary data were involved (e.g., images or files), it would be summarized here, but this operation focuses on JSON 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 "monitoring" domain of the Aruba Central API for this operation.
  • No additional external services are required beyond the Aruba Central API.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired API tokens.
    • Network connectivity issues preventing access to Aruba Central API endpoints.
    • Incorrect filter values leading to empty result sets.

  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check API credentials and network.
    • Errors indicating invalid parameters usually mean filters or limits are set incorrectly.

  • Resolutions:

    • Verify that the API key or OAuth2 token is correctly configured and has necessary permissions.
    • Ensure the domain is set to "monitoring" for this operation.
    • Double-check filter values for correctness and existence in your Aruba Central environment.
    • Enable Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion