NOTE: There are multiple ways to implement the basic disaggregated Junos
OS architecture on various platforms. Details can vary greatly. This topic
describes the overall architecture.
The virtualization of the simple software process running on fixed hardware poses several
challenges in the area of interprocess communication. How does, for example, a VNF
with a NAT function work with a firewall running as a container on the same device?
After all, there might be only one or two external Ethernet ports on the whole device, and
the processes are still internal to the device. One benefit is the fact that the interfaces
between these virtualized processes are often virtualized themselves, perhaps as SXE
ports; which means that you can configure a type of MAC-layer bridge between processes
directly, or between a process and the host OS and then between the host OS and another
process. This supports the chaining of services as traffic enters and exits the device.
JDM provides users with a familiar Junos OS CLI and handles all interactions with
underlying Linux kernel to maintain the “look and feel” of a Juniper Networks device.
Some of the benefits of the disaggregated Junos OS are:
•
The whole system can be managed like managing a server platform.
•
Customers can install third-party applications, tools, and services, such as Chef,
Wiireshark, or Quagga, in a virtual machine (VM) or container.
•
These applications and tools can be upgraded by using typical Linux repositories and
are independent of Junos OS releases.
•
Modularity increases reliability because faults are contained within the module.
•
The control and data planes can be programmed directly through APIs.
Related
Documentation
Disaggregated Junos OS VMs on page 6•
• Understanding Physical and Virtual Components on page 12
• Understanding Virtio Usage on page 8
• Understanding SR-IOV Usage on page 10
• Comparing Virtio and SR-IOV on page 11
5Copyright © 2017, Juniper Networks, Inc.
Chapter 1: Architecture Overview
To Next Page
Loading...
