HN721: Goodbye Network Cowboys, Hello Total Network Operations
Feb 16, 2024
auto_awesome
The podcast discusses the need for standardization in network engineering, the importance of networking and community, adopting DevOps for network operations, the impact of being seen as a rock star in the workplace, capturing information and routinizing processes in network management, and adopting Total Network Operations in network operations.
Standardization is necessary in network operations to make networks consistent and manageable across organizations.
The role of a Network Operations Architect helps bridge the gap between technical silos and ensures a holistic view of network operations.
Implementing T-NOPS principles and processes, along with network automation, improves the efficiency and resiliency of network operations.
Deep dives
The Need for Standardization in Network Operations
The podcast episode discusses the need for standardization in network operations. The complexity of modern networks, with various encapsulations and overlays, poses a challenge for network architects and engineers. For years, the focus has been on making things work without considering long-term consequences. This has resulted in networks that are highly unique to each organization, making it difficult for new engineers to understand and manage. The guest speaker, Scott Rabon, proposes a solution called Total Network Operations (T-NOPS), which aims to bring standardization to network engineering and operations. By adopting a holistic view of network operations and intentionally evaluating new technologies, T-NOPS seeks to create a framework for building networks that is consistent, efficient, and aligned with business objectives.
The Role of a Network Operations Architect
As part of T-NOPS, the podcast explores the concept of a Network Operations Architect. This role focuses on zooming out of individual silos within the operations team and thinking about how different tools and processes interconnect. The Network Operations Architect has a responsibility to evaluate new technologies and tools and their potential impact on operations. This role helps bridge the gap between technical silos and ensures a holistic view of network operations. By having someone in this role, organizations can better align network operations with business requirements and improve overall resiliency and efficiency.
Incremental Adoption and Benefits of T-NOPS
The adoption of T-NOPS can be approached incrementally. Organizations can start by encouraging a systems thinking approach, where individuals and teams look beyond their immediate silos and consider the interconnections between different areas of network operations. This can be done without significant cost and helps foster collaboration and a holistic view of operations. Additionally, the intentional evaluation of new technologies and tools allows organizations to make informed decisions and avoid chasing after the latest trends. By gradually implementing T-NOPS principles and processes, organizations can improve network resiliency, lower costs, and create a more sustainable and efficient operating environment for their operations teams.
Integration with Network Automation
T-NOPS and network automation are closely intertwined. Network automation plays a crucial role in implementing T-NOPS principles and processes. Automation allows for the routinization of network functions, reducing reliance on individual rockstars and ensuring consistency and repeatability in service delivery. Furthermore, automation provides more time for operations teams to focus on cross-silo collaboration, evaluating new technologies, and aligning network operations with business objectives. T-NOPS and network automation go hand in hand in improving the overall efficiency, effectiveness, and resiliency of network operations.
Adapting T-NOPS to Multi-Vendor Networks
T-NOPS is applicable to multi-vendor networks. Organizations can leverage the interoperability and integration capabilities provided by the product ecosystem to make T-NOPS principles work across different network platforms. While the presence of multiple vendors may introduce complexities, the increasing emphasis on integrations and the flexibility of modern tools enable organizations to adopt T-NOPS regardless of their network infrastructure. By leveraging testing and careful evaluation, organizations can ensure the successful implementation of T-NOPS in multi-vendor environments.
The days of network cowboy heroism are over… or at least they need to be. It’s time for network engineering to grow up and standardize how networks are built. Not only will this make life easier for all of us as we inherit networks when we move from company to company, but it’s the only... Read more »
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
