Advanced NetBox IPAM Setup for Network Engineering Teams – 2026 Edition
In this NetBox IPAM tutorial, we cover how to turn NetBox into a reliable, automatically updated source of truth for IP address management — including prefixes, VRFs, interface assignments, and VLANs — without manual data entry.
We use Simple-Facts, an open-source discovery and sync tool, to automate the entire workflow from network scanning to NetBox population.
The primary challenge with NetBox isn’t the software itself, but the human element required to maintain it. In many organizations, NetBox begins as a pristine database but quickly devolves into a read-only archive. Because network engineers are often stretched thin, the manual overhead of documenting every new prefix or VRF assignment becomes a secondary priority. When documentation relies on manual entry, a single week of rapid changes can lead to spreadsheet drift, where the reality of the wire no longer matches the records in the database.
This lack of real-time accuracy creates a dangerous ripple effect. Without a trustworthy source of truth, automated workflows become risky to execute, as they may be operating on stale data. Furthermore, incident response slows down significantly when engineers have to double-check IP-to-device mappings manually during a crisis. By identifying these friction points, it becomes clear that automation isn’t just a luxury; it is a necessity for maintaining NetBox as a living, reliable resource.
Even after deploying NetBox, teams struggle with:
Result: NetBox becomes another stale database instead of the single source of truth.
The primary aim of this guide is to demonstrate a streamlined, low-friction workflow using Simple-Facts to bridge the gap between your live network and your documentation. Rather than suggesting a complete organizational overhaul, this tutorial provides a practical proof-of-concept for automating the discovery of IPv4 addresses, prefixes, and VRF contexts. By highlighting how a single tool can parse device configurations and populate NetBox in minutes, we illustrate a clear, repeatable path to maintaining a “living” source of truth without the burden of manual data entry.
After following these steps, you will have:
Time estimate: Initial setup + pilot = 1–2 days. Full population of 100–300 devices = under 15 minutes.
# Recommended: use uv for fast, isolated installs
uv venv
source .venv/bin/activate
uv pip install git+https://gitlab.com/netodata/simple-facts.git
# Alternative: classic pip
pip install git+https://gitlab.com/netodata/simple-facts.gitVerify:
sfacts --versionCreate ~/.sfacts/config.yaml (or use environment variables):
netbox:
url: https://netbox.yourcompany.com
token: YOUR_NETBOX_API_TOKEN
verify_ssl: true # set false only for self-signed certs in labTest connection:
sfacts netbox testStart with a known subnet (management, server, loopback, etc.):
sfacts discover --subnet 10.10.10.0/24 --output discovery-mgmt.json
# or scan multiple subnets
sfacts discover --subnet 10.10.10.0/24 --subnet 172.16.0.0/16 --output discovery.jsonThis performs ARP + basic SNMP/SSH probes to find live devices.
sfacts facts --input discovery.json --output facts.jsonThis step connects via Netmiko (SSH) and parses output using TextFSM/ntc-templates.
Collected data includes:
Before committing changes to your production database, the dry-run serves as a critical safety net for network state synchronization. This phase allows you to simulate the entire population process, generating a detailed preview of exactly how Simple-Facts intends to modify your NetBox records. It is the moment where you can catch potential logic errors, such as incorrect VRF mappings or misidentified device types, without the risk of corrupting your existing data or creating duplicate entries.
By carefully reviewing this output, you can verify that the tool is correctly interpreting your network’s hierarchy, from parent prefixes down to individual interface assignments. This “look before you leap” approach builds confidence in the automation, ensuring that when you finally execute the real sync, the resulting NetBox state is a precise, clean reflection of your actual infrastructure. It effectively transforms a high-risk data migration into a predictable, verifiable administrative task.
sfacts netbox sync \
--input facts.json \
--site-name "Production DC1" \
--dry-run \
--verboseReview output:
Once the dry-run confirms everything is in order, executing the real sync pushes the discovered data into NetBox, instantly transforming it from an empty shell into a populated source of truth. This step automatically creates and links devices, interfaces, IPs, and VRFs, effectively digitizing your network’s current state. Within minutes, your IPAM tables move from stale or nonexistent to a high-fidelity map of your infrastructure, ready to support audits and automation.
sfacts netbox sync \
--input facts.json \
--site-name "Production DC1" \
--role router # optional: set default role if not auto-detectedAfter sync:
Create a simple cron job:
# /etc/cron.d/sfacts-daily
0 5 * * * root cd /opt/sfacts && \
sfacts discover --subnet 10.0.0.0/8 --output /var/run/sfacts/discovery.json && \
sfacts facts --input /var/run/sfacts/discovery.json --output /var/run/sfacts/facts.json && \
sfacts netbox sync --input /var/run/sfacts/facts.json --site-name "Production" >> /var/log/sfacts.log 2>&1Add error alerting (e.g., via healthchecks.io or simple email script).
By automating the data pipeline, you unlock NetBox’s most powerful capabilities that are often too complex to maintain manually. This setup natively supports VRF-aware overlapping IPs, allowing you to manage identical subnets across different customer or tenant contexts without database conflicts. Furthermore, it builds a dynamic prefix hierarchy, providing instant visibility into IP utilization and “free” space, which enables your team to use the NetBox API for self-service IP requests and safer, data-driven automation.
show run / show ip vrf--workers 10Start small: pilot one subnet → measure time savings → scale. This NetBox IPAM tutorial workflow eliminates manual toil and makes NetBox the living source of truth your automation deserves.
