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 detailed information about gateway tunnels within a network. Specifically, the "Gateway Tunnel Detail" operation fetches comprehensive data about a particular tunnel on a specified gateway device.

Typical use cases include:

  • Network administrators monitoring specific VPN or LAN tunnels on gateways to troubleshoot connectivity or performance issues.
  • Automation workflows that gather tunnel status and metrics for reporting or alerting.
  • Integrations that require up-to-date tunnel configuration and health details for network management dashboards.

For example, you might use this node to automatically pull the status and statistics of a named tunnel on a gateway identified by its serial number and site ID, enabling proactive network maintenance.

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 identifying the target device (required).
Site ID Site identifier to filter gateway details (required by API).
Tunnel Name Name of the tunnel to retrieve details for (required).

Output

The node outputs JSON data containing detailed information about the specified gateway tunnel. This typically includes tunnel status, configuration parameters, performance metrics, and health indicators as returned by the Aruba Central Next Gen API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key credential configured in n8n.
  • The node depends on proper API authentication and authorization to access gateway monitoring data.
  • Network connectivity to Aruba Central services is necessary.

Troubleshooting

  • Common Issues:

    • Missing or incorrect serial number, site ID, or tunnel name will cause the API call to fail or return no data.
    • Insufficient API permissions or expired credentials can result in authentication errors.
    • Network connectivity problems may prevent successful API communication.
  • Error Messages:

    • Errors during execution are caught and logged with descriptive messages.
    • Typical error messages include "Unknown error in node execution" if the underlying issue is not explicitly reported.
    • Enabling Debug Mode provides detailed logs to help identify the root cause.
  • Resolution Tips:

    • Verify all required input properties are correctly set.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Enable Debug Mode to get verbose logging for troubleshooting.
    • Check network connectivity and firewall settings.

Links and References

Discussion