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

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

  • JCNR-12595: Cloud-Native Router deployed with Layer 2 circuit configuration reports Invalid Protocol error for ARP requests —The Cloud-Native Router deployed with Layer 2 circuit configuration reports Invalid Protocol error for ARP requests received from customer edge routers for IPv4 address resolution.

  • JCNR-12583: Cloud-Native Router deployed with Layer 2 circuit configuration displays Incorrect flags in the vRouter Circuit Cross Connect (CCC) table—When deployed with Layer 2 circuit configuration, the Cloud-Native Router displays incorrect flags in the vRouter CCC table for specific scenarios such as underlay ECMP and no-control-word configured. No traffic drop is observed.

  • JCNR-12576: VXLAN Tunnel Endpoint (VTEP) configuration if modified does not get updated in the Cloud-Native Router dataplane—For a Cloud-Native Router deployment with static VXLAN, if the VTEP configuration is modified, the change is not updated in the Cloud-Native Router dataplane. As a workaround, you must restart routing to update the change.

  • JCNR-12540: Cloud-Native Router deployed with SR-MPLS configuration does not correctly program the MPLS label for VRFs configured with vrf-table-label statement—When deployed with SR-MPLS configuration and the VRF configured with the vrf-table-label statement, the Cloud-Native Router does not correcly program the MPLS table, resulting in traffic drop. The vrf-table-label statement enables all routes in the VRF routing table to be advertise with the table next hops. As a workaround, remove the vrf-table-label statement and configure static routes to advertise the prefixes.

  • JCNR-12530: Readiness checks are not supported for single-pod Cloud-Native Router installation—Readiness checks do not run for single-pod Cloud-Native Router installation even if enabled in the helm chart configuration.