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 gateway clusters. Specifically, for the "Get Summary of Cluster Tunnel Health" operation under the Gateway resource, it fetches a summarized health status of tunnels within a specified gateway cluster. This is useful for network administrators who want to monitor the connectivity and performance of tunnels in their gateway clusters, helping them quickly identify issues or confirm healthy operation.

Practical examples include:

  • Monitoring tunnel health to proactively detect and resolve connectivity problems.
  • Generating reports on cluster tunnel status for network audits.
  • Integrating tunnel health summaries into broader network monitoring workflows.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting (true/false).
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, sites) or "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is relevant.
Cluster Name The name of the gateway cluster for which to get the tunnel health summary.

Output

The node outputs JSON data representing the summary of the cluster tunnel health. This typically includes aggregated health metrics, status indicators, and possibly counts or lists of tunnels categorized by their health state. The exact structure depends on the API response but generally provides a concise overview of tunnel connectivity and performance within the specified cluster.

If binary data were involved (not indicated here), it would represent files or media related to the cluster health, but this operation focuses on JSON summary 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 correct setup of the API domain ("monitoring" or "configuration") and valid cluster names existing in the Aruba Central environment.
  • No additional external services are required beyond Aruba Central API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing cluster name will cause the API call to fail or return empty results.
    • Incorrect domain selection may lead to unsupported operations or errors.
    • Network connectivity issues or expired API tokens can cause authentication failures.
  • Error Messages:

    • Errors during execution will be caught and reported with messages such as "Unknown error in node execution" or specific API error messages.
    • Enabling Debug Mode helps reveal detailed logs that can assist in diagnosing issues.
  • Resolutions:

    • Verify the cluster name is correct and exists in Aruba Central.
    • Ensure the API domain matches the intended operation.
    • Refresh or reconfigure API credentials if authentication errors occur.
    • Enable Debug Mode to get verbose logging for deeper insight.

Links and References

  • Aruba Central Next Gen API Documentation (for detailed API endpoints and data structures)
  • n8n Documentation on creating and using custom nodes
  • Network monitoring best practices for gateway clusters and tunnels

Discussion