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

# NDLC process
The NDLC process remains the same for making changes to the network:

1. Create a working branch from the master branch for every change.
2. Develop and test code.
3. Commit often.
4. Comment code where applicable.
5. Execute playbook.
6. Perform pull requests to merge approved code changes into the master branch.

Now that there could potentially be an impact on the network because of changes, there is a need to incorporate more traditional network administration personas to evaluate the required Cisco commands. How, where, and in what order commands should be executed, as well as the impact, if any, of the change to the network needs to be assessed. Other considerations such as outage planning for impactful changes or all test plans are required.  An example of outage planning is to consider  possible fail-overs, notifications to impacted users and services, change management, and approvals. . Updates to out of repository information should be included in the approval process such as NMS, diagrams, and legacy documentation.    The process should also include evidence of the new automated documentation and testing that will be performed. Some CLI validation may be required as part of an automated change.

Orchestrate the playbook to gather information about the pre-change state of the network, execute the
changes, and recollect the new post-change state of the network.

# Gather information
Here, execute some of the pre-canned network reconnaissance code. Or, craft new, playbook-specific,
information-gathering code that runs before changing anything. Output these files for use in validating the
change, or roll back if we must back out of a change.

# Execute check mode with verbosity
The most powerful aspect of Ansible is the ability to run playbooks in check mode. Since changes are
being made to the network and that always holds a potentially negative impact, the playbook can be
executed in check mode with verbosity enabled. This lets the playbook identify what is changing, in what order, and on what devices. 
```bash
ansible-playbook network_change.yml --check –v
```

# Execute playbook
After performing a dry run in check mode and validating that the intent is reflected in the output,
execute the playbook and automate the network changes. Remove the check mode option and re-run the
playbook. Verbosity can be enabled to provide a similar view as check mode, with the detailed output of
each task in the playbook and how it is executed.
```bash
ansible-playbook network_change.yml -v
```

# Regather information
Recollect the information about the new state of the network post-change. This output can be
compared to the pre-change output to validate the success of the change, and the impact the change may
have on routing tables or other information on the network. 

Let's learn about the new process involved when handling tactical playbooks.

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

Process

NDLC process