Book Image

Practical Network Automation - Second Edition

By : Abhishek Ratan
Book Image

Practical Network Automation - Second Edition

By: Abhishek Ratan

Overview of this book

Network automation is the use of IT controls to supervise and carry out everyday network management functions. It plays a key role in network virtualization technologies and network functions. The book starts by providing an introduction to network automation, and its applications, which include integrating DevOps tools to automate the network efficiently. It then guides you through different network automation tasks and covers various data digging and performing tasks such as ensuring golden state configurations using templates, interface parsing. This book also focuses on Intelligent Operations using Artificial Intelligence and troubleshooting using chatbots and voice commands. The book then moves on to the use of Python and the management of SSH keys for machine-to-machine (M2M) communication, all followed by practical use cases. The book also covers the importance of Ansible for network automation, including best practices in automation; ways to test automated networks using tools such as Puppet, SaltStack, and Chef; and other important techniques. Through practical use-cases and examples, this book will acquaint you with the various aspects of network automation. It will give you the solid foundation you need to automate your own network without any hassle.
Table of Contents (9 chapters)

Sample use case

Let's see an example of consuming the Splunk API to be used through voice interaction using Alexa. This can be extended to perform hands-free troubleshooting and remediation through voice interactions, which means an engineer does not need to be physically present at a particular location to perform network operations.

In this example, we ask Alexa to show us any routers that have the management (Loopback45) interface down on the router. Alexa will call the Ops API (endpoint of the API web framework), which in turn will interact with Splunk to fetch the status of the Loopback45 interface for all routers, and would respond with the name of the router that has an interface down.

For our example, we have turned down the Loopback45 interface on rtr1. It is up and functioning on other routers (rtr2, rtr3, and rtr4).

Here are the steps to implement/configure troubleshooting...