A Pathway to Disaggregation via Juniper OS

While Juniper had numerous objectives associated with the disaggregation of Junos, 2 in particular stand out. Firstly, Juniper wanted to supply an architecture which totally decoupled platform software and network functionalities from the essential hardware. This clearly implies that, when you buy a QFX5200 switch, you?ll see that Junos is now a virtual control plane known as vJunos.

This separation permits Junos to concentrate singularly on control plane undertakings like OSPF, BGP and MPLS VPN minus concerns for platform-centric particulars or what packet forwarding engine is linked with the switch ASIC. This allows Juniper the capability to supply next-generation platforms with negligible modifications to the OS, returning a much quicker ?time to innovation? from a hardware viewpoint.

Another objective of disaggregation is to provide open, direct access to the hardware forwarding engine via standard, open APIs via a SDK. The focus here is on ?standard? and ?open?; at Juniper, supplying an open platform implies supplying direct hardware programming abilities via support for a Switch Abstraction Interface (SAI) and direct control over the hardware through a set of famous APIs, irrespective of the hardware.

It is worth remembering that the QFX5200 switches are the earliest Juniper platforms to provide totally open and unparalleled container and VM support. The inside environment permits any application (3rd-party, native binaries, RPMs and VMs) to be assimilated into a root container, allowing the user a ?sandbox? area where deployed software is totally secluded from the innate host Linux OS.

This method is in divergence to other sellers who permit applications or RPMs to be deployed directly on their systems, revealing severe susceptibilities and generating the possibility for disastrous system failure should an application go crazy. That being said, the QFX5200 is the foremost Juniper platform to supply a totally open virtualized environment, opening a window of opportunity for anybody interested in NFV, Service-Chaining, SDN, or just wanting to run a 3rd-party application.

Disaggregated Junos and the Future

Although the QFX5200 is the initial Juniper platform providing a truly open architecture, as software abilities advance with each release, other products will embrace the same architecture and supply the same abilities. These consist of a total virtualization infrastructure adept at making a sandbox environment which permits any native binary, container, RPM or VM to be deployed devoid of needing code to be compiled or waiting for a 3rd party to incorporate new software.

The virtualization substructure interacts directly with the data plane, supplying a dedicated inside connection to the front-panel ports. This permits users to push probes straight from any 3rd-party VM into the data path and carry out analytical activities. This is just one instance; there are many more. Juniper also allows users who are aware of and like CLI the choice to continue using it; those who aren?t acquainted with the CLI have direct access to the Linux environment. Junos itself is now a virtual construct, running as a VM and fixated predominantly on the control plane, which is totally distant from the hardware and platform particulars.

On the API flank, a set of control plane, data plane and platform-centric APIs are supplied. This is indispensable to administering, monitoring, and crafting networks today. With all of these abilities at the vanguard, it implies only one thing: if you?re a network engineer, Junos hasn?t actually changed, but if you?re in DevOps, your life just got a lot better.

Need more guidance? Justÿcontact us today.

Juniper OS Open Source Universal Telemetry Collector – Part 2

Additionally, no free tools are obtainable that supply a simple solution for mining Netconf data for network monitoring purpose. An easy, open solution for gathering, normalizing and envisioning all Junos KPIs would be a major step ahead for these clients. This is how the open-source universal collector (OpenNTI) was born.

Open-Source Collector

OpenNTI is bundled as a set of Docker containers, which are able to be run on any operational system supporting Docker.

Each container is constructed in a ?plug-and-play? manner. Everything has been preconfigured so that the user only has to initiate the container and stream data to it; collected information can then be shown in preconfigured user dashboards. Trivial information input is needed only if you want to collect information utilizing Netconf over SSH.

OpenNTI supports numerous streaming formats:

ÿÿ JTI: GPB/UDP (for the MX Series routing platforms)

ÿÿ AnalyticsD: JSON/UDP (for the QFX Series switching platforms)

Differentiated UDP ports are utilized to obtain streamed information from differentiated device types; each UDP port is related to a Fluentd input plugin. Normalized information is created once the information has been processed by the FluentD input plugin. A preconfigured FluentD output plugin writes structured information as a time-series into the InfluxDB database. This super flexible architecture permits users to simply interchange an output plugin if needed. For instance, a differentiated database can be replaced, as a substitute of InfluxDB.

KPI values, which are not obtainable through the JTI interface, can be demanded from time to time by utilizing Netconf over SSH.

The Grafana UI is preconfigured with dashboards for both the Data Streaming Collector and Data Collection Agent.

The same Docker container admits syslog happenings, which are saved to the same InfluxDB. This permits significant events (such as modifications in the configuration or error syslogs) to be overlaid on all graphs in a shared dashboard.

OpenNTI supplies a simple method to gather, normalize and envision every KPI obtainable in Junos. While not an endorsed Juniper product, Juniper is making this tool obtainable to the Juniper Networks user community as an open source project.

To help grow its utilization, Juniper has also created a sequence of short ?how to? videos which can assist with an overview of OpenNTI.

Need more guidance? Justÿcontact us today.

Juniper OS Open Source Universal Telemetry Collector – Part 1

The Simple Network Management Protocol (SNMP)?established and simple to utilize?still is the principal monitoring protocol for networking equipment. Nevertheless, as technology advances, SNMP is presenting some restrictions in tackling today?s most persistent problems. For example:

ÿÿ Pull vs. push: SNMP utilizes a ?pull? model where servers begin data collection on a set schedule?for example every 2 minutes. Nevertheless, a lot can occur in 2 minutes, and a plethora of data?like traffic drops caused by bottlenecks?can be squandered if polling isn?t performed more regularly. A ?push? model which reports distinguished happenings or data, initiated by pre-set starting points, activities or happenings, is desirable.

ÿÿ Not all data is obtainable in SNMP: While fifteen years ago SNMP supplied the most perceptibility into and data about network equipment, that is no more the situation. Modern network operating systems incorporate feature rich APIs which allow users to organize their equipment to access all kinds of data in a programmatic manner. As an example, on Juniper equipment which is running the Junos OS, Netconf and Yang data models can be utilized to gather information at smaller intermissions, focused by happenings, and by using streaming technology ? which is not possible with old-style SNMP.

The capability to collect statistical information at scale is mainly due to Junos Telemetry Interface (JTI), a super scalable distributed collection engine developed to assist network operators stream statistics and event states to data collectors, network controllers, or comparable equipment for real-time or post investigation.

JTI utilizes a ?push? client which subscribes itself to key performance indicators or KPIs (like interface data) which are streamed straight from a device. The data format can be binary (e.g. Google Protobuf) or JSON based. In certain platforms, statistics streaming is performed completely in hardware to ensure the optimum general system performance.

Need more guidance? Justÿcontact us today.

OpenConfig and Junos Empower Network Programmability

All through the previous year, the OpenConfig initiative and operator group has been in power in full force creating a collection of vendor independent data-models which lay the base and supply the building blocks of a next-gen arrangement, operations and streaming telemetry context. Juniper Networks has been proactively involved in the OpenConfig initiative from the beginning, allowing support for the arrangement of key internet routing protocols and the providing of core network element data through OpenConfig demarcated models and scalable cutting edge RPC frameworks.

OpenConfigÿGoals

Dependable Vendor-Neutral Models

One of the core goals of the OpenConfig initiative is to create vendor-neutral data models for the configuration and administration of network fundamentals. These days there are at least as many differentiated configuration schemas for routing protocols as there are dealers. Even inside each vendor there may be numerous instruments for arranging undistinguishable functionalities across differentiated platforms and network operating systems. This multiplicity considerably increases the expense for operators when creating back-end systems which intermingle with these network fundamentals.

By outlining a set of vendor-neutral data models for frequently utilized features and protocols, the configuration procedure can be radically streamlined across platforms and vendors. Having these models in hand, an operator can construct offline plans and serialize configuration information into the desired format for intake by a vendor/platform in a reliable manner without needing to worry about creating the suitable vendor-centric syntax to impact a specific configuration.

Declarative Configuration

One of the key principles of OpenConfig operations is the utilization of declarative configuration. This allows operators to stipulate their configuration purpose and have the network component identify how to apply that purpose. The load of needing to outline the exact steps to realize that goal is removed from the network operator and put back on to the network component.

From its launch, Junos OS has empowered declarative device arrangement. Operators who implement the OpenConfig models and use them on Junos can be guaranteed that they will be able to implement the models in a declarative way while the Junos translation engine completes the implementation centric activities.

Model Only Frequently Installed Features

The models and the functionality being demarcated inside the OpenConfig group do not try to be all things to everybody. Rather, the purpose is to model only frequently installed features inside operator?s networks. By definition, this leaves some functionalities out-of-scope for OpenConfig models. Due to the malleable disposition of the Junos application and packaging of OpenConfig support, Juniper Networks (and clients themselves) are able to outspread the abilities of the baseline OpenConfig models and supplement these models and the matching mapping abilities to allow the utilization of Junos-centric features while keeping in place the vendor-autonomous baseline models.

While providing support for the OpenConfig models, Junos has been careful to supply clear deviances where there may be variances amongst the baseline definition (in terms of units, application chain of command, etc.) and where there may be empty gaps in coverage areas. Clients may want to extend the baseline models themselves, or Juniper Networksÿmay choose to provide expansions to the baseline models for frequently used Junos functionalities which are not present in the baseline models in order to simplify installations for clients.ÿ

Relationship with The Other Models

Over the previous few years, there has been an eruption of YANG-based modeling undertakings inside the IETF. While it is very inspiring to see the energy behind the application of a shared model-based method to IETF technologies, there are a few challenges linked with the propagation of models, their relationship with each other, and the reliability of organization over numerous disparate models.

Modular Delivery

In line with the goals of the OpenConfig group to quickly iterate, Juniper is decoupling the delivery of OpenConfig model support from the base Junos OS release procedures. This implies that as the preexisting models mature and new ones become obtainable, Juniper can ship OpenConfig bundles disjointedly and autonomously from Junos releases. As a result, an operator can qualify a release for installation in their network and later on incrementally implement the utilization of OpenConfig models by deploying autonomous OpenConfig bundles from Juniper as the equivalent models are developed.

Need more guidance? Justÿcontact us today.

Juniper OS ? Opening a Window into a Box of Surprises

Advent calendars are employed all over the world to count down the days remaining to Christmas. ÿFirst utilized by German Lutherans to keep a tab on the track the ?advent? in the direction of the most significant holiday in the year, advent calendars have now become a universal Christmas adornment in many homes all over the globe.

Advent calendars usually take the shape of a big quadrilateral card with having a certain quantity of windows. Each window indicates a day in December leading up to Christmas. ÿEvery day one of these windows is opened to show a hidden treasure, which can be a verse, story, picture, toy, or, most usually, a chocolate delicacy.

In a manner, Juniper?s Junos OS is similar to an advent calendar.

The appearance of open-source toolkits, virtualization technologies, and DevOps procedures has marshaled in a new age of modernization. Service providers and companies alike now must possess a network operating system which is open, super programmable, and have a malleable structural design which reacts to ever-changing marketing circumstances.

Junos OS was a chief disruption to the networking business when it was launched 20 years back, and it endures to be the industry?s foremost Operating System today. Juniper has made it simpler than ever before to benefit from the power of control, automation, and orchestration via uninterrupted access to the Junos OS control plane existing on Juniper routing and switching equipment, whether by using the Juniper Extension Toolkit (JET) or effortlessly via a broad range of open-source automation toolkits like Puppet, Chef, Ansible, Snabb, and Salt.ÿJunos also provisions support for PyEZ, a micro framework for Python created by Juniper, which allows developers to remotely tailor and automate equipment running Junos.

Similar to an advent calendar, Junos supplies a differentiated window behind what is a new and delightful surprise giving you the ability to truly automate your networking environment.

There are limitless opportunities with Juniper?s automation.ÿ Please see the Automation Use Cases at Juniper Networks for further information.

Need more guidance? Justÿcontact us today.

Juniper OS is Adding Automation and Analytics to the Most Scalable Routers

Junos Provides Scalable Investments for Long Term Advantages

Provided the rapid speed of revolutionary changes and the downward pressures which rivalry has retained on telecommunications connectivity and services price structures, old-style ?rip and replace? updates are no longer an economically feasible choice. In its place, service providers must concentrate on substructure investments which assure the users of swiftness and scalability to increase their return on investment (ROI).

At the network edge, service-focused routers which have been purpose-built for investment-protection scale provide a practical way forward. These modular edge routers empower the simple addition of upgraded switch fabrics, routing engines, and line cards which allow service providers enhanced capacity and the capability to benefit from emerging technologies?without necessitating a huge forklift network upgrade.

Enhancing Operations to Maximize ROI

In tandem with investments in potent, scalable edge routers, service providers can enhance return-on-investment (ROI) by updating their operational environs. Physically exhaustive services conception and provisioning procedures are not fast enough for the modern day market realities, and operations expenditures are quickly outstripping revenue expansion. A DevOps methodology to operations can address these challenges. Fruitful DevOps practices utilize processes automation and analytical tools which are completely incorporated into the network.

  • Automation assists service providers in creating and delivering network-centric services without the delay, expense, and risks related to old style manual operations; it also supplies APIs and standards-based protocols which minimize integration and interoperability problems with 3rd-party apps and back-office systems.
  • Analytical abilities provide effective new methods of monitoring, enhancing, and monetizing the network, utilizing real-time awareness for fundamentals, subscribers, and applications.

Differentiation

Juniper has been working closely with service providers all over the world to assist them in succeeding in their respective ferociously competitive, ever-growing industry models. Juniper endeavors to revolutionize aggressively to produce solutions powered for robust business outcomes. Juniper?s incessant endeavors have resulted in new, investment-safeguarding performance and scale improvements for the industry-leading MX Series 3D Universal Edge Router portfolio. Juniper has also launched automation and analytical tools like the Juniper Extension Toolkit for Junos OS, which streamlines 3rd-party application assimilation with Juniper OS, and the Junos Telemetry Interface, which provides high-frequency telemetry statistics for performance monitoring and enhancement tools.

Via these exciting new features, Juniper arms service providers with a robust set of benefits to assist them in maximizing the ROI and stay ahead of their competitors: investment-safeguarding scalability for immense expansion, and a simplified operations environment. Working in tandem, these features assist service providers in getting more value out of their corporate networks today and well into the future.

Need more guidance? Justÿcontact us today.

Disaggregating Juniper OS for Data Center Modernization

The fundamental substructure of the modern day IT data center has to be constructed on a concrete base, but one which is flexible enough to acclimatize to the daily ever-changing business requirements. That flexibility needs to also encompass the data center networking equipment and software; they need to permit users to activate new features, functionalities, and services with the same speed as today?s evolving business needs.

Juniper has identified a requirement for a disaggregation of networking equipment and software to provide IT companies with the flexibility to run the software they require, when they require it, on the hardware platform of their selection. This disaggregation also permits enterprises to control their software expenditure over time, while interchanging their deployed equipment as and when needed.

To provide for this requirement, Juniper has designed a disaggregated version of the Junos Operating System substructure. It?s modular, founded on Linux, and constructed from the ground up for automation and programmability. The disaggregated software permits users to administer the data center switch similar a server?you can run 3rd-party applications, tools, and virtualized services in a virtual machine (VM), or as containers right on the switching device.

Why the need for Disaggregated Software?

This improved software infrastructure provides a plethora of advantages. Administering the system as if it were a server breaks up the preexisting IT silos, and it permits DevOps and NetOps teams to cooperate, so they can minimize delivery times and expenditures for IT services. The substructure also leads to increased dependability, integrating In-Service-Software-Upgrade (ISSU), with Junos software running on a Virtual Machine (VM). And with these modularized constituents, the software can comprise faults inside an affected module.

Disaggregated software allows companies to install whatever 3rd-party applications, tools, and services they require directly onto the switching device. They are able to upgrade applications which are running natively by utilizing normal Linux depositories, without needing to wait for a new Juniper OS release.

Automation and programming tools like Puppet, Chef, Ansible, and services including firewall, analytics, deep packet inspection, Wireshark, and zero touch provisioning (ZTP) is able to run right on the switching device. IT staff is now able to program the switch?s control or data plane straight via APIs, thereby enhancing networking processes.

Data Center Innovations Platform

Juniper?s disaggregated software substructure opens up a new platform which empowers companies and Juniper?s partners to bring more IT revolutions and provide value-added services for the data center, in a structural model similar to application stores for smart phones.

Supplementing the improved Junos software substructure, Juniper has launched a data center switch which provides support for Juniper?s disaggregated hardware and software model. The QFX5200 pools high-performance switching with the features, functionalities, and processing power of a quad-core CPU server, supplying speeds ranging from 10GbE to 100GbE and providing support for the evolving new 25GbE and 50GbE Ethernet standards.

The QFX5200 switch having disaggregated Juniper OS software is supported closely with Juniper?s open, easy, and intelligent MetaFabric structural design, therefore allowing companies the flexibility they require to construct the best-in-class public, private, or hybrid cloud data centers which will power their business into the next decade.

Need more guidance? Justÿcontact us today.