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 monitoring and configuration data related to gateways. Specifically, for the Gateway resource and the Get Summary of Gateway Tunnel Health operation, it fetches a summarized health status of gateway tunnels. This is useful for network administrators who want to monitor the health and performance of their gateway tunnels in real time or as part of automated workflows.

Practical examples include:

  • Automatically retrieving tunnel health summaries to trigger alerts if any tunnel shows degraded performance.
  • Integrating tunnel health data into dashboards for centralized network monitoring.
  • Using the summary data to correlate with other network events or logs for troubleshooting.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting (true/false).
Domain API domain to interact with:
- Monitoring: Monitor devices, clients, and sites.
- Configuration: Configure devices, groups, and profiles.
Serial Number Gateway serial number (string). Required when Domain is "monitoring" and Resource is "gateways".
Site ID Site ID to filter gateway details (string). Required by API when Domain is "monitoring" and Resource is "gateways".

Output

The node outputs JSON data representing the summary of the gateway tunnel health. The exact structure depends on the API response but typically includes aggregated health metrics such as tunnel status, error rates, latency, and throughput summaries.

If binary data were involved (not indicated here), it would represent raw data like logs or reports, but this node focuses on JSON-formatted health summaries.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node uses the n8n workflow environment and depends on internal helper modules for executing operations and logging.
  • No external dependencies beyond the Aruba Central API and standard n8n credentials are required.

Troubleshooting

  • Common issues:

    • Missing or invalid serial number or site ID parameters will cause the API call to fail.
    • Incorrect domain selection may lead to unsupported operations or empty responses.
    • Network connectivity issues or expired API tokens can cause authentication failures.
  • Error messages:

    • Errors during execution are caught and logged with descriptive messages.
    • Typical errors include "Unknown error in node execution" or specific API error messages returned from Aruba Central.
    • Enabling Debug Mode provides detailed logs that help identify the root cause.
  • Resolution tips:

    • Verify all required input properties are correctly set.
    • Ensure the API credentials are valid and have necessary permissions.
    • Use Debug Mode to get verbose logs for troubleshooting.

Links and References

Discussion