CLI For Network Changes? Welcome To 2005.


To analyze the current trends in network automation, we ran a survey that included over 550 enterprises from around the world and across industries. One of the questions asked was, “What is the primary method of making network changes in the environment,” for which the response given by half of the participants was “CLI on individual devices.

While this may have been perfectly alright fifteen years ago, it’s definitely a big no-no at this age and at this time. Digital Transformation has caught hold of DevOps with an iron grip, and applications are being churned, modified, and updated at an unprecedented rate. Every change that happens at the application layer involves the network. Logging into each device in the network and making edits on its CLI is anticlimactic – imagine making the application team wait a week because you need to prepare the network for the change. Making network changes through CLI is a major impediment to the ideals of speed, agility, and innovation that Digital Transformation espouses.

33.3% of respondents use the respective vendor’s network management solution to make network changes. While this is undoubtedly better than CLI (especially as most of these solutions are GUI-based), the total cost attached to investing in each of these solutions is prohibitory. Also, this is a classic example of vendor lock-in, which again stifles innovation.

What are the other methods by which the rest of the enterprises make network changes? And are they effective? Read all about it in the State Of Network Automation 2020 report. Get your free copy here.

Related Articles:   How to Migrate a VIP from One Environment to Another Faster

Want more great content?

Subscribe to our blog to get tech tips, industry news, and thought leadership articles right in your inbox!