rConfiglibrenms.org ↗
rConfigPair LibreNMS with rConfig.
rConfig reads your LibreNMS device list over the API and backs up, diffs and checks every device's configuration.
Lab tested against LibreNMS 26.10.2. Read-only: nothing is written back to LibreNMS.
LibreNMS knows every device. rConfig keeps their configs.
LibreNMS knows every device and graphs every port. It doesn’t keep a versioned, searchable history of their configs with compliance checks.
That is where LibreNMS config backup usually starts: a separate tool beside it. Many teams run Oxidized for that. rConfig is another option, and it reads the device list LibreNMS already holds, so there is no second inventory to maintain. Every configuration lands in a versioned archive from the first sync.
Sync, capture, prove.
Three moves take a LibreNMS inventory to backed up, checked and audit ready.
Sync
rConfig reads the device list from LibreNMS and keeps it in step on a schedule. Each device gets its template, credentials and category from a LibreNMS device group.
Capture
Scheduled backups of every synced device, stored and diffable. Every change is kept as a version you can compare and restore.
Prove
Compliance policies run against every synced device. Audit evidence exports from the same place.
How rConfig syncs with LibreNMS.
Four steps, from a read-only user to a scheduled sync.
Authorise
Create a read-only LibreNMS user with the global-read role and an API token.Map
Create LibreNMS device groups namedrconfig::device_profile::<profile>. A dynamic group such asos = iosxemaps every IOS-XE device to one rConfig profile automatically, including devices added later.Scope
Optionally filter by device group, OS, device type or location. Disabled devices are skipped by default.Sync
Preview, run, then schedule. From the CLI, runphp artisan rconfig:integration-v2-run --driver=librenms.
Built for LibreNMS users.
The jobs the NOC, the security team and the auditor each need from network configuration management.
Multi vendor configuration backup
Cisco, Juniper, Arista, Fortinet, Palo Alto, Huawei, Nokia, MikroTik, HPE, Aruba and 200 more. Hourly, daily or on demand.
Change detection with a readable diff
See exactly what changed, line by line, since the last known good version. Filter out noise like timestamps and session identifiers.
NIS2, DORA and CIS compliance reporting
Write policies once, run them against every LibreNMS device. Export evidence your auditor can actually read.
One click configuration restore
Push a known good configuration back to any device, with approvals and a full audit trail.
Bulk configuration deployment
Apply the same template across every LibreNMS device that matches a filter, in a single job with preview and rollback.
Full audit trail, exportable on demand
Who changed what, when, from where. Export the report your auditor asks for.
Deploys alongside LibreNMS.
rConfig talks to LibreNMS over its API and nothing else. SNMP community strings and v3 passwords that LibreNMS returns are discarded and never stored by rConfig.
rConfig and Oxidized, next to LibreNMS.
LibreNMS’s own documentation points to Oxidized for config backup. Oxidized is free, and it is a good fit if all you need is a plain backup of each device’s config.
rConfig is the option to look at when you want more around that backup. It syncs the device list from LibreNMS, so templates, credentials and categories follow your device groups. It runs scheduled compliance checks, shows diffs and restores in a UI, and adds RBAC and an audit trail.
You can run rConfig beside Oxidized while you compare the two on your own devices.
The LibreNMS integration, at a glance.
Everything your architecture review will ask about. Share this section with your security team before the demo.
- rConfig version
- V8.4.2 and later
- Status
- Lab tested against LibreNMS 26.10.2; customer field testing required
- LibreNMS versions
- Current releases with the v0 API. Built and tested on 26.10
- Authentication
- API token (X-Auth-Token) for a global-read user
- Transport
- HTTPS REST, read-only
- Device profiles
- From LibreNMS device groups named
rconfig::device_profile::<slug>(static or dynamic) - Filters
- Device group, OS, device type, location
- Disabled devices
- Skipped by default; optional
- Sync triggers
- Manual, scheduled task, or CLI
- CLI
php artisan rconfig:integration-v2-run --driver=librenms- Write-back
- None
- Security
- SNMP community strings and v3 passwords that LibreNMS returns are discarded, never stored
- Documentation
- LibreNMS driver docs, Device Sync V2 overview
LibreNMS config backup: common questions
What network engineers ask before they connect LibreNMS to rConfig. If yours isn't here, ask it on the demo call.
Does LibreNMS back up device configurations?
Not by itself. LibreNMS can show configs from Oxidized or RANCID if you run one of those beside it. rConfig is the backup, diff and compliance system.
Is rConfig an Oxidized alternative for LibreNMS?
It can be. Oxidized is free and works well for plain config backup. rConfig also syncs the device list from LibreNMS, runs scheduled compliance checks, shows diffs and restores in a UI, and adds RBAC and an audit trail.
Which LibreNMS versions work?
Current releases with API v0. The driver was tested on LibreNMS 26.10.2.
What permissions does the token need?
Read-only. Use a user with the global-read role so rConfig sees every device. LibreNMS silently returns fewer devices to users with less access.
Can I sync only some devices?
Yes, by device group, OS, device type or location.
How does rConfig know which template and credentials to use?
From LibreNMS device groups named after an rConfig Device Profile. Dynamic groups make this automatic.
Does rConfig write back to LibreNMS?
No. The token can be read-only.
What happens when a device is removed from LibreNMS?
By default rConfig unlinks it and keeps the device and its backup history.
Do I need a separate licence?
No. Device Sync V2 is part of rConfig V8 Pro.
See the sync running against your own LibreNMS.
Book 30 minutes with an rConfig engineer. We'll point the integration at your LibreNMS device list, back up a handful of your devices, and run a compliance check against a policy that matters to your team.