Guide That Contains This Content
[+] Expand All
[-] Collapse All

Introduction to Junos Applications

Using tools provided by Juniper Networks, third-party developers, called providers can create innovative applications and manipulate existing features of the Junos OS. The term application, as used in this guide, refers to an application built by a provider.

So applications run on the Routing and System applications (formerly called the RE SDK), the Services applications (formerly called the Services SDK), or the Remote Routing and System applications (also known as the Remote applications).

  • Routing and System applications run on the control plane. Typically, these applications perform network management and protocol signaling. They also initiate servers. Positioned on the control plane, Routing Engine applications can coordinate other subsystems and services. A Routing Engine is always present in any device, so these applications are always deployable without the addition of any extra hardware or software.
  • Services applications run on the services plane. The services plane is specialized to enable high-performance, customized, and stateful packet processing on the transit or monitored traffic selected for servicing. Services applications may also perform operations similar to Routing and System applications, but such activities typically supplement packet processing.
  • With the development of the JunosV App Engine platform, providers can also build custom applications that run on other operating systems in a virtual environment. The JunosV App Engine enables non-Junos third-party applications to integrate with the Junos operating system (OS). Unlike the on-box integration model where applications are fully ported to run on Junos OS. JunosV App Engine enables these remote applications to run in their native environment requiring network integration only at the programming interfaces exposed by the network device. Each remote application gets built along with its native OS into a virtual device and is then packaged into an installable Junos package. Upon installation onto a Juniper device, the virtual device is deployed as a guest on top of a hypervisor running on the JunosV App Engine platform. You can learn more about the remote applications that run on the JunosV App Engine from the JunosV App Engine Administration Guide.

    As of Junos OS Release 14.1, remote applications no longer necessarily require the JunosV App Engine to run if they invoke JDAF services by configuring the jdaf statement at the [edit services] hierarchy level. The jdaf statement configures the routing instances on which JDAF is enabled. If the jdaf statement is not configured, then JDAF is disabled.

On some of the smaller Juniper Networks devices, physical modules do not necessarily plug in to a chassis. Rather a single box contains the necessary hardware. Nonetheless, applications are still supported in the control and services planes and we continue to use the Routing Engine and services modules terminology.

Modified: 2017-08-31