Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API
Join our community

Actions82

Overview

This node interacts with Aruba Central Next Gen API to retrieve monitoring data related to Access Points (APs), specifically focusing on radio noise floor metrics for a given radio within an AP. It is useful in network management scenarios where administrators need to monitor wireless signal quality and interference levels by analyzing the noise floor of radios in access points.

Typical use cases include:

  • Monitoring the radio environment to detect interference or noise issues.
  • Collecting historical noise floor data over a specified time range for trend analysis.
  • Integrating noise floor data into broader network health dashboards or alerting systems.

For example, a network engineer can use this node to fetch the noise floor data of a specific radio on an AP identified by its serial number, optionally specifying a time range to analyze changes over time.

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). For this operation, "Monitoring" is used.
Serial Number Access point serial number identifying the specific AP to query.
Radio Number Radio number within the access point to specify which radio's noise floor data to retrieve.
Time Range Optional collection specifying start and end times (ISO 8601 format) for data retrieval, allowing filtering of results within a specific period.

Output

The node outputs JSON data containing the radio noise floor information retrieved from the Aruba Central API. The structure typically includes timestamped noise floor values for the specified radio on the access point. This data can be used directly or further processed in workflows.

If binary data were involved (not indicated here), it would represent raw or encoded sensor data, but this node focuses on JSON-formatted monitoring metrics.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured in n8n credentials (an API key credential).
  • The node depends on internal helper modules for executing operations and logging, bundled within the node implementation.
  • No external libraries beyond those bundled with n8n are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or radio number will cause the API call to fail.
    • Incorrect time range formats or invalid date ranges may result in empty or error responses.
    • Network connectivity issues or expired API tokens will prevent successful data retrieval.

  • Error Messages:

    • Errors during execution are caught and logged with descriptive messages.
    • Typical errors include "Unknown error in node execution" if unexpected exceptions occur.
    • To resolve, verify input parameters, ensure valid API credentials, and check network connectivity.

  • Debug Mode:

    • Enabling Debug Mode provides detailed logs that help identify issues during node execution.

Links and References

Discussion