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 health information about sites and their devices. Specifically, for the "Site Health" resource and the "List Sites with Device Health" operation, it fetches a paginated list of sites along with detailed device health data for each site.

This node is beneficial in scenarios where network administrators want to monitor the operational status and health metrics of multiple sites and their associated devices from Aruba Central. It helps in proactive network management by providing insights into device performance and potential issues across sites.

Practical examples:

  • Fetching a list of all monitored sites with their device health status to generate reports or dashboards.
  • Integrating site and device health data into an internal monitoring system for alerting and troubleshooting.
  • Automating periodic health checks of network infrastructure distributed across various locations.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting
Domain API domain to interact with; options are:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Limit Number of sites to return per request (maximum 100)
Offset Number of sites to skip before starting to collect the result set

Output

The node outputs an array of JSON objects representing sites with their device health overview. Each item typically contains:

  • Site identification details (e.g., site name, ID)
  • Aggregated health status of devices within the site
  • Metrics or statuses indicating device health conditions

If binary data were involved, it would be summarized here, but this node focuses on JSON data output related to site and device health.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an 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.
    • Exceeding API rate limits when requesting large numbers of sites.
    • Incorrect domain selection causing unexpected results or errors.
  • Error messages:
    • Errors during execution will provide descriptive messages such as "Unknown error in node execution" or specific API error messages.
    • Enabling "Debug Mode" can help reveal detailed logs to diagnose issues.
  • Resolutions:
    • Verify API credentials and renew if necessary.
    • Adjust Limit and Offset parameters to manage pagination properly.
    • Ensure the correct Domain is selected based on the intended operation.

Links and References

Discussion