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 a summary of the cluster tunnel status for a specified gateway cluster. It is useful in network monitoring and management scenarios where administrators need to quickly assess the health and connectivity status of tunnels within a gateway cluster. For example, it can be used to monitor VPN or inter-site tunnels to ensure they are operational and identify any connectivity 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, sites), "Configuration" (configure devices, groups, profiles)
Cluster Name Gateway cluster name (required when using Monitoring domain and specific operations related to cluster tunnel status)

Output

The node outputs JSON data containing the summary of the cluster tunnel status for the specified gateway cluster. This typically includes details such as tunnel health, connectivity status, and possibly metrics or counts related to tunnels in the cluster. The exact structure depends on the API response but generally provides an overview useful for monitoring purposes.

If binary data were involved (not indicated here), it would represent files or other non-JSON content related to the cluster tunnels, but this node focuses on JSON summaries.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node depends on the external Aruba Central Next Gen service being accessible.
  • Proper configuration of the API domain ("Monitoring" or "Configuration") is necessary to target the correct API endpoints.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common Issues:

    • Incorrect or missing cluster name will cause the API call to fail or return no data.
    • Using the wrong domain option may result in invalid endpoint errors.
    • Network connectivity issues to the Aruba Central API can cause timeouts or connection errors.
    • Insufficient permissions or expired API credentials will lead to authentication errors.
  • Error Messages:

    • Errors during execution are caught and logged with descriptive messages.
    • Typical error messages include "Unknown error in node execution" if the error is not well-defined.
    • Authentication failures or permission denials will be reported by the API and surfaced by the node.
  • Resolution Tips:

    • Verify the cluster name is correct and exists in Aruba Central.
    • Ensure the selected domain matches the intended operation.
    • Check API credentials and renew if expired.
    • Enable Debug Mode to get detailed logs for troubleshooting.

Links and References

  • Aruba Central Next Gen API Documentation (official site)
  • n8n documentation on creating custom nodes and handling API integrations

Discussion