A Closer Look: Zero Touch Provisioning Vs Manual Configurations
Our previous post about zero touch provisioning (ZTP) details the basics about what makes ZTP work. You need to have the proper scripting and automation tools, along with a well-designed workflow. These help you test and prepare configurations in a lab environment, and ultimately lead to deployments that are faster, consistent, and automatic.
In this article, we’re going to take a closer look at zero touch provisioning to see how it compares to manual methods of deploying networks.
But first, here’s a recap about ZTP:
- What is it? — Zero touch provisioning automates network configuration tasks, so you can deploy new networks simply by connecting & booting your devices.
- Why use it? — Scaling can be a chore. You need to coordinate so many devices and IT resources, and staff need to be on-site to tediously configure each appliance. ZTP eliminates all of this so you can scale on demand.
- What are the benefits? — On the network side, ZTP eliminates the need for time-consuming, error-prone manual configurations. Using well-tested scripts, you can automate deployments with networks that build themselves quickly, consistently, and reliably. For business, this means a more nimble network edge that can keep up with growth. You get the security of shipping unconfigured devices, the cost savings of reduced on-site support, and the consistency of automation. Deploying takes minutes and gives you the peace of mind knowing that your new networks meet compliance standards.
Now, let’s take a look at common ways of provisioning that you’re probably familiar with, and how zero touch provisioning makes them obsolete.
If you’re not familiar with zero touch provisioning, you know the hassle that comes with manually deploying networks. Once you acquire all of your physical network appliances and IT resources, you need to get them on-site at your new location. This involves coordinating shipments and staff travel plans, which oftentimes leads to waiting periods and expensive delays. Staying on track to meet your timelines can be a joke even before deployment begins.
After tackling the logistical hurdle, the real work starts. Your on-site IT staff must connect to each device separately, and then make configurations using the command line interface (CLI).
- This is time consuming — Connecting to each device requires staff to provide their credentials to gain access. Once they’re granted access, they must manually enter commands into the CLI, which can take minutes or even hours depending on the configuration. This needs to be repeated for each appliance until the entire stack is properly configured and the network can be deployed.
- This leads to errors — Human error is a major contributor to network outages and downtime. Requiring manual input for each network appliance means more chances for mistakes. This could be an overlooked typo on the CLI, installation of an old and incorrect configuration file, or something as simple as mixing up port assignments.
- This burdens your staff — Performing hundreds or even thousands of manual tasks for each deployment requires an extensive, on-site staff presence. Even with an experienced and highly-skilled team, setting up your network can take days’ worth of work and pulls employees away from more business-critical tasks.
Minimal Touch Provisioning
Different methods have been developed to address some of the drawbacks to manual configuration. One of these includes minimal touch provisioning (MTP), which is essentially a process improvement. MTP involves working with a pre-approved set of commands that can be easily pasted, either individually or as a batch, into the CLI. The advantage here is mostly in time savings, as simple copy/paste tasks involve significantly fewer keystrokes than manually entering every command.
However, this minimal touch approach inherits some of the same drawbacks, and introduces its own.
- This still requires on-site staff — MTP doesn’t reduce the need for on-site staff to configure your stacks. As with manual provisioning, setting up using MTP still requires teams to manually input configurations into the CLI. More important business activities must take a back seat while your engineers deploy each new location.
- This still exposes you to errors — A minimal touch approach isn’t without human error. Your IT staff still need to connect separately to each device. And even though they have a predetermined set of commands at their disposal, simple mistakes can happen due to fatigue, forgetfulness, or improper keystrokes.
- This requires extensive testing — MTP requires you to test your configuration in a lab environment before deploying to production networks. This helps you fix potential issues and develop configuration commands that are highly repeatable. However, the drawback is that this extensive work upfront doesn’t eliminate the manual work required for each deployment.
Zero Touch Provisioning
Zero touch provisioning makes the most of scripting and automation. ZTP virtually eliminates all of the issues that come with a manual or minimal touch approach, by combining the right tools with process improvements. There are no headaches involving shipping devices, coordinating staff, or keeping up with deployment schedules.
Of course, preparing configurations requires thorough planning and testing upfront, but you’re left with a network that’s highly nimble and can scale right when you need it.
Here are some reasons why it’s called “zero touch”:
- Scripting and automation carry out all the tasks that are usually delegated to staff for manual input.
- You only need to perform the simple physical tasks — just connect the power & network cables, boot your devices, and then the network builds itself.
- You don’t need specialized staff on-site. All you need is someone to physically install your devices.
Zero touch provisioning also allows you to pinpoint and fix potential human errors in your lab environment. This way you can ensure that all of your commands and configuration files are correct before they’re pushed to your new networks.
What does Nodegrid bring to ZTP?
ZTP comes with several significant benefits for your networking capabilities and your business, from branch locations that can be deployed fast, to the cost savings that come with minimal on-site support. ZPE Systems’ Nodegrid adds even more to your zero touch toolkit so you can get even more from each deployment.
Nodegrid features consolidated, all-in-one network appliances, which means a smaller stack that can handle every network function. You can get on location easier with fewer capital expenses, and reduced shipping costs and travel costs.
On top of this, zero touch provisioning with Nodegrid allows you to push configurations to other devices. This includes devices from many vendors. As long as you properly test and configure your scripts, you can extend your zero touch provisioning capabilities simply by connecting devices to your Nodegrid appliances.
After your initial deployment, your Nodegrid appliances can connect to ZPE Cloud for easy and convenient configuration management. You can eliminate the need to juggle files and updates. ZPE Cloud stores all your config files and supports automation, so you can push changes and make other adjustments automatically, and from the safety of the cloud.