Sponsored By: Itential
There are many different components involved in network automation, including application programming interfaces (APIs), operating systems, scripting languages, data modeling languages, templating languages, system admin tools, and new DevOps methodologies.
As service providers and enterprises start to expand their automation strategies, they rapidly move from scripting to orchestration. But this too can have its limitations, and more importantly, can entail significant investment. This paper outlines an alternative approach to developing a network automation strategy, one that is devised top-down, based on user stories and workflows, rather than bottom-up, based on the tools and systems needed to automate such workflows.
- Device provisioning – using templates (such as Ansible or Salt) with configuration parameter files (written in languages such as YAML) to generate consistent config files
- Data collection – using open source tools to pull the data you want from network devices, not just what your existing monitoring tools allow
- Configuration validation – checking security compliance and automatically triggering
remediation if there is a violation
- Troubleshooting – automating the analysis of fault and performance data to find root causes
more quickly and reliably, and to predict future issues
Download this white paper to read more about how to develop and expand your network automation strategy.