Inside the Bell Labs Model: How Operations Drive Data Center Fabric Reliability

Hi, I am Mitch Ashley with the Futurum Group. Today we're unpacking the Nokia Bell Labs recently developed model for data center fabric reliability. We'll look at how the fabric design plus operations, especially automation and AIOps, can move enterprises from a legacy PMO baseline to an FMO with Nokia's Sr.

1 nines availability and shrink downtime significantly. And I'm Scott Roan. With Al, it's the age of operations.

You know, hardware still matters, but operations dominate outcomes. You know, day two and beyond. This Bell Lab's model includes significant detail, and today we'll zoom in on some key areas and operations.

We'll also talk on talk, touch on the significant financial impact as well. Um, you know, the model shows that reliability gains can result in real cost reduction and, uh, that should be no surprise to those of us who've been, you know, in the ops world for some time. Very good.

Well, the model treats configuration NetOps is one of the main areas for improvement, including common cause failures. So what does it mean in practice, Scott? The, the model shows the most significant reduction in downtime measured in absolute terms, you know, minutes, um, eliminated per year is achieved during the config and provisioning phase, driven by decrease in configurated errors.

There are multiple key components and mechanisms in the Nokia solution At the heart of the model, first you have SR Linux, the operating system developed for modern data center operations. It facilitates efficient structured and language agnostic comms between system components, minimizing operational complexity and reducing the likelihood of user error. Next, you've got features like ZTP zero touch provisioning, which are integral to EDA.

That further eliminate manual intervention takes the human out of the loop for opportunities to inject errors, um, and contributing to that enhanced reliability for operational efficiency. And then there's ida's digital twin construct. It provides like, for like environment, um, to design and validate network configs with correct intent inputs.

This minimizes config and provisioning errors and the configs generated in the digital twin directly mirror production that's not special configs in the twin, um, and then modified to push in production. It's actually the same configurations reliability is further enforced and improved by it's built-in dry run validation routines prior to every config being pushed into the network, helping ensure accuracy and consistency before changes are put into the live network. Now you mentioned the term age of operations.

So talk to us about why is ops a primary lever in this model? At the simplest level, you know, once you stand up a data center fabric, most of the day-to-day work in net ops is around operations and monitoring. And with AI ops entering the room here, we have a day one killer app that drives the use for net NetOps natural language processing.

I can talk to the fabric to see what's going on. We also benefit from increased programmatic access to the fabric. For example, SR Linux provides a single API for set get and streaming telemetry resulting in less operational complexity in minimizing, minimizing mis configs.

1 nines. When all these features are combined from a network operating system architecture perspective, the event handling system and Sr. Linux and EDA is capable of proactive predefined actions based on things like port saturation packet drops, looking at other network conditions to automatically trigger corrective actions and prevent network degradation and mitigate issues before they occur.

So putting that all together, it sounds like what you're saying is tools operationalize the design. That's a really good summary of a very long description, Mitch. Um, exactly.

You know, design gives you redundancy, operations makes it reliable every day. The details matter for sure. So planned work can still hurt, uh, availability.

How does, how does the model address that and, and Sr. Linux in particular, and how do they handle ongoing maintenance such as upgrades, patches, the things that we commonly do? We need to point out the fact that SR.

Linux uses an unmodified Linux kernel. This is what the rest of the world is using for Linux. That's gives you, uh, the ability to tap into a worldwide community of developers hammering away at it every day, identifying potential performance and security issues across many, many different application areas, not just networking.

In addition to that, e DAP provides built-in capability to ensure network reliability during maintenance operations. You can use the platform to gracefully gain traffic, drain traffic from uh, a node and put nodes into maintenance mode. Um, preventing service disruptions, minimizing traffic loss.

EA also centralized and stream centralizes and streamlines the upgrade process. When a route router's locked and is ready to reboot, it significantly reduces the actual maintenance window. IDA also gives you group-based upgrades and stage promotion, um, to shrink maintenance windows.

Reduce the time used for maintenance windows and limit that blast radius. You can pick targeted nodes, you can automate pre and post checks, and you can roll forward only when your, uh, process gates get passed altogether. These features, um, result in enhanced reliability and minimize downtime.

All the upgrade steps can be tested, um, with, um, the EA digital twin functionality in a like, to like environment. This is what gives you impact, um, and reduces, uh, maintenance issues for far less annual downtime as you move from your present mode of operation to your future mode of operation. Excellent.

So who should people talk to at Nokia to see how this model and can apply to their environment, their data center network? Well, to learn more about the model Sr. Linux and EA, contact your Nokia account team or your regional business center contacts and they'll work with you to work through the details.

Thank you, Scott. Appreciate uh, you sharing us some interesting facts from the study. Thanks, Mitch.