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 switching-related data such as VLANs, links, and switching information. The "List NAC" operation under the "Switching" resource retrieves a list of Network Access Control (NAC) entries, optionally filtered by a MAC address. This is useful for network administrators who want to monitor or audit devices connected to the network at the switching layer.
Practical examples include:
- Listing all NAC entries to see which devices are currently authenticated on the network.
- Filtering NAC entries by a specific MAC address to check the status or details of a particular device.
Properties
| Name | Meaning |
|---|---|
| MAC Address | Optional filter to specify a MAC address (e.g., "00:11:22:33:44:55") to narrow the NAC list results to that device. |
Output
The node outputs JSON data representing the list of NAC entries retrieved from LibreNMS. Each entry typically contains details about the network device authenticated via NAC, such as MAC address, port, VLAN, authentication status, and possibly timestamps or other metadata related to the NAC session.
If binary data were involved (not indicated here), it would represent raw files or attachments, but this operation focuses on structured JSON data.
Dependencies
- Requires an API key credential for authenticating with the LibreNMS API.
- The node expects the LibreNMS instance URL and API token configured in the credentials.
- The LibreNMS API must be accessible from the n8n environment where this node runs.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect LibreNMS URL or network connectivity issues can prevent API calls.
- Providing an invalid MAC address format may result in no data returned or errors.
- Error messages:
- Authentication errors usually indicate problems with the API key or permissions.
- HTTP errors like 404 or 500 suggest endpoint issues or server-side problems.
- Resolutions:
- Verify API credentials and permissions in LibreNMS.
- Confirm the LibreNMS base URL is correct and reachable.
- Ensure the MAC address filter, if used, follows the standard MAC address format.