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, allowing users to interact programmatically with various LibreNMS resources. Specifically, for the "Ports" resource and the "Get IP Addresses" operation, the node retrieves the list of IP addresses associated with a specified network port. This is useful in scenarios where network administrators need to gather detailed IP information tied to specific device ports for monitoring, auditing, or troubleshooting purposes.
Practical examples include:
- Fetching all IP addresses assigned to a particular switch port to verify network configuration.
- Automating inventory updates by extracting port IP data.
- Integrating port IP details into broader network management workflows.
Properties
| Name | Meaning |
|---|---|
| Port ID | The unique identifier of the port whose IP addresses you want to retrieve. |
Output
The node outputs JSON data containing the IP addresses associated with the specified port. The structure typically includes an array or list of IP address objects or strings linked to that port. This output can be used downstream in workflows for reporting, alerting, or further processing.
If the node supports binary data output (not indicated here), it would represent related binary content such as exported reports or snapshots, but this operation focuses on JSON data.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the credentials.
- Optionally, SSL certificate validation can be skipped based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing Port ID will cause the operation to fail.
- Incorrect API credentials or insufficient permissions may result in authorization errors.
- Network connectivity problems between n8n and the LibreNMS server can cause request failures.
- If the LibreNMS API endpoint URL is misconfigured, requests will not succeed.
Error messages:
- "Port ID is required" — Ensure the Port ID property is provided.
- "Unauthorized" or "Authentication failed" — Verify API credentials and permissions.
- "Resource not found" — Confirm the Port ID exists in LibreNMS.
- "Network error" — Check network connectivity and API URL correctness.
Resolving these usually involves verifying input parameters, credentials, and network setup.