The Future of Network Operations: Navigating the Shift Toward Agentic AI and Autonomous Systems

The landscape of network operations is currently undergoing one of the most significant transformations since the transition from hardware-centric environments to software-defined networking. As enterprises grapple with increasing complexity, the sheer scale of modern infrastructure is beginning to outpace the capacity of traditional manual management. In a recent industry discussion, Rekha Shenoy and Irfahn Khimji of BackBox sat down with Scott Robohn to explore the trajectory of network operations (NetOps) as the industry moves toward the year 2030. The conversation centered on the emergence of "agentic NetOps"—a paradigm shift where artificial intelligence does not merely suggest actions but possesses the agency to execute them—and the critical necessity of maintaining operational control through robust backup and rollback strategies.

The evolution of NetOps has historically moved in waves. For decades, the primary interface for network engineers was the Command Line Interface (CLI), requiring deep specialized knowledge and manual entry for every configuration change. While the introduction of basic automation and scripting helped alleviate some of the repetitive burdens, the industry is now standing on the precipice of a much more profound change. The move toward agentic AI represents a departure from simple "if-then" automation toward systems that can understand intent, analyze real-time conditions, and take proactive steps to maintain network health and security.

The Rise of Agentic NetOps

At the heart of the discussion was the concept of "agentic" systems. Unlike traditional AI, which might provide a dashboard of alerts or a set of recommendations that a human must then approve and implement, agentic AI is designed to operate with a level of autonomy. In a NetOps context, this means an AI agent could identify a performance bottleneck, determine the necessary configuration changes across multiple vendors’ equipment, and execute those changes without direct human intervention at every step.

However, the shift to agentic NetOps is not merely a technical upgrade; it is a fundamental change in how network teams interact with their infrastructure. Shenoy and Khimji highlighted that the transition to 2030 will require teams to move from being "doers" to being "orchestrators." In this new model, the role of the network engineer involves setting the guardrails, defining the desired state of the network, and supervising the AI agents that carry out the day-to-day operations. This shift promises to solve the "talent gap" by allowing senior engineers to focus on high-level architecture and strategy rather than losing hours to routine maintenance or firefighting.

The promise of agentic AI is particularly relevant as networks become more distributed. With the rise of edge computing, multi-cloud environments, and the Internet of Things (IoT), the number of endpoints and nodes that require management is exploding. Humans simply cannot scale at the same rate as the digital infrastructure they are tasked with protecting. By 2030, the consensus suggests that autonomous or semi-autonomous agents will be a requirement for operational viability, rather than a luxury for the most advanced enterprises.

Balancing Automation with Operational Control

One of the most pressing concerns for NetOps teams is the loss of control. When an automated system—especially one driven by complex AI models—makes a change, there is an inherent risk that the change could lead to unforeseen consequences or network downtime. The discussion with Robohn emphasized that the fear of the "automated mistake" is one of the primary barriers to the adoption of advanced NetOps tools.

To mitigate this risk, the experts from BackBox argued that automation must be inextricably linked with backup and rollback strategies. For an agentic system to be trusted, it must operate within a framework that captures the state of the network before and after every action. If an AI agent attempts to optimize a routing protocol and inadvertently causes a segment of the network to go offline, the system must have the capability to instantly recognize the failure and roll back to the last known good configuration.

This "safety net" approach is what allows organizations to embrace higher levels of automation without compromising the stability of their business operations. As NetOps teams look toward 2030, the maturity of an organization will likely be measured not by how much automation they use, but by how effectively they can recover from an automated error. The integration of real-time backups into the automation workflow ensures that the "human in the loop" can step in when necessary, but more importantly, it ensures that the system itself is self-correcting.

The Evolving Role of the Network Engineer

A significant portion of the conversation was dedicated to the human element of this technological shift. There is a common anxiety in the industry that AI and automation will render the network engineer obsolete. However, Shenoy and Khimji offered a more optimistic and nuanced perspective. They suggested that the role is not disappearing but is instead undergoing an essential evolution.

The network engineer of 2030 will likely need a different skillset than the engineer of 2010. While a fundamental understanding of networking protocols (like BGP, OSPF, and TCP/IP) remains foundational, there is an increasing need for proficiency in data science, API integration, and policy management. The engineer becomes a policy-maker, defining the "intent" of the network—such as security parameters, latency requirements, and redundancy levels—and then monitoring the AI agents to ensure that the actual state of the network aligns with that intent.

This evolution also changes the daily "rhythm" of network operations. Currently, many teams operate in a reactive mode, responding to tickets and outages as they occur. In an agentic NetOps future, the workflow becomes more proactive. Engineers will spend their time refining the models, auditing the actions taken by AI agents, and ensuring that the infrastructure is resilient enough to handle future demands. The shift is from "fixing the network" to "improving the network’s ability to fix itself."

Preparing for the 2030 Landscape

As organizations look toward the end of the decade, the path forward involves a gradual building of trust in automated systems. This process starts with automating the most mundane and repetitive tasks—such as OS updates, configuration backups, and compliance checks—and slowly moving toward more complex, "closed-loop" operations.

The experts noted that the transition to 2030 is also about tackling technical debt. Many organizations are held back by legacy systems that do not easily support modern APIs or automated workflows. Part of the journey toward agentic NetOps involves modernizing this underlying infrastructure to ensure it can communicate effectively with AI-driven management layers.

Furthermore, the conversation touched on the importance of multi-vendor environments. Very few enterprises rely on a single hardware provider, meaning that any agentic AI system must be "vendor-agnostic." It must be able to translate high-level intent into the specific syntax required by different routers, switches, and firewalls across a diverse ecosystem. This is a challenge that BackBox has focused on, providing a unified platform that can bridge the gap between different hardware generations and manufacturers.

Ultimately, the vision for 2030 is one of partnership between human intelligence and machine agency. By delegating the heavy lifting of data processing and routine execution to AI agents, network teams can reclaim their time to focus on innovation. The key to reaching this future safely lies in the rigorous application of operational best practices: visibility, backup, and the ability to roll back changes at a moment’s notice.

Episode Links:

Watch this episode on YouTube

BackBox