Hi,
RR are like any other BGP router, it must be able to resolve BGP next-hop before considering the route usable. Now, most likely your RR is not running MPLS therefore its inet.3 table is empty and it considers all inet-vpn routes as unusable. Check with "show route table bgp.l3vpn.0 hidden".
To populate inet.3 on the RR, you have several ways more or less complex.
- You may use rib group to import IGP learned loopbacks from inet.0 to inet.3
- Or very simple, just add a static default discard route in inet.3 (set routing-options rib inet.3 static route 0.0.0.0/0 discard)
The static discard route is not an issue, the RR must just think the next-hop is reachable to reflect a route, it doesn't need to be able to use it itself.
Hope this help...
Regards,
C
------------------------------
CHRISTOPHE LEMAIRE
------------------------------
Original Message:
Sent: 04-15-2022 05:31
From: QUENTIN GABREL
Subject: L3VPN via vRR
Hello !
I'm trying to build a MPLS L3VPN with vRR.
Each PE gets routes in the right table (vrf-xxx-001.inet.0) but do not exchange routes between them.
Each PE have a BGP session to vRR. ISIS is used as IGP and MPLS/LDP is activated. PE advertises routes to vRR.
Should I create vrf in vRR ?
I don't know where to start my debugging...
Any idea ?
Thanks in advance !
------------------------------
QUENTIN GABREL
------------------------------