Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API
Join our community

Actions82

Overview

This node interacts with the Aruba Central Next Gen API to retrieve information about devices. Specifically, the "Get All Devices" operation under the "Device" resource fetches a list of devices monitored or configured in Aruba Central. This is useful for network administrators who want to automate device inventory retrieval, monitor device status, or integrate device data into other workflows.

Practical examples include:

  • Automatically fetching all devices to generate reports or dashboards.
  • Integrating device lists into asset management systems.
  • Triggering alerts or actions based on device presence or attributes.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting
Domain API domain to interact with; options: "Monitoring" (monitor devices, clients, and sites), "Configuration" (configure devices, groups, and profiles)
Return All Whether to return all results or only up to a given limit (only shown when Domain is "Monitoring", Resource is "Device", Operation is "Get All Devices")
Limit Max number of results to return (shown only if Return All is false; minimum 1, maximum 100)

Output

The node outputs JSON data containing an array of device objects retrieved from the Aruba Central API. Each item in the output corresponds to a device with its associated properties as provided by the API. The exact structure depends on the API response but typically includes device identifiers, status, configuration details, and metadata.

If binary data were involved (e.g., device images or logs), it would be summarized here, but this node focuses on JSON device data.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node uses internal helper modules for executing operations and logging.
  • No additional external dependencies are indicated beyond the Aruba Central API access.

Troubleshooting

  • Common issues:
    • Authentication failures due to invalid or expired API credentials.
    • Network connectivity problems preventing API calls.
    • Exceeding API rate limits when requesting large numbers of devices.
  • Error messages:
    • Errors during execution will provide descriptive messages such as "Unknown error in node execution" or specific API error messages.
    • Enabling Debug Mode can help reveal detailed logs to diagnose issues.
  • Resolutions:
    • Verify that the API authentication token or key is valid and has necessary permissions.
    • Check network connectivity and firewall settings.
    • Use the "Limit" property to restrict the number of devices fetched per call or enable "Return All" cautiously.

Links and References

Discussion