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 information about device ports when using the "Ports" resource with the "Get All" operation. This operation retrieves a list of all ports from LibreNMS, optionally allowing users to specify which columns (fields) they want returned for each port.
This node is beneficial in scenarios where network administrators or automation workflows need to gather comprehensive port data from their monitored devices, such as auditing port configurations, monitoring port statuses, or integrating port information into other systems.
Practical examples include:
- Fetching all ports with specific details like interface name, port ID, and alias to generate reports.
- Integrating port data into dashboards for real-time network visualization.
- Automating compliance checks by retrieving port attributes across multiple devices.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters: |
| Columns | Comma-separated list of column names to return for each port, e.g., ifName,port_id,ifAlias. Allows filtering the response to only include specified fields. |
Output
The node outputs JSON data representing an array of port objects retrieved from LibreNMS. Each object contains properties corresponding to the requested columns or all available port fields if no columns are specified.
If binary data were involved (not indicated here), it would typically represent files or media related to ports, but this node focuses on JSON data output only.
Dependencies
- Requires connection to a LibreNMS instance with API access enabled.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL and SSL certificate validation settings are configurable via credentials.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying invalid column names in the "Columns" option may result in incomplete or empty responses.
- Network connectivity problems between n8n and LibreNMS server can cause request timeouts or errors.
Error messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- HTTP 400 or 404 errors may suggest incorrect resource paths or unsupported query parameters; check the "Columns" input and LibreNMS API documentation.
- SSL certificate errors can be resolved by enabling the option to allow unauthorized certificates if using self-signed certs.