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 (JCNR) release 23.4.

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

  • JCNR-5647: L2 frames with non-default priority are being dropped on bond interface—L2 QoS is not supported in Juniper Cloud-Native Router release 23.4.

  • JCNR-5627: IPv6 traffic limitation on IRB interface—JCNR does not allow IPv6 packets with size above 1490 through an IRB interface. Ensure you do not allow IPv6 traffic with a packet size surpassing 1490 to pass through an IRB interface to avert packet drops and to maintain stable performance.

  • JCNR-5621: [ECMP] Flow stickiness not working, tested with two and three ECMP paths and just two flows—Flow stickiness for IPv6 traffic with SR-MPLS is non-functional.

  • JCNR-5581: After vrouter restart, the vif mtu gets reset to 9000 (default) irrespective of the value set by cprd—The maximum transmission unit (MTU) is reset to its default value when the vRouter restarts, even though the cRPD shows a different value. If required, you need to manually set the required value after the vRouter restarts.

  • JCNR-5521: JCNR-L3: JCNR on GCP instance N16-standard, vrouter stops forwarding soon after it is up—JCNR deployment on Google Cloud Platform (GCP) supports only N8-standard for VM deployments. The N16-standard is not supported.

  • JCNR-5520: Invalid route calculation by OSPF protocol after vrouter pod restart—If the vRouter pod is restarted then there could be issues with OSPF protocol functioning. As a workaround, restart the cRPD pod whenever the vRouter pod restarts.

  • JCNR-4827: JCNR L3 GCP: IPv6 underlay isn't working once interface being part of JCNR as fabric interface—JCNR does not support IPv6 underlay interfaces in GCP deployments.