rConfig - Config Restore

8 mins V8 Pro+

The Config Restore feature enables precise, granular restoration of device configurations directly from any configuration output page. Whether you need to restore a single line or an entire configuration block, this feature provides safe, auditable, and efficient configuration management.

Caution

Config Restore is a powerful feature that makes live changes to network devices. Always review generated commands carefully before execution, and consider testing in a non-production environment first.

Overview

Config Restore introduces the ability to restore partial or complete configuration blocks with context-aware command generation, device-specific profiles, and full audit tracking.

Key Capabilities

• Granular Selection: Restore specific configuration sections or entire configs
• Context-Sensitive Commands: Automatically generates device-specific configuration mode commands
• Custom Device Profiles: Define configuration, save, and exit commands per device type
• Priority Queuing: Execute urgent restores with high-priority queue support
• Full Audit Trail: All restore operations are stored in device configuration history
• ChangeForge Integration: Future-ready for approval workflow integration

Why It Matters

• Faster Remediation: Quickly restore configurations during outages or misconfigurations
• Safe Operations: Preview and edit all commands before execution
• Compliance Ready: Complete audit trail for regulatory requirements
• Flexible Workflows: Support for both emergency and planned configuration changes

Video Walkthrough

Accessing Config Restore

Location

The Config Restore button is located on any configuration output page in the button toolbar above the configuration display, positioned to the top-left alongside the copy and download buttons.

Button States

• Disabled (Default): Button is inactive when no configuration text is selected
• Active (Red Icon): Highlights with a red warning icon when configuration is selected, indicating the potentially impactful nature of the action

Tip

The red icon serves as a visual reminder that configuration restoration can affect live network devices. Always proceed with caution.

Using Config Restore

Step 1: Select Configuration

1. Navigate to any device configuration output page
2. Use your mouse to highlight the configuration section you want to restore
   • Select a single line for targeted changes
   • Select multiple lines for block restoration
   • Select all (Ctrl+A / Cmd+A) for complete configuration restore

Step 2: Open the Config Restore Generator

1. Click the now-active Config Restore button (red icon)
2. The Config Restore Generator dialog opens, displaying:
   • Your selected configuration text
   • Device type selector dropdown
   • Generated restore command preview
   • Additional options and controls

Step 3: Configure Device Type

Note

Most network devices require specific commands to enter configuration mode, save changes, and exit properly. The device type selector ensures the correct command syntax is used.

1. Select the appropriate device type from the dropdown
2. Common device types include:
   • Cisco IOS/IOS-XE (uses conf t, write mem, exit)
   • Cisco NX-OS (uses configure terminal, copy running-config startup-config)
   • Arista EOS (uses configure, write memory)
   • Juniper Junos (uses configure, commit, exit)
   • And more…

The system automatically inserts the appropriate:

• Configuration mode command (e.g., conf t)
• Your selected configuration
• Save command (e.g., write mem)
• Exit command (e.g., exit)

Step 4: Review and Edit Generated Commands

The generated restore commands appear at the bottom of the dialog. This text is fully editable, allowing you to:

• Add additional commands before or after the configuration
• Modify the configuration syntax if needed
• Remove auto-generated commands if not required
• Add custom verification commands

Example Generated Command Set:

conf t
interface GigabitEthernet0/1
 description Uplink to Core Switch
 switchport mode trunk
 switchport trunk allowed vlan 10,20,30
exit
write mem
exit

Step 5: Priority Queue (Optional)

At the bottom of the dialog, enable the High Priority checkbox if:

• The restore is time-sensitive or urgent
• The rConfig server is experiencing high load
• The configuration change addresses an active incident

High-priority restores are placed in an expedited queue for immediate processing.

Step 6: Execute Restore

1. Click Show Instructions if you need guidance (minimal instructions displayed)
2. Review all commands one final time
3. Click Execute or Restore to send commands to the device
4. Monitor progress in the Queue Manager

Managing Device Types

Viewing Device Types

Click the icon next to the device type dropdown to access device type management.

Creating Custom Device Types

1. Click Add Device Type
2. Configure the following:
   • Device Type Name: Descriptive name (e.g., “Cisco ASA Firewall”)
   • Configuration Mode Command: Command to enter config mode
   • Save Command: Command to save configuration
   • Exit Command: Command to exit config mode
3. Click Save

Example Custom Device Type:

• Name: Fortinet FortiGate
• Config Mode: config global
• Save Command: end
• Exit Command: exit

Editing Device Types

1. Select a device type from the list
2. Click the Edit icon
3. Modify commands as needed
4. Save changes

Deleting Device Types

1. Select a device type from the list
2. Click the Delete icon
3. Confirm deletion

Caution

Deleting a device type that is in use may affect existing scheduled or queued restore operations. Ensure no active operations reference the device type before deletion.

Monitoring and Verification

Queue Manager

All config restore operations appear in the Queue Manager, where you can:

• Monitor execution status
• View real-time progress
• Review completion status
• Identify any errors or failures

Configuration History

Once a restore operation completes, rConfig automatically stores:

• The exact commands sent
• The device response output
• Timestamp and user information
• Success/failure status

To view restore history:

1. Navigate to the device page
2. Open the Configuration History tab
3. Locate the restore entry by timestamp
4. Review the complete restore output for audit and analysis

Tip

Configuration history provides a complete audit trail for compliance, troubleshooting, and rollback scenarios.

Integration with ChangeForge

Note

ChangeForge integration is coming soon and will enable approval-based configuration workflows.

Future Capabilities

When ChangeForge integration is released, Config Restore will support:

• Approval Workflows: Submit restore requests for manager/peer review
• Change Windows: Schedule restores during approved maintenance windows
• Multi-Stage Approvals: Enterprise change management processes
• Automated Rollback: Revert configurations if post-change validation fails

Currently, all restore operations execute immediately upon confirmation.

Best Practices

Before Restoring

1. Verify Device State: Ensure the target device is online and accessible
2. Review Configuration: Double-check the selected configuration text
3. Check Device Type: Confirm the correct device type profile is selected
4. Edit Commands: Review and customize generated commands if needed
5. Consider Impact: Assess potential service disruption

During Restoration

1. Monitor Queue: Watch the Queue Manager for execution status
2. Stay Available: Be ready to troubleshoot if issues arise
3. Verify Connectivity: Ensure stable network connection during execution

After Restoration

1. Review Output: Check configuration history for execution results
2. Verify Configuration: Confirm changes were applied correctly
3. Test Functionality: Validate that services are operating as expected
4. Document Changes: Add notes to configuration history if needed

Troubleshooting

Common Issues

Restore button remains disabled

• Ensure you have selected configuration text
• Try selecting a different section
• Refresh the page and try again

Incorrect commands generated

• Verify the correct device type is selected
• Edit the device type profile if commands are outdated
• Manually edit the generated commands before execution

Restore fails to execute

• Check device connectivity
• Verify credentials are valid
• Review error message in Queue Manager
• Check device logs for authentication or authorization issues

High-priority queue not working

• Verify you have permissions to use priority queue
• Check Queue Manager for current queue depth
• Contact administrator if priority queue is disabled

Getting Help

If you encounter issues with Config Restore:

1. Review the configuration history for error messages
2. Check the Queue Manager for execution details
3. Verify device type profiles are correctly configured
4. Consult rConfig documentation for device-specific guidance
5. Contact rConfig support with:
   • Device type and model
   • Generated commands (sanitized)
   • Error messages from Queue Manager
   • Configuration history output

Security Considerations

Caution

Config Restore makes live changes to production network devices. Ensure proper access controls and approval processes are in place.

Access Control

• Implement role-based access control (RBAC) for Config Restore
• Restrict high-priority queue access to senior engineers
• Audit all restore operations regularly
• Consider requiring two-person integrity for critical devices

Audit Trail

Every restore operation is logged with:

• Username and timestamp
• Source configuration selection
• Generated and executed commands
• Device response output
• Success/failure status

Review audit logs regularly for compliance and security monitoring.

Frequently Asked Questions

Q: Can I restore configurations to multiple devices at once?
A: Currently, Config Restore operates on a single device per operation. Multi-device restore capabilities are planned for a future release.

Q: What happens if a restore partially fails?
A: The complete output is stored in configuration history. Review the output to determine which commands succeeded and manually complete or rollback as needed.

Q: Can I schedule restores for later?
A: Not currently. With ChangeForge integration, scheduled and approval-based restores will be supported.

Q: Are restores reversible?
A: Config Restore does not automatically create backups or rollback points. Always capture a backup before making changes, and use configuration history to manually revert if needed.

Q: Can I export restore commands without executing?
A: Yes, copy the generated commands from the dialog for documentation or execution through other tools.

Summary

Config Restore provides network engineers with a powerful, flexible tool for granular configuration management. By combining context-aware command generation, device-specific profiles, priority queuing, and comprehensive audit trails, rConfig enables safe, efficient restoration workflows that support both emergency response and planned maintenance scenarios.

For more information on related features, see:

• Configuration Management
• Queue Manager
• Device Management
• Audit and Compliance (coming soon with ChangeForge)