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, allowing users to interact programmatically with various LibreNMS resources. Specifically, for the "Ports" resource with the "Get" operation, it retrieves detailed information about a specific network port identified by its unique Port ID. This is useful in scenarios where you need to fetch configuration or status details of a particular device port within your network monitored by LibreNMS.
Practical examples include:
- Automatically retrieving port details to verify configurations during network audits.
- Integrating port status checks into automated workflows for network health monitoring.
- Fetching port metadata to correlate with other network management tools.
Properties
| Name | Meaning |
|---|---|
| Port ID | The unique identifier of the port to retrieve information for. This is a required string input. |
Output
The node outputs JSON data representing the detailed information of the specified port. This typically includes attributes such as port name, status, speed, description, and other metadata as provided by LibreNMS for that port.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the port, but this is not applicable for the "Get" operation on ports.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the LibreNMS instance URL configured in the credentials.
- The node uses the LibreNMS REST API v0 endpoint to perform operations.
- SSL certificate validation can be optionally skipped based on credential settings.
Troubleshooting
- Common issues:
- Invalid or missing Port ID will cause the request to fail.
- Incorrect API credentials or URL will result in authentication errors.
- Network connectivity issues between n8n and LibreNMS server may cause timeouts or connection errors.
- Error messages:
- "Port not found" indicates the specified Port ID does not exist; verify the ID.
- Authentication errors suggest invalid API keys or misconfigured credentials.
- SSL errors may occur if the LibreNMS server uses self-signed certificates and the option to skip SSL validation is not enabled.