Solution

Zero Touch Provisioning

Plug in a device and ConnectMyAssets does the rest. The platform detects the new device on your network, reads its serial number, and automatically pushes the right configuration and firmware. No DHCP tricks, no TFTP server, no vendor portal. Just plug in and walk away.

  • ✓Automatic detection when device is plugged in
  • ✓Serial number identification, no vendor protocol required
  • ✓Golden config templates with site-specific variables
  • ✓Automatic firmware upgrade before config push
  • ✓Branch office deployment without on-site engineers
  • ✓Automated post-provisioning validation
ConnectMyAssets, ZTP Onboarding
PROVISIONINGsw-branch-nyc-01
✓Device detected: 10.50.1.10
✓Serial retrieved: FOC2345X1AB
✓ZTP profile matched: branch-access-nyc
✓Firmware upgraded: IOS-XE 17.9.4
...Deploying golden config: branch-access-v3.2
○Post-provisioning validation
Site: NYC Branch OfficeStep 5 of 6

A Different Approach to ZTP

Traditional ZTP relies on DHCP options, TFTP servers, and vendor-specific protocols like Cisco PnP or Juniper ZTP. Setting this up requires infrastructure changes, separate server roles, and a different process per vendor. ConnectMyAssets takes a different approach: the platform detects the device itself, reads its serial number, and drives the entire provisioning from the central appliance. No infrastructure changes. No vendor-by-vendor setup. One workflow for every device on your network.

End-to-End Automated Provisioning

From device detection to production readiness, every step of the provisioning lifecycle is automated and auditable.

🔍

Automatic Device Detection

ConnectMyAssets continuously scans your network for new devices. When a new device is plugged in, the platform detects it within minutes, connects to it, and reads its serial number. No DHCP option configuration, no bootstrap server, no vendor-specific protocol required.

🔑

Serial-Based Identification

Pre-register device serial numbers in ConnectMyAssets before shipping. When the platform detects a new device and reads its serial, it instantly matches it against the pending ZTP queue. Each serial is linked to a site, a golden config template, and a target firmware version, so the platform knows exactly what to deploy.

📋

Golden Config Templates

Maintain a library of approved, production-ready configuration templates. Each template includes variables for site-specific values: management IP, VLAN assignments, OSPF area, BGP AS number. When a ZTP match is found, ConnectMyAssets renders the correct template with the right site variables and pushes it to the device. Templates are version-controlled.

💿

Automatic Firmware Upgrade

The same serial-based detection drives firmware upgrades. ConnectMyAssets reads the current firmware version on the device, compares it against the target version defined for that serial, and stages the upgrade automatically. The device fetches the firmware image from ConnectMyAssets and applies it without any manual intervention.

🏢

Branch Office Deployment

Ship pre-registered devices directly to branch offices. When local staff plug in the device, ConnectMyAssets handles everything from the central platform: detection, serial match, firmware upgrade if needed, configuration push, and validation. No network engineer needs to travel to the site. No phone calls to walk someone through a console cable setup.

✅

Automated Post-Provisioning Validation

After provisioning, ConnectMyAssets runs validation checks: management reachability, running config vs. golden template, firmware version confirmation, and inventory registration. If any check fails, the platform alerts your team with specific diagnostics. Once all checks pass, the device enters production status and joins your regular backup and monitoring cycles.

How It Works

01

Pre-Register Serials

Before the device ships, add its serial number to ConnectMyAssets. Associate it with a site, a golden config template, and a target firmware version. That is everything the platform needs. When the device appears on the network, ConnectMyAssets is already expecting it.

02

Plug In

Local staff connect the device to the network and power it on. No console cable, no CLI access, no technical skills required on site. ConnectMyAssets detects the new device via its network scan, connects to it, reads the serial number, and matches it to the pending ZTP entry.

03

Config & Firmware Pushed, Validated

ConnectMyAssets pushes the target firmware if needed, then deploys the golden config rendered with site-specific variables. The device fetches everything directly from the ConnectMyAssets appliance. Once provisioning completes, automated validation confirms the device is correctly configured and it enters your managed inventory.

FAQ

Frequently Asked Questions

Common questions about Zero Touch Provisioning

How does ConnectMyAssets ZTP work without a DHCP or TFTP server?

ConnectMyAssets uses its own network scanning engine to detect new devices as soon as they are plugged in. It connects to the device, reads its serial number, and matches it against the list of serials pre-registered as pending ZTP. The device then fetches its configuration and firmware directly from the ConnectMyAssets appliance. No DHCP option 66/67, no TFTP server, and no vendor-specific ZTP protocol (Cisco PnP, Juniper ZTP, etc.) is required.

Do I need to configure anything on the network before ZTP works?

The only requirement is that the new device is reachable from the ConnectMyAssets appliance on the network. ConnectMyAssets handles everything else: detection, serial identification, config rendering, and push. The device just needs to be on a subnet that the ConnectMyAssets collector can scan. No changes to your DHCP server, no bootstrap server setup, no vendor portal registration.

How does firmware upgrade work during ZTP?

When ConnectMyAssets detects a new device and matches its serial, it reads the current firmware version. If the running firmware differs from the target version defined for that serial, the platform stages the upgrade automatically. The device fetches the firmware image from the ConnectMyAssets appliance, applies it, and reboots. Once back online, ConnectMyAssets pushes the golden configuration. The same serial-based mechanism is also used for scheduled firmware upgrades on existing managed devices.

How do I deploy devices to remote branch offices with ZTP?

Pre-register the device serial number in ConnectMyAssets, assign a site, a golden config template, and a firmware target. Ship the device to the branch. When local staff plug it in, ConnectMyAssets detects it from the central platform, reads the serial, and pushes the configuration and firmware automatically. No network expertise is required on site. Your central team monitors the entire onboarding process from the ConnectMyAssets dashboard.

What happens if ZTP provisioning fails?

ConnectMyAssets monitors every step of the ZTP workflow. If any step fails, connection refused, serial not found, config syntax error, firmware download error, the platform logs the failure with detailed diagnostics and alerts your team immediately. You can review the failure reason, correct the issue (for example, fix a template variable), and retrigger the provisioning remotely. The device remains in a pending state until provisioning succeeds.

Is ZTP secure? How are configurations and credentials protected?

Security is built into every layer. Credentials used to connect to devices are stored in the ConnectMyAssets RSA-encrypted Vault and never exposed in plaintext. Configuration files are delivered directly from the on-premises appliance to the device, no data transits through any external server or cloud service. Device authentication relies on serial number verification to ensure only pre-registered devices receive configurations. All provisioning activities are logged in an immutable audit trail.

Deploy Network Devices Without Sending Engineers

Plug in a device, ConnectMyAssets detects it, matches the serial, and pushes the right config and firmware automatically. Golden templates, automated firmware upgrades, and post-deployment validation, all from one on-premises appliance.