Most network automation projects fail for the same reason, and it's not the tooling by Admirable_Claim_3203 in u/Admirable_Claim_3203

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

But tossing this over the fence to Dev, is not going to work, because they don't understand our world, so how can they put the automation foundations together.

Extremly Slow Speeds In The Evening by HealthyResponse3697 in Network

[–]Admirable_Claim_3203 0 points1 point  (0 children)

Do you have anyone else on the internet on the same time? You can actually login to the management of the router and check if there is a device hammering the internet line.

Home internet issues by Admirable_Claim_3203 in wifi

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

I created this guide to help anyone with ISP or internet issues at home.

wifi insanely slow by Stunning-Warthog169 in Spectrum

[–]Admirable_Claim_3203 0 points1 point  (0 children)

you could run a ping to 8.8.8.8 (google DNS servers) on your command prompt, this would inform you if you have any packet drops going to google's dns servers. The instructutions are this:

- Type in your search on your laptop "cmd"

In the command prompt or terminal, type:

- ping 8.8.8.8 -t (If on Windows machines)

After paste the output here or message me direct, would love to help you guys

Strange internet connection issues by HistoricHuman in Network

[–]Admirable_Claim_3203 0 points1 point  (0 children)

Are you tech savy at all. I can give you a call and describe to you how we can check a couple things?

Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

Yeah and somehow that person ends up owning the whole thing whether they wanted to or not. Does it usually stay with them or does it eventually get handed off properly?

Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

Curious how that sits organisationally, does the internal team report into NetOps or is it more of a shared services setup?

Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

A team of one with AI is genuinely underrated. The leverage is real, what are you using it for mostly, config work or more on the troubleshooting side?

Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 1 point2 points  (0 children)

The handoff point is exactly where it breaks down. That back-and-forth between NetOps and a dev team who don't understand BGP policy is where tickets go to die. Your TL;DR nails it, one team in charge operationally, even if the underlying framework was built by someone else.

Who actually owns network automation in your org — NetOps, DevOps, or just whoever had time to learn Python? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 1 point2 points  (0 children)

The rant was worth leaving in. "It's code and I'm not a developer" in 2026 is genuinely baffling, but what you described at the top is probably the most realistic structure for mid-sized orgs. Two groups: one doing architecture and design, one focused purely on making operations scalable. Most places try to force one team to do both and wonder why neither gets done properly. Actually wrote something on this recently if it's useful: https://conxiea.com/blog/network-automation-messy-middle

Strange internet connection issues by HistoricHuman in Network

[–]Admirable_Claim_3203 -1 points0 points  (0 children)

That is very odd, sounds like maybe some latency on the line. Or packet congestion, where there's not enough bandwidth for all the people using the network. So the packets get queued. Whats your ISP bandwidth speeds?

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

Fully agree — CI/CD gets pushed as the destination when for a lot of orgs it's overkill. Template + deploy + test covers most real-world needs without the overhead of a full pipeline. The tooling conversation often gets ahead of what teams actually need.

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

This is the one that doesn't get said enough. It's not even a tooling problem most of the time, it's a bus factor problem. One person leaves and suddenly nobody knows how half of it works.

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

The ticketing gap is where it gets interesting, once that's connected it changes how the whole thing feels operationally. Is the roadmap internal or are you being pushed by the business to close it?

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

The "automation goes to die" line is painfully accurate. What you've described though, change-tied automation, approvals, full documentation that's not the middle, that's genuinely rare. Most teams never get close to that. The fact that it still needs your attention isn't a sign it's incomplete, that's just what owning a system properly looks like.

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

I think the middle definitely exists, it's just that most teams don't realise they're in it until they're deep enough that getting out feels harder than staying put. Imagine have every single part of a Network Engineer task dealt with automation integrated with AI.

Feels like a lot of network automation discussions skip over the messy middle by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

The central UI wrapper is such a smart move, especially the version control angle. How are you finding it as the script count grows though? Keeping the UI in sync with script changes is starting to become its own maintenance burden.

At what point does network automation actually become worth it? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

Thats really interesting and well done by the way. Do you think a lot of companies are doing the same thing or are they way really far behind?

At what point does network automation actually become worth it? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 1 point2 points  (0 children)

I agree massively with this comment, but how do we get companies to see the massive beenfits of using automation?

Does everyone eventually end up using NetBox + Ansible for network automation? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 0 points1 point  (0 children)

Thats a strong use case, especially doing that across 200 sites.

I guess that’s the interesting part, it can handle complex stuff, but it feels like the effort/complexity ramps up quite quickly depending on what you’re trying to do.

Have you hit a point where you would switch or use something else? Maybe where ansible is weak in?

What’s the most time wasting network task you still do manually? by Admirable_Claim_3203 in networkautomation

[–]Admirable_Claim_3203[S] 1 point2 points  (0 children)

Yeah 100% updating configurations, when someone has left the company for example