Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Cloud-Native Router User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Cloud-Native Router as a Transit Gateway

Release: JCNR 23.3
{}
Change Release
date_range 27-Nov-24
Cloud-Native Router can act as a transit gateway for external traffic. As a transit gateway, Cloud-Native Router is neither the source nor the destination for the traffic, but an intermediate hop. It acts as a vanilla router to switch traffic between multiple physical interfaces.

Starting with Juniper Cloud-Native Router (JCNR) Release 23.2, Cloud-Native Router can now act as a transit gateway for external traffic. As a transit gateway, Cloud-Native Router is neither the source nor the destination for the traffic, but an intermediate hop. It acts as a vanilla router to switch traffic between multiple physical interfaces. Depending on the forwarding state, Cloud-Native Router can encapsulate or decapsulate the traffic between interfaces.

Note:

Starting with Cloud-Native Router Release 23.2, Cloud-Native Router supports multiple fabric interfaces that enable it to function as a transit gateway.

Cloud-Native Router has to be deployed in the L3 mode to perform the transit router functionality. Add all physical interfaces (physical and virtual functions) as fabric interfaces in the helm chart before deploying the JCNR. The deployed Cloud-Native Router does not support editing or changing the fabric interfaces during run time. However, you can create or remove pod interfaces during run time. Here are example helm chart configurations:

content_copy zoom_out_map
fabricInterface:
  - ens2f2:
      ddp: "auto"
  - ens1f1:
      ddp: "auto"
content_copy zoom_out_map
 fabricInterface:
    - subnet: 10.0.3.0/24
      gateway: 10.0.3.1
      ddp: "off"
    - subnet: 10.0.5.0/24
      gateway: 10.0.5.1
      ddp: "off"

You need to configure an IP address on the loopback interface and use it as a tunnel endpoint for each Cloud-Native Router instance. The loopback IP address is the next hop address which BGP advertises to its peers. All data packets with encapsulations like MPLSoUDP will have the outer IP address as this loopback IP address. The loopback IP address is reachable via any of the physical interfaces. The loopback IP address should be in a /32 subnet without a MAC address. For example:

content_copy zoom_out_map
set interfaces lo1 unit 1 family inet address 10.0.0.1/32
footer-navigation