Bulk Network Configuration Deployment
Push a configuration change to 50, 200 or 2000 devices without doing it one by one. Template-based mass deployment with dry-run preview, rolling rollout by wave, and automatic rollback if something goes wrong. The risk of deploying at scale, managed.
- ✓Template-based deployment with per-site variable substitution
- ✓Target devices by tag, site, vendor, type or manual list
- ✓Dry-run: preview the exact diff on every device before executing
- ✓Rolling deployment by wave with configurable pause and thresholds
- ✓Automatic rollback on failure to pre-change snapshot
- ✓Full audit trail: who deployed what, to which devices, with which results
Deploying at Scale Is a Risk Management Problem
Pushing a configuration change to a single device is straightforward. Pushing it to 200 devices in production is an entirely different challenge. A typo in a template, a missing variable for one site, or a vendor-specific syntax difference can silently fail on dozens of devices or, worse, cause an outage. ConnectMyAssets treats bulk deployment not as "running a script on many devices" but as a controlled change process: preview before execute, deploy in waves, verify after each wave, and roll back automatically if something goes wrong. These are the same principles that govern production software deployments, applied to network configuration.
Controlled Bulk Deployment at Any Scale
From template definition to post-deployment verification, every step of the mass configuration change process is designed to minimize risk.
Template-Based Deployment
Define a configuration snippet with variables, for example NTP server set to {{ntp_server}} or SNMP community to {{snmp_community}}, and apply it to any selection of devices with the right values per site. ConnectMyAssets renders the template for each target device, substituting site-specific variables before pushing. The same template works for 1 device or 2000: the workflow does not change, only the target scope does. Templates are version-controlled, so you always know which version was deployed to which device and can roll back to any previous state.
Bulk Device Targeting
Select deployment targets by tag, site, device type, vendor, or manual list. You can target all Cisco routers tagged "branch-office", all Juniper switches in the Paris site, all Fortinet firewalls in your fleet, or a hand-picked list of specific devices. Combine filters to build the exact scope you need. Deploy to 1 device or 5000 through the same workflow: there is no separate "bulk mode". ConnectMyAssets executes the same deployment logic regardless of scope, which means your testing on 5 devices transfers directly to 500.
Dry-Run Validation
Before any deployment executes, ConnectMyAssets lets you preview exactly what will be pushed to each device with all variables resolved. The dry-run shows the rendered configuration diff per device: what lines will be added, what will be removed, and the final state after the change. You can review the preview for the entire scope or drill down to individual devices. If a variable is missing for a specific device or the rendered config contains a syntax error, the dry-run catches it before a single change is made. Dry-run results are saved so you can share them for peer review before approving execution.
Rolling Deployment
Deploy in waves instead of hitting all devices at once. Configure wave size (for example 10 devices per wave), the pause duration between waves, and the success threshold required to continue (for example pause if more than 5% of devices in a wave fail). ConnectMyAssets executes the first wave, waits for results, applies the pause, then proceeds to the next wave. If a wave result falls below the success threshold, the deployment halts automatically and alerts your team before impacting more devices. Rolling deployment is especially important for large fleets where a bad template variable or an unexpected vendor quirk could affect thousands of devices if deployed all at once.
Automatic Rollback on Failure
If a device fails during deployment, ConnectMyAssets can automatically trigger a rollback on that device, restoring its last known good configuration. Rollback behavior is configurable: roll back only the failed device, roll back the entire wave, or halt and alert without automatic rollback if you prefer manual control. The rollback uses the configuration snapshot taken by ConnectMyAssets before the deployment started, so the restore target is always the exact pre-change state, not a template approximation. Failed devices and their rollback status appear in real time on the deployment progress dashboard.
Deployment Audit Trail
Every bulk deployment is fully logged: who triggered it, when it started and ended, which template was used, which devices were targeted, the rendered configuration per device, and the result for each device (success, failure, rollback). The audit trail is immutable and searchable. You can retrieve the full record of any past deployment, compare what was deployed across different runs of the same template, and export deployment reports for change management documentation or compliance evidence. For regulated environments, the audit trail proves that configuration changes were controlled, reviewed, and executed as intended.
How It Works
Define Your Template and Targets
Create the configuration snippet in ConnectMyAssets using variable syntax for any site-specific values. Name the template, tag it with the device types it applies to, and define the variable list with default values and per-site overrides. Then build your target scope using filters: by tag, site, vendor, device type, or a manual list. ConnectMyAssets shows you the total count of matched devices before you proceed. You can save the template and target definition as a reusable job for future deployments of the same change.
Dry-Run and Validate
Before execution, run a dry-run to preview the exact diff that will be applied to each device. ConnectMyAssets resolves all variables per device and shows you the rendered configuration change, line by line. Review the preview, check for missing variables or syntax issues, and share it with a colleague for peer approval if your change management process requires it. Once you are satisfied with the preview, configure the rolling deployment settings: wave size, inter-wave pause, success threshold, and rollback policy. Then approve the deployment for execution.
Deploy, Monitor and Rollback if Needed
ConnectMyAssets executes the deployment wave by wave. A real-time dashboard shows each device status: pending, in-progress, success, failed, or rolled back. The progress counter updates live as each device completes. If a device fails and rollback is configured, the rollback executes automatically and the device status updates to show whether the restore succeeded. Once all waves complete, the deployment summary shows the final counts per status and a link to the full audit trail. You can re-run the deployment on failed devices without touching the successful ones.
Related Platform Features
Frequently Asked Questions
Common questions about bulk network configuration deployment
How many devices can be targeted simultaneously?
ConnectMyAssets has no hard limit on the number of devices in a single bulk deployment job. In practice, organizations regularly run jobs targeting thousands of devices. The rolling deployment feature controls how many devices are actively configured at the same time (wave size), which you can tune based on your infrastructure capacity and risk tolerance. Whether you are deploying to 50 devices or 5000, the workflow is identical: define the template, set the targets, run the dry-run, configure wave settings, and execute.
What happens if the deployment fails on some devices?
Each device is handled independently. If a device fails, it does not affect the other devices in the deployment. Depending on your rollback policy, ConnectMyAssets will either automatically restore the failed device to its pre-change configuration, halt the wave and alert your team for manual intervention, or log the failure and continue to the next wave. After the deployment completes, you have a clear list of failed devices with the specific error reason for each. You can investigate, fix the root cause (for example, a missing variable value or a connectivity issue), and re-run the deployment targeting only the failed devices. Devices that succeeded are not touched in a re-run.
How do I handle different variable values per site or per device?
ConnectMyAssets has a layered variable resolution system. You define variables at three levels: global defaults, site-level overrides, and device-level overrides. When the template is rendered for a specific device, ConnectMyAssets uses the most specific value available: device-level if set, then site-level if set, then global default. For example, your NTP server template variable might have a global default of "0.pool.ntp.org", a site-level override for the Paris site pointing to an internal NTP server, and a device-level override for one specific router that needs a different NTP configuration. The dry-run shows you the resolved value for every variable on every device before you execute, so you can verify the resolution is correct.
Can I schedule the deployment for a maintenance window?
Yes. After configuring the template, targets, and rolling deployment settings, you can schedule execution for a specific date and time rather than running it immediately. ConnectMyAssets will execute the deployment at the scheduled time, applying all the same wave and rollback logic. You can set up notifications so your team receives alerts when the scheduled deployment starts, when each wave completes, and when the full job finishes. If you need to cancel a scheduled deployment before it runs, you can do so from the deployment dashboard at any time before execution begins.
How do I verify that the deployment was correctly applied on all devices?
ConnectMyAssets performs a post-deployment verification step on each device. After pushing the configuration change, the platform retrieves the running configuration from the device and confirms that the expected lines are present in the actual running config, not just acknowledged by the device as accepted. Devices where the verification diff does not match the expected result are flagged separately from devices that failed during push. The deployment summary report shows three categories: deployed and verified, deployed but not verified (diff mismatch), and failed to deploy. For devices in the "deployed but not verified" state, ConnectMyAssets shows you the exact diff between expected and actual, so you can investigate the discrepancy.
Does bulk deployment support all vendors?
Yes. ConnectMyAssets supports bulk configuration deployment across all major network vendors: Cisco (IOS, IOS-XE, IOS-XR, NX-OS), Juniper (JunOS), Fortinet (FortiOS), Palo Alto Networks (PAN-OS), Aruba, Arista (EOS), and many others. In a multi-vendor environment, you can either create vendor-specific templates (one for Cisco, one for Juniper) and run them as separate jobs, or use a single template with conditional blocks if the configuration syntax is similar enough across your target devices. ConnectMyAssets handles the SSH connection and configuration push natively for each vendor, so there is no need for separate tooling per vendor.
Stop Configuring Devices One by One
Templates, dry-run, rolling deployment and automatic rollback: push configuration changes to your entire fleet with the same confidence you would have deploying to a single device.