Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


System Requirements for Wind River Deployment

Read this section to understand the system, resource, port, and licensing requirements for installing Juniper Cloud-Native Router on a Wind River deployment.

Minimum Host System Requirements

This section lists the host system requirements for installing the cloud-native router on a baremetal server.

Table 1: Cloud-Native Router Minimum Host System Requirements
Component Value/Version Notes
CPU Intel x86 The tested CPU is Intel(R) Xeon(R) Silver 4314 CPU @ 2.40GHz
Host OS Debian GNU/Linux 11.3 (Bullseye)
Kernel Version 5.10 5.10.0-6-amd64
  • Intel E810 with Firmware 4.00 0x80014411 1.3236.0

  • Intel E810-CQDA2 with Firmware 4.000x800144111.3236.0

  • Intel XL710 with Firmware 9.00 0x8000cead 1.3179.0

Wind River Cloud Platform 22.12  
IAVF driver Version  
ICE_COMMS Version  
ICE Version ICE driver is used only with the Intel E810 NIC
i40e Version 2.18.9 i40e driver is used only with the Intel XL710 NIC
Kubernetes (K8s) Version 1.24 The tested K8s version is 1.24.4
Calico Version 3.24.x  
Multus Version 3.8  
Helm 3.9.x  
Container-RT containerd  

Resource Requirements

This section lists the resource requirements for installing the cloud-native router on baremetal servers.

Table 2: Cloud-Native Router Resource Requirements
Resource Value Usage Notes
Data plane forwarding cores 2 cores (2P + 2S)  
Service/Control Cores 0  
UIO Driver VFIO-PCI To enable, follow the steps below:
cat /etc/modules-load.d/vfio.conf
Hugepages (1G) 6 Gi

Lock the controller and get the memory processors using below command:

source /etc/platform/openrc
system host-lock controller-0 
system host-memory-list controller-0
To set the huge pages, run the following command for each controller:
system host-memory-modify controller-0 0 -1G 64 
system host-memory-modify controller-0 1 -1G 64

View the huge pages with the following command:

system host-memory-list controller-0

Unlock the controller:

system host-unlock controller-0
JCNR Controller cores .5  
JCNR vRouter Agent cores .5  

Miscellaneous Requirements

This section lists additional requirements for installing the cloud-native router on baremetal servers.

Table 3: Miscellaneous Requirements
Cloud-Native Router Release Miscellaneous Requirements
Enable the host with SR-IOV and VT-d in the system's BIOS.
Isolate CPUs from the kernel scheduler:
source /etc/platform/openrc
system host-lock controller-0
system host-cpu-list controller-0
system host-cpu-modify -f application-isolated -c 4-59 controller-0
system host-unlock controller-0
Set IOMMU. For example:
echo Y > /sys/module/vfio_iommu_type1/parameters/allow_unsafe_interrupts
echo Y > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
Configure persistence for vfio and vfio-pci kernel modules after node reboot:

Add the module names to /etc/modules-load.d/vfio.conf:

# sudo su
# cat /etc/modules-load.d/vfio.conf
Configure IPv4 and IPv6 addresses for the interfaces allocated to JCNR. For example:
source /etc/platform/openrc
system host-lock controller-0
system host-if-modify -n ens1f0 -c platform --ipv4-mode static controller-0 ens1f0
system host-addr-add 1 ens1f0 24
system host-if-modify -n ens1f0 -c platform --ipv6-mode static controller-0 ens1f0
system host-addr-add 1 ens1f0 abcd:: 112
system host-if-list controller-0
system host-addr-list controller-0
system host-unlock controller-0

Additional kernel modules need to be loaded on the host before deploying JCNR in L3 mode. These modules are usually available in linux-modules-extra or kernel-modules-extra packages. Run the following commands to add the kernel modules:

cat /etc/modules-load.d/crpd.conf

Applicable for L3 deployments only.

Run the ip fou add port 6635 ipproto 137 command on the Linux host to enable kernel based forwarding.

NetworkManager is a tool in some operating systems to make the management of network interfaces easier. NetworkManager may make the operation and configuration of the default interfaces easier. However, it can interfere with the Kubernetes management and create problems.

To avoid the NetworkManager from interfering with the interface configurations, perform the following steps:

  1. Create the file, /etc/NetworkManager/conf.d/crpd.conf.
  2. Add the following content in the file.
    Note: enp* indicates all interfaces starting with enp. For specific interface names, provided a comma-separated list.
  3. Restart the NetworkManager service by running the command, sudo systemctl restart NetworkManager.
  4. Edit the sysctl file on the host and paste the following content in it:
  5. Run the command sysctl -p /etc/sysctl.conf to load the new sysctl.conf values on the host.
Verify the core_pattern value is set on the host before deploying JCNR:
sysctl kernel.core_pattern
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e

You can update the core_pattern in /etc/sysctl.conf. For example:


Port Requirements

Juniper Cloud-Native Router listens on certain TCP and UDP ports. This section lists the port requirements for the cloud-native router.

Table 4: Cloud-Native Router Listening Ports
Protocol Port Description
TCP 8085 vRouter introspect–Used to gain internal statistical information about vRouter
TCP 8070 Telemetry information-Used to see telemetry data from cloud-native router
TCP 9091 vRouter health check–cloud-native router checks to ensure contrail-vrouter-dpdk process is running, etc.
TCP 50052 gRPC port–JCNR listens on both IPv4 and IPv6
TCP 8081 JCNR Deployer Port
TCP 666 rpd
TCP 1883 Mosquito mqtt–Publish/subscribe messaging utility
TCP 9500 agentd on cRPD
TCP 21883 na-mqttd
TCP 50051 jsd on cRPD
TCP 51051 jsd on cRPD
UDP 50055 Syslog-NG

Download Options

To deploy JCNR on a Wind River deployment you can download the helm charts from the Juniper Support Site.

Note: Before deploying JCNR on a Wind River deployment via helm charts downloaded from the Juniper support site, you must whitelist as the JCNR image registry.

JCNR Licensing

Starting with Juniper Cloud-Native Router (JCNR) Release 22.2, we have enabled our Juniper Agile Licensing (JAL) model. JAL ensures that features are used in compliance with Juniper's end-user license agreement. You can purchase licenses for the Juniper Cloud-Native Router software through your Juniper Account Team. For details about managing multiple license files for multiple cloud-native router deployments, see Juniper Agile Licensing Overview.


Starting with JCNR Release 23.2, the JCNR license format has changed. Request a new license key from the JAL portal before deploying or upgrading to 23.2 or newer releases.