Command Groups

Network Device Command Groups Management in rConfig V8

Note

Please note that the term ‘Categories’ has been updated to ‘Command Groups’ to better reflect their functionality from Version 7.2.0 onwards. It will take some time to fully transition to the new terminology. Until then, ‘Command Group’ will be the primary term, but you may continue to see references to ‘Categories’ in URLs, permission tables, etc.

Understanding Command Groups

Command Groups represent a foundational organizational construct in rConfig V8, serving as the primary mechanism for associating devices with their configuration retrieval commands. This design pattern enables administrators to efficiently manage large-scale network environments by grouping devices with similar operational characteristics and command requirements.

The Core Principle: Every device in rConfig must be assigned to exactly one Command Group. This one-to-many relationship between Command Groups and devices ensures configuration consistency while providing the flexibility to execute vendor-specific or role-specific commands across device populations.

Command Groups fulfill three critical functions within the rConfig ecosystem:

1. Device Organization for Scheduled Tasks - Enables bulk configuration retrieval operations across device populations
2. Compliance Policy Application - Groups devices for unified policy enforcement and audit operations
3. Command Set Association - Defines the specific CLI commands executed during configuration downloads

The third function represents the most critical aspect of Command Group design. The commands attached to a Command Group directly determine what configuration data is retrieved from member devices during both scheduled and manual operations.

Caution

Command Groups without attached commands will generate errors and cannot be assigned to devices or scheduled tasks. The system enforces this requirement to prevent incomplete configuration operations.

Command Group Architecture

Understanding the relationship between Command Groups, devices, and commands is essential for effective rConfig deployment:

Command Execution Flow: When rConfig initiates a configuration download (whether manual or scheduled), the system performs the following sequence:

1. Identifies the target device’s assigned Command Group
2. Retrieves all commands associated with that Command Group
3. Establishes connection to the device using stored credentials
4. Executes each command sequentially
5. Captures and stores command output as configuration data

Design Considerations:

The Command Group architecture requires administrators to think strategically about device classification. Organizations typically design Command Groups around one or more of these factors:

• Vendor Platform (Cisco IOS, Arista EOS, Juniper JunOS)
• Device Role (Core, Distribution, Access Layer)
• Geographic Location (Data Center, Branch Office, Remote Sites)
• Management Domain (Production, Development, DMZ)
• Command Requirements (Full config vs. operational state data)

Key Architectural Rules:

• One device can belong to only one Command Group
• One Command Group can contain multiple devices
• Command Groups must have at least one attached command before device assignment
• Manual device downloads execute commands based on the device’s Command Group assignment
• Scheduled tasks target all devices within specified Command Groups

Planning Your Command Group Strategy

Before creating Command Groups, develop a classification strategy that aligns with your network architecture and operational requirements. Consider the following approach:

Step 1: Inventory Your Command Requirements

Different device types and vendors require different command sets. Document what commands you need for each device category:

Cisco IOS Routers:
  - show running-config
  - show startup-config
  - show ip route
  - show ip bgp neighbors
  - show inventory

Cisco Nexus Switches:
  - show running-config
  - show vpc
  - show vpc consistency-parameters global
  - show port-channel summary

Step 2: Identify Device Groupings

Analyze your network topology and determine logical device groupings. Ask these questions:

• Which devices run identical or similar command sets?
• Do devices share common management requirements?
• Are there geographic or functional boundaries that affect command needs?
• Do security or compliance requirements mandate different command sets?

Step 3: Balance Granularity vs. Manageability

More Command Groups provide fine-grained control but increase administrative overhead. Fewer Command Groups simplify management but may result in executing unnecessary commands on some devices.

Recommended Approach: Start with broader categories and subdivide only when command requirements genuinely differ. For example, create separate Command Groups for “Cisco_Routers_BGP” and “Cisco_Routers_OSPF” only if the routing protocol necessitates different command sets.

Example Command Group Design Patterns

Pattern 1: Vendor-Based Organization

This approach groups devices primarily by vendor and platform, ideal for multi-vendor environments:

Command Group	Member Devices	Attached Commands
Cisco_IOS_Routers	Router1 Router2 Router3	show running-config show ip route show ip bgp neighbors show ip protocols
Cisco_NX_Switches	Nexus_Core_1 Nexus_Core_2	show running-config show vpc show interface status show cdp neighbors detail
Arista_Switches	Arista_Leaf_1 Arista_Leaf_2	show running-config show ip route show lldp neighbors show interfaces status
Juniper_Firewalls	SRX_FW_1 SRX_FW_2	show configuration show security policies show security zones

When to Use: Multi-vendor environments where command syntax varies significantly between platforms. This pattern ensures vendor-specific commands are only executed against compatible devices.

Pattern 2: Role-Based Organization

This approach groups devices by network function, suitable for single-vendor environments:

Command Group	Member Devices	Attached Commands
Core_Routers	BR_Core_1 US_Core_1 IRE_Core_1	show running-config show ip route show ip bgp show ip bgp summary
Distribution	Dist_Switch_1 Dist_Switch_2	show running-config show spanning-tree show etherchannel summary
Access_Switches	Access_SW_1 Access_SW_2	show running-config show version show mac address-table
Edge_Devices	Edge_1 Edge_2 Edge_3	show running-config show ip route show interface status

When to Use: Homogeneous environments where device role determines command requirements more than vendor platform.

Pattern 3: Hybrid Organization

Combines vendor and role considerations for complex environments:

Command Group	Member Devices	Attached Commands
Cisco_Core_BGP	Core_R1 Core_R2	show running-config show ip bgp show ip bgp neighbors show ip route bgp
Cisco_Core_OSPF	Core_R3 Core_R4	show running-config show ip ospf show ip ospf neighbor show ip route ospf
HP_Edge_Minimal	HP_Clos_1 HP_Clos_2	show running-config
Cisco_Access_Standard	Switch1 Switch2 Switch3	show running-config show version show lldp neighbors

When to Use: Large enterprise environments with diverse requirements where both vendor differences and operational roles impact command needs.

Creating Command Groups

Prerequisites

Before creating Command Groups, ensure you have:

• Administrative access to rConfig V8
• Documented command requirements for each device category
• Understanding of your device inventory and classification strategy
• List of commands to be attached to each Command Group

Adding a New Command Group

Navigate to Configuration > Command Groups from the main rConfig menu.

Step-by-Step Process:

1. Initiate Creation

   • Click the Add Command Group button in the top-right corner
   • The system presents the Command Group creation form

2. Configure Basic Properties

   • Name: Enter a descriptive name following your naming convention
     • Use clear, consistent naming (e.g., Cisco_IOS_Routers, not Group1)
     • Consider including vendor, platform, or role in the name
   • Description: Provide detailed information about the Command Group’s purpose
     • Document what devices should be assigned to this group
     • Note any special considerations or command requirements
     • This description appears in device assignment workflows

3. Save the Command Group

   • Click Save to create the Command Group
   • The system creates the Command Group in a “pending commands” state

Note

Newly created Command Groups appear with a warning indicator until commands are attached. This is expected behavior and prevents incomplete configuration operations.

4. Attach Commands
   • From the Command Groups listing page, locate your new Command Group
   • Click the Commands action button (or Edit and navigate to commands section)
   • Select commands from the available command library
   • Commands must be created separately in the Commands interface before attachment
   • Click Save to finalize the command associations

Verification Steps:

After creating and configuring a Command Group:

1. Confirm the Command Group appears in the listing without error indicators
2. Verify all intended commands are properly attached
3. Test the configuration by assigning a device and performing a manual download
4. Review the downloaded configuration to ensure all expected command outputs are captured

Command Group Naming Best Practices

Effective naming conventions improve long-term maintainability:

Recommended Patterns:

• {Vendor}_{Platform}_{Role} - Example: Cisco_IOS_Core
• {Location}_{DeviceType} - Example: DataCenter_Switches
• {Function}_{Protocol} - Example: Routers_BGP

Avoid:

• Generic names like Group1, Test, Misc
• Names that don’t reflect purpose or content
• Overly long names that truncate in UI elements
• Special characters that may cause database issues

Editing Command Groups

Existing Command Groups can be modified to accommodate changing requirements:

Modifiable Properties:

• Command Group name and description
• Attached command sets
• Command execution order (if applicable)

Non-Modifiable Constraints:

• Cannot delete Command Groups with assigned devices (must reassign devices first)
• Cannot remove commands if they’re referenced in scheduled tasks (remove from tasks first)

To Edit a Command Group:

1. Navigate to Configuration > Command Groups
2. Locate the target Command Group in the listing
3. Click the Edit action button
4. Modify desired properties
5. Click Save to apply changes

Caution

When modifying commands attached to a Command Group, be aware that the changes immediately affect all devices in that group. The next configuration download for those devices will execute the updated command set.

Managing Commands Within Command Groups

Understanding the Commands Relationship

Commands in rConfig V8 are independent entities that are associated with Command Groups through a many-to-many relationship. This architecture enables:

• Reusing the same command across multiple Command Groups
• Modifying a command once and having changes propagate to all associated Command Groups
• Fine-tuning command execution per Command Group

Attaching Commands

From the Command Group Interface:

1. Navigate to the Command Group edit page
2. Select the Commands tab or section
3. Choose commands from the available command library
4. Use search or filtering to locate specific commands quickly
5. Add commands using the selection interface
6. Save the Command Group to apply changes

Command Selection Considerations:

• Order Matters: Commands execute in the order they appear in the Command Group
• Dependencies: Some commands may depend on output from previous commands
• Performance: More commands increase download time and storage requirements
• Relevance: Only attach commands that produce useful output for the device category

Command Execution Order

Commands execute sequentially in the order they’re attached to the Command Group. This sequence can be critical for certain operations:

Example Scenario - Configuration Mode Commands:

Correct Order:
1. enable (enter privileged mode)
2. configure terminal (enter configuration mode)
3. show running-config (capture configuration)

Incorrect Order:
1. show running-config (fails - not in privileged mode)
2. enable
3. configure terminal

For most rConfig use cases involving read-only show commands, execution order is less critical. However, maintain logical groupings (e.g., all routing commands together, all interface commands together) for easier output analysis.

Removing Commands from Command Groups

To detach a command from a Command Group:

1. Edit the Command Group
2. Navigate to the commands section
3. Deselect or remove the target command
4. Save the changes

Caution

Removing commands from a Command Group affects all devices in that group immediately. Future configuration downloads will no longer execute the removed commands. Historical configuration data containing those command outputs remains accessible in the database.

Command Groups in Operational Workflows

Scheduled Configuration Downloads

Scheduled tasks in rConfig target Command Groups rather than individual devices. This design enables efficient bulk operations:

Creating a Scheduled Task:

1. Navigate to Tasks > Scheduled Tasks
2. Create a new task
3. Select target Command Groups
4. Configure schedule parameters
5. The task executes commands from selected Command Groups against all member devices

Multi-Command Group Scheduling:

A single scheduled task can target multiple Command Groups simultaneously:

Scheduled Task: "Daily Configuration Backup"
Target Command Groups:
  - Cisco_IOS_Routers (15 devices)
  - Cisco_NX_Switches (8 devices)
  - Arista_Switches (12 devices)

Execution:
  - 35 total devices backed up
  - Each device executes commands from its assigned Command Group
  - Different command sets executed per group as configured

This approach provides flexibility while maintaining device-specific command requirements.

Manual Configuration Downloads

When performing manual downloads from the device interface or CLI, rConfig uses the device’s assigned Command Group to determine which commands to execute:

UI Manual Download:

1. Navigate to device details page
2. Click Download Configuration button
3. System retrieves commands from device’s Command Group
4. Executes commands and displays results

CLI Manual Download:

cd /var/www/html/rconfig8/current
php artisan rconfig:download-device {device_id}

The CLI command automatically uses the Command Group associated with the specified device. There is no way to override Command Group commands during manual downloads—this ensures consistency and prevents configuration drift.

Compliance Policy Application

Command Groups serve as the organizational unit for compliance policy enforcement:

Compliance Workflow:

1. Define compliance policies with expected configuration patterns
2. Associate policies with Command Groups
3. rConfig runs compliance checks against devices in those groups
4. Policy violations are reported per device with remediation guidance

Example Compliance Scenario:

Command Group: "PCI_Compliant_Switches"
Devices: 50 access switches in cardholder data environment
Compliance Policies:
  - SSH enabled, Telnet disabled
  - AAA authentication configured
  - Logging to central syslog server
  - Port security on access ports

rConfig periodically checks all 50 devices for policy compliance
based on configuration data retrieved via Command Group commands.

Command Group Error States and Resolution

Common Error: No Attached Commands

Symptom:

The Command Groups listing page displays an error indicator next to the Command Group name. The error message states: “This Command Group has no attached commands.”

Command Groups Error Indicator

Cause:

The Command Group was created but no commands have been associated with it. This is a normal intermediate state during Command Group creation.

Resolution:

1. Click the Edit or Commands button for the affected Command Group
2. Navigate to the command attachment interface
3. Select at least one command from the command library
4. Save the Command Group
5. Verify the error indicator disappears from the listing page

Prevention:

While rConfig allows saving Command Groups without commands initially (to enable a two-step creation process), complete the command attachment immediately after creation to avoid confusion and prevent accidental device assignments.

Error: Cannot Assign Device to Command Group

Symptom:

When attempting to assign a device to a Command Group, the system displays an error or the Command Group doesn’t appear in the selection dropdown.

Cause:

The target Command Group has no attached commands. rConfig prevents device assignment to Command Groups without commands to ensure all devices have actionable command sets.

Resolution:

1. Attach commands to the Command Group (see previous section)
2. Return to device assignment interface
3. The Command Group now appears in available selections

Error: Command Group Cannot Be Deleted

Symptom:

Attempting to delete a Command Group fails with an error message indicating the group is in use.

Cause:

The Command Group is currently assigned to one or more devices, or is referenced in active scheduled tasks.

Resolution:

1. Identify Dependencies:

   • Navigate to the Command Group details page
   • Review the devices list showing all assigned devices
   • Check scheduled tasks that reference this Command Group

2. Reassign Devices:

   • For each device assigned to the Command Group:
     • Edit the device settings
     • Assign to a different, appropriate Command Group
     • Save the device configuration

3. Update Scheduled Tasks:

   • Edit any scheduled tasks referencing the Command Group
   • Remove the Command Group from task targets or delete the task
   • Save task changes

4. Delete the Command Group:

   • Once all dependencies are resolved
   • Return to Command Groups listing
   • Delete the now-unused Command Group

Tip

Before deleting a Command Group, document its purpose and command list. This information may be valuable if you need to recreate similar functionality later.

Advanced Command Group Strategies

Dynamic Command Groups for Lifecycle Management

Organizations with device lifecycle processes can leverage Command Groups to implement staged command sets:

Example: Device Onboarding to Decommission

Command Group: "New_Devices_Validation"
Purpose: Minimal command set for newly added devices
Commands:
  - show version
  - show inventory
  - show running-config

Command Group: "Production_Full_Backup"
Purpose: Comprehensive configuration capture for production devices
Commands:
  - show running-config
  - show startup-config
  - show version
  - show inventory
  - show ip route
  - show ip interface brief
  - show cdp neighbors detail
  - show lldp neighbors

Command Group: "Decom_Final_Snapshot"
Purpose: Final configuration capture before device removal
Commands:
  - show tech-support
  - show running-config
  - show startup-config

Workflow:

1. New device added → assigned to New_Devices_Validation
2. After validation → reassigned to Production_Full_Backup
3. Before removal → temporarily reassigned to Decom_Final_Snapshot
4. Final snapshot captured → device removed from rConfig

Command Groups for Troubleshooting

Create specialized Command Groups containing diagnostic commands for troubleshooting scenarios:

Command Group: "BGP_Troubleshooting"
Commands:
  - show running-config | section bgp
  - show ip bgp summary
  - show ip bgp neighbors
  - show ip bgp
  - show ip route bgp
  - show ip protocols

Command Group: "Interface_Diagnostics"
Commands:
  - show interfaces
  - show interfaces status
  - show interfaces counters
  - show interfaces description
  - show logging | include interface

Usage Pattern:

1. Device experiencing issues remains in normal Command Group
2. Administrator temporarily reassigns device to diagnostic Command Group
3. Manual configuration download captures diagnostic information
4. After troubleshooting, device returned to original Command Group

This approach preserves normal configuration backup schedules while enabling deep diagnostic data capture when needed.

Environment-Specific Command Groups

Separate Command Groups by environment to implement different command strategies:

Production Environment:
  - Minimal commands to reduce load
  - Focus on configuration backup
  - Exclude potentially disruptive show commands

Development Environment:
  - Comprehensive commands for full visibility
  - Include operational state commands
  - Diagnostic and debugging commands included

Lab Environment:
  - Experimental commands
  - Extended timeout values
  - Test new command combinations before production deployment

Vendor Migration Strategies

When migrating from one vendor platform to another, Command Groups facilitate parallel operations:

Phase 1: Pre-Migration
  - Maintain existing Command Groups for current vendor
  - Create new Command Groups for replacement vendor
  - Both groups operational simultaneously

Phase 2: Migration
  - As devices are replaced, reassign from old to new Command Groups
  - Historical configuration data preserved from original devices
  - New devices immediately backed up with appropriate commands

Phase 3: Post-Migration
  - After all devices migrated, archive old Command Groups
  - Document migration for compliance and audit purposes

Command Group Performance Considerations

Impact on Backup Duration

The number and complexity of commands in a Command Group directly affects configuration download time:

Factors Affecting Performance:

• Command Count: Each command requires device processing and network transmission
• Command Output Size: Commands producing large outputs (show tech-support) increase transfer time
• Device Response Time: Older devices or congested networks may respond slowly
• Command Complexity: Some commands require significant device CPU/memory

Optimization Strategies:

1. Right-Size Command Sets: Include only necessary commands

   • Question each command’s value: “Will I use this output?”
   • Remove redundant or rarely-used commands

2. Separate Operational vs. Configuration Data:

   Command Group: "Daily_Config_Backup"
   - show running-config
   - show startup-config
   
   Command Group: "Weekly_Full_Snapshot"
   - show running-config
   - show startup-config
   - show version
   - show inventory
   - show ip route
   - show ip interface brief

   Use separate scheduled tasks with different frequencies

3. Consider Command Execution Time:

   • Avoid commands that take multiple seconds to complete
   • Be cautious with show tech-support on large devices
   • Test new commands on a single device before adding to group

4. Monitor and Adjust:

   • Review backup job duration metrics
   • Identify Command Groups with excessive runtime
   • Optimize command sets based on actual performance data

Scaling Command Groups

As your rConfig deployment grows, Command Group design impacts scalability:

Small Deployments (< 100 devices):

• Broader Command Groups acceptable
• Performance impact minimal
• Simpler management preferred

Medium Deployments (100-1000 devices):

• More granular Command Groups recommended
• Separate by performance characteristics
• Consider network segmentation in design

Large Deployments (> 1000 devices):

• Highly optimized Command Groups essential
• Group devices by backup window requirements
• Implement multi-tier command strategies
• Consider geographic distribution in scheduling

Enterprise-Scale Considerations:

For deployments exceeding 5,000 devices, contact rConfig Enterprise Support for optimization guidance including:

• Custom command execution strategies
• Distributed backup architectures
• Advanced performance tuning
• Database optimization for command output storage

Security Considerations

Command Security Implications

Commands executed via Command Groups run with the credentials configured for each device:

Security Considerations:

• Credential Exposure: Commands appear in configuration history
• Privileged Commands: Some commands require elevated privileges
• Sensitive Data: Command output may contain passwords or keys (show running-config)
• Command Injection: Validate commands before adding to Command Groups

Caution

Be extremely cautious with commands that modify device configuration. rConfig is designed for configuration retrieval (read-only operations). Write operations should be performed through the Script Integration Engine (SIE) with appropriate change control.

Recommended Security Practices:

1. Limit Privileged Commands: Include only necessary commands requiring elevated access
2. Review Output: Examine command results for sensitive information exposure
3. Implement Encryption: Enable configuration encryption for sensitive environments
4. Audit Command Changes: Monitor modifications to Command Group command lists
5. Test Before Production: Validate new commands in lab environment first

Integration with Other rConfig Features

Command Groups and Compliance Policies

Compliance policies leverage Command Groups for device categorization and policy application:

Integration Points:

• Policies are associated with specific Command Groups
• All devices in a Command Group inherit applicable policies
• Policy checks run against configuration data retrieved via Command Group commands
• Compliance reports group violations by Command Group

Example Integration:

Command Group: "Internet_Edge_Routers"
Attached Commands: show running-config, show ip route, show ip bgp

Associated Compliance Policies:
  - "Internet Edge Security" (checks for ACLs, uRPF)
  - "BGP Best Practices" (validates BGP configuration)
  - "Logging Requirements" (ensures proper logging configured)

All devices in "Internet_Edge_Routers" are automatically checked
against these three policies during compliance runs.

Command Groups and Change Management

rConfig’s Change Management suite (Change Pulse, Change Forge) operates on Command Groups:

Change Pulse Integration:

• Monitors configuration changes for devices in Command Groups
• Alert rules can target specific Command Groups
• Change reports aggregate by Command Group
• Baseline comparisons group devices by Command Group

Change Forge Integration:

• Configuration changes can be deployed to entire Command Groups
• Deployment schedules target Command Groups
• Rollback operations work across Command Group members

Command Groups and Reporting

Reports in rConfig often use Command Groups as organizational boundaries:

Available Reports:

• Configuration Backup Status by Command Group: Success/failure rates per group
• Command Group Membership: Devices assigned to each group
• Command Execution Time: Average backup duration per Command Group
• Compliance by Command Group: Policy violation rates across groups

Migration from Legacy Categories

For administrators upgrading from rConfig versions prior to 7.2.0:

Understanding the Terminology Change

The feature previously called “Categories” has been renamed to “Command Groups” to better reflect its purpose and usage pattern. This is a terminology change only—the underlying functionality remains consistent.

What Changed:

• User-facing labels now read “Command Groups” instead of “Categories”
• Documentation references updated to “Command Groups”
• API endpoints retain original naming for backward compatibility

What Stayed the Same:

• Database structure unchanged
• Existing Categories automatically become Command Groups
• All device assignments preserved
• Command associations maintained
• Scheduled tasks continue functioning without modification

Note

This terminology inconsistency is temporary and will be fully resolved in future updates as all components transition to “Command Groups.” It does not affect functionality or operations.

Actions Required

For Existing Deployments:

No action required. Your existing Categories function as Command Groups without any configuration changes.

For New Documentation:

Update any custom documentation, runbooks, or training materials to use “Command Groups” terminology for consistency with current rConfig documentation.

For API Integrations:

If you have custom scripts or integrations that reference “categories”:

• Continue using existing API endpoints (they remain functional)
• Plan to update to new endpoints when announced
• Monitor rConfig release notes for API changes

Command Group Video Tutorial

The following video demonstrates the complete workflow for adding and editing Command Groups, including command attachment and error resolution:

Troubleshooting Common Issues

Issue: Commands Not Executing During Backup

Symptoms:

• Scheduled backup completes but configuration data is empty or incomplete
• Manual download produces no output or errors
• Device logs show connection but no command execution

Diagnostic Steps:

1. Verify Command Group Assignment:

   # Check device Command Group assignment
   Navigate to: Devices > [Device Name] > Edit
   Confirm: Command Group field shows appropriate group

2. Confirm Commands Are Attached:

   Navigate to: Configuration > Command Groups > [Group Name]
   Verify: Commands section lists expected commands
   Check: No error indicators on Command Groups page

3. Test Command Execution:

   • Manually SSH to device using same credentials as rConfig
   • Execute each command from Command Group manually
   • Verify commands produce expected output
   • Check for permission or syntax errors

Common Causes and Solutions:

Cause	Solution
Command Group has no commands	Attach commands to the Command Group
Commands contain syntax errors	Edit commands to correct syntax
Device credentials insufficient privileges	Update device credentials to privileged account
Commands not compatible with device	Review and update command syntax for device type
Network connectivity issues	Verify network path to device

Issue: Slow Backup Performance

Symptoms:

• Scheduled tasks take excessive time to complete
• Backup jobs timeout before completion
• System resources (CPU/memory) spike during backups

Diagnostic Steps:

1. Identify Problematic Command Groups:

   • Review backup job logs for duration per device
   • Group slow devices by Command Group
   • Isolate Command Groups with consistent slow performance

2. Analyze Command Sets:

   For each slow Command Group:
   - Count total commands attached
   - Identify commands producing large output (show tech-support)
   - Note commands with known slow execution (show logging)

3. Test Individual Command Performance:

   • SSH to representative device
   • Time each command execution manually
   • Identify specific slow commands

Resolution Strategies:

1. Optimize Command Groups:

   • Remove unnecessary commands
   • Move diagnostic commands to separate troubleshooting group
   • Split large Command Groups into smaller, focused groups

2. Adjust Command Set:

   • Replace show tech-support with specific targeted commands
   • Use command filters (show running-config | include keyword)
   • Remove redundant commands providing duplicate data

3. Implement Tiered Backup Strategy:

   Daily Command Group: "Config_Only_Daily"
   - show running-config
   - show startup-config
   
   Weekly Command Group: "Full_Backup_Weekly"
   - show running-config
   - show startup-config
   - show version
   - show inventory
   - show ip route
   - show ip interface brief

   Move devices between groups based on backup schedule needs

4. Optimize Scheduled Tasks:

   • Reduce simultaneous device count per task
   • Stagger backup windows for different Command Groups
   • Increase task timeout values if appropriate

Issue: Cannot Delete Command Group

Symptoms:

• Delete button disabled or produces error
• Error message: “Command Group cannot be deleted while in use”
• Command Group persists after delete attempt

Diagnostic Steps:

1. Check Device Assignments:

   Navigate to: Configuration > Command Groups > [Group Name]
   Review: Devices tab showing assigned devices
   Count: Number of devices in group

2. Check Scheduled Task References:

   Navigate to: Tasks > Scheduled Tasks
   Search: Tasks containing target Command Group
   Review: Each task's Command Group selections

Resolution:

1. Reassign Devices:

   • For each device in the Command Group:
     • Edit device configuration
     • Select alternative appropriate Command Group
     • Save changes
   • Verify all devices removed from target Command Group

2. Update or Delete Scheduled Tasks:

   • For each task referencing the Command Group:
     • Edit task configuration
     • Remove Command Group from selections
     • Add alternative Command Group or delete task
     • Save task changes

3. Verify Dependencies Cleared:

   • Return to Command Group details
   • Confirm no devices listed
   • Confirm no scheduled task references

4. Delete Command Group:

   • Click Delete button
   • Confirm deletion
   • Verify Command Group removed from listing

Note

rConfig prevents orphaned devices (devices without a Command Group) by enforcing dependency checks before Command Group deletion. This protective behavior ensures all devices maintain valid command associations.

Best Practices Summary

Design Principles

1. Purpose-Driven Design: Create Command Groups based on clear operational requirements, not arbitrary groupings
2. Command Minimalism: Include only commands that provide actionable information
3. Consistent Naming: Implement standardized naming conventions across all Command Groups
4. Documentation: Maintain descriptions explaining each Command Group’s purpose and intended device types
5. Regular Review: Periodically audit Command Groups to remove obsolete configurations

Operational Guidelines

1. Test Before Production: Validate new Command Groups with single device before bulk assignment
2. Monitor Performance: Track backup duration and optimize Command Groups causing delays
3. Implement Change Control: Require approval for modifications to production Command Groups
4. Maintain Consistency: Avoid creating duplicate or overlapping Command Groups
5. Plan for Scale: Design Command Group structure to accommodate growth

Security Best Practices

1. Least Privilege Commands: Include only necessary commands, especially those requiring elevated privileges
2. Review Command Output: Understand what data each command exposes
3. Control Command Group Modifications: Restrict who can edit Command Groups and attached commands
4. Audit Changes: Regularly review logs for Command Group and command modifications
5. Test Security Impact: Evaluate new commands in isolated environment before production deployment

Maintenance Recommendations

1. Quarterly Review: Assess Command Group structure and membership every three months
2. Performance Monitoring: Track backup job metrics to identify optimization opportunities
3. Documentation Updates: Keep Command Group descriptions current with operational changes
4. Cleanup Unused Groups: Archive or delete Command Groups no longer serving active devices
5. Align with Network Changes: Update Command Groups when network architecture or device roles change

Quick Reference

Command Group Lifecycle

1. Create Command Group
   ↓
2. Attach Commands
   ↓
3. Assign Devices
   ↓
4. Configure Scheduled Tasks (optional)
   ↓
5. Monitor and Optimize
   ↓
6. Update as Needed
   ↓
7. Reassign Devices Before Deletion
   ↓
8. Delete Command Group

Key Relationships

Command Groups (1) ←→ (Many) Devices
Command Groups (Many) ←→ (Many) Commands
Command Groups (Many) ←→ (Many) Scheduled Tasks
Command Groups (1) ←→ (Many) Compliance Policies

Common Operations

Operation	Path	Notes
Create Command Group	Configuration > Command Groups > Add	Must attach commands before device assignment
Edit Command Group	Configuration > Command Groups > Edit	Changes affect all member devices
Attach Commands	Command Groups > Edit > Commands	Commands must exist before attachment
Assign Device to Group	Devices > Edit > Command Group	Device can only belong to one group
View Group Members	Command Groups > View > Devices	Shows all assigned devices
Delete Command Group	Command Groups > Delete	Must remove all dependencies first

Command Group Limits

Metric	Recommended	Maximum	Notes
Commands per Group	5-10	No hard limit	Performance degrades with many commands
Devices per Group	100-500	No hard limit	Consider subdividing large groups
Groups per System	10-50	No hard limit	More groups increase management overhead
Command Groups per Task	1-5	No hard limit	Tasks can target multiple groups

Related Documentation

Understanding Command Groups is essential for working with many other rConfig features. Reference these related documents:

• Commands - Creating and managing the commands attached to Command Groups
• Devices - Assigning devices to Command Groups and device management
• Scheduled Tasks - Creating automated backup tasks targeting Command Groups
• Compliance Policies - Applying policies to Command Groups
• Change Management - Monitoring changes across Command Groups
• Script Integration Engine - Executing configuration changes on Command Group devices

Summary and Key Takeaways

Command Groups represent a fundamental organizational structure in rConfig V8, serving as the bridge between devices and the commands used to retrieve their configurations. Effective Command Group design directly impacts backup efficiency, compliance enforcement, and operational workflows.

Essential Points to Remember:

• Every device must be assigned to exactly one Command Group
• Command Groups must have attached commands before device assignment
• Commands attached to a Command Group determine what configuration data is retrieved
• Manual and scheduled downloads both use Command Group command associations
• Command Group structure should reflect your network architecture and command requirements
• Performance optimization begins with right-sized command sets per Command Group
• Plan Command Groups strategically before large-scale device onboarding

Getting Started:

1. Analyze your device inventory and document command requirements per device type
2. Design Command Group structure aligned with your network architecture
3. Create Command Groups with descriptive names and detailed descriptions
4. Attach appropriate commands to each Command Group
5. Test configuration downloads on single devices before bulk operations
6. Monitor performance and adjust Command Groups as needed

For additional assistance with Command Group design or optimization for large-scale deployments, contact rConfig Enterprise Support.

---

Next Steps:

• Create Your First Command - Learn how to create commands that can be attached to Command Groups
• Add Devices - Assign your first devices to Command Groups
• Schedule Automated Backups - Configure scheduled tasks targeting your Command Groups