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

This lesson uses the same topology as the [Hands-On: Display FRR facts](https://www.educative.io/courses/automate-your-network/hands-on-display-frr-facts) lesson. Instead of displaying the facts for the FRR routers on the console, this time we will be storing their configuration details in a simple text file.


# FRR on Ansible
The playbooks in this lesson use the `frr.frr` ansible module to query information from FRR routers. 

We are using SSH to connect to the routers. 

The `save_config.yml` file is a playbook that saves the current configuration for all routers into a `config` directory. The playbook creates this directory itself. A separate `.txt` file, named after the router's hostname, is created for each router in the inventory as well. 

For instance, if a router's hostname is `172.20.20.2`, a file `config/172.20.20.2_config.txt` will be created. 

The playbook uses the super-simple `Templates/Config.j2` template to save the configuration to text files. 

Other ansible values that one may query are listed in the [frr.frr.frr_facts documentation](https://github.com/ansible-collections/frr.frr/blob/main/docs/frr.frr.frr_facts_module.rst). Some examples include:

- `ansible_net_version`: The FRR version on the device
- `ansible_net_mem_stats`: Memory statistics for the device
- `ansible_net_hostname`: The hostname of the device


# Running the playbook
In the example below, we have six devices on our network: `PC1`, `PC2`, and `PC3` grouped under `PCs`, and `router1`, `router2`, `router3` grouped under `routers`. 

Let's take a look at how we can gather information about our FRR devices using ansible.


Running the widget at the end of this lesson will automatically run the command:
```
ansible-playbook save_config.yml
```
This will run the `save_config.yml` playbook for all devices in the `routers` group.


To limit the output to just a single device, we can add the `--limit` flag and provide the IPv4 address of the device we want to single out. 

We can get the IPv4 addresses of our devices by using:
```
cat /etc/ansible/hosts
```

An example of running the playbook with the `--limit` flag is as follows:
```bash
ansible-playbook save_config.yml --limit 172.20.20.2
```
This will limit the task to the device with the provided IP.


> If we want to modify and re-run the playbooks, we can use a console-based text editor (Vim, nano) in the terminal window. Then, re-issue the `ansible-playbook` command. If you modify the playbooks in the widget's graphical editor, press **"Run"** to update the underlying container with your updated file(s).

Try it out in the widget below:

Let's learn how to use Ansible to retrieve and store configuration details for FRR routers.

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

Hands-On: Save FRR Configuration