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 operations related to network devices. The "Get Ports" operation under the "Devices" resource retrieves information about the ports of a specified network device. This is useful for network administrators who want to programmatically access port details such as status, configuration, and statistics from devices monitored by LibreNMS.
Practical examples include:
- Automatically fetching port statuses for a device to monitor link health.
- Integrating port data into dashboards or alerting systems.
- Auditing device port configurations across the network.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique ID of the device whose ports you want to retrieve. |
Output
The output JSON contains detailed information about the ports of the specified device. Each item in the output corresponds to a port on the device and includes attributes such as port name, status, speed, description, and other relevant metadata provided by LibreNMS.
If the node supports binary data (not explicitly shown here), it would typically represent attachments or files related to ports, but this operation primarily returns structured JSON data about device ports.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the base URL of the LibreNMS instance configured in credentials.
- The LibreNMS API must be accessible from the n8n environment.
- Optional setting to allow skipping SSL certificate validation if using self-signed certificates.
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.
- Incorrect or expired API authentication token.
- SSL certificate errors if the LibreNMS server uses self-signed certificates and the option to skip validation is not enabled.
Error messages:
- Authentication errors indicate invalid API credentials; verify and update the API key.
- 404 Not Found may mean the device ID/hostname does not exist in LibreNMS.
- Timeout or connection refused errors suggest network or firewall issues.