Greetings,
Georgi, I understand that it is the Juniper concept. But as I am curious, I still have to understand the basis of this, since other vendors are able to achieve this objective.
Can you explain the reason in detail?
------------------------------
Guilherme Rigueti
------------------------------
Original Message:
Sent: 10-30-2024 12:15
From: GEORGI SINAPOV
Subject: BGP ROUTE LEAK
Greetings,
This is how Juniper concept of leaking is constructed.
A route has primary routing table (whatever its origin is) and leaking it to any other table, makes the next one secondary. You can leak routes only in this direction, not between secondary tables. Here is an example of L3VPN route, received via MP-BGP and installed in VPN1.inet.0
user@host> show route 1.1.1/24 detail table bgp.l3vpn.0 | grep tables
Oct 30 17:09:15
Secondary Tables: VPN1.inet.0
userv@host> show route 1.1.1/24 detail table VPN1.inet.0 | grep table
Oct 30 17:11:51
Primary Routing Table: bgp.l3vpn.0
Once the prefix is installed locally in VPN1, it cannot "go" any other place.
Best e-gards,
Georgi Sinapov
Core Network Architect
Original Message:
Sent: 10/30/2024 11:33:00 AM
From: Guilherme Rigueti
Subject: BGP ROUTE LEAK
Hi guys.
I am returning here with an old topic already discussed by other colleagues to understand why it is not work or what needs to be done to achieve the objective, where we are not getting it right.
Why can't I "leak" routes that I learned (received) via VPNv4 (using L3VPN scenario of course) to another routing table, specifically the main one (inet.0). Only routes learned locally in the VRF can I "leak" to inet.0.
------------------------------
Guilherme Rigueti
------------------------------