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, specifically providing access to routing information such as BGP, OSPF, and other routing data. The "List IP Addresses" operation under the Routing resource retrieves a list of IP addresses known to LibreNMS, optionally filtered by IP address family (IPv4, IPv6, or all). This is useful for network administrators who want to programmatically query and analyze IP address allocations and routing details within their monitored network.
Practical examples include:
- Automating inventory of IP addresses used in the network.
- Filtering IP addresses by type to generate reports or trigger alerts.
- Integrating IP address data into other systems for network management or auditing.
Properties
| Name | Meaning |
|---|---|
| Address Family | IP address family to filter by. Options: All (no filter), IPv4, IPv6 |
Output
The node outputs JSON data containing the list of IP addresses retrieved from LibreNMS. Each item in the output typically represents an IP address entry with associated metadata such as address, type, and possibly related routing information. The exact structure depends on the LibreNMS API response but generally includes fields relevant to IP addresses in the routing context.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to a LibreNMS instance with API access enabled.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL and SSL certificate validation settings are configurable via credentials.
- No additional external dependencies beyond the LibreNMS API.
Troubleshooting
- Common issues:
- Authentication failures due to incorrect or missing API key.
- Network connectivity problems to the LibreNMS server.
- Filtering by address family may return empty results if no matching IP addresses exist.
- Error messages:
- Unauthorized or 401 errors indicate invalid API credentials.
- Timeout or connection refused errors suggest network or server availability issues.
- Resolutions:
- Verify API key correctness and permissions.
- Check LibreNMS server status and network accessibility.
- Confirm that the requested address family has data in LibreNMS.
Links and References
- LibreNMS Official Website
- LibreNMS API Documentation
- n8n documentation on HTTP Request Node (for understanding API calls)