vrf-table-label is set.
ok.
Def {
instance-type vrf;
interface lo0.1;
route-distinguisher 16000:16100;
vrf-import def-import;
vrf-export def-export;
vrf-target target:16000:16100;
vrf-table-label;
}
Internet {
instance-type vrf;
interface ge-0/0/3.0;
interface lo0.2;
route-distinguisher 16000:16000;
vrf-export Internet-export;
vrf-target target:16000:16000;
vrf-table-label;
routing-options {
interface-routes {
rib-group inet Internet-to-Def;
}
auto-export;
}
protocols {
bgp {
group Uplinks {
neighbor 222.103.80.1 {
description AS9604;
export AS16000-Export;
peer-as 9604;
}
}
}
}
}
rib-groups {
Internet-to-Def {
import-rib [ Internet.inet.0 Def.inet.0 ];
import-policy rib-Internet-to-Def;
}
Def-To-Internet {
import-rib [ Def.inet.0 Internet.inet.0 ];
import-policy Def-to-Inet-Pol;
}
}
user@vmx3# show policy-options policy-statement rib-Internet-to-Def
term 1 {
from {
route-filter 222.103.80.23/32 exact;
}
then {
community add DefCommunity;
accept;
}
}
term 2 {
then reject;
}
user@vmx3# run show route table Def.inet.0
Def.inet.0: 6 destinations, 9 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
222.103.80.23/32 *[Direct/0] 20:06:07> via lo0.2222.103.80.43/32 *[Direct/0] 1d 18:25:41
> via lo0.1
user@vmx3# run show route table Def.inet.0 222.103.80.23 detail
Def.inet.0: 6 destinations, 9 routes (6 active, 0 holddown, 0 hidden)
222.103.80.23/32 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Address: 0x68218c
Next-hop reference count: 3
Next hop: via lo0.2, selected
State: <Secondary Active Int>
Age: 20:10:34
Validation State: unverified
Task: IF
Announcement bits (1): 0-KRT
AS path: I
Communities: target:16000:16100
Primary Routing Table Internet.inet.0
user@vmx3# run show route table Def.inet.0 advertising-protocol bgp 222.103.80.1
Def.inet.0: 6 destinations, 9 routes (6 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 222.103.80.43/32 Self 100 I
222.103.80.23/32 is not advertising :(
------------------------------
Vlad Sol
------------------------------
Original Message:
Sent: 08-26-2021 09:08
From: GABRIEL FLORES
Subject: Re-advertise direct leaked routes to other routers in VRF
Hi Vlad,
im not sure about your topology, but if this is an l3vpn, i think you might be missing the option "VRF-table-label".
Try it out, if this still doesnt work, please share the config of your VRFs + show route advertising-protocol bgp x.x.x.x.
------------------------------
GABRIEL FLORES
Original Message:
Sent: 08-25-2021 15:23
From: Vlad Sol
Subject: Re-advertise direct leaked routes to other routers in VRF
I have a simple configuration with two MXes.
R1 have two routing instances with type vrf: InstanceA and InstanceB
R2 have only InstanceB vrf.
I've leaked some routes from InstanceA to InstanceB route table on R1 (and i see that route in InstanceB.inet.0 table on R1).
But i don't see that routes on R2 in InstanceB route table.
Is it possible to re-advertise this routes to R2 ?
------------------------------
Vlad Sol
------------------------------