Gain insights into automating network reconnaissance, orchestrating repetitive changes, and transforming network configuration management. Discover CI/CD pipeline migration for full network automation.

ansibleFinal1.tar.gz

gitjob

CIPhosts

CIPhosts-copy

gather_info

gather_important_facts

facts_to_md

facts_to_csv_html

tools

frr01

frr02

first_gather_important_facts

​​Network automation begins with automating network reconnaissance. This is accomplished by gathering important information from network devices while building a library of dynamic on-demand utilities and generating living documentation. Starting small, the course exhibits the simplicity and elegance of network automation.

Next, you will learn how to automate larger changes that require a high number of repetitive steps. These changes will be executed serially in a specific orchestrated order, making them perfect for an automated solution. After gaining comfort with the new tools, you can fully transform network configuration management to an automated, intent-based, self-documenting system.

The final step is learning how to migrate to a continuous integration/continuous delivery (CI/CD) pipeline, thereby fully automating the network.

Automate Your Network

The impact of automation on IT should not be underestimated. It involves a lot of changes and learning. It is not just the tools or new file types or data formats. The very mindset of IT itself,  not just the tools and new file types or data formats, can be very hard to change. The acceptance of innovation is often opposed by risk adversity and natural resistance to change. Network automation will absolutely lead to changes in core processes for change management and network operations. For example, the automation of network maintenance could mean some restructuring or refocusing of staff. 

Manual intervention is the only thing that can break network automation. Manual changes are in direct contrast with intent-based networks and will be overwritten by the automation solutions. Therefore, it is essential that everyone involved with the network fully understands and agrees with the new direction and processes. With that said,  it is important to strike a balance. In an emergency, the CLI can never be replaced. However, organizations must be sure to track all out-of-band changes applied to fix the issue. These changes should be included in the code repository as an out-of-band emergency branch. Similarly, all the manual emergency changes should be captured and incorporated into the repository.


Let's look at the impact that automation will have on IT.

Introduction

What Is Network Automation?

Why Automate the Network?

How to Automate the Network

Where to Start with Network Automation

Repository Structure

Network Reconnaissance

Tactical Playbooks

Data Models and Dynamic Templates

Dynamic Intent-Based Documentation

Configuration Management

Continuous Integration/Continuous Delivery

Conclusion

Impact on IT