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 clusters, specifically focusing on the "Gateway Cluster Leader Details" operation within the "Gateway" resource. It is useful for network administrators who need to monitor and manage gateway clusters in their Aruba Central environment. For example, it can be used to fetch the leader details of a specific gateway cluster to verify its status or troubleshoot cluster-related issues.

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).
Cluster Name The name of the gateway cluster for which to retrieve leader details.

Output

The node outputs JSON data containing the details of the gateway cluster leader. This typically includes information such as the cluster leader's identity, status, and possibly other metadata related to the cluster's health and configuration. The exact structure depends on the API response but generally provides comprehensive insight into the cluster leader's state.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node expects proper configuration of the API domain ("monitoring" or "configuration") to target the correct endpoint.
  • No additional external dependencies are indicated beyond the Aruba Central API access.

Troubleshooting

  • Common Issues:

    • Incorrect or missing cluster name will result in failure to retrieve leader details.
    • Using the wrong domain option may cause the API call to fail or return irrelevant data.
    • Network connectivity issues or invalid API credentials will prevent successful execution.
  • Error Messages:

    • Errors are caught and logged with a message indicating "Unknown error in node execution" if no specific message is available.
    • Detailed debug logs can be enabled via the "Debug Mode" property to help diagnose issues.
    • If the API returns an error, the node throws a descriptive error message that can guide corrective actions.

Links and References

Discussion