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 functionality to list VRFs (Virtual Routing and Forwarding instances) within the routing resource. This operation is useful for network administrators who want to retrieve and filter VRF information from their monitored devices. Practical use cases include auditing VRF configurations across devices, troubleshooting routing issues by examining VRF assignments, or automating inventory updates of network segmentation.
Properties
| Name | Meaning |
|---|---|
| VRF Filters | A collection of filters to narrow down the VRFs returned. Options include: |
| - Hostname | Filter VRFs by device hostname or device ID. |
| - VRF Name | Filter VRFs by the name of the VRF. |
Output
The node outputs JSON data representing a list of VRFs matching the specified filters. Each item in the output typically contains details about a VRF instance such as its name, associated device, and other routing-related metadata as provided by LibreNMS. The output does not include binary data.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the base URL of the LibreNMS instance configured in credentials.
- The node sends HTTP requests to the LibreNMS API endpoint
/api/v0with appropriate query parameters based on the filters set.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Invalid hostname or VRF name filters may result in empty responses.
- Network connectivity issues between n8n and LibreNMS server can cause request timeouts or errors.
Error Messages:
- Authentication errors usually indicate invalid API keys or insufficient permissions.
- HTTP 404 or 400 errors suggest incorrect API endpoint usage or malformed queries.
Resolutions:
- Verify that the API key credential is correct and has necessary permissions.
- Double-check filter values for typos or unsupported characters.
- Ensure the LibreNMS server URL is reachable from the n8n environment.