New Features
This section describes the new features in the Juniper Cloud-Native Router 22.2 release.
New Features in Juniper Cloud-Native Router Release 22.2
-
Juniper Cloud-Native Router Controller (cRPD or JCNR-Controller)–The JCNR-controller is based on our tried-and-tested containerized routing protocol daemon, cRPD. We use cRPD in the cloud-native router to provide the control plane functions and interface with the JCNR-vRouter component. See Juniper Cloud Native Router Controller.
-
JCNR-vRouter–JCNR-vRouter is a dataplane development kit (DPDK)-based forwarding plane. JCNR-vRouter is able to provide high-speed L2 forwarding using DPDK and enforce L2 access control lists (ACLs). See JCNR-vRouter.
JCNR-vrouter uses a component known as the vRouter-agent to receive communication from the cRPD.
See JCNR-vRouter.
-
JCNR-CNI–Juniper Cloud-Native Router uses the container network interface application, JCNR-CNI to provide container network and Kubernetes Pod interfaces. See JCNR-CNI.
-
Software Licensing–Juniper Cloud-Native Router release 22.2 introduces the Juniper agile software license model. In the 22.2 Release, we do not enforce license compliance, we only report out-of-compliance status. See Juniper Cloud-Native Router LIcensing
-
Configuration by Helm Chart–Juniper Cloud-Native Router supports deployment-time configuration with the use of Helm charts.
-
NETCONF–You can configure the Juniper Cloud-Native Router control plane using the NETCONF protocol.
-
Networking Features
-
L2 Mode DPDK Forwarding Plane–Juniper Cloud-Native Router supports L2 mode in the DPDK forwarding plane for fabric and workload interfaces
-
Ethernet Packet Switching–Juniper Cloud-Native Router operated in L2 mode activates ethernet switching capabilities in the forwarding plane.
-
MAC Address Handling–Juniper Cloud-Native Router Release 22.2 operated in L2 mode allows the forwarding plane to handle MAC addresses without involving the control plane (MAC learning and aging)
-
Bridge Domain Support–Juniper Cloud-Native Router supports bridge domains
-
VLAN Tagging–Juniper Cloud-Native Router supports VLAN tagging on logical interfaces
-
Trunk Port Support–Juniper Cloud-Native Router operated in L2 mode allows for the creation of trunk ports which allow multiple VLANs to transit the port.
-
Support for Multiple Interface Types–Juniper Cloud-Native Router operated in L2 mode allows fabric and pod interfaces of the following types:
- Kernel mode access interfaces that are used to bypass the DPDK forwarding plane in favor of the kernel-based forwarding plane
- Virtio trunk interfaces that can pass traffic from multiple VLANs
- Multiple Virtio sub interfaces that can each pass VLAN-tagged traffic
-
Fabric Interface Functions Support–Juniper Cloud-Native Router fabric interfaces can be based of Virtual Functions or Physical Functions of a NIC
-
IP Address Allocation for Application Pods–Juniper Cloud-Native Router Release 22.2 supports allocation of IP addresses for Kubernetes application pods by the JCNR-CNI.
See JCNR-CNI.
-
L2 Access Control Lists (ACL)–Juniper Cloud-Native Router Release 22.2 running in L2 mode supports the creation and enforcement of L2 access control lists (ACL) based on MAC address or ethertypes
See L2 ACL
- Traffic Rate Limiting–Juniper Cloud-Native Router Release 22.2 allows for the rate limiting of L2 broadcast and multicast traffic
-
NIC Support–Juniper Cloud-Native Router Release 22.2 supports special features such as VLAN offload and Dynamic Device Personalization (DDP) on the following NICs:
- Intel 810
-
Event Notification Support–Juniper Cloud-Native Router uses syslog-ng to convert event logs from various Pods and containers into JSON-encoded notifications.
-
Automatic Generation of Bridge Domains and JCNR-Controller Configuration–Juniper Cloud-Native Router automatically generates bridge domain and JCNR-Controller configuration during deployment through the use of Helm charts.Juniper Cloud-Native Router Deployment Guide.
-
Kubernetes (K8s) Liveness Probes for JCNR-Controller and JCNR-vRouter–Juniper Cloud-Native Router supports Kubernetes liveness probes for JCNR-Controller and JCNR-vRouter containers.