rConfigopennms.com ↗
rConfigPair OpenNMS with rConfig.
rConfig imports the nodes OpenNMS Horizon and Meridian monitor, then backs up, diffs and checks every device's configuration.
Lab tested against OpenNMS Horizon 35.0.5 and awaiting customer field testing. Read-only: nothing is written to OpenNMS.
OpenNMS monitors every node. rConfig keeps their configs.
OpenNMS already holds the list of network devices you care about. rConfig reads that list, so there is no second inventory to maintain.
Every device OpenNMS monitors also gets its configuration backed up, and the device list stays in step on a schedule. Every configuration lands in a versioned archive from the first import.
Sync, capture, prove.
Three moves take an OpenNMS node list to backed up, checked and audit ready.
Sync
rConfig imports nodes from OpenNMS and keeps the device list in step on a schedule. Each device gets its template, credentials and category from an OpenNMS surveillance category.
Capture
New devices get an initial configuration backup straight after import. Every change after that is kept as a version you can compare and restore.
Prove
Compliance policies run against every imported device. Audit evidence exports from the same place.
How rConfig syncs with OpenNMS.
Four steps, from a plain OpenNMS user to a scheduled sync.
Authorise
Use an OpenNMS user with no extra roles. rConfig only reads.Map
Add OpenNMS surveillance categories namedrconfig::device_profile::<profile>. Each one picks the rConfig Device Profile a node gets: template, credentials, vendor and category. Other categories can come across as rConfig tags.Scope
Optionally filter by surveillance category, requisition and monitoring location. OpenNMS applies the filters, so only matching nodes are transferred.Sync
Run Extract Preview, then Sync Preview, then Full Sync. Schedule it as an Integration V2 Job. Devices that need a decision go to Problem Devices.
Built for OpenNMS 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 OpenNMS 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 OpenNMS 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 OpenNMS.
Device credentials stored in OpenNMS asset records, such as a login, an enable password or an SNMP community, are never copied into rConfig. rConfig uses the credentials from its own Device Profiles.
The OpenNMS 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
- Licence
- Part of rConfig V8 Pro
- Status
- Lab tested against OpenNMS Horizon 35.0.5; awaiting customer field testing
- OpenNMS products
- Horizon and Meridian
- Transport
- OpenNMS REST API, read-only
- Permissions
- A plain OpenNMS user with no extra roles
- Imported fields
- Hostname (node label), management IP address, serial number, model, vendor
- Vendor source
- Asset record, or the SNMP sysObjectID when the asset record is empty
- Management IP
- SNMP primary interface, falling back to another managed interface
- Device profiles
- From surveillance categories named
rconfig::device_profile::<profile> - Tags
- Other surveillance categories, optionally
- Filters
- Surveillance category, requisition, monitoring location. OR within a field, AND across fields, applied by OpenNMS
- Paging
- 500 nodes at a time
- Preview
- Extract Preview, Sync Preview, then Full Sync
- Sync triggers
- Scheduled as an Integration V2 Job
- Review queue
- Problem Devices
- Linking
- Open in OpenNMS button on each imported device
- First backup
- Initial backup straight after import
- Write-back
- None
- Security
- Credentials in OpenNMS asset records (login, enable password, SNMP community) are never copied into rConfig
- Documentation
- OpenNMS driver docs, Device Sync V2 overview
OpenNMS, Horizon and Meridian are trademarks of their owner, The OpenNMS Group. This integration is not endorsed by The OpenNMS Group. See opennms.com.
OpenNMS config backup: common questions
What network engineers ask before they connect OpenNMS to rConfig. If yours isn't here, ask it on the demo call.
How does rConfig get devices from OpenNMS?
rConfig reads nodes from the OpenNMS REST API. It imports each node's hostname (the node label), management IP address, serial number, model and vendor.
Which OpenNMS versions work?
OpenNMS Horizon and Meridian, through the REST API, from rConfig V8.4.2. The driver was lab tested against OpenNMS Horizon 35.0.5 and is awaiting customer field testing.
What permissions does the OpenNMS user need?
A plain OpenNMS user with no extra roles is enough. rConfig only reads.
Which IP address does rConfig use?
The node's SNMP primary interface. If the node has none, rConfig falls back to another managed interface.
Where does the vendor come from?
From the node's asset record. When that is empty, rConfig uses the device's SNMP sysObjectID.
How does rConfig know which template and credentials to use?
From a surveillance category named rconfig::device_profile::<profile>. It decides which rConfig Device Profile (template, credentials, vendor and category) a node gets. Other categories can be imported as rConfig tags.
Can I import only some nodes?
Yes. Filter by surveillance category, requisition and monitoring location. Values within one field are combined with OR, and different fields with AND. OpenNMS applies the filters itself, so only matching nodes are transferred.
Does rConfig copy device credentials from OpenNMS?
No. A login, enable password or SNMP community stored in an OpenNMS asset record is never copied into rConfig. rConfig uses the credentials from its own Device Profiles.
Does rConfig write to OpenNMS?
No. The integration is read-only. rConfig never changes anything in OpenNMS.
Can I preview an import before it runs?
Yes. Run Extract Preview, then Sync Preview, then Full Sync. Devices that need a decision go to Problem Devices for review.
Does it cope with a large OpenNMS install?
rConfig requests nodes 500 at a time, so it reads a large OpenNMS install page by page.
Do I need a separate licence?
No. Device Sync V2 is part of rConfig V8 Pro.
See the import running against your own OpenNMS.
Book 30 minutes with an rConfig engineer. We'll point the integration at your OpenNMS nodes, preview the import, and back up a handful of your devices.