Categories

Category cover

Automation
155 posts

Category cover

Learning paths
119 posts

Category cover

CISO
22 posts

Category cover

Security
20 posts

Category cover

Notes
19 posts

Category cover

Personal Security
18 posts

Category cover

Infrastructure
12 posts

Category cover

OT/ICS
5 posts

Category cover

Books
3 posts

Category cover

UNetLab
3 posts

Category cover

Write-up
3 posts

Category cover

OSInt
2 posts

Category cover

My life
1 posts

Populating our SSOT with Automation

Andrea Dainese
July 10, 2024
Post cover

Now, we need to populate our Single Source of Truth (SSOT). Manually adding interfaces for each device is impractical. Hence, automating this process by reading device configurations and creating corresponding SSOT objects is essential.

Currently, there’s no official system for automatic device discovery. This led me to develop NetDoc  years ago, though it’s currently exclusive to Netbox.

Let’s create a simple automation to efficiently handle this task.

Tools We’ll Use:

Assuming the device is manually created in our SSOT for convenience, our automation will focus solely on populating interfaces.

Let’s proceed step-by-step to develop our automation.

Parameters Needed for Our Automation

Our automation requires the following parameters to function effectively:

  • nautobot_base_url: The URL to access Nautobot.
  • nautobot_apikey: The API key for making REST API requests to Nautobot.
  • host: The IP address of the physical device to be read.
  • username: The username used to access the physical device.
  • password: The password used to access the physical device.

You can create the API key on Nautobot by navigating to User -> Profile -> API Tokens -> Add a token.

Continue reading the post on Patreon .