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, specifically focusing on Gateway resources. The "Gateway Cluster Connectivity Graph" operation retrieves connectivity graph data for a specified gateway cluster. This is useful for network administrators who want to visualize or analyze the connectivity status and topology of gateway clusters within their network infrastructure.

Practical examples include:

  • Monitoring the health and connectivity between gateways in a cluster.
  • Diagnosing network issues related to cluster communication.
  • Visualizing cluster topology for capacity planning or 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
Cluster Name Gateway cluster name (string). Required to specify which cluster's connectivity graph to retrieve.

Output

The node outputs JSON data representing the connectivity graph of the specified gateway cluster. This typically includes information about cluster members, their connections, and possibly the status or health of these connections.

If binary data were output, it would represent files or images related to the connectivity graph visualization, but based on the code and properties, the output is JSON structured data describing the cluster connectivity.

Dependencies

  • Requires an API key credential for authenticating with Aruba Central Next Gen API.
  • The node depends on the executeOperation helper function that handles the actual API call.
  • No additional external services beyond Aruba Central Next Gen API are required.
  • Proper configuration of the API domain and cluster name is necessary.

Troubleshooting

  • Common Issues:

    • Incorrect or missing cluster name will result in errors or empty results.
    • Network connectivity issues or invalid API credentials can cause authentication failures.
    • Selecting the wrong domain (Monitoring vs Configuration) may lead to unexpected responses or errors.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check API credentials and network connection.
    • Detailed debug logs can be enabled via the "Debug Mode" property to get more insight into failures.
  • Resolution Tips:

    • Verify the cluster name is correct and exists in Aruba Central.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Enable debug mode to capture detailed logs for support or further diagnosis.

Links and References

Discussion