16+ years developed and run in production

Multi-vendor network configuration management

Back up, compare and manage configurations across Cisco, Juniper, Arista, Fortinet, Palo Alto and other supported network devices. Start with 200+ ready device profiles, or define connection settings and collection commands for legacy and custom equipment.

If a device exposes configuration through a supported connection method, rConfig can be configured to collect it. We can help validate the profile and commands for your device.

Check my device coverage

Bring your device list. We will check it with you.

200+ ready profiles
Six collection methods
Built for enterprise, ISP and OT networks

TRUSTED WORLDWIDE

VENDOR COVERAGE

Device profiles for multi-vendor networks

Start with ready profiles for the vendors you already use. Whether a device is covered depends on its model, operating system, access method and the commands needed to collect its configuration.

Cisco
Juniper
Arista
Fortinet
Palo Alto
Huawei
Nokia
MikroTik
HPE
Aruba
Extreme
Ruckus

If a device is not listed, define a custom profile or use a script. You do not need to wait for a new rConfig release, although unusual devices may need engineering help to validate.

Ready profiles cover common platforms. Legacy and custom equipment needs a custom profile, which we can help you validate.

HOW IT WORKS

How multi-vendor configuration collection works

A device profile defines how rConfig connects to a device and which commands collect its configuration. Support depends on the device offering one of these collection methods, so the vendor name alone does not set the limit.

Configure device access
Choose how the configuration is collected: SSH, Telnet, REST API, TL1 (a command language used over an underlying connection) or a custom script. With xFTP, the device sends its configuration to rConfig.
Collect device configurations
The device profile defines the connection settings and the commands to run. rConfig runs them on a schedule to collect the configuration.
Review configuration history
Compare stored versions to see what changed on each device. Restore workflows depend on the device, profile and edition.

Optical transport too. rConfig speaks TL1 natively, so Ciena 6500, Cisco ONS 15454 and Infinera DTN-X shelves sit in the same inventory as your routers, on the same schedules, with the same diffs. See TL1 configuration management.

Collected configurations are stored with version history so engineers can compare revisions and investigate changes across vendors. Supported editions also provide compliance checks and automation workflows, helping teams apply consistent operating standards across different device families.

CUSTOMER EVIDENCE

Configuration management for enterprise, ISP and OT networks

Danish Road Authority
Roadside cameras, sensors and signs.
OTIoT
SABIC
SCADA and industrial equipment.
SCADAIndustrial
Logix
Core network and FttX devices.
ISPFttX

~200,000 devices one Tier 1 ISP estate on rConfig, read the telecom case study

Device figures approximate, published with customer permission.

FAQ

Multi-vendor network configuration management FAQs

Does rConfig support my vendor?

Support depends on the device model, operating system, access method and the commands needed to collect its configuration, not on the vendor name alone. rConfig includes 200+ ready device profiles, and a custom profile can cover platforms or OS versions they do not.

What if my device is not listed?

You can create a custom profile that defines the connection settings and the commands used to collect the configuration, or use a script for devices that need one. You do not need to wait for a new rConfig release. Unusual devices may need engineering assistance to validate prompts, commands and output, and we can help with that.

Can rConfig manage old or unusual equipment?

Yes, where the configuration can be reached through a supported collection method: SSH, Telnet, REST API, TL1, xFTP or a custom script. Many legacy systems fit, but each device still needs to be validated, and OT and IoT equipment is assessed device by device rather than assumed. Restoring a configuration depends on the device and its profile.

Can you test our devices first?

Yes. Send us the vendor, model, OS version, access method and the commands that show or export the configuration, and we will check them with you. Do not include passwords or other credentials in the form.

Can I compare configuration changes across different vendors?

rConfig stores versions of each device's configuration and shows the differences between those versions for that device. Configurations from different vendors are not translated into equivalent syntax, so a comparison is between versions of the same device, not between a Cisco and a Juniper configuration.

Not sure if your devices will work?

Send us your list. We will show you what is ready and what needs a custom profile.