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 switching-related data. Specifically, the "Get Device Links" operation fetches information about the network links associated with a specified device. This is useful for network administrators who want to visualize or audit the physical and logical connections of a particular network device within their infrastructure.
Practical examples include:
- Auditing all active links on a switch to verify network topology.
- Troubleshooting connectivity issues by examining link statuses.
- Automating documentation of device interconnections.
Properties
| Name | Meaning |
|---|---|
| Device | The target device identified by its hostname (FQDN) or numeric device ID to query links. |
Output
The node outputs JSON data representing the links related to the specified device. This typically includes details such as connected ports, remote devices, link status, and other metadata describing each link. The exact structure depends on the LibreNMS API response but generally provides comprehensive link-level information for the device.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to a LibreNMS instance with API access.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the LibreNMS API must be set in the credentials.
- Optionally, SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
Common Issues:
- Invalid device identifier: Ensure the device name or ID exists in LibreNMS.
- Authentication errors: Verify that the API token is correct and has sufficient permissions.
- Network connectivity problems: Confirm that n8n can reach the LibreNMS server URL.
- SSL errors: If using self-signed certificates, enable the option to skip SSL validation.
Error Messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 Not Found may mean the device does not exist or the endpoint is incorrect.
- Timeout or connection refused errors suggest network or server availability issues.
Resolving these usually involves checking credentials, device identifiers, and network configurations.