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-related data such as BGP, OSPF, and other routing information. The "Get VRF" operation under the "Routing" resource retrieves details about a specific Virtual Routing and Forwarding (VRF) instance identified by its VRF ID.
This node is useful in scenarios where network administrators or automation workflows need to programmatically query routing configurations or status from LibreNMS. For example, it can be used to fetch VRF details for auditing, monitoring, or integrating routing data into broader network management dashboards.
Properties
| Name | Meaning |
|---|---|
| VRF ID | The unique identifier of the VRF to retrieve. This is a required string input specifying which VRF's information to fetch. |
Output
The node outputs JSON data representing the VRF details retrieved from LibreNMS. The structure typically includes all relevant properties of the VRF such as its name, description, associated routing protocols, and any other metadata LibreNMS provides for that VRF.
If the node supports binary data output, it would generally relate to attachments or exported files, but for this operation, the output is purely JSON-based routing information.
Dependencies
- Requires an API key credential for authenticating with the LibreNMS API.
- Needs the base URL of the LibreNMS instance configured in the credentials.
- The node uses LibreNMS REST API v0 endpoints.
- SSL certificate validation can be optionally skipped based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing VRF ID will cause the API call to fail or return no data.
- Incorrect API credentials or URL misconfiguration will result in authentication errors.
- Network connectivity problems between n8n and LibreNMS server may cause timeouts or connection failures.
Error messages:
- Authentication errors usually indicate invalid API keys or insufficient permissions.
- "Not Found" errors suggest the specified VRF ID does not exist.
- SSL errors may occur if the LibreNMS server uses self-signed certificates and the option to skip SSL validation is not enabled.
Resolutions:
- Verify the VRF ID exists in LibreNMS.
- Check and update API credentials and URL.
- Enable skipping SSL certificate validation if using self-signed certs.
- Ensure network connectivity and firewall rules allow communication.