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 switching-related data such as VLANs, links, and other switching information. The "Get Link" operation under the "Switching" resource retrieves detailed information about a specific network link identified by its Link ID. This is useful for network administrators who want to programmatically query details of a particular network connection within their monitored infrastructure.
Practical examples include:
- Fetching link status or metadata for troubleshooting connectivity issues.
- Automating inventory updates by retrieving link details.
- Integrating link information into dashboards or alerts.
Properties
| Name | Meaning |
|---|---|
| Link ID | The unique identifier of the network link to retrieve information about. |
Output
The output JSON contains detailed information about the specified network link. This typically includes properties such as link status, connected devices or ports, VLAN assignments, bandwidth, and other metadata relevant to the link in the LibreNMS system.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the link, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the LibreNMS instance URL configured in the credentials.
- The node depends on the LibreNMS REST API v0 endpoint to fetch switching data.
- Proper network access to the LibreNMS server is necessary.
Troubleshooting
- Invalid Link ID: If the provided Link ID does not exist, the node may return an error or empty response. Verify the Link ID is correct.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Network connectivity issues: Confirm that the n8n instance can reach the LibreNMS server URL.
- SSL certificate errors: If using self-signed certificates, enable the option to allow unauthorized certificates in the credentials.
- API version mismatch: The node expects LibreNMS API v0; ensure the LibreNMS instance supports this version.