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 detailed information about BGP (Border Gateway Protocol) sessions. Specifically, the "Get BGP Session" operation fetches data for a single BGP session identified by its unique ID. This is useful in network management scenarios where administrators need to monitor or audit BGP session status, configuration, and statistics directly from LibreNMS.
Practical examples include:
- Automatically retrieving BGP session details to verify connectivity or troubleshoot routing issues.
- Integrating BGP session data into dashboards or reports.
- Triggering alerts or workflows based on BGP session state changes.
Properties
| Name | Meaning |
|---|---|
| BGP Session ID | The unique identifier of the BGP session to retrieve. This is required to specify which BGP session's details should be fetched. |
Output
The node outputs JSON data representing the details of the requested BGP session. This typically includes properties such as session state, peer IP, AS numbers, uptime, prefixes received/advertised, and other relevant BGP metrics as provided by LibreNMS.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the BGP session, but this is not applicable for this operation.
Dependencies
- Requires an active connection to a LibreNMS instance via an API key credential.
- The node expects the LibreNMS API URL and authentication token to be configured in the credentials.
- Network access to the LibreNMS server must be available from the n8n environment.
Troubleshooting
- Common Issues:
- Invalid or missing BGP Session ID will cause the operation to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems between n8n and LibreNMS can cause timeouts or unreachable errors.
- Error Messages:
- Authentication failures usually indicate invalid API keys or insufficient permissions.
- "Not Found" errors suggest the specified BGP Session ID does not exist.
- SSL certificate validation errors may occur if LibreNMS uses self-signed certificates; ensure the option to allow unauthorized certs is set if needed.
Links and References
- LibreNMS Official Documentation
- LibreNMS API Documentation
- BGP Concepts - Cisco (for understanding BGP session data)