Hello and welcome to module 7 of the NetBox 'Zero-to-Hero' course. In Module 6: Setting up the WiFi, Susan added the required Wireless LANs using some simple Python scripts to interact with the NetBox REST API. In this Module, Eric will use Ansible to extract data from NetBox and then use that data to automate the creation of basic device configurations for the WAN Router (Cisco IOS) and the Access Switch (Juniper JunOS), at the new Brisbane branch office.
By the end of this module you will be able to:
- Set up Ansible to use NetBox as the source of it's Dynamic Inventory
- Write Ansible playbooks to make REST API calls to NetBox and extract the required data to build the device configurations
- Automate the generation of device configuration files using Jinja templates, passing in the data extracted from NetBox as variables
If you'd like to follow along with the examples used in this course, it's super easy to do, and you have a few options:
- Run NetBox as a container with NetBox Docker - This is the quickest way to get your own dedicated NetBox instance going and it only takes a few minutes to spin up on your laptop!
- Follow the official documentation and do a full installation of all the NetBox components. These instructions have been tested on Ubuntu and CentOS Linux.
- Use the public demo instance of NetBox
- Sign up for a free trial of NetBox Cloud (hosted, managed NetBox with enterprise grade capabilities).
The software versions used in the video for this module are:
NetBox v3.3.2Python v3.8.9ansible-core v2.13.4ansible package v6.4.0pynetbox v6.6.2netaddr v0.8.0
Ansible runs on Linux based systems, and is installed as a Python package. Follow these steps to set up Ansible on your own system - it takes less than 5 minutes!
You can use NetBox as the source for the Ansible Inventory (the list of devices you are are automating against), and to use this the file ansible.cfg has the following line added:
inventory = ./netbox_inv.yml
This points to the file ./netbox_inv.yml which in our example looks like this:
plugin: netbox.netbox.nb_inventory
validate_certs: False
group_by:
- device_roles
- sites
So this means that Ansible will now load the inventory dynamically from NetBox and will group the devices by their role and site. You can configure to suit your own requirements, by referring to the docs.
Using templates for network device configurations has many advantages for Network Engineers. First and foremost you get consistency - for example if you standardize your branch office networks so that you use the same device types for all of your WAN Routers and Access Switches, and the connectivity and configuration of them is the same, then the only differences between devices at different sites will be a few 'variables' such as:
- hostname
- IP addresses
- interface descriptions
- VLANs
- Routing protocol information
This means you can write a standard template for each device type, that includes all the static content that every device should have, plus variables for dynamic content that differs per device. An automation tool then simply substitutes the values for a specific device in for the 'variable' placeholders. We'll see this in action in the demo video. This means you KNOW that the configuration you have generated will be error free and consistent across all devices when it is used.
Another huge advantage of using templates is the amount of time it saves - imagine you are deploying a new data center with hundreds of switches that all use a very similar configuration - by using Jinja templates and a tool to render them you can literally generate all the device configurations in seconds. This frees up more of your time to play with that cool new NetDevOps tool you heard about on the Network Automation Nerds podcast!
It should be noted that there are other template languages around, but Jinja aligns well with other tools used in Network Automation such as Python (Jinja was built for Python) and Ansible. We are using Ansible as the automation tool in this tutorial, but you could just as easily use another too like Nornir or just pure Python scripts to achieve the same result.
There are some great Jinja tutorials for network automation out there such as this one, but as a quick intro and example specific to NetBox, let's say we have made an API call to the endpoint /api/dcim/devices/2/ and this returns some json output similar to this
{
"id": 2,
"url": "http://netbox/api/dcim/devices/2/",
"display": "AUBRI01-RTR-1",
"name": "AUBRI01-RTR-1",
"device_type": {
"id": 2,
"url": "http://netbox/api/dcim/device-types/2/",
"display": "ISR4321",
"manufacturer": {
"id": 1,
"url": "http://netbox/api/dcim/manufacturers/1/",
"display": "Cisco",
"name": "Cisco",
"slug": "cisco"
},
"model": "ISR4321",
"slug": "isr4321"
}
}
We can then use the following in a Jinja template to render a config snippet that has a variable for the device hostname:
{% raw %}
!
hostname {{ device.json.results[0]['name'] }}
!
{% endraw %}
The first word hostname is the static content of the config, applicable to all devices and the text between the curly braces {{ }} is the variable. The value being injected dynamically into the template variable is the value of the name key from the json results returned by the request. The end result of this is the final rendered configuration snippet:
!
hostname AUBRI01-RTR-1
!
Jinja templates also have powerful features like loops, logic operators, and string manipulation. Take this JunOS interface template for example:
{% raw %}
{%- for intf in interfaces.json.results %}
{% if 'vlan' in intf.name %}
vlan {
{% for ip in ip_addresses.json.results %}
{%- if ip.assigned_object.name == intf.name %}
unit {{ intf.name.split('.')[1] }} {
family inet {
address {{ ip.address }};
}
}
}
{%- endif %}
{% endfor %}
{% endif %}
{%- endfor %}
{% endraw %}
To explain whats happening here - for each interface intf, if the interface name intf.name contains the the text vlan, then for each of the ip_addresses if the ip.assigned_object_name is equal to the name of the interface intf.name, then insert the value it has for the unit name by splitting the intf.name at the dot . and using the 2nd element of the resulting list (lists in Python start at 0) as the value. Then finally add the value of the ip.address into the variable place-holder for the IPv4 address.
This results in the following configuration snippet being rendered for the interface vlan.50:
vlan {
unit 50 {
family inet {
address 192.168.2.2/26;
}
}
}
At first glance this might seem complicated, but it's really quite straightforward and once you get your first template done the rest will be easy. You can also use the all the templates and playbooks that accompany this course to help get you started.
So, as you can see, automating network device configurations using Jinja templates is already incredibly powerful, but when you combine this with NetBox as the Source Of Truth, you are well on your way to NetDevOps Nirvana!
In the demo Eric will be making use of a NetBox feature called Configuration Contexts. From the official docs:
Configuration context data (or "config contexts" for short) is a powerful feature that enables users to define arbitrary data that applies to device and virtual machines based on certain characteristics. For example, suppose you want to define syslog servers for devices assigned to sites within a particular region. In NetBox, you can create a config context instance containing this data and apply it to the desired region.
The configuration context that Eric is using contains the following data, and it will apply to all devices/VMs in the Asia Pacific Region:
`{
"name-servers": [
"8.8.8.8",
"9.9.9.9"
],
"ntp-servers": [
"192.168.4.10",
"192.168.4.11"
],
"snmp-ro-community": "R34d0nlY",
"syslog-servers": [
"192.168.4.12",
"192.168.4.13"
]
}
This data will be returned in the responses to the calls made by Ansible to NetBox REST API endpoints, and can then be injected dynamically into the Jinja configuration templates, along with all the other device data pulled from NetBox.
Eric has created 3 Jinja templates:
cisco-ios.j2- for the Cisco WAN Routerjuniper-junos.j2- for the Juniper Access Switchjuniper-junos-set.j2- for the Juniper Access Switch but using the Set command format
The data that will be pulled from NetBox to inject into the templates when they are rendered by Ansible is:
- hostname
- ip name servers
- ntp servers
- syslog servers
- snmp community and location
- interfaces
- descriptions
- IP addresses (if L3)
- 802.1Q mode and VLANs (if L2)
- VLANS
Disclaimer The configurations generated in this demo are not production ready by any stretch, and are purely used to illustrate how to extract the data from NetBox as your network source of truth to be consumed by an automation tool (Ansible in this case) to generate example configs. You would need to extend the templates to suit your own device types and configuration requirements, but you can certainly use them as a starting point.
OK, so with all that said - let's get to the fun stuff!! This video will step you through the whole process from setting up NetBox as the source for the Ansible Inventory through to generating the finished configuration files.
If you are following along you can find the Ansible playbooks in the course Git Repository and you can use these as a starting point for building your collection of playbooks for NetBox.
In this module you have learned how to set up Ansible to use NetBox as the source of truth for it's Dynamic Inventory, and how to use Ansible to extract device data from NetBox and use this to automate the generation of device configuration files using Jinja templates.
If you fancy a challenge why not develop these playbooks and templates further and improve them? Maybe you could add descriptions for the switch interfaces and add that logic to the JunOS templates? Maybe you could make them more efficient, or you could try using Nornir or Python instead of Ansible to pull data from NetBox and render the configs.
In Module 8: What About Virtualization? you will learn how NetBox models Virtualization, including Cluster Types, Clusters, Platforms, VM's and VM Interfaces. You will also learn how to model network services and associate them with devices or VM's, along with specific IP addresses.
If you have any questions as you go through the course then pop on over to the NetBox Zero to Hero channel on the NetDev Community Slack! If you aren't already a member then you can sign up for free here.
- Zero To Hero Git Repo
- Official NetBox Documentation
- NetBox Docker
- NetBox Cloud is a hosted solution offered by NetBox Labs