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

As NFV gains mainstream production status across carriers and service providers worldwide, important facts about the realities of a software-defined network world are coming to light.


Service levels for network functions—more commonly referred to as “service assurance”—is a concept created in the days when network functions were anything but virtual. These network services were tied to physical devices, and that hardware was “assured” to deliver its assigned “services” at a specified up-time.


In NFV, those now-virtualized network functions—or VNFs—must still meet desired service targets in order for the network to support its assigned applications at expected levels.



Enterprise applications are rapidly evolving while embracing modern “cloud-native” or “cattle” architectures such as microservices and becoming more dynamic and distributed. These applications are frequently the centerpiece of updated corporate strategies, generating new business and revenue. 


OpenStack Summit in Sydney – Vote for Juniper Related Talks

by Juniper Employee ‎07-28-2017 02:08 PM - edited ‎07-31-2017 09:15 PM

OpenStack Summit is approaching and headed to the land down under on November 6, 2017. For those who plan to attend OpenStack Summit for the first time ordo not know much about the event, this event is hosted by the OpenStack foundation every six month and is a great opportunity for OpenStack community members and developers worldwide to meet and plan for the future. Within OpenStack, there are two events. The conference and exhibition hall where you can listen to all the presentations and visit booths, and the design summit for developers to discuss new features and advancements of each project.


Juniper Networks will be participating as a sponsor in many of the OpenStack activities and will have a booth in the exhibit hall. Juniper has worked with their partners and customers again this year to submit various talks and sessions at the summit ranging from topics such as, Cloud Automation, Virtualization, Security, and IoT. This year, the summit has received an overwhelming amount of submissions from all over the globe and you get to choose which topics you would like to see presented at the conference.


It's the End of Network Automation as We Know (And I Feel Fine)

by Moderator Moderator ‎07-25-2017 07:38 PM - edited ‎08-03-2017 07:16 PM


This article was originally posted on July 5th on The New Stack at


Network automation does not an automated network make. Today’s network engineers are frequently guilty of two indulgences. First, random acts of automation hacking. Second, pursuing aspirational visions of networking grandeur — complete with their literary adornments like “self-driving” and “intent-driven” — without a plan or a healthy automation practice to take them there.


Can a Middle Way be found, enabling engineers to set achievable goals, while attaining the broader vision of automated networks as code? Taking some inspiration from our software engineering brethren doing DevOps, I believe so.


Introduction to the E2 Controller

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

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 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.


Hope SPRINGs Eternal

by Juniper Employee on ‎06-20-2017 04:41 AM

There is great interest in the promise of an SDN enabled network. Source Packet Routing in Networks (SPRING) is an SDN enabled method of routing where a centralized controller maintains the network resources and can steer traffic based on the application’s need.


As applications evolve to take advantage of the traffic engineering capability of SPRING, they will need to operate a mixed SPRING and RSVP-TE network. SPRING and RSVP-TE traffic routes independently, but they may share common links.


Are Service Meshes the Next-gen SDN?

by Moderator Moderator ‎06-19-2017 10:32 PM - edited ‎06-28-2017 08:20 AM

Whether you’re adopting a containers- or functions-as-a-Service stack, or both, in the new world of micro-services architectures, one thing that has grown in importance is the network... <cut>


The idea and implementation of a service mesh is fairly new. The topic is also garnering a lot of attention because they handle the main networking challenges listed above (esp #1 & 2), and much more in the case of new projects like the CNCF Linkerd and newly launched project Istio.


Since I’ve written about SDN for container stacks before, namely OpenContrail for Kubernetes and OpenShift, I’m not going to cover it super deeply. Nor am I going to cover service meshes in general detail except to make comparisons. I will also put some references below and throughout. And I’ve tried to organize my blog by compartmentalizing the comparisons, so you can skip technical bits that you might not care for, and dive into the ones that matter most to you.


So on to the fun! Let’s look at some of the use cases and features of services meshes and compare them to SDN solutions, mostly OpenContrail, so we can answer the question posed in the title. Are service meshes the “Next-Generation” of SDN?logos service mesh.png





Juniper demonstrates a complete end-to-end NFV solution in NIA Interop Testing

by Juniper Employee ‎06-02-2017 08:09 AM - edited ‎06-08-2017 12:21 AM

Another phase of NFV interop testing was announced by The New IP Agency (NIA) this past March, and as with previous phases run by EANTC, Juniper took up the challenge and participated in a big way! 

By the time the dust had settled, Juniper was able to demonstrate interoperability of all of its participating platforms, and was the only vendor to successfully participate in all three categories tested in this phase.




SD-WAN: The Next Disruption of Virtualization


Come hear more about this topic at the Telecom Council on June 1st.


Serverless Can Smarten Up Your DevOps & Infrastructure Stack

by Moderator Moderator ‎05-25-2017 10:20 AM - edited ‎05-25-2017 10:48 AM

serverless-code-2170396_1920.jpgAs IT organizations and cultures reshape themselves for speed, we’ve seen a trend away from IT as a service provider, to IT as:

  • a collection of smaller micro-service provider teams,
  • each operating and measuring like autonomous (micro-)product teams,
  • each building and running technology systems as micro-services.

Now you’ve heard me cover the intersection of microservices and containers quite a bit, along with CaaS/Kubernetes or PaaS/OpenShift orchestration. In this blog, I’m going to change it up a bit and talk about the other kind of microservices building block: code functions.


Here I’m talking about microservices run atop of a serverless computing a.k.a. function-as-a-service (FaaS) stack. Serverless is a 2-years-new yet already well-covered topic. If you need a primer this one is the best I’ve found.


In my last blog, I examined avoiding cloud lock-in by bringing your own devops and software-defined infrastructure stack: bringing your own open-source/standard toolchain across public/private IaaS, you maintain portability and harmonized, if not unified, hybrid cloud policy. This software-defined infrastructure stack, underpinning the user- or business-facing applications, is also still just a bunch of software applications. FaaS is just one example of an increasingly popular app-developer technology that can be employed by infrastructure developers too, though this one hasn’t gotten much attention yet in that regard.


If you read the primer above, you won’t have learned that the popularity of FaaS systems like Lambda to reduce developer friction has led to a number of open source projects like OpenWhisk, and others that to sit atop of a CaaS/PaaS (such as Fission or Kubeless). If a FaaS is likely to exist in the application stack, it may well make sense to standardize on incorporating one into devops and infrastructure stack. Let’s see.


Juniper Networks Technical Books