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

## Host variables
Information that is unique to a specific device should be modeled in the host variable for that device.
Follow the same standards, if possible, as `group_vars`. Have a `host_defaults` section along with all the
other applicable data dictionaries such as `host_vrfs`, `host_vlans`, `host_interfaces`, and
`host_port`_channels. Looking at the data model for one of the distribution layer switches, `DIST01`, a
partial configuration is started for `DIST01` from the coverage provided by the `[CAMPUS-DISTRIBUTION]` `group_vars` data model. Now, complete the unique configurations specific to `DIST01`
using `host_vars`.

The intent is to uniquely identify the device on the network, configure the following features and
options according to corporate standards, and act as a functional building distribution switch in a specific
location on the campus. All multicast, vrfs, vrf list, OSPF routing, VLANs, SVIs, STP root, port-channels, and the physical interfaces on the device must be coded in the data model. 

### `DIST01`
Let's take a look at the host variable `DIST01.YML` file:


# Host variables
Information that is unique to a specific device should be modeled in the host variable for that device.
Follow the same standards, if possible, as `group_vars`. Have a `host_defaults` section along with all the
other applicable data dictionaries such as `host_vrfs`, `host_vlans`, `host_interfaces`, and
`host_port`_channels. Looking at the data model for one of the distribution layer switches, `DIST01`, a
partial configuration is started for `DIST01` from the coverage provided by the `[CAMPUS-DISTRIBUTION]` `group_vars` data model. Now, complete the unique configurations specific to `DIST01`
using `host_vars`.

The intent is to uniquely identify the device on the network, configure the following features and
options according to corporate standards, and act as a functional building distribution switch in a specific
location on the campus. All multicast, vrfs, vrf list, OSPF routing, VLANs, SVIs, STP root, port-channels, and the physical interfaces on the device must be coded in the data model. 

## `DIST01`
Let's take a look at the host variable `DIST01.YML` file:


Let's learn about some of the host variables used in the code configurations.

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

Data Models: Host Variables

Host variables

`DIST01`