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 tunnel MOS (Mean Opinion Score) score trends for a given AP tunnel. The MOS score is a key metric used in network quality assessment, reflecting the perceived voice quality over the tunnel.

Typical use cases include:

  • Monitoring voice quality trends over AP tunnels to detect degradation or issues.
  • Integrating MOS score trends into network dashboards or alerting systems.
  • Historical analysis of tunnel performance for troubleshooting or capacity planning.

For example, a network administrator can use this node to fetch MOS score trends for a specific AP tunnel over a defined time range to identify periods of poor voice quality and correlate them with other network events.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options: "Monitoring" (monitor devices, clients, sites), "Configuration" (configure devices, groups, profiles). For this operation, "Monitoring" is used.
Serial Number Access point serial number identifying the AP whose tunnel MOS score trend is requested.
Tunnel ID Identifier of the tunnel for which the MOS score trend data is retrieved.
Time Range Optional collection specifying the start and end times (ISO 8601 format) for data retrieval, allowing filtering of the MOS score trend within a specific period.

Output

The node outputs JSON data containing the MOS score trend information for the specified AP tunnel. The structure typically includes timestamps and corresponding MOS scores, representing how the voice quality has varied over time.

If binary data were involved (not indicated here), it would represent raw or processed data related to the MOS scores, but this node focuses on JSON output.

Example output snippet (conceptual):

[
  {
    "timestamp": "2024-04-01T00:00:00Z",
    "mosScore": 4.2
  },
  {
    "timestamp": "2024-04-01T01:00:00Z",
    "mosScore": 3.9
  }
]

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token configured via n8n credentials (an OAuth2 or API key credential).
  • The node depends on internal helper modules for executing operations and logging, bundled within the node's codebase.
  • Proper permissions on the Aruba Central account to access monitoring data for APs and tunnels.

Troubleshooting

  • Common Issues:

    • Invalid or missing serial number or tunnel ID will cause the API call to fail.
    • Incorrect time range formats or invalid date values may result in no data returned or errors.
    • Network connectivity issues or expired API tokens can cause authentication failures.
    • Selecting the wrong domain (e.g., "Configuration" instead of "Monitoring") will not return monitoring data.

  • Error Messages:

    • "Unknown error in node execution": Generic catch-all; check detailed debug logs if enabled.
    • Authentication errors: Ensure API credentials are valid and have required scopes.
    • Validation errors: Confirm that required properties like serial number and tunnel ID are provided and correctly formatted.

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

Links and References

Discussion