Known Limitations
This section describes issues and limitations present in Juniper Cloud-Native Router (JCNR) release 24.4.
Known Issues and Limitations in Juniper Cloud-Native Router Release 24.4
-
JCNR-10715: SRv6 routes not reinstated in cRPD after a restart—The SRv6 routes are not reinstated in cRPD pod upon restart for Cloud-Native Router instances deployed as ingress or egress nodes. This results in traffic loss.
-
JCNR-10729: Certain sequences of valid subscription paths in a gNMI-based telemetry request do not work—When sending gNMI-based telemetry requests to the Cloud-Native Router, certain sequences of valid subscription paths may not work. As a workaround you can split the request into multiple sets of subscriptions.
-
JCNR-10757: Sub-Interfaces created using cRPD configlets are not deleted in the kernel upon deletion of the configlet resource—When sub-interfaces created using a configlet are deleted from the cRPD configuration by deleting the configlet resource, the kernel does not reflect the change. This can create inconsistencies in the cRPD and vRouter agent configuration.