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 statistics about a gateway's uplink modem. Specifically, the "Get Gateway Uplink Modem Stats" operation fetches performance and status metrics for a specified gateway device identified by its serial number.

Typical use cases include network monitoring and troubleshooting scenarios where administrators need to analyze the health and performance of gateway uplinks. For example, it can be used to track modem signal quality, connection stability, or data throughput trends to proactively detect issues or verify network configurations.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting
Domain API domain to interact with; options are: "Monitoring" (monitor devices, clients, sites) or "Configuration" (configure devices, groups, profiles)
Serial Number The unique serial number of the gateway device for which uplink modem stats will be retrieved

Output

The node outputs JSON data containing the uplink modem statistics for the specified gateway. This typically includes various performance metrics such as signal strength, error rates, throughput, and other modem-specific telemetry relevant to the gateway's uplink interface.

If binary data were involved (e.g., firmware files or logs), it would be summarized accordingly, but this operation focuses on JSON-formatted statistical data.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number: Ensure the serial number is correctly provided and corresponds to an existing gateway.
    • Authentication failures: Verify that the API credentials are valid and have sufficient permissions.
    • Network connectivity problems: Confirm that n8n can reach the Aruba Central API endpoints.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check debug logs if enabled.
    • Credential or permission errors: Usually indicate misconfigured or expired API tokens.

Enabling "Debug Mode" property helps by providing detailed logs during execution, aiding in pinpointing issues.

Links and References

Discussion