Restoring Network Configs Just Got Smarter in rConfig V8

If you’ve ever been knee-deep in troubleshooting and wished you could quickly roll back just a section of a config — not the entire device — you’ll love what’s new in rConfig V8.0.2.

Meet Config Restore, a feature designed to take the pain (and risk) out of restoring configs.

Why this feature, and why now?

Over the years, one request kept popping up from our community and customers:
"I don’t want to roll back the whole config. I just need to fix the broken bit — fast."

That’s why Config Restore made it into our top-requested feature list for V8. Admins told us repeatedly that all-or-nothing restores wasted time, created unnecessary risk, and added stress in outage scenarios. With V8, we delivered exactly what was needed: a safe, device-aware way to restore only what matters.

The problem

Traditionally, restoring a configuration has been an all-or-nothing process. That’s fine if your device is completely misconfigured. But in reality, most fixes come down to small tweaks:

• A network device down situation where only one faulty module or service needs reactivation.

• A card or interface down requiring you to restore a specific interface configuration, not the entire router or switch.

• An ACL restore where one mistaken rule is blocking business-critical traffic.

Manually crafting restore snippets for those changes can be error-prone, slow, and stressful — especially during an outage.

The solution

With Config Restore, you can now select any portion of a configuration — or the entire config if needed — and restore it directly.

• The restore button sits on every config output page, right next to copy/download.

• Once you highlight a section, the restore button activates (with a red warning icon to remind you this is a serious action).

• Clicking it launches the Config Restore Generator, which automatically wraps your selected config in the right device-specific commands.

For example, it can insert:

• Entering configuration mode (conf t)

• Saving (write mem)

• Exiting (end)

rConfig comes with built-in profiles for different device types, but you can also create, edit, or delete your own — so the restore process always matches your exact environment.

Why it matters

• Granularity: Fix only what’s broken, whether that’s an ACL rule or a single interface.

• Consistency: Generate device-aware restore commands every time.

• Control: Manually edit commands before sending.

• Urgency: Mark a restore as high priority to jump the queue when seconds count.

• Auditability: Every restore is logged as part of the device’s configuration history.

And this is just the beginning. Config Restore will soon tie directly into ChangeForge, rConfig’s approval workflow engine. That means future restores can be routed through a review process before hitting production devices — giving you governance and compliance baked into every action.

What’s next

And this is just the beginning. Config Restore will soon tie directly into ChangeForge, rConfig’s approval workflow engine. That means future restores can be routed through a review process before hitting production devices — giving you governance and compliance baked into every action.

See it in action

We’ve created a simple interactive demo video to walk you through this feature. Check it out below.

Closing

Whether you’re fixing a misconfigured ACL, rolling back a failed interface change, or simply testing device behavior during a network device outage, Config Restore makes the process safer, faster, and smarter.

Upgrade to rConfig V8.0.2 today and put Config Restore to work for your network.