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 allowing management of network devices. The "Rename" operation under the "Devices" resource enables users to change the hostname of a specified device within LibreNMS. This is useful in scenarios where device hostnames need to be updated to reflect changes in network topology, naming conventions, or organizational standards.
Practical examples include:
- Renaming a device after it has been replaced or reconfigured.
- Standardizing device names across the network for easier identification.
- Correcting typos or outdated hostnames in the monitoring system.
Properties
| Name | Meaning |
|---|---|
| Device | The current hostname or unique identifier of the device to rename. |
| New Hostname | The new hostname that will replace the existing one for the specified device. |
Output
The node outputs JSON data representing the result of the rename operation. Typically, this includes confirmation details such as the updated device information or status messages indicating success or failure. There is no indication that binary data is output by this operation.
Dependencies
- Requires an active 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 must be properly set in the node credentials.
Troubleshooting
Common issues:
- Invalid device identifier: If the provided device hostname or ID does not exist, the operation will fail.
- Insufficient permissions: The API token used may lack rights to modify device information.
- Network connectivity problems between n8n and LibreNMS server.
- Incorrect new hostname format or conflicts with existing device names.
Error messages and resolutions:
- "Device not found": Verify the device identifier is correct and exists in LibreNMS.
- "Unauthorized" or "Forbidden": Check API credentials and permissions.
- "Invalid hostname": Ensure the new hostname complies with LibreNMS naming rules.
- SSL errors: Adjust SSL certificate validation settings if using self-signed certificates.