LibreNMSInstall

Overview

The node integrates with the LibreNMS network monitoring system to retrieve inventory information about devices. Specifically, the "Get All Inventory" operation under the "Inventory" resource fetches comprehensive inventory data for a specified device by its hostname or device ID. This is useful in scenarios where network administrators want to audit hardware components, check installed modules, or gather detailed device inventory for asset management and troubleshooting.

Practical examples include:

• Automatically collecting hardware inventory details from network devices to update an asset database.
• Monitoring changes in device components over time.
• Integrating inventory data into broader network management workflows.

Properties

The property "Device" is required and expects a string representing either the hostname or the unique identifier of the device whose inventory you want to retrieve.

Output

The node outputs JSON data containing the full inventory details of the specified device. This typically includes hardware components, modules, serial numbers, and other relevant inventory metadata as provided by LibreNMS.

If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the inventory, but this is not evident from the provided code.

Dependencies

• Requires connection to a LibreNMS instance via its API.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL and SSL certificate validation settings are configurable through credentials.
• No additional external dependencies beyond the LibreNMS API.

Troubleshooting

• Common issues:

  • Invalid or missing device hostname/ID will result in no data or errors.
  • Incorrect API credentials or URL misconfiguration can cause authentication failures.
  • Network connectivity problems between n8n and LibreNMS server may lead to request timeouts.

• Error messages:

  • Authentication errors usually indicate invalid API tokens or insufficient permissions.
  • "Device not found" errors suggest the specified device does not exist in LibreNMS.
  • SSL certificate errors may occur if the server uses self-signed certificates and the option to allow unauthorized certs is not enabled.

To resolve these, verify device identifiers, ensure correct API credentials, confirm network access, and adjust SSL settings as needed.

Links and References

• LibreNMS Official Documentation
• LibreNMS API Documentation

Note: This summary is based on static analysis of the provided source code and input properties.