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 monitoring data related to gateway devices. Specifically, the "Get Gateway Port Frames Errors Trend" operation fetches time-series data about error trends on a specified port of a gateway device. This is useful for network administrators who want to monitor the health and performance of gateway ports over time, identify error spikes, and troubleshoot connectivity or hardware issues.

Practical examples include:

  • Tracking frame errors on a specific gateway port to detect potential physical layer problems.
  • Monitoring port error trends before and after configuration changes or firmware updates.
  • Integrating error trend data into dashboards or alerting systems for proactive network maintenance.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting (true/false).
Domain API domain to interact with:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Serial Number Gateway serial number identifying the target device (string).
Port Number Gateway port number for interface operations (string).
Time Range Optional timestamp range for data retrieval (defaults to last 3 hours):
- Start Time (ISO 8601 datetime)
- End Time (ISO 8601 datetime)

Output

The node outputs JSON data representing the trend of port frame errors over the specified time range for the given gateway port. The structure typically includes timestamps and corresponding error counts or metrics that indicate the number or rate of frame errors detected on the port.

If binary data were output, it would represent raw or processed data files related to the trend, but this node focuses on JSON time-series data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API via an API key credential configured in n8n.
  • The node depends on proper API authentication and authorization to access gateway monitoring data.
  • No additional external services are required beyond Aruba Central Next Gen API.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number or port number will cause the API call to fail.
    • Incorrect time range format or invalid dates may result in no data returned or errors.
    • Network connectivity issues or expired API credentials can prevent successful data retrieval.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check API credentials and network.
    • API-specific errors indicating unauthorized access or resource not found usually mean incorrect serial number or insufficient permissions.
  • Resolutions:

    • Verify the gateway serial number and port number are correct and exist in Aruba Central.
    • Ensure the API key credential is valid and has necessary permissions.
    • Use Debug Mode to get detailed logs for diagnosing issues.

Links and References

Discussion