rConfigsolarwinds.com ↗
rConfigPair SolarWinds NPM with rConfig.
Sync your SolarWinds inventory into rConfig. rConfig imports the nodes your self-hosted SolarWinds Platform already monitors, then backs up, diffs and checks every device's configuration.
Field tested against a self-hosted SolarWinds Platform server. Read-only: nothing is written to SolarWinds.
SolarWinds NPM monitors every node. rConfig keeps their configs.
SolarWinds Network Performance Monitor already holds the list of network devices you care about. rConfig reads that list from Orion, so there is no second inventory to maintain.
Every node SolarWinds NPM 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.
This page is for teams keeping SolarWinds NPM. Moving configuration management off SolarWinds NCM instead? See rConfig as a SolarWinds NCM alternative.
Sync, capture, prove.
Three moves take a SolarWinds NPM node list to backed up, checked and audit ready.
Sync
rConfig imports nodes from SolarWinds NPM and keeps the device list in step on a schedule. Each device gets its template, credentials and category from an Orion group.
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 SolarWinds NPM.
Four steps, from a read-only Orion account to a scheduled sync.
Authorise
Create a read-only Orion account and open the SWIS port (17774, or 17778 on older installs) from rConfig to your SolarWinds server.Map
Add Orion groups namedrconfig::device_profile::<profile>. Each one picks the rConfig Device Profile a node gets: template, credentials, vendor and category. Other groups can come across as rConfig tags.Scope
Optionally filter by vendor, machine type, custom property, Orion group or polling method. Unmanaged nodes are left out by default.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 SolarWinds NPM 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 SolarWinds NPM 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 SolarWinds NPM 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 SolarWinds NPM.
Self-hosted SolarWinds Platform only. SolarWinds Observability SaaS uses a different API and is not supported. The Orion password is stored encrypted in rConfig and never shown again after you save it.
The SolarWinds NPM 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.3 and later
- Licence
- Part of rConfig V8 Pro
- Status
- Field tested against a self-hosted SolarWinds Platform server
- SolarWinds products
- Self-hosted SolarWinds Platform (Orion), including Network Performance Monitor. SolarWinds Observability SaaS is not supported
- Transport
- SolarWinds Information Service (SWIS) REST API over HTTPS, read-only SWQL queries
- Port
- 17774, or 17778 on installs older than SolarWinds Platform 2023.1
- Authentication
- Orion username and password; a local Orion account is recommended
- Permissions
- A read-only Orion account. Account limitations decide which nodes rConfig sees
- TLS
- Certificate checks on by default; SWIS uses a self-signed certificate until you install a trusted one
- Imported fields
- NodeID, hostname (Caption, then SysName, then DNS), IP address, vendor, machine type
- Device profiles
- From Orion groups named
rconfig::device_profile::<profile> - Tags
- Other Orion groups, optionally
- Filters
- Vendor, machine type, custom property, Orion group (nested groups included), polling method. Unmanaged nodes left out by default
- Paging
- 500 nodes at a time, in NodeID order
- Preview
- Extract Preview, Sync Preview, then Full Sync
- Sync triggers
- Scheduled as an Integration V2 Job
- Review queue
- Problem Devices
- Several servers
- One integration instance per SolarWinds server, each with its own links
- Linking
- Open in SolarWinds button on each imported device
- First backup
- Initial backup straight after import
- Write-back
- None
- Security
- The Orion password is stored encrypted and never returned by the rConfig API
- Documentation
- SolarWinds NPM driver docs, Device Sync V2 overview
SolarWinds, SolarWinds NPM and Orion are trademarks of their owner, SolarWinds Worldwide, LLC. This integration is not endorsed by SolarWinds. See solarwinds.com.
SolarWinds NPM integration: common questions
What network engineers ask before they connect SolarWinds NPM to rConfig. If yours isn't here, ask it on the demo call.
How does rConfig get devices from SolarWinds NPM?
rConfig runs read-only SWQL queries against Orion.Nodes through the SolarWinds Information Service (SWIS) REST API. It imports each node's ID, hostname, IP address, vendor and machine type.
Which SolarWinds versions work?
Self-hosted SolarWinds Platform (Orion), including Network Performance Monitor, from rConfig V8.4.3. SolarWinds Observability SaaS uses a different API and is not supported.
Which port does rConfig connect to?
The SWIS port on your SolarWinds server: 17774 on SolarWinds Platform 2023.1 and later, or 17778 on older installs. It is separate from the web console port, so open it from rConfig.
What does the Orion account need?
A read-only Orion account with no admin or node management rights. A local Orion account is the most reliable choice. SWIS only returns the nodes the account's limitations allow, so give it the same view as the devices you want in rConfig.
Does it work with the default self-signed certificate?
Yes. Certificate checks are on by default. Install a trusted certificate on the SolarWinds server, or turn off Verify TLS if you accept the self-signed one.
How does rConfig know which template and credentials to use?
From an Orion group named rconfig::device_profile::<profile>. It decides which rConfig Device Profile (template, credentials, vendor and category) a node gets. Other groups can be imported as rConfig tags.
Can I import only some nodes?
Yes. Filter by vendor, machine type, custom property, Orion group (nested groups included) and polling method, for example to leave out ICMP-only nodes. Unmanaged nodes are left out by default.
Does rConfig write to SolarWinds?
No. The integration is read-only. rConfig never changes anything in SolarWinds.
What happens if a sync fails part way through?
The run stops with a message that names what to check, such as the SWIS port, the account or the certificate. rConfig changes no device links for that run.
Can I connect more than one SolarWinds server?
Yes. Add one integration instance per SolarWinds server. Each instance keeps its own links between SolarWinds nodes and rConfig devices.
Does it cope with a large SolarWinds install?
rConfig reads nodes 500 at a time in NodeID order, so it reads a large install page by page.
Do I need a separate licence?
No. Device Sync V2 is part of rConfig V8 Pro.
Is this the same as moving off SolarWinds NCM?
No. This integration keeps SolarWinds NPM in service and imports the nodes it monitors. If you are moving configuration management off SolarWinds NCM, see rConfig as a SolarWinds NCM alternative.
See the import running against your own SolarWinds NPM.
Book 30 minutes with an rConfig engineer. We'll point the integration at your Orion nodes, preview the import, and back up a handful of your devices.