This section describes the new features and enhancements to existing features in this release.
Kubernetes support—Starting in cRPD Release 20.1R1, you can install the cRPD application in a Kubernetes environment. The deployment is supported in different kinds such as Pod, Job, Deployment, DaemonSet using
.yamlfiles. The number of cRPD instances is increased or decreased using the parameters defined in the
Sharding and updateIO support—Starting in cRPD Release 20.1R1, you can enable sharding and updateIO options on the cRPD. You can also configure the BGP protocol with the support of route reflector functionality using inet, inet6, inet-vpn, inet6-vpn and route-target unicast families.
With sharding enabled, the incoming updates for a RIB table are handed to one of the shards and the processing of the prefix happens in the shard. Because shards run in different threads and can run on different cores, rpd is able to run in parallel on a multicore processor.
UpdateIO offloads the decoding and formatting from rpd (and also from rpd shards), allowing near optimal packing, without the need for the shards to synchronize generation of the updates.
You cannot configure the VRF type l3vpn and also run set system processes routing bgp rib-sharding on cRPD.
set next-hop self is not supported.
The label allocation process in Layer 3 vpn is not supported for inet-vpn and inet6-vpn unicast families. The l3vpn families are not sharded, but are kept in the main rpd process. Prefixes appear as invalid labels.
Supported Features on cRPD
The following features are supported on cRPD:
BGP route reflector in the Linux container
BGP add-path, multipath, graceful restart helper mode
BGP, OSPF, OSPFv3, IS-IS, and Static
BMP, BFD, and Linux-FIB
Equal-cost multipath (ECMP) support
JET for programmable RPD
Junos OS CLI
Management using the open interfaces, NETCONF and SSH
IPv4 and IPv6 routing
You require a license to activate cRPD software features. cRPD supports 1-year and 3-year subscription models only.