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 IP address information for a specified network device. It is useful in scenarios where you need to programmatically access device IP details for inventory management, network troubleshooting, or automation workflows that depend on device addressing data.
For example, you might use this node to:
- Automatically fetch and log all IP addresses assigned to a device after discovery.
- Integrate device IP data into a CMDB (Configuration Management Database).
- Trigger alerts or actions based on changes in device IP assignments.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique ID of the device whose IP addresses you want to retrieve. This must be provided as a string. |
Output
The node outputs JSON data containing the IP addresses associated with the specified device. The structure typically includes details such as IP address, type (IPv4/IPv6), interface, and possibly status or description depending on LibreNMS API response.
If the node supports binary data output (not indicated here), it would represent related device data in binary form, but for this operation, the focus is on JSON-formatted IP address information.
Dependencies
- Requires an active connection to a LibreNMS instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the LibreNMS API and SSL certificate validation settings must be set in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing device identifier will cause the API call to fail or return no data.
- Network connectivity problems between n8n and LibreNMS server can result in request timeouts or errors.
- Incorrect API credentials or insufficient permissions may lead to authorization errors.
Error messages:
- "Device not found" indicates the provided device hostname or ID does not exist in LibreNMS.
- "Unauthorized" or "Forbidden" suggests invalid API credentials or lack of required permissions.
- SSL certificate errors may occur if the LibreNMS server uses self-signed certificates and the node is not configured to allow unauthorized certs.
To resolve these, verify the device identifier, check API credentials, ensure network accessibility, and adjust SSL settings as needed.