Migrate from Infoblox NetMRI to rConfig V8 Core

After reading this page, you can migrate your Infoblox NetMRI device inventory into rConfig V8 Core using the NetMRI Import Tool. Unlike file based sources, NetMRI is queried directly over its REST API, so the workflow starts with a one time connection setup, then follows the same map, load, and import pattern used by the other import tools. (V8+)

Note

Running rConfig Pro? See the Pro NetMRI migration guide on the separate rConfig Pro, Enterprise, and Vector documentation site.

When to use this

Use this page when you are moving off Infoblox NetMRI and want your device inventory in rConfig V8 Core without re-entering each device by hand. It suits teams that want dedicated configuration backup and versioning rather than NetMRI’s broader network discovery focus. If you are still comparing the two, see why rConfig is a strong Infoblox NetMRI alternative; this page covers the migration itself.

What you get from the migration

NetMRI focuses on network discovery and automation. rConfig V8 Core provides a dedicated network configuration management platform with versioned configuration backups: full history and diffing of every device configuration. The NetMRI Import Tool makes the transition straightforward by pulling your inventory directly from the API and bulk importing devices with consistent templates, vendors, and categories.

Some features are Pro, Enterprise, or Vector only

Advanced scheduling with dependency management and configuration snippet deployment across device groups are part of the Pro, Enterprise, and Vector editions, documented at docs.rconfig.com. They are not part of V8 Core.

How it works

The import process follows four steps:

1. Configure the NetMRI connection: store and test the NetMRI REST API connection details.
2. Create device type mappings: define how NetMRI device types translate to rConfig templates, vendors, and categories.
3. Load devices from NetMRI: query the NetMRI API and generate import ready JSON.
4. Import devices to rConfig: bulk import devices with validated configurations.

File locations

The import tool uses the following file locations:

• Connection file: storage/app/rconfig/netmri_connection.json
• Temporary files: storage/app/rconfig/tempdir/
• Import JSON files: storage/app/rconfig/tempdir/rconfig_import_YYYY-MM-DD_HH-mm-ss.json

These directories are created automatically if they do not exist.

Prerequisites

Before importing devices, make sure you have:

• A reachable NetMRI appliance with the REST API enabled (the connection defaults to HTTPS on port 443)
• NetMRI API credentials with permission to read the device inventory
• Administrator access to rConfig V8 Core
• Device templates, vendors, and categories configured in rConfig matching your NetMRI device types
• At least one credential set created in rConfig (NetMRI does not export usable device passwords)
• SSH or command-line access to the rConfig server

Step 1: Configure the NetMRI connection

Before you can load any devices, tell rConfig how to reach the NetMRI API. The connection details are stored at storage/app/rconfig/netmri_connection.json.

Run the base command to see the available options:

php /var/www/html/rconfig/artisan rconfig:netmri-connection

The command supports the following options:

• --setup - Set up the NetMRI connection interactively
• --test - Test the existing connection
• --show - Show the current connection info
• --edit-filters - Edit the device filters applied when loading
• --set-url=URL - Update the API URL
• --clear - Clear the stored connection info
• --info - Display command help and usage information

Run the setup wizard to store the connection:

php /var/www/html/rconfig/artisan rconfig:netmri-connection --setup

The wizard prompts you for the host, port (defaults to 443), username, password, and whether to verify the TLS certificate.

Test the connection before going any further:

php /var/www/html/rconfig/artisan rconfig:netmri-connection --test

Tip

Testing after setup confirms rConfig can authenticate against the NetMRI API before you spend time loading devices.

Review or remove the stored configuration at any time:

php /var/www/html/rconfig/artisan rconfig:netmri-connection --show
php /var/www/html/rconfig/artisan rconfig:netmri-connection --clear

Step 2: Create device type mappings

NetMRI uses its own device type and vendor naming. rConfig uses templates. Map each NetMRI device type to an rConfig template, vendor, and category before importing.

Run the interactive mappings command:

php /var/www/html/rconfig/artisan rconfig:netmri-device-mappings

This command lets you view, add, edit, and remove mappings between NetMRI device types and rConfig templates. For each mapping you provide:

• NetMRI device type: the device type reported by NetMRI
• rConfig template: the device template ID to use for this device type
• Vendor: the vendor ID associated with this device type
• Category: the category ID for organising devices
• Tags: multi-select tags for device classification
• Prompts: device enable and main prompts (use {device_name} as the placeholder)

Caution

Accurate mappings are critical for successful imports. Verify the template, vendor, and category IDs exist in rConfig before creating mappings, or the import will fail with an invalid ID error.

Step 3: Load devices from NetMRI

Run the load command to query the NetMRI API and convert the returned devices into an intermediate JSON file:

php /var/www/html/rconfig/artisan rconfig:netmri-load-devices

The command supports the following options:

• --batch-size=100 - Number of devices to fetch per API request (default: 100)
• --info - Display command help and usage information

The loader fetches devices in batches, applies your device type mappings, and writes a timestamped JSON file to storage/app/rconfig/tempdir. Set a larger batch size for big inventories:

php /var/www/html/rconfig/artisan rconfig:netmri-load-devices --batch-size=250

Note

The JSON file is an intermediate artifact. Review it before importing to confirm the device details and template mappings look correct.

Step 4: Import devices to rConfig

Once you are happy with the JSON file, import it into rConfig:

php /var/www/html/rconfig/artisan rconfig:netmri-import-devices /path/to/rconfig_import.json

The command supports the following options:

• --dry-run - Preview the import without modifying the database
• --info - Display command help and usage information

Preview the import first with a dry run. It validates each device and reports what would be imported without writing any records:

php /var/www/html/rconfig/artisan rconfig:netmri-import-devices \
  --dry-run \
  /path/to/rconfig_import.json

Run the actual import once the dry run looks correct:

php /var/www/html/rconfig/artisan rconfig:netmri-import-devices \
  /path/to/rconfig_import.json

Note

All imports use database transactions. If any error occurs during import, all changes roll back automatically. Devices that already exist are skipped.

Complete workflow example

# Step 1: Configure and test the NetMRI connection
php /var/www/html/rconfig/artisan rconfig:netmri-connection --setup
php /var/www/html/rconfig/artisan rconfig:netmri-connection --test

# Step 2: Create device type mappings
php /var/www/html/rconfig/artisan rconfig:netmri-device-mappings

# Step 3: Load devices from NetMRI
php /var/www/html/rconfig/artisan rconfig:netmri-load-devices --batch-size=100

# Review the generated JSON file
cat storage/app/rconfig/tempdir/rconfig_import_2025-01-25_14-30-45.json

# Step 4: Preview import (dry run)
php /var/www/html/rconfig/artisan rconfig:netmri-import-devices \
  --dry-run \
  storage/app/rconfig/tempdir/rconfig_import_2025-01-25_14-30-45.json

# Step 5: Run the production import
php /var/www/html/rconfig/artisan rconfig:netmri-import-devices \
  storage/app/rconfig/tempdir/rconfig_import_2025-01-25_14-30-45.json

Common gotchas

Caution

Watch for these issues during a NetMRI migration:

• Credentials do not transfer. NetMRI does not export usable device passwords, so create at least one credential set in rConfig before loading. The load command fails with “No device credentials found in the system” if none exist.
• Missing mappings skip devices. Devices with no matching mapping are skipped during loading with “No mapping found for device type”. Re-run rconfig:netmri-device-mappings to add the missing type.
• Invalid template, vendor, or category IDs fail the import with “Template ID X does not exist” or “Vendor ID X not found”. Confirm the IDs exist under Settings before mapping.
• Self signed certificates block the connection test. Set verify SSL to off when running --setup if your NetMRI appliance uses a self signed certificate.

Troubleshooting

Why does the connection test fail?

The connection test or load command cannot reach NetMRI. Re-run the connection test and confirm the host, port, and credentials:

php /var/www/html/rconfig/artisan rconfig:netmri-connection --test

If you use a self signed certificate, set verify SSL to off when running --setup.

Why does loading report no credential sets?

Loading fails with “No device credentials found in the system”. Create at least one credential set in rConfig:

• Navigate to Settings > Credentials
• Create a new credential set with valid SSH credentials
• Re-run the load devices command

Why are devices skipped with a mapping error?

Devices are skipped during loading with “No mapping found for device type”. Add the missing mapping:

php /var/www/html/rconfig/artisan rconfig:netmri-device-mappings

Why does the import report an invalid ID?

The import fails with “Template ID X does not exist” or “Vendor ID X not found”. Verify the IDs exist in rConfig (Settings > Templates, Vendors, or Categories) and update the mapping with the correct IDs.

Why are some devices marked as duplicates?

Validation shows “Device with same name or IP already exists”. Duplicates are automatically skipped during import. Review the import summary to confirm which devices were skipped.

Post-import tasks

After a successful import:

1. Verify the device inventory: navigate to Devices and confirm all devices imported correctly.
2. Review credentials: check that devices have appropriate credential assignments.
3. Test connectivity: use the device debug command to verify the connection to sample devices.
4. Check relationships: verify tags, vendors, categories, and templates are correctly assigned.
5. Configure schedules: set up automated backup schedules for device groups.

Frequently asked questions

Can I export the device inventory from Infoblox NetMRI?

Yes. rConfig queries NetMRI directly over its REST API and converts the returned devices into an import ready JSON file. The load command fetches devices in batches and applies your device type mappings.

Will device credentials transfer from NetMRI?

No. NetMRI does not export usable device passwords. Create at least one credential set in rConfig before loading devices, then assign credentials to the imported devices afterwards.

Does the NetMRI REST API need to be enabled?

Yes. Enable the REST API on the NetMRI appliance and use an account that can read the device inventory. The connection defaults to HTTPS on port 443.

Does rConfig replace NetMRI for configuration management?

Yes, for configuration backup and versioning. See the full feature comparison on rconfig.com for a side by side breakdown.

What’s next

• Oxidized Import: migrate a device inventory from Oxidized into rConfig V8 Core.
• Rancid Import: migrate a device inventory from RANCID into rConfig V8 Core.
• Scheduled Tasks: automate configuration backups for your imported devices.