Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Known Limitations

This section describes issues and limitations present in Juniper Cloud-Native Router release 22.4

Known Issues and Limitations in Juniper Cloud-Native Router Release 22.4

  • JCNR-3173: After Refresh Deployment of JCNR in L3 Mode, the Pod Virtual Interface (VIF) Has an Invalid Virtual Routing and Forwarding (VRF) Reference–As a workaround, you can restart the routing process in the cRPD pod (restart routing immediately) or you can restart the vRouter pod.

  • JCNR-3171: L2 Firewall Filter May Not Get Applied in Certain Scenarios–We have found two scenarios in which firewall filters (ACL) may not get applied:

    • If you install cloud-native router with ACL configured in the template

    • If you run could-native router with configured ACL and the vRouter crashes

  • JCNR-3170: In L2 Mode, Cloud-Native Router Cannot Be Deployed if Kubernetes cpumanager is Installed–This configuration is not supported.

  • JCNR-3060: cRPD Randomly Disables MPLS Family on Interfaces–cRPD randomly disables the MPLS family hierarchy in interface configurations. The disabled configuration affects SR-MPLS LSPs. As a workaround, you can issue the restart routing immediately command.

  • JCNR-2917–In certain circumstances, you might witness BGP flaps and cRPD pod restart if BGP routes are withdrawn while traffic passes through them. To avoid this issue, adjust the BFD liveness-detection as shown in the following two commands:

    set protocols bgp group <group-name> bfd-liveness-detection minimum-receive-interval 320

    set protocols bgp group <group-name> bfd-liveness-detection transmit-interval minimum-interval 300