SDN and NFV Era
Showing results for 
Search instead for 
Do you mean 

Introduction to the E2 Controller

by Juniper Employee ‎06-28-2017 08:19 AM - edited ‎07-05-2017 12:35 PM


To handle increasing requirements, networking has layered capability on top of capability for decades in an incremental pursuit of improvement. The result has been that networks have scaled in terms of doing what they need to do, but they have done so at the expense of complexity. Put more simply, networks have gotten better while networking has gotten worse.


This is largely what spawned the SDN movement. The recognition that management and control needed to be simplified led architects to seek out abstraction. Of course, by abstracting configuration, operators lose some of the pinpoint control. But in giving up control, they gain the ability to scale operationally.


Abstraction was initially about using centralized controllers as API brokers. Controllers basically were responsible for translating policy constructs into vendor-specific configuration. As that control model has evolved, it has led to the rise of intent-based networking.


Intent-based networking is predicated on the idea that operators should specify what needs to happen without necessarily explicitly declaring how it is to happen. More directly, operators need to describe behaviors and constraints in a way that avoids needing to translate that into explicit configuration.


The combination of controllers and intent-based models are the next generation in management in control, particularly in service-driven networks where behavior is complex and requires distributed coordination.


Intent-Based Networking

What is intent?  Intent-based models declare “what” to do but not “how” to do it.  For example, an operator may want to create a connectivity service.  They do not describe route-targets, route-distinguishers, BGP address-families nor specific packet encapsulations.  Rather they declare that a p2p connectivity service should be created between two service points.  In turn, the SDN Controller, E2, transforms that declaration into service-, device- and technology-specific semantics and propagates them to network devices.




Intent can also be thought of as the single source of truth that describes the intended state of an infrastructure. In its essence, intent represents business rules, users, applications, policies, inventory, constraints, capabilities, and design elements, and it is highly variable in nature across different networking scenarios. Without a single source of truth, you can spend most of your time developing middleware that simply synchronizes all the truth that is otherwise distributed, leaving little time for actually caring for existing services or architecting new ones.


As an example, today, many systems measure compliance based on configuration verification. This means that configurations essentially become the source of the truth. While they certainly are a source of truth, the biggest problem is that it is very difficult, if not impossible, to determine the intent of those configurations within a complex system. To be specific, a bug in a device’s software may expose vulnerabilities even in the presence of a perfectly compliant configuration.

Intent moves operators away from managing configuration. Here are some basic tenets of intent:


  • Intent is stable: It doesn’t change as a result of a link going down, changing router vendors, upgrading software, or any other change to the infrastructure. This property frees applications from the underlying network details.
  • Intent is non-specific: Intent is not specific to protocols, vendor operating systems, media types, or packet formats. Because it is abstracted from changes to the infrastructure, intent-based networking eliminates the impact of changes to the intent.
  • Intent is common: The interface is designed to allow different services, developed independently, to express their resource requirements in a common language.
  • Intent scales out, not up: It doesn’t change when you go from one network controller domain with a million ports to a thousand network controllers with a thousand ports each.
  • Intent provides context: When different systems push low-level rules, there is always a risk of conflicting changes to the system state. Attempts to examine these rules (of the form “match this header and perform this action”) and resolve such issues have been unsuccessful because at this low level of abstraction, it is impossible to decode the overall intent of the services pushing the rules.

By implementing an intent-based interface on E2 it will deliver the benefits described above and, in turn, pave the way for simpler yet more optimized solutions.


E2 Concept

E2 is an SDN Controller that instantiates network service instances across nodes of a network, whether physical or virtual. Continuous streams of telemetry data from each network device assist the engine in placing service instances.  E2 leverages intent-based service models to describe the resulting network service instances.



Intent: a high-level description of a network service request. Such requests will result in a decision on where it [service instance] should be placed, based on request type, available resources and network status.


The intent is then transferred to the network elements using a combination of configuration and control APIs exposed by the network devices. The engine receives a wide variety of real-time telemetry data streamed from the network devices, including network topology, network utilization, link and path latency, flow data, routing information, and application and user metrics. These telemetry streams are utilized to make intelligent placement decisions to ensure optimal utilization of network and nodes. The system also provides lifecycle event orchestration for workflow customization.


E2 is not another network management system. An NMS typically does not make decisions! E2 will make decisions by optimizing the placement of services, leveraging control and telemetry data exposed by modern network elements.  E2 offers a unique combination of intent-based service abstraction, network resource orchestration and optimization along with advanced analytics to automate the process of translating a service request into a service instance configured and active on the most optimal resource.  Tasks such as service placement, service assurance, service maintenance and resource optimization and even capacity planning when it comes to service capabilities, will no longer require human or manual intervention but will be automated, leveraging advanced analytics.



Contrail Controller, an SDN controller from Juniper Networks, is currently deployed by vendors to orchestrate the creation of virtual networks in data centers. E2 is being built on top of the Contrail platform to orchestrate service provider networking. Some of the unique functionalities E2 provides include:


  • Service Abstraction
  • Vendor neutral
  • Multi-vendor support

By abstracting services, Contrail allows SDN to function as a compiler by translating abstract, high-level workflows to low-level configuration. This is achieved primarily through the data models, which essentially leverages SDN as a compiler. The data model allows applications to express their intent in a declarative rather than an imperative manner, the fundamental aspect of E2 architecture. The data manipulated by the application also stays within Contrail, which makes the application virtually stateless.  The consequence of this design is E2 applications are freed from the complexities of high availability, scale and peering.




The configuration node of E2 is responsible for transforming any change in high-level service data model to a corresponding set of changes in the low-level technology data model. This is conceptually similar to a Just In Time(JIT) compiler


The Contrail data model is vendor neutral, and it has multi-vendor support to interact with network devices like Juniper, Alcatel, Cisco etc. It works by first translating the low-level data model to a meta tree (an intermediate representation format) and then rendering to vendor-specific configuration.





Edge and Aggregation

Today, most of the SPs want the ability to do network service automation. Access Edge and Aggregation SPs manage the most complex services, residential, mobile, internal OSS, business edge customers etc. and automation becomes a crucial part of their business success. One use case is they need to backhaul customer circuits to the edge service layer based on the network resources and the live state of the network.




E2 addresses the problem by enabling:

  • Intent-based service creation from vendor input, and
  • Service placement from intent, taking into account the telemetry for live network state

A few other SP requirements are:

  • Ability to bring down network nodes to maintenance without services running on those nodes being impacted
  • Ability to deploy a new network node to the network for capacity and redirect services seamlessly
  • Ability to move services across different network nodes in the network, intelligently

Routing and Traffic Engineering

The most fundamental aspect of the routing and traffic engineering use cases within the E2 space is the manipulation of routing policy as a result of the analysis of telemetry data.  Whether the policy manipulation is meant to influence traffic engineering or exit/ingress peer engineering or security is somewhat irrelevant. By collecting and analyzing flow-based telemetry, one can describe how to change routing policy to maintain optimal forwarding in small FIB routers or load-balance egress or ingress traffic across a set of peers, for example.  Furthermore, through the correlation of multiple BGP address families, it is possible to validate several different kinds of data-plane and control-plane synchronization faults without injecting synthetic probes into a network.




Another important routing-specific use case is leveraging “BGP as an API” in the network.  BGP is a powerful protocol for routing state distribution, but, at times, BGP best-path computation can result in unanticipated results.  The route-server and RPD API extensions to Junos, combined with E2, enables client-specific RIB modification to become a reality.




Last but not least, almost every VPN/service scenario in modern networks warrants the dissemination of routing state, via BGP, in the form of a specific BGP address family. Through its intent-based models, E2 orchestrates client-specific configuration, which is complex in and of itself.  But also optimizes the optimal placement and resource utilization of virtual entities, such as route reflectors, used for scalable propagation of the VPN/service specific reachability information.




Intent-based control is the only means by which operators will be able to thrive in an era that is simultaneously more demanding on its services and requires that operations be both cost-efficient and fast. But intent models will be hyper-contextual, meaning they need to developed not just for use cases but also specific deployments. Juniper has built out an intent-based framework that allows for these models to be developed and used, in combination with real-time data being streamed from the infrastructure.



Colby Barth,

Babu Singarayan,

Nitin Kumar,


on ‎06-28-2017 05:01 PM

Hi cbarth,


Nice post Smiley Happy

I understand the whole picture of Intent based controlling. 


Is there any product going to be release from Juniper?

If yes, I am very egar to take a look at this product.




Juniper Networks Technical Books
About the Author
  • Prior to Juniper acquisition, Ankur was the Founder and CEO of Contrail Systems Inc - a pioneer in standards based network virtualization and scale-out networking software. Ankur has over 15 years of experience in building world-class networking products and leading high performance teams. Prior to Contrail, Ankur served as Chief Technology Officer and VP of Engineering at Aruba Networks, where he played critical roles in the rapid expansion of team, products, and global businesses. Before Aruba, Ankur helped drive Juniper’s initial entry into and expansion of the Ethernet Switching market. Ankur received his MSEE from Stanford University & BSEE from the University of Southern California.
  • David Noguer Bau is the head of Telco Vertical Marketing at the SP Strategic Marketing team in Juniper Networks. He has extensive experience in Service Provider network evolution and regularly runs executive sessions with technical and marketing teams of important telecom operators to accelerate the adoption of virtualisation. David is based in Barcelona and has over 15 years of experience in the telecommunications sector. Prior joining Juniper Networks, Mr. Noguer Bau spent seven years at Nortel where he was a Business Development Manager specializing in Carrier Ethernet and Broadband areas. Before Nortel he worked at Eicon-Dialogic as Technical Manager in Spain. David has been the Country Marketing Chair at Metro Ethernet Forum for Spain. Mr. Noguer has wide experience speaking at international Conferences. He was graduated as Computer Engineer by Universitat Autonoma de Barcelona (UAB) and has an executive MBA from EADA Barcelona and executive education at the Thunderbird School of Global Management (Arizona) and the Henley Business School (UK). The views expressed here are my personal opinions , have not been reviewed or authorized by Juniper Networks and do not necessarily represent the views of Juniper Networks.
  • Donyel Jones-Williams is the Director of Service Provider Product Marketing Management overseeing all of Juniper's Service Provider Products for Juniper Networks. In this role, he leads all of the internal and external marketing activities for Juniper with respect to routing, automation, SDN and NFV. Prior to joining Juniper Networks in January 2014, Donyel was a Senior Product Line Manager for Cisco Systems with in the High End Optical Routing Group managing product lifecycle for multiple products lines helping telecom providers operate efficiently and effectively including; ONS 155xx Product Family, ONS 15216, ONS 15454 MSTP, Carrier Packet Transport Product Family, ME 2600x, & ASR 9000v. He also negotiated favorable agreements with 3rd-party vendors furnishing components and parts and conducted both outbound and inbound marketing (webinars, case study-development, developed and delivered both business & technical at Cisco Live 2005-2012). Donyel graduated from California Polytechnic State University-San Luis Obispo with a Bachelor of Science in Computer Science. While attending Cal Poly SLO he was a collegiate student athlete playing football as a wide receiver and a key member of the National Society of Black Engineers. Donyel is now an active volunteer for V Foundation.
  • Remarkably organized stardust.
  • Jennifer Blatnik is vice president of cloud, security and enterprise portfolio marketing at Juniper Networks with focus on enterprise deployments of security, routing, switching, and SDN products, as well as cloud solutions. She has more than 20 years of experience helping enterprises solve network security challenges. Before joining Juniper, Jennifer served multiple roles at Cisco Systems, Inc., including directing product management for security technologies aimed at small to medium enterprises, as well as supporting managed services, cloud service architectures and go-to-market strategies. She holds a B.A. in Computer Science from University of California, Berkeley.
  • Jerry oversees all aspects of OpenLab which serves as a catalyst to spark the development of new innovative software applications or solutions that leverage the power of SDN/network programmability and intelligence. OpenLab is unique within Juniper and with its polished facility, globally accessible lab, and educational programs – such as the SDN “hackathons,” it serves as a tool for customer, partners, and academia. Prior to this position, Jerry led the development, management and marketing of the company’s strategic partnerships for video/unified communications, optical networking, and content/media delivery. In addition to handling the day-to-day oversight of the partnerships, he established new cross-partner go-to-market processes to drive and manage joint field opportunities. Before joining Juniper, Jerry led the Lucent Technologies application hosting/service provider marketing organization. He has over 25 years of experience in the data networking field with a focus on strategic alliance development, marketing, and technical field support. Jerry possesses a BS degree in Computer Science from St. John’s University in New York. He is active as a Juniper ambassador within the technology and academic community which includes advisory board positions with both NJIT and Rutgers in New Jersey.
  • I have been in the networking industry for over 35 years: PBXs, SNA, Muxes, ATM, routers, switches, optical - I've seen it all. Twelve years in the US, over 25 in Europe, at companies like AT&T, IBM, Bay Networks, Nortel Networks and Dimension Data. Since 2007 I have been at Juniper, focusing on solutions and services: solving business problems via products and projects. Our market is characterized by amazing technological innovations, but technology is no use if you cannot get it to work and keep it working. That is why services are so exciting: this is where the technology moves out of the glossy brochures and into the real world! Follow me on Twitter: @JoeAtJuniper For more about me, go to my LinkedIn profile:
  • Mark Belk is the National Government Chief Architect at Juniper Networks
  • Mike Marcellin is Senior Vice President and Chief Marketing Officer, leading the global marketing team responsible for marketing Juniper’s product and services portfolio and stewarding the brand, driving preference for Juniper in the market, training our partners and account teams, and developing a differentiated information experience for our customers. Before joining the global marketing organization, Marcellin led business strategy and marketing for Juniper’s industry-leading portfolio of high-performance routing, switching and security products. Prior to joining Juniper in 2010, Marcellin served as Vice President of Global Managed Solutions for Verizon, where he oversaw product development and marketing of its managed IP networking, hosting, security and IT solutions for businesses around the world. He also served as Vice President of Global Product Marketing for Verizon Business, executive director of Verizon Business’ IP and Ethernet portfolio as well as leading the company’s eCRM marketing division. Marcellin began his career with MCI in 1994. Marcellin is a Board Member for the Telecommunications Industry Association and a Board Member of US Ignite, an NSF-sponsored initiative. Marcellin holds two patents and was a Rodman Scholar at the University of Virginia, where he received a bachelor of science degree with distinction in systems engineering. He is based in Sunnyvale, California.
  • I love the intracacy and intimacy of succesful communications. Why and how people engage with each other is fascinating. I am also consumed with the way IT changes behaviours, values and expectations in society. I bring this sense of wonder to my role in EMEA Service Provider Marketing Programs at Juniper Networks. Down time: My passions are music, reading, politics, Derby County and playing the guitar (and the harmonica). You can follow me elsewhere: twitter: @neilpound my personal blog: my LinkedIn account: Neil Pound
  • Paul Obsitnik is Vice President of Service Provider Marketing for Juniper Networks Platform Systems Division (PSD), responsible for the marketing of Juniper’s portfolio of high performance routing, switching, and data center fabric products to Service Providers globally. Paul's team is responsible for marketing strategy, product marketing, go-to-market planning, and competitive analysis worldwide for the Service Provider segment. Obsitnik has extensive experience in marketing, sales and business development positions with a proven track record in creating technology markets. He has served in senior marketing and sales management positions at several companies including BridgeWave Communications, ONI Systems, NorthPoint Communications and 3Com. Paul holds a Bachelor of Science with Honors in Electrical Engineering from the United States Naval Academy and a Master of Business Administration from the Harvard Graduate School of Business. Obsitnik is based in Sunnyvale, California.
  • Praful Lalchandani is a Product Manager at Juniper Networks focussing on the Data Center portfolio. Praful is a seasoned veteran in the networking industry, with experience spanning over 15 years building networking products and helping service providers, cloud providers and enterprises with their networking requirements.
  • Pratik Roychowdhury currently leads product management for Juniper's SDN and Cloud Software product namely Contrail. He has been with Juniper Networks for the last six years, leading product management activities for Juniper’s Network Virtualization and Network Programmability products and taking some of these products from concept to release. Overall, Pratik has spent 16+ years in the hi-tech industry assuming various roles including product development at Citrix, strategy & product management at early stage start-ups, and technology investment banking at UBS. Pratik has a B.Tech in Electrical Engineering from Indian Institute of Technology and an MBA from Univ of Michigan, Ann Arbor (Ross School of Business).
  • VP of engineering, Juniper Networks & founder, AppFormix Entrepreneur and founder with successful exits from two networking startups. Sumeet holds more than 20 patents with technologies implemented in shipping products and has received numerous awards from organizations as diverse as MIT and Interop. His AppFormix team at Juniper Networks is shipping an automated, real-time monitoring environment that uses AI and machine learning to autonomously mitigate application and network function issues before they impact QoS or user experience.