rib-exports (Routing Options)
Syntax
rib-exports {
restart-timer; value in seconds;
rib-export-group {
policy;
to-rib;
}
traceoptions {
file;
flag;
}
}Hierarchy Level
[edit routing-options]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
You can clone active BGP primary or secondary routes from one virtual routing and forwarding (VRF) routing information base (RIB) to another VRFs RIBs. You can also clone routes from one VRF RIB to the inet.0 or inet6.0 routing tables. Cloned routes always become the primary route in the VRF RIB or inet table into which they're cloned.
You can clone routes only if the destination and source RIB addresses belong to the same family and sub-family (i.e. unicast/multicast).
set routing-options rib-exports rib-export-group <rib-export group name> to-rib <routing table name> set routing-options rib-exports rib-export-group <rib-export group name> to-rib <routing table name> policy <policy-name>
Using the same RIB as both the source and destination in rib-export group settings results in a configuration error. For example, in the following configuration, the source and destination RIBs are the same, resulting in a configuration error during commit.
set routing-options rib-exports rib-export-group VRF-A-VRF-A-Cloned to-rib VRF-A.inet.0 set routing-instances VRF-A routing-options rib VRF-A.inet.0 rib-export VRF-A-VRF-A-Cloned
Use the show route rib-exports command to view the group of RIBs in
which the primary or secondary routes are cloned.
Export a RIB-Export group through a routing instance using the
rib-export statement. This statement allows attaching a single
RIB-Export group to a routing table.
set routing-instances <instance name> routing-options rib <routing table name> rib-export <rib-export group name>
You can configure a drop attribute policy with the rib-export-strip
statement to remove the BGP cluster-list attribute. You would do this to re-advertise a
route back to the source route reflector, or a route reflector with the same
cluster-list attribute. This would apply when the route reflectors aren't fully meshed.
The originator-id attribute is implicitly set to "self" when the cluster-list attribute
is removed.
set policy-options policy-statement <policy-name> term <term-name> then rib-export-strip cluster-list set policy-options policy-statement <policy-name> term <term-name> then accept set policy-options policy-statement <policy-name> then reject set routing-options rib-exports rib-export-group <rib-export group name> to-rib <routing table name> policy <policy-name>
Options
| restart-timer | Specify the time in seconds to support graceful restart.
|
| rib-export-group | Specify the RIB-Export group name, and then configure additional statements to
create and export routes.
|
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 25.2R1.
rib-export-strip statement introduced in Junos OS Release 25.2R1.