However, even though network automation has become increasingly popular, most organizations are still managing their network infrastructure manually by a CLI or GUI. Why is this? By Sean Cavanaugh.
This manual CLI work often means that network engineers are reactive and constantly drowning with break-fix network issues because of manual mis-configurations, or the inability to implement change quickly and efficiently.
Because network engineers are so busy firefighting in their day job, they don’t have time to look at a new activity like automating, even though automation will save them time and money in the long run. I fundamentally believe that network automation is not an all or nothing situation. You need to adopt network automation in small increments so you can earn yourself, and your team more time. In other words, start small and think big. I put together this video to help network engineers brainstorm five great use cases for network automation. This list is not exhaustive; there are many more use-cases that you can do with network automation, but this is meant to give network administrators an idea of what is possible.
The video post contains following sections:
- Configuration backup and restore
- Infrastructure awareness
- Scoped configuration management
- Operational state validation
- Automated netops
The article also contains links to further resources and reading. Whether you are beginning your automation journey or a seasoned veteran, there are a variety of resources to enhance your automation knowledge. Nice one!
[Read More]