Book Image

Network Automation Cookbook

By : Karim Okasha
Book Image

Network Automation Cookbook

By: Karim Okasha

Overview of this book

Network Automation Cookbook is designed to help system administrators, network engineers, and infrastructure automation engineers to centrally manage switches, routers, and other devices in their organization's network. This book will help you gain hands-on experience in automating enterprise networks and take you through core network automation techniques using the latest version of Ansible and Python. With the help of practical recipes, you'll learn how to build a network infrastructure that can be easily managed and updated as it scales through a large number of devices. You'll also cover topics related to security automation and get to grips with essential techniques to maintain network robustness. As you make progress, the book will show you how to automate networks on public cloud providers such as AWS, Google Cloud Platform, and Azure. Finally, you will get up and running with Ansible 2.9 and discover troubleshooting techniques and network automation best practices. By the end of this book, you'll be able to use Ansible to automate modern network devices and integrate third-party tools such as NAPALM, NetBox, and Batfish easily to build robust network automation solutions.
Table of Contents (15 chapters)

Administering a Multi-Vendor Network with NAPALM and Ansible

Network Automation and Programmability Abstraction Layer with Multivendor support (NAPALM), as the name implies, is a multi-vendor Python library intended to interact with different vendor equipment, and it provides a consistent method to interact with all these devices, irrespective of the vendor equipment used.

In previous chapters, we have seen how to interact with different network devices using Ansible. However, for each vendor OS, we had to use a different Ansible module to support that specific OS. Furthermore, we saw that the data returned from each vendor OS is completely different. Although writing a playbook for multi-vendor devices is still possible, it requires the use of multiple different modules, and we need to work with the different data structures returned by these devices. This is the main issue that...