Book Image

Mastering Python Networking - Fourth Edition

By : Eric Chou
Book Image

Mastering Python Networking - Fourth Edition

By: Eric Chou

Overview of this book

Networks in your infrastructure set the foundation for how your application can be deployed, maintained, and serviced. Python is the ideal language for network engineers to explore tools that were previously available to systems engineers and application developers. In Mastering Python Networking, Fourth edition, you'll embark on a Python-based journey to transition from a traditional network engineer to a network developer ready for the next generation of networks. This new edition is completely revised and updated to work with the latest Python features and DevOps frameworks. In addition to new chapters on introducing Docker containers and Python 3 Async IO for network engineers, each chapter is updated with the latest libraries with working examples to ensure compatibility and understanding of the concepts. Starting with a basic overview of Python, the book teaches you how it can interact with both legacy and API-enabled network devices. You will learn to leverage high-level Python packages and frameworks to perform network automation tasks, monitoring, management, and enhanced network security, followed by AWS and Azure cloud networking. You will use Git for code management, GitLab for continuous integration, and Python-based testing tools to verify your network.
Table of Contents (19 chapters)
17
Other Books You May Enjoy
18
Index

Lab topology

For the network lab, we will reuse the network topology we used in Chapter 8Network Monitoring with Python – Part 2. The network gear will have the management interfaces in the 192.168.2.0/24 management network with the interconnections in the 10.0.0.0/8 network and the subnets in /30s.

Where can we install the ELK Stack in the lab? In production, we should run the ELK stack in a dedicated cluster. In our lab, however, we can quickly spin up a testing instance via Docker containers. If a refresher of Docker is needed, please refer to Chapter 5, Docker Containers for Network Engineers.

Following is a graphical representation of our network lab topology:

Figure 1: Lab topology
Device Management IP Loopback IP
r1 192.168.2.218 192.168.0.1
r2 192.168.2.219 192.168.0.2
r3 192.168.2.220 192.168.0.3
r5 192.168.2.221 192.168.0.4
r6 192.168.2.222 192.168.0.5

The Ubuntu hosts information is as follows:

Device Name...