"We don't have time for network automation."(You can't afford not to.)

Tobias Johansson
3 days ago
4 min read

We hear this very often from our customers as well.

For most IT organizations, the reality is messy:

Small teams
Heavy operational workload
Even more technical debt

So even if the motivation is there, network automation often gets postponed:“Later, when we have more resources.”

But here’s the point:

It’s not when you have time that you need network automation – it’s when you don’t.

Lack of resources? You're not alone.

In fact, you're part of the majority.

A global study from Juniper found that:

59% of network engineers don’t have time to learn automation tools
54% lack the necessary background knowledge
50% don’t have management support for automation

According to Gartner, fewer than 10% of companies today have automated more than half of their network operations – but that number is expected to rise to 30% by 2026.

The good news? You don’t need a “perfectly clean” environment to take the first step.All you need is a clear why – and an idea of what would actually save your team time.

Where to start? Small steps, big wins.

We've helped many teams get started without million-dollar budgets or large automation departments.

Here are a few examples of tasks our customers have automated – with minimal effort and major impact:

⚙️ Config backups

Automatically back up all router and switch configs every night. Sounds basic – but it brings peace of mind and saves time.

→ Tools: Ansible, RANCID, custom Python scripts

⚙️ Device inventory & documentation

Centralizing network data in a tool like NetBox creates your “source of truth.” This gives you visibility and structure to enable further automation.

→ Tools: NetBox, Oxidized, CMDB integrations

⚙️ Standard changes

Need to add a VLAN, update an ACL, or deploy new QoS profiles? Script it once – reuse it forever.

→ Tools: Ansible, Nornir, NSO

More beginner-friendly automation ideas

If you're ready to go a step further, here are other good starting points:

Collect device data (e.g., CDP neighbors, routing tables, active interfaces, software versions, licenses, hardware models) and feed it into your IaC/SoT system.
Build standardized device configurations to ensure consistency.
Schedule regular config backups and compare versions to detect changes.
Generate reports on non-compliant devices to ensure standards are met.
Validate that devices meet security policies to reduce risk.
Add devices to monitoring and management systems for better visibility.
Integrate devices into your CMDB for improved documentation.
Push config changes to multiple devices simultaneously.
Validate configs before deployment – ideally in a lab setup (e.g., Containerlab).
Automate software updates to keep systems current.
Standardize troubleshooting procedures for faster resolution.
Run pre/post-change tests to ensure stability.

Simple, powerful tools to start with

You don’t need to build your own automation framework from scratch.

There are plenty of proven tools – open source and commercial – to help you take the first step. Here are a few we often recommend:

🛠️ Ansible

A favorite among network teams. Great for automating tasks like backups, config changes, and provisioning. No advanced coding – just human-readable YAML playbooks. Supported by Cisco, Juniper, Arista, and more.

🛠️ NetBox

An open-source “source of truth” for networks. Store data on devices, links, and IPs to drive informed automation based on accurate information.

🛠️ Nornir

A bit more technical than Ansible, but extremely flexible if you want Python-based control. Great for custom environments.

🛠️ Cisco NSO (Network Services Orchestrator)

A model-based orchestration platform for multi-vendor environments. Ideal for organizations that want structured, service-driven configuration management.

🛠️ Nokia EDA (Event-Driven Automation)

Perfect if you want to trigger automation based on real-time events. Execute actions automatically in response to alarms or failures – using modern, open standards.

Whether you start with open-source tools like Ansible and NetBox or head toward larger platforms like NSO or EDA, the point is the same: start from where you are.Choose what fits your team, your network, and your goals.

The best part? Many of these tools are open source, well-supported – and you can get started without committing to expensive licenses or overhauling your existing network.

“There’s no tool that fits our environment.”

And that’s okay.

Some use Cisco NSO or Nokia EDA – others build custom solutions with Python and REST APIs.What matters isn’t which tool you use – it’s that it works for you.

Automation isn’t a product – it’s a journey.And every organization needs to find its own path.

“But our network is a mess.”

That’s exactly why it’s time to automate.When you’re dealing with:

27 different configuration patterns
Legacy equipment
Manual processes

…it’s nearly impossible to bring order without automation.

It starts by identifying recurring tasks, standardizing them, and managing them as code.

The result?

Fewer errors
Predictable configurations
Easier troubleshooting
More time for strategic work

So… what’s the next step? 🤔

We’ve helped many companies who were exactly where you are:

✓ No time

✓ No visibility

✓ No plan

But with the right support, the right tools, and a pilot project that makes sense, they’ve moved from constant firefighting to structured, result-driven automation.

And now, we want to help more teams take that same journey.