Network Device Import Methods - CSV, API, Manual & Integration Guide
Network Device Import Methods - CSV, API, Manual & Integration Guide
Section titled “Network Device Import Methods - CSV, API, Manual & Integration Guide”Before rConfig can back up configurations, you need devices in the system. Whether you’re setting up a new installation with hundreds of devices or adding a single router, rConfig gives you five methods to get it done. Choose the approach that matches your situation.
Getting Devices Into rConfig
Section titled “Getting Devices Into rConfig”The Five Import Methods
Section titled “The Five Import Methods”1. Manual Entry (The Direct Approach)
Section titled “1. Manual Entry (The Direct Approach)”Best for: Adding 1-5 devices, testing, or when you need full control over every field.
Click Add Device from the Devices table and fill in the form. You’ll specify the device name, IP address, credentials, vendor/model, category, and connection settings. This is straightforward but gets tedious fast if you’re adding more than a handful of devices.
When to use manual entry:
- Initial testing and proof-of-concept setups
- One-off additions (new router, replacement switch)
- When the device configuration is unique or complex
- Learning the rConfig device model before bulk imports
2. Device Cloning (The Time-Saver)
Section titled “2. Device Cloning (The Time-Saver)”Best for: Adding similar devices—routers in the same site, switches with identical configs, or any devices that share most settings.
Find an existing device that’s close to what you need, click the clone button, and rConfig copies everything except the device name and IP address. This is surprisingly useful when you’re building out sites with standardized equipment.
What gets cloned:
- Vendor and model
- Credentials
- Connection protocol settings
- Category and tags
- Command templates
- All custom settings
What you change:
- Device name (required)
- IP address (required)
- Anything else that differs
When to use cloning:
- Deploying standardized equipment across sites
- Adding multiple devices of the same type
- Maintaining consistency in device configuration
- Rapid expansion scenarios
3. REST API (The Programmer’s Choice)
Section titled “3. REST API (The Programmer’s Choice)”Best for: Automation, scripting, external integrations, or when devices are already in another system.
rConfig’s REST API lets you POST device records programmatically. If you’ve got device data in spreadsheets, databases, monitoring tools, or other management platforms, write a script to push that data into rConfig. You can also query, update, and delete devices via API.
Common API use cases:
- Automated device provisioning workflows
- Syncing with CMDBs or ticketing systems
- Custom provisioning portals
- CI/CD pipeline integration
- Bulk operations via scripting (Python, Bash, PowerShell)
API capabilities:
- Create devices (POST)
- Read device data (GET)
- Update existing devices (PUT/PATCH)
- Delete devices (DELETE)
- Query and filter device lists
4. CSV Import (The Bulk Loader)
Section titled “4. CSV Import (The Bulk Loader)”Best for: Importing 10-1000+ devices at once, migrating from other systems, or working with spreadsheet data.
Export your device list from wherever it lives now (another tool, a spreadsheet, a database query), format it as CSV, and upload it through Settings → Import/Export. rConfig maps your columns to device fields and creates all the records in one shot.
CSV import workflow:
- Export or create a CSV file with device data
- Ensure column headers match rConfig’s expected format (or use the template)
- Navigate to Settings → Import/Export
- Upload the CSV
- Map columns (if needed)
- Validate and import
What you can import via CSV:
- Core device fields (name, IP, vendor, model, category)
- Credentials (username, password, enable password)
- Connection settings (protocol, port, timeout)
- Tags (comma-separated)
- Custom fields
CSV import tips:
- Download the CSV template from rConfig first
- Test with 5-10 devices before bulk importing
- Keep your source CSV as backup
- Check for duplicate IPs or names before importing
5. Device Sync Integrations (The Automated Solution)
Section titled “5. Device Sync Integrations (The Automated Solution)”Best for: Organizations already using Netbox, Nautobot, or Zabbix as their source of truth.
If you’re running a proper IPAM/DCIM system or monitoring platform, don’t duplicate work. Set up a Device Sync integration and let rConfig pull device records automatically. Your source system owns the device inventory; rConfig consumes it.
Supported integrations:
- Netbox: Full device sync with site, role, and platform mapping
- Nautobot: Same rich integration as Netbox
- Zabbix: Pull monitored hosts directly into rConfig
How Device Sync works:
- Configure the integration with API credentials
- Map fields between the source system and rConfig
- Run a sync (manual or scheduled)
- rConfig creates/updates devices automatically
- Future syncs keep everything current
Integration benefits:
- Single source of truth (your IPAM/DCIM)
- No manual data entry or CSV wrangling
- Automatic updates when devices change
- Consistent data across platforms
- Reduced human error
Device Sync use cases:
- Large organizations with established inventory systems
- Teams already using Netbox for IP/device management
- Environments where device data changes frequently
- Multi-tool ecosystems that need data consistency
Device Sync Overview | Netbox Integration | Nautobot Integration | Zabbix Integration
Choosing the Right Method
Section titled “Choosing the Right Method”Here’s a quick decision tree:
- 1-5 devices, unique configs? → Manual entry
- Adding devices similar to existing ones? → Clone
- Already have device data in another system? → Check if there’s an integration, otherwise API or CSV
- 10-1000 devices from a spreadsheet? → CSV import
- Using Netbox/Nautobot/Zabbix? → Device Sync integration
- Need ongoing automation? → API or Device Sync
You can mix and match these methods. Many teams use Device Sync for the bulk of their infrastructure, manual entry for test devices, and cloning for rapid site deployments.
What Happens After Import
Section titled “What Happens After Import”Regardless of how devices get into rConfig, they all follow the same path:
- Device record created in the database
- Credentials validated (if testing is enabled)
- Category and tags applied for organization
- Command templates assigned based on vendor/model
- Device becomes available for backup tasks, policy compliance, and reporting
Once devices are in rConfig, you can:
- Run manual or scheduled configuration backups
- Apply compliance policies
- Send configuration snippets
- Generate inventory reports
- Compare configurations over time
Related Documentation
Section titled “Related Documentation”- Device Management Fundamentals - Core device concepts and workflows
- Device Connectivity Process - How rConfig connects to devices
- Universal Device Support - Multi-vendor device support
- CLI Commands - Automation and scripting commands
- Device Inventory Management - Comprehensive device data collection
Quick Start Recommendations
Section titled “Quick Start Recommendations”First-Time Setup
Section titled “First-Time Setup”Start with manual entry for 2-3 test devices to learn the system, then move to your bulk import method.
Small Deployments (< 50 devices)
Section titled “Small Deployments (< 50 devices)”Manual entry or CSV import works fine. Don’t over-engineer it.
Medium Deployments (50-500 devices)
Section titled “Medium Deployments (50-500 devices)”CSV import for initial load, then API or manual entry for ongoing additions.
Large Deployments (500+ devices)
Section titled “Large Deployments (500+ devices)”Device Sync integration if you have Netbox/Nautobot, otherwise CSV for bulk and API for automation.
Multi-Site Standardized Equipment
Section titled “Multi-Site Standardized Equipment”Clone liberally. Build a template device for each site/type and clone it for new additions.