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 24.2.

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

  • JCNR-6166: Modifying the route-distinguisher of an active routing-instance is not supported— JCNR does not support modifying the route-distinguisher of an active routing-instance and the event is considered catastrophic. To modify the route-distinguisher deactivate the routing-instance, make the change and activate the routing-instance.

  • JCNR-6211: Setting an MTU higher than the recommended 1500 bytes on JCNR interfaces for Microsoft Azure Cloud Platform deployments results in BGP flapping— Azure Cloud Platform recommends an MTU <=1500 on interfaces. If JCNR is deployed using a fabric interface with MTU higher than 1500 bytes, it results in packet drops while sending BGP updates and eventually BGP flapping.

  • JCNR-4248: Keepalived cores are generated when VRRP is initially configured in cRPD— When VRRP is initially configured in cRPD or deleted and re-configured, keepalived cores are generated in the /var/crash directory.

  • JCNR-8275: Interface VLAN sensors not supported for L3 VLAN Sub-Interfaces— Interface VLAN sensors for gNMI based telemetry are not support for L3 VLAN sub-interfaces.

  • JCNR-8498: JCNR Forwarding plane not fragmentating VLAN-tagged frames with size greater than 8968 bytes— The JCNR forwarding plane does not fragment VLAN-tagged frames with size greater than 8968 bytes. The frames are currently dropped.

  • JCNR-8492: JCNR VPC Gateway does not support exchanging IPv6 routes over IPv4 BGP peers— The JCNR VPC Gateway application does not support exchanging IPv6 routes over IPv4 BGP peers even when enableIPv6 flag is enabled.

  • JCNR-8470: JCNR VPC Gateway fails to configure route filter and prefix list for Routing Policy— When a routing policy is defined in the VPC Gateway application, it fails to deploy the configuration with the defined routeFilter and prefixList parameters.

  • JCNR-8448: Unable to modify the default gRPC server port configuration— Modification of the default gRPC server port configuration using the grpcTelemetryPort parameter in the helm chart does not work. The gRPC server continues to listen on port 500053.

  • JCNR-8389: JCNR Forwarding plane drops destination traffic if Neighbor Discovery (ND) fails to resolve on remote Provider Edge (PE) router—The JCNR forwarding plane drops outgoing traffic if ND for the destination fails to resolve on the remote PE router. Resolve ND between remote PE router and the destination as a workaround.

  • JCNR-8370: AWS VPC Route table not updated when a route is withdrawn or deleted from the JCNR source routing table— When a route is withdrawn or deleted from the JCNR source routing table, the corresponding AWS VPC route table is not updated.

  • JCNR-8332: Loopback interface IP configuration is not removed when the JCNR VPC Gateway application is deleted— The Loopback interface IP configuration is not removed when the JCNR VPC Gateway application is deleted. In a multinode JCNR deployment, the loopback interface IP must be manually removed after the VPC gateway application is deleted.

  • JCNR-8311: JCNR TWAMP Ingress/Egress Delay and Jitter measurements are prone to errors due to clock synchronization between devices— The JCNR TWAMP ingress/egress delay and jitter measurements are affected by clock synchronization between devices and may not be reliable.

  • JCNR-8264: TWAMP telemetry data is available via gNMI only if the test-count is set to the default value (0)— The TWAMP telemetry data is available via gNMI only if the test-count is set to the default value (0).

  • JCNR-8487: Restarting the vRouter-agent pod with running traffic causes one of the fabric tap interfaces to go down—If the vRouter-agent pod is restarting with running traffic, one of the fabric tap interfaces do not come up due to a flood of trap resolve requests to the agent. The behavior recovers in due time.

  • JCNR-8260: When deployed on VMWare Tanzu, the JCNR Forwarding plane drops traffic with rx_missed_errors when restarted with running traffic— In JCNR deployment on VMWare Tanzu, restarting the vRouter with running traffic may result in traffic drop with rx_missed_errors in the dpdkinfo -x command output.