Lab 06 - Modeling IPAM

Lab Overview

It's time for some IPAM (IP Address Management)! We are going to be creating VLANs, importing Prefixes and IP Addresses as well as creating our own CSV file.

Table of Contents

Lab 06 - Modeling IPAM

• Task 1 - Create new Prefix/VLAN Roles
  • Step 1-1 - Login via the web browser to Nautobot
  • Step 1-2 - Create new Prefix/VLAN Roles with the web form
• Task 2 - Import and create VLANs
  • Step 2-1 - Find 09_nautobot_VLANs.csv in the files subdirectory
  • Step 2-2 - Import the VLANs
  • Step 2-3 - Create VLANs with the web form
  • Step 2-4 - Associate a VLAN with an Interface
• Task 3 - Import Prefixes
  • Step 3-1 - Find 10_nautobot_prefixes.csv in the files subdirectory
  • Step 3-2 - Import Prefixes
• Task 4 - Import IP Addresses
  • Step 4-1 - Find 11_nautobot_ip_addresses.csv in the files subdirectory
  • Step 4-2 - Import IP Addresses
• Task 5 - Review IP Address utilization and details
  • Step 5-1 View IP Address Utilization
  • Step 5-2 - Step 5-2 Investigate the details
• Task 6 - Create Prefixes and IP Addresses for your Stadium
• Task 7 - Review the imported and manually-entered results
  • Step 7-1 - Find the tenant
  • Step 7-2 - Review the Tenant stats

Task 1 - Create new Prefix/VLAN Roles

Step 1-1 - Login via the web browser to Nautobot

If you have not already, use a web browser to navigate to your instance of Nautobot at https://{{ your pod }}. We will be using the Nautobot GUI for the remainder of this lab so there won't be a need for a terminal. Log into Nautobot by using the login option in the upper right of the Nautobot homepage. You can log in as the superuser you created in a previous lab or the superuser account included with your lab environment, the credentials for this account will be provided by the instructor.

Step 1-2 - Create new Prefix/VLAN Roles with the web form

A Role indicates the function of a prefix or VLAN. Before creating a Prefixes it is recommended, but not required, to create Roles. Click on the IPAM menu drop down and select Previx/VLAN Roles. A CSV file with common Roles is included in the files folder, 08_nautobot_ipan_roles.csv, but these Roles have already been included in the dataset for this lab. So, let's create some new Roles. Click on the blue Add button in the upper right of the Roles list view.

There isn't much to this form, just Name, Slug, Weight. We haven't discussed weight yet. In general, it means the order in which something is shown or processed, lower numbers first. This can be quite significant when dealing with something like Configuration Contexts, but in this case it simply controls the order of the Roles in forms and the list view. Items that have a matching weight are ordered alphabetically. Practice creating Prefix/VLAN Roles by adding two new Roles with the following attributes:

• Name: Voice
• Slug: voice

• Weight 2000

• Name: Security

• Slug: security
• Weight 3000

To speed up the creation of new objects, after completing the form, click on Create and Add Another.

After creating the new Roles, if you return to the Prefix/VLAN Roles list view, you'll notice Voice and Security are at the bottom of the list because of the higher weights. The roles will also appear in this same order when selecting a Prefix/VLAN role from a web form.

Task 2 - Import and create VLANs

First a few details about VLAN objects in Nautobot.

Each VLAN may be assigned to a Site, Tenant, and/or VLAN group.
Each VLAN must be assigned a Status. The following statuses are available by default:

• Active
• Reserved
• Deprecated

In general, VLANs can have overlapping names and IDs. The exception to this is VLANs within a VLAN Group: each VLAN within a group must have a unique ID and name.

A VLAN Group may be assigned to a specific site, but a Group cannot belong to multiple sites. VLANs may be assigned to a specific site as well.

Step 2-1 - Find 09_nautobot_VLANs.csv in the files subdirectory

Under the files subdirectory on your pod, one of the sample data files is 09_nautobot_VLANs.csv. If you look at the data for the VLANs in this CSV file, you will see that each VLAN is being assigned to a Site, which gives them site-specific-scope. VLANs assigned to a particular Site cannot be added to Devices belonging to a different Site. If we had instead left these VLANs unassigned, they would have been put into the global-scope and could be added to a Device at any Site.

Step 2-2 - Import the VLANs

Select the IPAM drop down menu from the top of the page and click the blue import button next to VLANs. Import the VLANs listed on 09_nautobot_VLANs.csv by either uploading the file or copy/pasting the data into the form. If successful, you should see the following confirmation page:

Step 2-3 - Create VLANs with the web form

In this step we will create two VLANs, it would be tedious to create a full set that matches the VLANs imported in the previous step and creating two is enough to demonstrate the process. Click on the IPAM drop down menu and select the green button next to VLANs.

Create two VLANs with the attributes listed below, substituting values based on your Site if necessary. Note that the Security and Voice roles appear at the bottom of the list in the form. Don't forget to use the Create and Add Another button to speed up the process.

• ID: 99
• Name: hou01-101-mgmt
• Status: Active
• Role: mgmt
• Region: Texas
• Site: HOU01

• Tenant: Nautobot Football Stadiums

• ID: 1000

• Name: hou01-101-server-server
• Status: Active
• Role: server
• Region: Texas
• Site: HOU01
• Tenant: Nautobot Football Stadiums

Step 2-4 - Associate a VLAN with an Interface

Click on the Devices drop down menu and select Devices. Use the search box in the upper right to find the Devices you created, in my case a search for hou01 did the trick.

Click on the name of the edge device, which should be of Type Arista DCS-7280CR2-60, this will take you to the detail page for that device.

This Device instance has 61 interfaces, you can confirm this by looking at the Interfaces tab just under the name at the top of the page. Click on that tab to see the list of Interfaces.

Scroll to the bottom of the list and click the yellow pencil on the Managment1 Interface to edit the details of this interface.

Scroll down the form until you see the 802.1Q Switching section, add the attributes below and save the form. You'll notice only VLANs in the correct scope appear in the form.

• 802.1Q Mode: Access
• Untagged VLAN: hou01-101-mgmt

Return to the VLANs list page by clicking on the IPAM drop down menu and selecting VLANs. Use the search box in the upper right to search for the newly associated VLAN. Once again hou01 worked for me as the name of the VLANs I created both start with hou01. Click on the ID of the VLAN, in my case 99, to go to the detail page for that VLAN.

Click on the Device Interfaces tab to see which Interfaces have been associated with the VLAN. The Interface can even be edited right from this page by clicking the yellow pencil icon.

Task 3 - Import Prefixes

A prefix is an IPv4 or IPv6 network and mask expressed in CIDR notation (e.g. 192.0.2.0/24). A prefix entails only the "network portion" of an IP address: All bits in the address not covered by the mask must be zero. (In other words, a prefix cannot be a specific IP address.)

Nautobot will organize prefixes and show total utilization of IP addresses. Let's add a few and then upload some IP Addresses to see how they are reported by Nautobot.

Step 3-1 - Find 10_nautobot_prefixes.csv in the files subdirectory

Under the files subdirectory on your pod, one of the sample data files is 10_nautobot_prefixes.csv. Open it up and take a look at the Prefix data. For this simple example, we'll be adding a handful of Prefixes with the following fields: prefix, status, tenant, site, role.

Step 3-2 - Import Prefixes

Select the IPAM drop down menu from the top of the page and click the blue import button next to Prefixes. Import the Prefixes listed on 10_nautobot_prefixes.csv by either uploading the file or copy/pasting the data into the form. If successful, you should see the following confirmation page:

Task 4 - Import IP Addresses

Step 4-1 - Find 11_nautobot_ip_addresses.csv in the files subdirectory

Under the files subdirectory on your pod, one of the sample data files is 11_nautobot_ip_addresses.csv. Open it and take a look at the IP Address data. Looking at the two rightmost columns, you can see each IP Address is being assigned to a specific Interface on a Device.

Step 4-2 - Import IP Addresses

Select the IPAM drop down menu from the top of the page and click the blue import button next to IP Addresses. Import the IP Addresses listed on 10_nautobot_ip_addresses.csv by either uploading the file or copy/pasting the data into the form. There are 148 IP Addresses to import, so it may take a few seconds to complete. If successful, you should see the following confirmation page:

Task 5 - Review IP Address utilization and details

Step 5-1 View IP Address Utilization

Click on the IPAM drop down menu at the top of the page and select Prefixes top open the Prefix list view. Filter the view to only show the Nautobot Football Stadiums Tenant. Once the list is Filtered you should see something like the image below.

The total utilization for the Prefix is given Prefix is provided as a percent, and you can easily see the assigned Tenant, Site and Role. The Container status is merely a summary of all the children of that container. Here is a list of the Statues that are built into Nautobot:

• Container - A summary of child prefixes
• Active - Provisioned and in use
• Reserved - Designated for future use
• Deprecated - No longer in use

Step 5-2 Investigate the details

Click on the Prefix 10.41.0.0/24 to open its detail page. Here, you can see additional details for just this Prefix.

You may be wondering what Is a pool means. If enabled, Nautobot will treat this prefix as a range (such as a NAT pool) wherein every IP address is valid and assignable. This logic is used when identifying available IP addresses within a prefix. If this flag is disabled, Nautobot will assume that the first and last (broadcast) address within an IPv4 prefix are unusable.

Click the IP Addresses tab at the top and select any IP Address associated with this Prefix. This will take you to the detail page for a single IP Address. There is a great deal of information here including a full list of related IP Addresses.

Task 6 - Create Prefixes and IP Addresses for your Stadium

Time for some practice. Create and import CSV data for your stadium, using the Prefix and IP Address CSV files as a template. If you get stuck the answers for the HOU01 stadium are included in the files directory (files 15 and 16). The idea here is to get familiar with Nautobot IPAM, and the more practice, the better!

Task 7 - Review the imported and manually-entered results

Step 7-1 - Find the tenant

Return to the Tenants list by clicking on the Organization drop down menu and selecting Tenants. From this list click on Nautobot Football Stadiums to view the detail page for that Tenant.

Step 7-2 - Review the Tenant stats

The total number of IP Addresses and Prefixes may vary depending on how many you chose to include in the previous task.