Multi Layer Network Orchestration - A CENGN, Fujitsu, Juniper and CENX PoC



While computer technology in a wider sense has advanced rapidly and dramatically over the past three decades, networking has remained virtually unchanged since the 1990s. One of the main problems facing providers around the world is that the numerous multi vendor legacy systems still in service don’t support fast, accurate remote identification, troubleshooting and fault resolution. The lack of remote fault resolution capabilities is compounded by the complex, closed, and proprietary nature of legacy systems, as well as the proliferation of protocols at the Southbound end. As a result, networks are difficult to optimize, troubleshoot, automate, and customize. SDN (Software-Defined Networking) is set to solve these issues by decoupling the control plane, plus bringing the benefits of cost reduction, overhead reduction, virtual network management, virtual packet forwarding, extensibility, better network management, faster service activation, reduced downtime, ease of use and open standards.
Why Multi-layer SDN is Needed


One of the issues facing network operators is that there is no SDN controller with a streamlined topology view of both optical transport and packet layers. That’s why coordination between transport and IP/MPLS layer management is one of the most promising approaches to optimized, simplified multilayer network architecture. However, this coordination brings significant technical challenge, since it involves inter-operation between very different technologies on each of the network layers, each with its own protocols, approach and legacy for network control and management.


Traditionally, transport networks have relied on centralized network management through a Network Management System or Element Management System (NMS/EMS), whereas the IP/MPLS layer uses a distributed control plane to build highly robust and dynamic network topologies. These fundamentally different approaches to network control have been a significant challenge over the years when the industry has tried to realize a closer integration between both network layers.

Although there has been a lot of R&D in this area (one example would be OpenFlow adding optical transport extensions on version 1.3 onward), there are few, if any, successful implementations of multilayer orchestration through SDN.

It’s important to mention a common misconception about SDN, which is the assumption that SDN goes hand-in-hand with the OpenFlow protocol. OpenFlow (which is an evolution of Ethane protocol) is just a means to an end, namely separation of the control and data plane. OpenFlow is a communication protocol that gives access to the forwarding plane of a network element (switch, router, optical equipment, etc.). SDN isn’t dependent on Openflow specifically; it can also be implemented using other protocols for southbound communication, such as Netconf/Yang, BGP, XMPP, etc.
A Multi-layer, Multi-vendor SDN Proof of Concept

To address the issues outlined above, CENGN (Canada’s Center of Excellence in Next Generation Networks), in collaboration with Juniper Networks, Fujitsu, Telus and cenX, initiated a PoC to demonstrate true end-to-end multilayer SDN orchestration of an MPLS-based WAN over optical infrastructure.


In the PoC, the CENX CORTX Service Orchestrator serves as a higher layer orchestrator that optimally synchronizes the MPLS and Optical layers. The MPLS layer uses Juniper’s NorthStar SDN controller for Layer 2–3 devices and the Optical transport layer uses Fujitsu Virtuora® Network Controller. All northbound integration is through a REST API and upon notification of failures or policy violations this API dynamically adjusts the optical or packet layers via the SDN controllers, ensuring optimal routing and policy conformance.

Scenarios

The Proof of Concept Consists of the following scenarios:


STEP 1: FAILURE IN OPTICAL DOMAIN

  • Optical link failure (via cable pull or manual port failure).
  • Cortx Orchestrator gets link failure alarms from Virtuora, stores them and updates path info.



STEP 2: PACKET REROUTE

  • Cortx Service Orchestrator receives link failure alarms from Juniper MPLS, stores alarm.
  • Cortx Service Orchestrator receives updated topology information from SDN controllers.
  • Juniper MPLS automatically re-routes blue label-switched path and notifies Cortx Service Orchestrator of link state changes.

STEP 3: CORTX SRLG NOTIFICATION

  • Cortx Service Orchestrator processes new topology and raises alert of network policy. violation, which remains in effect until the situation is corrected.
  • Cortx Service Orchestrator notifies the operations user of policy violation.



STEP 4: PACKET DOMAIN ADJUSTMENTS

  • Virtuora turns up optical links and alerts Cortx Service Orchestrator of topology change
  • Policy violation is cleared when condition corrected
  • LSP is rerouted through new provisioned optical paths

Conclusion

This is an excellent model of how a collaborative, multi vendor, multilayer approach based on open standards can drive the industry towards the network of the future. By providing a functional example of real-time operations across multi vendor platforms, this project has shown that multilayer data connectivity orchestration—and the benefits it offers—is feasible in a realistic situation. Other proofs of concept at the CENGN laboratories will continue to advance SDN and NFV technologies, helping to refine functionality and move towards production systems. 
Location: Dallas, TX, USA

Comments

Post a Comment

Popular posts from this blog

AT&T FlexWare thoughts

Image
FlexWare is AT&T's latest offer for NFV (Network Function Virtualization) targeting software control of VNFs for enterprise customers. One of its greatest advantages is its multi-vendor approach, as It is offered in conjunction with AT&T VPN service and supports Juniper and Cisco virtual routers, Fortinet virtual security, and Riverbed virtual WAN accelerator. These AT&T-certified FlexWare Applications can be deployed on either small or medium industry standard FlexWare Devices and come with flexible AT&T or customer management options. According to Roman Pacewicz, SVP &T Business,   In less than 2 years, AT&T has been deployed to more than 2,000 sites globally, expanding to over 200 countries and territories. Orchestration is going to be done through IBM's cloud, cognitive, analytics and security infrastructure. AT&T can install an FlexWare Device on your premises, bring it online and manage it, just as we would a traditional managed network
Read more

Out with ECOMP and Open-O, in with ONAP - Battle for Open Orchestration

Image
For quite sometime, there hasn't been any real standard for MANO-NFV Orchestration and Automation, granted that there are plenty of excellent proprietary solutions but there wasn't a real open Source reference architecture on this regard.  Somewhere around 2015, two main initiatives where created: ECOMP and Open-O. ECOMP was part the Domain 2.0 initiative which goal was to virtualize up to 75% of AT&T network by 2020 by leveraging cloud technologies (AIC, AT&T integrated Cloud) and network virtualization while reducing CAPEX and achieving operational  The main issue was that there was no playbook to follow for virtualizing and software-controlling a Wide Area Network, ECOMP was the biggest software project to AT&T to date, tasked to address these key issues. It stands for Enhanced Control, Orchestration, Management and Policy . ECOMP is an infrastructure delivery platform and a scalable, comprehensive network cloud service.  It provides automation of many s
Read more

Demystifying SDN: Open SDN Approach

Image
Demystifying SDN: Open SDN Approach By Javier Guillermo  - Principal Consultant - September 16, 2017 The joke goes around that the true meaning of Software Defined Networking (SDN) is “Still Don’t Know”.  In short, SDN is a technology that allows network administrators to no longer be reliant on static architecture of traditional hardware/networks, but freed to centrally and dynamically manage the network via open, programmatic interfaces.  This is accomplished by separating the control plane (the system that decides where the network traffic will go) from the data plane (the systems that forward the traffic onto their destination). Software Defined Networking (SDN): Business Drivers What’s driving the need to change from the transitional method of managing networks and move towards a SDN approach?  There are three key catalysts in the industry driving the need for network change as show in the graphic below. Mobility, cloud, and IoT are three very real way
Read more