Resolved Issues

Resolved Issues in Juniper Cloud-Native Router Release 26.2

• JCNR-12595: Cloud-Native Router deployed with Layer 2 circuit configuration no longer reports Invalid Protocol error for ARP requests—The Cloud-Native Router deployed with Layer 2 circuit configuration now correctly processes ARP requests received from customer edge routers for IPv4 address resolution. The Invalid Protocol error is no longer observed.
• JCNR-12540: Cloud-Native Router deployed with SR-MPLS configuration now correctly programs the MPLS label for VRFs configured with the vrf-table-label statement—When deployed with SR-MPLS configuration and the VRF configured with the vrf-table-label statement, the Cloud-Native Router now correctly programs the MPLS table. No traffic drop is observed.
• JCNR-12530: Readiness checks are now supported for single-pod Cloud-Native Router installation—Readiness checks now run for single-pod Cloud-Native Router installation when enabled in the helm chart configuration.

• JCNR-12583: jvk interfaces no longer come up with the same VRRP MAC address—When Cloud-Native Router is deployed with L2 pod interfaces, jvk interfaces now come up with their unique CNI-assigned MAC addresses. Previously, all jvk interfaces incorrectly came up with the same VRRP MAC address, causing MAC move detection events in the vRouter.

• JCNR-13079: OP (Operational) scripts configured in cRPD are no longer lost after a cRPD pod restart—When local persistence is enabled, OP scripts placed in the /var/db/scripts/op directory in the cRPD pod are now retained across pod restarts. Previously, the /var/db/scripts/op directory was not mounted in the cRPD pod, causing all scripts to be lost after a restart.
• JCNR-13269: The first packet of a new flow is now correctly forwarded over an MPLSoUDP tunnel in GCP—When Cloud-Native Router is deployed with an L3VPN over MPLSoUDP tunnel configuration in GCP, the first packet of each new flow is now forwarded correctly. Previously, a label conflict in the forwarding metadata caused the first packet to be held and forwarded incorrectly, while subsequent packets in the same flow were unaffected.
• JCNR-12576: VXLAN Tunnel Endpoint (VTEP) configuration changes are now correctly updated in the Cloud-Native Router dataplane—For a Cloud-Native Router deployment with static VXLAN, changes to the VTEP configuration are now correctly updated in the Cloud-Native Router dataplane without requiring a routing restart.
• JCNR-12578: Cloud-Native Router deployed with Layer 2 circuit configuration now displays correct flags in the vRouter Circuit Cross Connect (CCC) table—When deployed with Layer 2 circuit configuration, the Cloud-Native Router now displays correct flags in the vRouter CCC table for scenarios such as underlay ECMP and no-control-word configured.