Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
The node integrates with the LibreNMS network monitoring system to retrieve routing information, specifically IP networks. It allows users to list IP networks filtered by IP address family (IPv4, IPv6, or all). This is useful for network administrators who want to automate the extraction of routing data from LibreNMS for monitoring, reporting, or further processing in workflows.
Practical examples include:
- Automatically fetching all IPv4 and IPv6 networks known to LibreNMS for inventory or audit purposes.
- Filtering and retrieving only IPv6 networks to analyze IPv6 deployment status.
- Integrating routing data into dashboards or alerting systems.
Properties
| Name | Meaning |
|---|---|
| Address Family | IP address family to filter by. Options: All (both IPv4 and IPv6), IPv4 only, or IPv6 only |
Output
The node outputs JSON data representing the list of IP networks retrieved from LibreNMS. Each item in the output typically contains details about an IP network such as its address, prefix length, and possibly associated metadata like device or interface information.
If binary data were involved (e.g., exporting routing tables as files), it would be summarized here, but this node focuses on JSON structured routing data.
Dependencies
- Requires connection to a LibreNMS instance with API access.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL and SSL certificate validation settings are configurable via credentials.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or missing API keys.
- Network connectivity problems reaching the LibreNMS server.
- Filtering by address family may return empty results if no matching networks exist.
Error messages:
- "Unauthorized" or "Authentication failed": Check API key validity and permissions.
- "Network error" or "Could not connect": Verify LibreNMS URL and network accessibility.
- Empty output when filtering: Confirm that the selected address family has corresponding IP networks in LibreNMS.