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 gateways, specifically focusing on VPN availability trends of a gateway uplink. It is useful for network administrators and engineers who want to monitor the health and performance of VPN connections through specific gateway uplinks over a defined time range.

Typical use cases include:

  • Tracking VPN uptime and downtime trends on a particular gateway uplink VLAN.
  • Diagnosing connectivity issues by analyzing VPN availability patterns.
  • Generating reports or alerts based on VPN availability metrics for network reliability assessments.

For example, a user can specify a gateway's serial number and uplink VLAN ID to fetch VPN availability trends over the last few hours or a custom time range, helping them understand if there are intermittent VPN outages or degradation.

Properties

Name Meaning
Debug Mode Enable detailed debug logs for troubleshooting purposes (true/false).
Domain API domain to interact with:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Serial Number The unique serial number identifying the gateway device to query.
VLAN ID VLAN ID of the uplink for which VPN availability trends are requested.
Time Range Optional start and end timestamps (ISO 8601 format) defining the period for data retrieval. Defaults to the last 3 hours if not set.

Output

The node outputs JSON data containing VPN availability trend information for the specified gateway uplink VLAN over the requested time range. This typically includes timestamped metrics indicating VPN uptime/downtime or availability percentages.

If binary data were involved (not indicated here), it would represent raw files or logs, but this node focuses on structured JSON metric data.

Dependencies

  • Requires an active connection to Aruba Central Next Gen API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on internal helper modules for executing operations and logging, bundled within the node implementation.
  • No external environment variables beyond standard API credentials are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing gateway serial number or VLAN ID will cause the API call to fail.
    • Incorrect time range formats may result in errors or empty data sets.
    • Network connectivity issues or expired API tokens can prevent successful data retrieval.
  • Error Messages:

    • "Unknown error in node execution": Generic catch-all error; check input parameters and API credentials.
    • Detailed debug logs can be enabled via the "Debug Mode" property to get more insight into failures.
  • Resolutions:

    • Verify that the serial number and VLAN ID correspond to existing resources in Aruba Central.
    • Ensure the time range is correctly formatted in ISO 8601 and logically consistent (start before end).
    • Refresh or reconfigure API credentials if authentication errors occur.
    • Enable debug mode to capture detailed logs for support or further diagnosis.

Links and References

  • Aruba Central Next Gen API Documentation (general reference for API endpoints and data models)
  • n8n Documentation on Custom Nodes and Credentials
  • ISO 8601 Date and Time Format Specification

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic import resolution.

Discussion