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 network gateways. Specifically, for the Gateway resource and the Get Summary of Gateway WAN Tunnel Health operation, it fetches summarized health information about WAN tunnels on a specified gateway device.

Typical use cases include:

  • Network administrators wanting to monitor the health status of WAN tunnels on their gateways.
  • Automated workflows that trigger alerts or remediation steps based on WAN tunnel health summaries.
  • Integration into dashboards or reporting tools to provide real-time WAN tunnel health insights.

For example, a user can input a gateway's serial number and receive a summary report of all WAN tunnels' health statuses, helping quickly identify any degraded or down tunnels.

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 The unique serial number of the gateway device for which to retrieve WAN tunnel health summary. Required when Domain is "Monitoring" and Resource is "Gateway".

Output

The node outputs JSON data containing the summary of the WAN tunnel health for the specified gateway. This typically includes aggregated health metrics such as tunnel status, uptime, error rates, or other relevant health indicators for each WAN tunnel associated with the gateway.

If binary data were involved (e.g., logs or reports), it would be included in a binary field, but this node focuses on JSON structured health summary data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests.
  • The node depends on internal helper modules for executing operations and logging, bundled within the node implementation.
  • No additional external dependencies beyond the Aruba Central API and proper credentials.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number will cause the API call to fail.
    • Incorrect domain selection (e.g., using "Configuration" domain instead of "Monitoring") may result in no data or errors.
    • Network connectivity issues or expired API tokens can prevent successful execution.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check credentials and network.
    • Errors indicating invalid serial number or unauthorized access suggest checking input values and API permissions.
  • Resolutions:

    • Verify the gateway serial number is correct and exists in Aruba Central.
    • Ensure the API credentials are valid and have sufficient permissions.
    • Enable Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion