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
This node integrates with the LibreNMS network monitoring system to retrieve and manage routing information, specifically BGP (Border Gateway Protocol) sessions in this context. The "List BGP Sessions" operation under the "Routing" resource allows users to fetch a list of BGP sessions from their monitored network devices.
Typical use cases include:
- Network administrators wanting to monitor the status and details of BGP sessions across their infrastructure.
- Automating network audits or compliance checks by extracting BGP session data.
- Integrating BGP session data into dashboards or alerting systems for proactive network management.
For example, a user can filter BGP sessions by device hostname, local ASN, remote ASN, or BGP session state to focus on specific parts of their network or particular session statuses.
Properties
| Name | Meaning |
|---|---|
| BGP Filters | A collection of filters to narrow down the BGP sessions returned. Options include: |
| - Hostname | Filter sessions by device hostname or ID. |
| - Local ASN | Filter sessions by the local Autonomous System Number (ASN). |
| - Remote ASN | Filter sessions by the remote Autonomous System Number (ASN). |
| - BGP State | Filter sessions by BGP session state. Possible values: Established, Idle, Active, Connect. |
Output
The node outputs JSON data representing the list of BGP sessions matching the specified filters. Each item in the output typically contains details about a BGP session such as device identifiers, ASNs, session states, and other relevant routing information.
If binary data were involved (not indicated here), it would represent associated files or attachments related to the sessions, but this node focuses on JSON structured data only.
Dependencies
- Requires connection to a LibreNMS instance with API access enabled.
- An API key credential must be configured in n8n to authenticate requests to LibreNMS.
- The LibreNMS API base URL and SSL certificate validation settings are configurable via credentials.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Network connectivity issues between n8n and LibreNMS server may result in request timeouts or errors.
- Using invalid filter values (e.g., non-existent hostnames or ASNs) may return empty results.
Error Messages:
- Authentication errors typically indicate invalid API keys or insufficient permissions; verify credentials.
- HTTP errors like 404 or 500 suggest issues with the LibreNMS API endpoint or server status.
- Validation errors may occur if filter parameters are malformed; ensure correct data types and values.