Ansible for Networking - Part 3: Cisco IOS

The third part of my ongoing series of posts on Ansible for Networking will cover Cisco IOS. For the other posts in this series so far, see the Start of the series and The Lab Environment All the playbooks, roles and variables used in this article are available in my Network Automation with Ansible repository Why IOS? Anyone who has worked in the network industry long enough will have encountered Cisco equipment at some point in their career. [Read More]

Ansible for Networking - Part 2: The Lab environment

This is the second part in my ongoing series on using Ansible for Networking, showing how to use Ansible to configure and manage equipment from multiple networking vendors. In the “Start of the series” post, I mentioned that the lab would consist of: - The KVM hypervisor running on Linux A virtual machine, running CentOS 8, that will run: - FRR - Acting as a route server Syslog Tacplus (for TACACS+ integration) Two routers/virtual machines of each vendor, one running as an “edge” router, one running as an “internal” router A control machine that Ansible will run from, over a management network to all machines This post goes through the Hypervisor, setting up the CentOS 8 virtual machine, and the control machine. [Read More]

Ansible for Networking - Part 1: The start of the series

For those who have been reading my posts for a while, they’ll know that while currently I’m a DevOps Engineer, I spent the previous decade managing and configuring service provider networks. For the majority of that time, the network was configured by hand. The closest most people in the industry had to an automation toolset was either using a spreadsheet with variables, their own scripts they had created, or delegating the task to multiple junior engineers. [Read More]