New Features, New Benefits
Network features and related policies can be mapped using these four constructs:
■ Domains: Apply configuration settings consistently across multiple devices. An example is a QoS configuration which may be different by business units, hence, different QoS domains would allow network engineers to assign QoS policies across all devices associated with specific business units in each region.
■ Features: Give the configuration settings for one device at a time, enabling functionality that the device can provide by itself. A good example is the configuration of a device-specific routing table where the device should forward incoming traffic.
■ Globals: Apply these configuration settings throughout the network; these are the same for every device in the network. A good example is NTP (network time protocol) where the central architecture team is defining the only NTP servers permissible for the network.
■ Custom: There will always be exceptions, so not everything may be practical to model in a general feature or domain concepts, especially specific exceptions to single devices only. For example, a specific set of Access Control Lists (ACLs) may only be needed on a single device. For these cases where no other dependencies with other features exist, just applying configuration data to a device may be acceptable.
Whatever network policy is needed can be built using a combination of these constructs. Inherent interdependencies can be flagged by network engineers early, so that a network management system can deploy them in the correct sequential order, optimally applying these features to individual devices as well as across the network to create the target policy. Abstracting network functionality into these types of models allows network engineers to re-focus on the actual network architecture and focus less on the mechanics of the management of configuration data. These lead to a number of benefits:
■ Any hardware, any manufacturer: How a device is configured is now based on how it should perform, by itself or in concert with other devices. As a result, the actual hardware itself, its specific OS/firmware or even the manufacturer no longer matters, as long as the device is capable of performing the desired functionality.
■ Logical separation: NetOps is logically separated from implementation and maintenance (DevOps). For example, architects can define the features, domains and global settings needed for a given network infrastructure, assemble them into logical groups and resolve any interdependencies. They can then be tested and validated by, for example, the security team. The assembled features, domains and globals are handed over to the operational team, who will deploy them onto the network and manage them over their lifecycle.
■ Communal wisdom: When networks are modeled through logical constructs, it allows for a wide exchange of best-practice reference designs based on common user requirements. Different teams of architects can exchange information about the models they use for specific network functionalities without having to revert to low-level configuration settings. This opens the possibility of creating network engineering communities that exchange specific models based on their desired use cases with clearly defined interdependencies and conflict resolution against other models.
Managing the Modern Network
What is needed to create a next-generation network management tool? Nothing less than the development of a sophisticated network-aware orchestration engine that is able to detect any interdependencies, resolve them and deploy network policies automatically over the network.
First, consider these non-technical challenges:
■ Users need to firmly believe that the logical network model will, in fact, result in the correct configuration of all devices in the network. Many network engineers are still most comfortable with command line interface (CLI) created from scripts and templates.
■ The primary focus of network engineers is on proper device configurations and ensuring the device is performing as intended. Any next-generation tools have been designed with a network engineering focus in mind, allowing network engineers to use the system with a much shorter learning curve and minimal programming expertise.
■ Get the buy-in of DevOps and NetOps teams, who may be skeptical to trust device configuration to a new management tool.
Technically speaking, here's what today's management tools should include:
■ Management to handle the high degree of customization needed.
■ Zero-touch provisioning so that the onboarding of new devices into the system is as fluid as possible, allowing generalist IT staff to install routers and trigger device provisioning automatically.
■ The ability to limit or flag unauthorized manual device configuration changes with automatic remediation when needed.
■ Configuration preview that allows dry runs of new configurations to understand all changes that may have to be performed, even on other network devices when needed.
■ Step-by-step verification of device provisioning actions with automatic revert on errors.
A New Approach
Organizations can bring their networks into present-day functionality with tools that provide complete abstraction of network functions while providing deeply integrated model interdependency verification, deployment previews and layer-by-layer provisioning. For example, replacing an existing device with a newer model, even if it's from a different vendor, can be detected and automatically provisioned. Such solutions that can resolve any potential conflicts and interdependencies, even across vendors, are becoming increasingly important as network devices are virtualized on common platforms and the individual strength of vendor-specific solutions are combined into one multi-vendor solution.
A model like this that addresses the entire stack provides clarity to architecture and implementation teams because the handoff points are well defined. This, in turn, leads to faster implementation of business requirements and higher reliability. Such a system creates quicker identification of and recovery from network outages, which increases customer confidence and satisfaction and saves money from unexpected downtime.
Dr. Stefan Dietrich is VP of Product Strategy at Glue Networks.
I've had the opportunity to work with a number of organizations embarking on their AIOps journey. I always advise them to start by evaluating their needs and the possibilities AIOps can bring to them through five different levels of AIOps maturity. This is a strategic approach that allows enterprises to achieve complete automation for long-term success ...
Sumo Logic recently commissioned an independent market research study to understand the industry momentum behind continuous intelligence — and the necessity for digital organizations to embrace a cloud-native, real-time continuous intelligence platform to support the speed and agility of business for faster decision-making, optimizing security, driving new innovation and delivering world-class customer experiences. Some of the key findings include ...
When it comes to viruses, it's typically those of the computer/digital variety that IT is concerned about. But with the ongoing pandemic, IT operations teams are on the hook to maintain business functions in the midst of rapid and massive change. One of the biggest challenges for businesses is the shift to remote work at scale. Ensuring that they can continue to provide products and services — and satisfy their customers — against this backdrop is challenging for many ...
Teams tasked with developing and delivering software are under pressure to balance the business imperative for speed with high customer expectations for quality. In the course of trying to achieve this balance, engineering organizations rely on a variety of tools, techniques and processes. The 2020 State of Software Quality report provides a snapshot of the key challenges organizations encounter when it comes to delivering quality software at speed, as well as how they are approaching these hurdles. This blog introduces its key findings ...
For IT teams, run-the-business, commodity areas such as employee help desks, device support and communication platforms are regularly placed in the crosshairs for cost takeout, but these areas are also highly visible to employees. Organizations can improve employee satisfaction and business performance by building unified functions that are measured by employee experience rather than price. This approach will ultimately fund transformation, as well as increase productivity and innovation ...
In the agile DevOps framework, there is a vital piece missing; something that previous approaches to application development did well, but has since fallen by the wayside. That is, the post-delivery portion of the toolchain. Without continuous cloud optimization, the CI/CD toolchain still produces massive inefficiencies and overspend ...
The COVID-19 pandemic has exponentially accelerated digital transformation projects. To better understand where IT professionals are turning for help, we analyzed the online behaviors of IT decision-makers. Our research found an increase in demand for resources related to APM, microservices and dependence on cloud services ...
The rush to the public cloud has now slowed as organizations realized that it is not a "one size fits all" solution. The main issue is the lack of deep visibility into the performance of applications provided by the host. Our own research has recently revealed that 32% of public cloud resources are currently under-utilized, and without proper direction and guidance, this will remain the case ...
The global shift to working from home (WFH) enforced by COVID-19 stay-at-home orders has had a massive impact on everyone's working lives, not just in the way they remotely interact with their teams and IT systems, but also in how they spend their working days. With both governments and businesses committed to slowly opening up offices, it's increasingly clear that a high prevalence of remote work will continue throughout 2020 and beyond. This situation begets important questions ...