Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

cJunosEvolved Architecture

This topic provides details of cJunosEvolved-BT and cJunosEvolved-BT architecture.

cJunosEvolved is a KVM based Docker container. The embedded EVO VM within the container provides the Junos OS Evolved control and management plane functionality. The EVO VM includes the Routing Engine and Packet Forwarding Engine. The BT and BX data plane ASIC simulators reside in the Linux side of the container.

Figure 1 shows the high-level architecture of cJunosEvolved and how it resides in an Ubuntu host server. cJunosEvolved can be deployed on a bare metal Ubuntu Linux server as well as from within an Ubuntu VM. The bare metal server is the preferred deployment model as the cJunosEvolved container embeds an EVO VM within it. Therefore, hosting it within another VM will use nested virtualization which inevitably slows the response of cJunosEvolved.

Figure 1: cJunosEvolved High Level Architecture cJunosEvolved High Level Architecture

cJunosEvolved-BT Architecture

This section describes the detailed cJunosEvolved-BT Architecture.

The Linux side of the container includes a single instance of the COSIM packet processing (cosim-pp) plus the BT ASIC simulator process.

The COSIM is situated between the external virtual ether (veth) data ports, the BT and the EVO VM. It facilitates packet processing between them.

Figure 2: cJunosEvolved-BT Architecture cJunosEvolved-BT Architecture

cJunosEvolved-BX Architecture

This section provides detailed information about cJunosEvolved-BX Architecture.

The Linux side of the container includes two instances of the COSIM packet processing (cosim-pp) plus the BX ASIC simulator process.

Each COSIM is situated between the external virtual ether (veth) data ports, it's corresponding BX and the EVO VM. It facilitates packet processing between them.

The BX ASIC is simulated in software. The Packet Forwarding Engine in EVO VM communicates with the data plane within the container for configuration, control and data packet processing.

Figure 3: cJunosEvolved-BX Architecture cJunosEvolved-BX Architecture

The EVO VM also contains the Routing Engine applications as well as other processes such as MGD for router configuration and the control and management plane. The EVO VM is started at cJunosEvolved initialization through QEMU-KVM.