You're reading from Network Automation with Nautobot Adopt a network source of truth and a data-driven approach to networking

Product type Paperback

Published in May 2024

Publisher Packt

ISBN-13 9781837637867

Length 816 pages

Edition 1st Edition

Languages

Python

Tools

Ansible

Concepts

Network Automation

Authors (9):

Ken Celenza

John Anderson

Gary Snider

Jason Edelman

Brad Haas

Glenn Matthews

Bryan Culver

Christian Adell

Josh VanDeraa

+5 more

View More author details

Table of Contents (26) Chapters

Preface

1. Part 1: Introduction to Source of Truth and Nautobot

2. Chapter 1: Introduction to Nautobot FREE CHAPTER

3. Chapter 2: Nautobot Data Models

4. Part 2: Getting Started with Nautobot

5. Chapter 3: Installing and Deploying Nautobot

6. Chapter 4: Understanding the User Interface and Bootstrapping Nautobot

7. Chapter 5: Configuring Nautobot Core Data Models

8. Chapter 6: Using Nautobot’s Extensibility Features

9. Chapter 7: Managing and Administering Nautobot

10. Part 3: Network Automation with Nautobot

11. Chapter 8: Learning about Nautobot APIs – REST, GraphQL, and Webhooks

12. Chapter 9: Understanding Nautobot Integrations for NetDevOps Pipelines

13. Chapter 10: Embracing Infrastructure as Code with Nautobot, Git, and Ansible

14. Chapter 11: Automating Networks with Nautobot Jobs

15. Chapter 12: Data-Driven Network Automation Architecture

16. Part 4: Nautobot Apps

17. Chapter 13: Learning about the Nautobot App Ecosystem

18. Chapter 14: Intro to Nautobot App Development

19. Chapter 15: Building Nautobot Data Models

20. Chapter 16: Automating with Nautobot Apps

21. Index

Why subscribe?

22. Other Books You May Enjoy

Appendix 1: Nautobot Architecture

1. Appendix 2: Integrating Distributed Data Sources of Truth with Nautobot

2. Appendix 3: Performing Config Compliance and Remediation with Nautobot

Backing up network devices

The next step is to use the inventory file we just tested (nautobot-inventory-01.yml) and verified with ansible-inventory to connect to those devices and perform a backup. Make sure to start small and expand from there. Starting small here is just performing configuration backup.

The nice thing about this is we can use a single multi-vendor Ansible core module, as shown here:

   - name: "BACKUP ALL CONFIGURATIONS"      ansible.netcommon.cli_config:
        backup: true
        backup_options:
          filename: "{{ ansible_host }}.cfg"
          dir_path: "{{ backups_dir }}/"

The backups_dir directory is a directory defined earlier in the playbook. Be sure to look at it on your filesystem or in...