Source of truth before automation
Establish one authoritative data source first, then automate.
Automation is only as good as the data it is built on. If network and data centre data is inconsistent, a playbook just spreads errors faster. That is why we first define an authoritative source for each object type, clean up the existing inventory and agree on a naming convention.
Only when the data is correct and maintaining it is part of every change do we build workflows on top of it. This costs time at the start and saves time with every later automation.
- network automation is planned
- network, IP and data centre data is spread across several tools or lists
- audits require a traceable inventory
- the environment is small and rarely changes
- nobody can take long-term ownership of data maintenance
In practice
Introducing NetBox and replacing Excel network documentation
Move network, IP and data centre data from scattered Excel lists into NetBox: cleansed, consistently named and embedded in operations.
Read use caseCI/CD and network automation in air-gapped environments
Control deployments and network changes through pipelines without internet access: traceable and within the classified-information requirements.
Read use caseRelated entries
- Adopt 12NetBox Source of truth for network, IP and data centre data.
- Trial 18Nautobot Source of truth with custom workflows and apps.
- Trial 08Network configuration from the source of truth Generate device configurations from the data in the source of truth.
- Hold 09Excel as the authoritative network documentation Workable as a stopgap, a risk as the environment grows.
History Adopt (New)
Which tools suit your operations?
In an initial call we review your tool landscape and show where a change pays off and where it does not.