Universal Network Device & Vendor Support

Universal Network Device Support - All Vendors, Protocols & Equipment Types

rConfig V8 Pro supports any device you can connect to and send commands to, across SSH, Telnet, REST API, TL1, xFTP, and custom scripts. There are no vendor certification lists. If you can connect to it, rConfig can back it up.

How broad is the device support?

Rather than certifying individual vendors, rConfig treats configuration management as a protocol and command problem. This means you can add support for a new device type in minutes by defining the connection method, authentication sequence, commands to run, and prompt patterns to match. Organizations worldwide use this to back up traditional network equipment alongside OT/SCADA systems, industrial controllers, building automation, and other infrastructure that conventional NCM platforms cannot reach.

The Architecture That Changes Everything

1. Template-Driven Command System

rConfig doesn’t hardcode vendor support. Instead, it uses a flexible command template system where you define:

Connection protocol (SSH, Telnet, API, TL1, xFTP, Script)
Authentication sequence (username/password, enable mode, privilege escalation)
Commands to execute (any valid commands the device accepts)
Prompt patterns (how to detect when the device is ready for input)
Output handling (pagination, ANSI codes, line endings)

What this means: If you can connect to it and type commands, rConfig can back it up. No vendor certification required. No waiting for the next software release to support a new device model.

2. Six Connection Methods

Most NCM platforms support SSH and maybe Telnet. rConfig provides six backup methods, each designed for different device categories and constraints:

SSH (Secure Shell)

The Standard: Encrypted, authenticated, works with 90% of modern network devices.

Cisco, Juniper, Aruba, HP, Dell, Extreme, Fortinet, Palo Alto
Linux servers, BSD systems, Unix appliances
Modern industrial controllers with SSH support
Cloud network services (AWS VPC, Azure networking)

Key capability: Full terminal emulation with privilege escalation support.

Telnet

The Legacy Protocol: Unencrypted but universally supported on older equipment.

Legacy Cisco IOS devices
Older HP ProCurve switches
Industrial equipment from the 1990s-2000s
Building automation controllers
Serial console servers and terminal servers

Why it matters: Equipment that predates SSH still needs backing up. Telnet support means you can manage infrastructure that competitors abandon.

REST API

The Modern Interface: Structured data exchange for API-enabled devices.

SD-WAN controllers (Meraki, Viptela, VeloCloud)
Cloud management platforms
Next-gen firewalls with REST APIs
Wireless controllers (Aruba Central, Cisco DNA Center)
Load balancers (F5, Citrix ADC)

Advantage: Native API backup for devices that expose configuration via REST endpoints.

TL1 (Transaction Language 1)

The Carrier Protocol: Management language for optical networking and carrier-grade transport equipment.

Ciena optical switches and transport systems (6500, 5170, etc.)
Nokia/ALU optical line systems
Carrier DWDM and ROADM equipment
Optical transport network (OTN) devices

Key capability: In-band TL1-over-SSH sessions with ACT-USER authentication sequences for carrier optical infrastructure that uses TL1 rather than standard CLI.

Custom Scripts (BYOC - Bring Your Own Connection)

The Universal Adapter: Execute custom scripts to retrieve configurations from anything.

Devices with proprietary management interfaces
Systems requiring multi-step authentication
Equipment with non-standard output formats
Integration with vendor-specific management tools
Anything you can script in Python, Bash, or PowerShell

Custom scripts: If none of the built-in methods work, write a script. rConfig executes it and stores the output.

xFTP (TFTP/FTP/SFTP/SCP)

The Push Model: Devices push configurations to rConfig rather than rConfig connecting to them.

Cisco devices configured to copy running-config tftp://rconfig
Network devices behind NAT or firewalls (can’t be reached directly)
Equipment that lacks an interactive shell
Legacy systems with only file transfer capabilities

Use case: Devices in remote sites with intermittent connectivity can push configs when links are up.

Combined capability: One platform, six backup methods covering virtually any device type.

Beyond the Network: Real-World Versatility

Case Study: European Highway Infrastructure

Challenge: A central European transportation authority manages thousands of roadside devices across a highway network:

Variable message signs (VMS) displaying traffic alerts
Speed detection systems
Traffic monitoring cameras
Weather sensors
Emergency call boxes

These devices run a mix of Windows Embedded, Linux, and proprietary embedded systems. Traditional NCM platforms couldn’t connect to them.

Solution: rConfig’s template system backed up all of them:

SSH for Linux-based cameras and sensors
Telnet for older VMS systems
API calls for newer intelligent signage
Custom scripts for Windows Embedded devices

Result: Complete configuration backup coverage across the entire highway infrastructure. When a speed detector fails, they restore the exact configuration from rConfig. When they update VMS firmware, they verify config drift. All managed from a single platform.

Case Study: Middle East Petrochemical Manufacturing

Challenge: A large petrochemical facility needed to back up SCADA systems and PLCs (Programmable Logic Controllers) controlling refinery operations. They’d been using a 30-year-old Unix server with custom scripts that nobody understood anymore. When that server died, they’d lose decades of configuration history.

Discovery: rConfig’s snippet feature—designed for sending configuration commands to network devices—worked perfectly for retrieving PLC programs and SCADA configurations.

Solution: They connected rConfig to Siemens PLCs, Schneider Electric SCADA systems, and Rockwell Automation controllers using:

Custom scripts for proprietary protocols
SSH for Linux-based SCADA servers
API connections for modern controllers

Result: They decommissioned the Unix server, migrated 30 years of configuration history to rConfig, and now have automated backups with full change tracking, compliance reporting, and diff comparison. The refinery control systems are backed up alongside the facility network infrastructure—one platform, complete visibility.

Case Study: Healthcare Building Automation

A hospital network uses rConfig to back up:

BACnet building controllers (HVAC, lighting)
Access control systems
Nurse call systems
Cisco and Aruba network switches
VoIP PBX configurations

Why: When critical infrastructure fails at 2 AM, they need to restore configurations fast. Having everything in rConfig means one platform, one restore process, one audit trail.

Proven Network Vendor Support

While rConfig works beyond traditional networking, it’s built on a rock-solid foundation of proven network device support. Organizations worldwide trust rConfig for:

Enterprise Networking

Cisco: IOS, IOS-XE, NX-OS, IOS-XR, ASA, WLC, Catalyst, Nexus
Juniper: JunOS, EX switches, SRX firewalls, MX routers
Aruba/HP: ProCurve, ArubaOS, CX switches, wireless controllers
Extreme: ExtremeXOS, EXOS, VSP
Dell: PowerConnect, OS6, OS9, OS10

Security Appliances

Palo Alto Networks: PAN-OS firewalls
Fortinet: FortiGate, FortiOS
Check Point: Gaia, SecurePlatform
Cisco ASA: Firewall, VPN concentrators
pfSense/OPNsense: Open-source firewalls

Wireless & SD-WAN

Cisco Meraki: Cloud-managed via API
Aruba Central: Cloud controllers
Ruckus: Wireless controllers
Ubiquiti: UniFi controllers
SD-WAN: Viptela, VeloCloud, Silver Peak

Load Balancers & ADC

F5 Networks: BIG-IP (all modules)
Citrix: NetScaler/ADC
A10 Networks: Thunder series
Kemp: LoadMaster

Data Center & Storage

Brocade/Broadcom: Fibre Channel switches
Cisco: MDS, UCS
NetApp: ONTAP controllers
Dell EMC: Storage arrays with SSH/API

Carrier & Service Provider

Nokia/ALU: Service routers
Ericsson: Network nodes
Huawei: Enterprise and carrier equipment
ZTE: Carrier infrastructure

The list goes on: Sophos, SonicWall, WatchGuard, Mikrotik, EdgeRouter, VyOS, Cumulus Linux, Arista, Mellanox, and hundreds more.

Why the architecture matters

1. No waiting for vendor updates

With hardcoded vendor support, adding a new device type means waiting for a software release. With rConfig’s template system, you define the connection details yourself and have working backups the same day.

2. Manage heterogeneous environments

Real networks aren’t monoculture. You have:

Cisco core, HP access layer
Palo Alto firewalls, F5 load balancers
Aruba wireless, Cisco phones
Linux servers, Windows boxes
Legacy equipment that “just works” and can’t be replaced

rConfig manages all of it from one platform.

3. Extend beyond IT

Network team backs up switches, OT team has custom scripts for SCADA, facilities team has no backup for building controllers. With rConfig, one platform covers IT, OT, and IoT with unified backup, change tracking, and compliance.

4. Future-proof your tooling

Your templates describe the connection and commands for each device type. If a vendor changes their product line or a new vendor emerges, you update the template, not the platform.

Full Suite Capabilities for Every Device

Every device backed up by rConfig gets the full platform capabilities, regardless of connection method:

Configuration Management

Automated backups on schedules or on-demand
Version control with unlimited history
Change tracking with before/after comparison
Rollback capability for failed changes

Compliance & Policy

Policy-based compliance using regex pattern matching
Automated compliance reports for audits
Configuration standards enforcement
Deviation detection from approved baselines

Change Automation

Snippet deployment to send configuration changes
Bulk operations across device groups
Task scheduling for change windows
Change validation with diff preview

Reporting & Analytics

Inventory reports with device properties
Compliance dashboards showing drift
Change history for troubleshooting
Audit trails for security and compliance

Integration

REST API for external system integration
Webhook notifications for change events
CSV export for offline analysis
Device sync from Netbox/Nautobot/Zabbix

The highway infrastructure gets compliance reporting. The SCADA systems get change tracking. The building controllers get version control. The connection method is an implementation detail; the platform capabilities are the same.

The Template System in Action

Creating support for a new device type takes minutes:

Example: Industrial PLC

Create Device Type: “Siemens S7-1500”
Set Connection Method: SSH
Define Commands:
- show config
- show hardware
- export program
Configure Prompts:
- Login prompt: login:
- Password prompt: Password:
- Ready prompt: S7>
Test: Run manual backup
Deploy: Assign to devices

Time investment: 15 minutes
Result: Full backup, change tracking, and compliance for an industrial controller that “network management platforms” can’t touch.

Use Cases Beyond Traditional Networking

Manufacturing & Industrial

SCADA systems (Siemens, Schneider, Rockwell)
PLCs and industrial controllers
Manufacturing execution systems (MES)
CNC machine controllers
Robotic system configurations

Building & Facilities

BACnet building controllers
HVAC management systems
Lighting control systems
Access control platforms
Fire alarm panels

Transportation & Infrastructure

Traffic management systems
Variable message signs
Toll collection systems
Railway signaling equipment
Airport systems

Telecommunications

VoIP PBX systems
Call managers
Session border controllers
Carrier switches
Media gateways

Energy & Utilities

Substation automation
Smart grid controllers
Renewable energy inverters
Power monitoring systems
Energy management platforms

Healthcare & Life Safety

Nurse call systems
Patient monitoring networks
Medical imaging systems
Laboratory equipment networks
Emergency notification systems

Vendor Comparison: Why rConfig is Different

Capability	rConfig V8 Pro	Traditional NCM Platforms
Vendor Certification Required	No	Yes
New Vendor Support	Minutes (create template)	Months (wait for vendor)
Custom/Proprietary Devices	Yes (templates + scripts)	No
OT/SCADA Support	Yes	No
IoT/Building Automation	Yes	No
API-Based Backup	Yes	Limited
xFTP Push Method	Yes	Rarely
Custom Script Integration	Yes	No
Connection Methods	6 (SSH, Telnet, API, TL1, Scripts, xFTP)	1-2 (SSH, maybe Telnet)

Getting started with non-traditional devices

Identify the connection method (SSH, Telnet, API, TL1, xFTP, or custom script)
Create a device type template with the appropriate commands, prompts, and authentication sequence
Test on a single device to validate connectivity and output
Deploy to a device group once validated
Enable platform capabilities (compliance, change tracking, reporting) as needed

What’s next

Device Connectivity Process - How rConfig establishes connections to devices
Device Import Workbook - Getting devices into the system in bulk
Script Integration Engine - Using custom scripts as a connection method
Connection Templates - Defining command templates for new device types