Many service providers have embarked on a major initiative to migrate their IP networks from purpose-built platforms to virtualized, software-based platforms heralding a new era of “programmable networks.” Service providers are increasingly looking to implement Network Function Virtualization (NFV) and Software Defined Network (SDN) technologies to evolve their networks to become more agile and elastic, better managed and orchestrated with automation; thereby driving lower CAPEX and OPEX. With virtualization, service providers look to gain control of service creation and innovate faster in response to customer and market needs and opportunities as well as to meet competitive challenges. Assuring the continuity of quality network services through this network evolution requires real-time visibility at the most granular level of these transitory virtualized elements.
The Business Case for Virtualization
Over the years, service provider networks have become complex, rigid, and inflexible in terms of service creation and delivery, slowing down the innovation cycle and driving up their capital and operational expenses. The tight integration between services software and purpose-built hardware has made it increasingly difficult to manipulate services “on-demand.” The business rationale for this transformation is to create a more dynamic and service-agile infrastructure where existing services can be changed “on-the-fly” and new services can be delivered rapidly in response to changing customer needs. Furthermore, the total cost of ownership can be reduced through improved automation and orchestration capabilities.
This is a very significant transformation, similar in nature to the TDM-to-IP transformation that started in the late 1990s. During this transformation, several central offices will convert from legacy architectures of purpose-built network elements to virtualized architectures with commercial off-the-shelf platforms hosting virtual network elements. These virtual network elements can be controlled from external software systems where the service creation and orchestration intelligence resides. Service providers will be in a position to offer differentiated services to their customers through their control of the orchestration platforms.
What is SDN? What is NFV? What's the Difference?
Brandon Butler offered a clear definition of these technologies in his 2017 article, “What’s the difference between SDN and NFV?” In that article, he described Software Defined Networking as “the idea of separating the control plane of a network from the data plane that forwards network traffic. The goal of this disaggregation is to create a network that is centrally managed and programmable. Some SDN implementations use a software-based management platform that controls commodity network hardware. Other approaches use an integrated hardware and software-approach.”
Further, he offered that “the fundamental idea of NFV is to virtualize network services and abstract them from dedicated hardware. NFV deployments typically use commodity servers to run software versions of network services that previously were hardware-based. These software-based services are called Virtual Network Functions (VNF) and would run in an NFV environment. Examples of VNFs include routing, firewalling, load balancing, WAN acceleration, and encryption. By virtualizing these network services, providers can offer customers these services dynamically, with the ability to spin them up down on demand.”
This new virtualized infrastructure is based on open standards for SDN and NFV. By virtualizing network functions, NFV allows network functions to be placed anywhere in the infrastructure and be moved as necessary. By separating control plane and data plane functions, SDN allows individual packet flows to be routed through the appropriate service layers as needed.
Service assurance solutions that are virtualized can also weave themselves into this architecture at both the NFV and SDN functionality. Such software-based solutions have the potential to provide more cost, effective visibility, proactive monitoring, and service triage.
Transitioning to NFV and SDN
To facilitate “on-demand” service turn up (and turn down) while maintaining service quality, service providers need a solution that provides real-time visibility all the way down to the VNF layer with real-time views and alerting functionality. This discrete level of visibility can also become part of the automation layer that enables the elasticity of networks with virtualization. In this way, service providers can transition their network and services to NFV and SDN with confidence.
~ John English, Sr. Solutions Marketing Manager, NETSCOUT