RECAP/RECORDING - nog.fi meeting 2026.06 https://isoclive.substack.com/p/fi-nog-2026-
A day of operational talks from Tampere: routing security, IPv6 architecture, DNS resilience, subsea infrastructure, AI tooling & EU telecom policy.
„Magst du vielleicht kurz auf die Bühne kommen damit zukünftige Arbeitgeber sehen wenn sie nicht einstellen wollen?“
@leyrer 2026
Ja ich befinde mich im ÖPNV
Ja der lachflash hat Blicke ausgelöst
Nein ich bereue nichts
Selten so gut gelacht. Das lass ich Montag mal in unseen configs suchen.
https://media.ccc.de/v/gpn24-660-besser-tunneln-mit-ssh#t=2276
#gpn24 #secops-was-here-looking-for-you #netops-hates-this-simple-trick

New survey on arXiv: Large Language Models for Agentic NetOps and AIOps.
The paper looks at LLM-based agents for incident diagnosis, root-cause analysis, configuration and change planning, policy checking, human approval, and safer operational decisions.
The core argument: reliability will depend less on the model alone, and more on evidence traces, tool boundaries, verification gates, rollback, and governance.

Large language models are increasingly being used to support network operations (NetOps) and artificial intelligence for IT operations (AIOps), including incident investigation, root-cause analysis, configuration synthesis, and limited self-healing. In both NetOps and AIOps, this shift is changing how tasks are managed. Agent-based operations work as workflows, from gathering evidence to taking action, following permissions, policies, and checks, and providing rollback options when necessary. This is crucial because operational decisions can have instant impacts. To make the argument concrete, we organise the relevant literature around the hierarchy of autonomy, tool scope, evidence traces, and assurance contracts. These contracts define what an agent may observe, propose, and execute. They also define the checks that must pass before any action is allowed. A consistent pattern appears across work on telemetry query recommendation, diagnosis, root-cause analysis, configuration synthesis, change planning, and limited self-healing. Operational reliability does not come chiefly from the model itself. It depends on the machinery around the model. We also argue that evaluation should go beyond static question answering. Agentic NetOps and AIOps systems require workflow-centred evaluation, including trace quality, bounded tool use, safe proposal generation, replay in sandboxed environments, and canary trials with rollback-aware scoring. Without these measures, a system may appear robust yet remain too fragile. Finally, we examine security, privacy, and governance risks that become acute when agents sit close to operational control surfaces. Taken together, the survey concludes that progress in intelligent NetOps and AIOps will depend on treating autonomy as a constrained operational control problem, whose outputs must be reliable, auditable, and securely deployable.
Every network vendor has an "AI-powered" story right now. Most of them are 10% of the actual solution. I broke down what the other 90% looks like after watching Aviz Networks demo their AI NOC platform at Network Field Day. #NFD #Networking #NetOps #AI
https://packitforwarding.com/index.php/2026/04/30/ai-more-than-a-bolt-on-solution-for-networking/

The post critiques the marketing use of "AI-powered" in network tools, highlighting the gap between flashy demos and real enterprise needs. It emphasizes the importance of multi-source data integration, on-premises hosting, and robust role-based access. Genuine AI solutions must address complexities beyond simple Q&A interfaces to be effective in real environments.
Autonomie scheitert nicht an schlechter AI, sondern an schlechter Architektur.
Skalierende Teams sind nicht smarter – sie sind besser designed. Sie behandeln Telemetry als Produkt, validieren mit Digital Twins und bauen Rollback ein. Auch das Human System muss mitgedacht werden. #AI #Automation #NetOps - Link im 2. Post
Как в Авито построили систему мониторинга BGP
Всем привет! Меня зовут Антон Ильичев, я сетевой инженер в Авито. В этой статье расскажу, зачем мы централизованно собираем и анализируем маршрутную информацию с сетевых устройств, причём тут протокол BMP и как устроена наша система мониторинга. В конце вас будет ждать лаба на docker-compose, которую вы можете запустить у себя и посмотреть на систему в действии. Статья будет полезна в первую очередь сетевым инженерам, командам SRE и мониторинга, которые отвечают за доступность и качество сервиса.
https://habr.com/ru/companies/avito/articles/1012780/
#bmp #bgp #monitoring #netops #troubleshooting #kafka #clickhouse #cisco #grafana #juniper
Is #RANCID still alive in production environments?
We’re considering integration with #NetXMS and trying to estimate real-world usage.
#networking #netops #opensource #NMS
Do you use it?
Sometimes figuring out whats happening over time in the Mikrotik changelogs isn't as easy as it should be..... I made a tool to display changelog entries and data in different ways, as well as searching all changelogs for keywords. (MLAG for instance is a good search keyword).
This is still in really early public availability, but its been useful for 2 out of 2 people I shared it with and so I expect it will be useful for a wider audience.
Just had a discussion on routable #IPv4 address space. This lead me to check #Bogon IP address space. I briefly fetched a public bogon list of a large provider, parsed the CIDR blocks and calculated the number of IPv4 addresses. Dividing this by 0.0.0.0/0 eventually lead to the discovery that 13.89% of the IPv4 address space is non-routable. Way more than I had anticipated.
Your daily dose of #netops knowledge... :)