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 to retrieve ARP (Address Resolution Protocol) table entries for a specified network device. This operation is useful for network administrators who want to query the ARP cache of devices to see IP-to-MAC address mappings, which helps in troubleshooting network connectivity and verifying device presence on the network.
A practical example use case is when an administrator wants to get the current ARP table from a specific device identified by its hostname or device ID to check which IP addresses are associated with which MAC addresses on that device.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the network device whose ARP table entries you want to retrieve. |
Output
The node outputs JSON data representing the ARP table entries retrieved from the specified device. Each entry typically includes details such as IP address, MAC address, interface, and possibly other metadata related to the ARP record.
If the node supports binary data output (not indicated explicitly here), it would generally represent raw data or files related to the ARP information, but this node primarily outputs structured JSON data.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the credentials.
- Optionally, SSL certificate validation can be skipped based on credential settings.
Troubleshooting
Common issues:
- Incorrect device hostname or ID may result in no data or errors.
- Network connectivity problems between n8n and LibreNMS server.
- Invalid or missing API authentication token causing authorization failures.
- SSL certificate errors if the LibreNMS server uses self-signed certificates and validation is not disabled.
Error messages:
- Authorization errors indicate invalid or missing API credentials; verify and update credentials.
- "Device not found" or empty results suggest the device identifier is incorrect or the device has no ARP entries.
- Network timeout or connection refused errors require checking network access and LibreNMS server status.