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 device health overview data within a specified site. It is useful for network administrators and IT professionals who want to monitor the health status of devices managed by Aruba Central, enabling proactive maintenance and troubleshooting.

Typical use cases include:

  • Fetching real-time or historical health metrics of network devices.
  • Integrating device health data into dashboards or alerting systems.
  • Automating health checks as part of network management workflows.

For example, a user can configure this node to query the device health overview at a specific timestamp to analyze past network conditions or enable debug mode to troubleshoot API communication issues.

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)
Query Time Timestamp in epoch milliseconds for the data request. If not provided, current time is used.

Output

The node outputs JSON data representing the device health overview retrieved from the Aruba Central API. This typically includes aggregated health metrics, status indicators, and possibly device-specific health details relevant to the queried site and time.

If binary data were involved (not indicated here), it would represent raw device reports or logs, but this node focuses on JSON structured health information.

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).
  • Network access to Aruba Central endpoints must be available.
  • No additional external dependencies beyond the API and n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or expired API credentials causing authentication failures.
    • Incorrect domain selection leading to unsupported operations.
    • Malformed or missing Query Time values resulting in unexpected data or errors.
    • Network connectivity problems preventing API calls.
  • Error Messages:

    • Errors during execution will report messages such as "Unknown error in node execution" or more specific API error messages if returned.
    • Enabling Debug Mode helps reveal detailed logs that can pinpoint issues like request payloads, response statuses, or internal exceptions.
  • Resolutions:

    • Verify and refresh API credentials.
    • Ensure the correct domain ("monitoring") is selected for this operation.
    • Provide valid epoch timestamps for Query Time or leave empty to use current time.
    • Check network connectivity and firewall settings.

Links and References

  • Aruba Central Next Gen API Documentation (official Aruba Networks developer portal)
  • n8n documentation on creating and configuring API nodes
  • Epoch timestamp converters for generating valid Query Time values

Discussion