Using RIB Groups for Route Sharing in the Junos®® OS
RIB Group Overview
RIB groups provide a method to control which routing table(s) receive and send routing information.
Routing Table 1
Routes
Non-Native Non-Native
Routing Table Routing Table 2
Routing Table Routing Table
Dynamic / Static / Dynamic / Static / Dynamic / Static / Routes Sent
Interface Routes Routes Interface Routes Routes Interface Routes Routes Routes to Neighbors
Typically incoming routing RIB groups allow you to redirect You can also install routing RIB groups also allow you to send
information is installed into its incoming routing information to a information into multiple routing routing information to neighbors
usual (native) routing table. different routing table on the device. tables simultaneously. from a non-native routing table.
Routing Instances and Tables
The process of populating a routing table is often thought of in Junos Device
simple terms – routes received from neighbors are placed into the Routing Table
appropriate routing table, and those routes are then sent on to Routes Received Routes Sent
Routes
from Neighbors to Neighbors
other neighbors. However, there are more elements to this process.
When routes arrive at the device, they are added to their related
protocol RIB. The protocol RIB runs its algorithm to determine Junos Device
Master/Default Routing Instance
which routes should be installed into the related routing table,
Import Export
and the appropriate routes are then ‘imported’ into the table, say inet.0
RIB RIB
inet.0. To send routing information to neighbors, relevant Routes Received Routes Sent
Protocol RIB Protocol Routes Protocol RIB
from Neighbors to Neighbors
routes are ‘exported’ from the routing table to the protocol RIB,
and then sent on to neighbors.
The sequence of steps described above happens per routing Junos Device
instance. By default, a Junos device has a single ‘master’ Master/Default Routing Instance
Import Export
routing instance, thus routes received on an interface belonging RIB
inet.0
RIB
to the master routing instance are installed into the related Routes Received Routes Sent
Protocol RIB Protocol Routes Protocol RIB
from Neighbors to Neighbors
routing table in the master routing instance, say inet.0. This is in
contrast to routes received on an interface belonging to another TEST Routing Instance
routing instance, say TEST. These routes are installed into the Import Export
[Link].0
RIB RIB
related routing table in the TEST routing instance, say Routes Received Routes Sent
Protocol RIB Protocol Routes Protocol RIB
from Neighbors to Neighbors
[Link].0.
Configuration
Configuring RIB groups involves two steps.
Route Sharing: Why Order Matters
1. Define a RIB group: Table containing the desired routing information The order of the import-rib statement defines the ‘source’ and ‘destination’ routing tables for route
routing-options { sharing. The source table is where the given routes are installed by default; the destination table(s)
Table(s) where the routing information should be added
rib-groups { identifies where to share the routes.
rg-name {
import-rib [ src-table dest-table(s) ]; For example, the statement Whereas, the statement
import-policy [ policy-name ]; import-rib [ inet.0 [Link].0 ] import-rib [ [Link].0 inet.0 ]
(Optional) Filter routes imported
export-rib table; into the destination table(s) does this: does this:
} Junos Device Junos Device
} (Optional) Non-default table from where routes are sent Master/Default Routing Instance Master/Default Routing Instance
} inet.0
Import RIB inet.0
Protocol RIB Protocol Routes Protocol Routes
2. Apply the RIB group (generalized):
protocols { TEST Routing Instance TEST Routing Instance
protocol { [Link].0 [Link].0
rib-group rg-name; Protocol Routes Protocol RIB Protocol Routes
} Import RIB
}
Example / Use Case
This example illustrates how to share directly connected (interface) routes. The Master and TEST routing instances each have
a configured interface. The goal is to make each interface’s local route information available in the other instance’s routing table.
user@device# show interfaces user@device# show routing-instances
et-0/0/0 { ## belongs to Master RI TEST {
unit 0 { ...
family inet { interface et-0/0/1.0;
address [Link]/24; routing-options {
} interface-routes {
} rib-group inet to-Master; ## send TEST int-routes to RG
} }
et-0/0/1 { ## assigned to TEST RI (at right) }
unit 0 { }
family inet {
address [Link]/24; Master (inet.0) inet.0
} Import RIB [Link]/24 *[Direct/0] 00:00:33
}
[Link]/24
> via et-0/0/1.0
Master -> TEST
et-0/0/0
} Interface
[Link]/32 *[Local/0] 00:00:33
Local via et-0/0/1.0
Routes [Link]/24 *[Direct/0] 00:08:26
user@device# show routing-options > via et-0/0/0.0
interface-routes { [Link]/32 *[Local/0] 02:21:22
rib-group inet to-TEST; ## send Master int-routes to RG Local via et-0/0/0.0
}
TEST ([Link].0) [Link].0
rib-groups {
to-TEST { ## share Master int-routes with TEST [Link]/24 *[Direct/0] 00:08:26
import-rib [ inet.0 [Link].0 ]; > via et-0/0/1.0
[Link]/24
[Link]/32 *[Local/0] 02:21:21
}
et-0/0/1
Interface Local via et-0/0/1.0
to-Master { ## share TEST int-routes with Master Routes [Link]/24 *[Direct/0] 00:00:33
import-rib [ [Link].0 inet.0 ]; Import RIB > via et-0/0/0.0
} TEST -> Master [Link]/32 *[Local/0] 00:00:33
Local via et-0/0/0.0
}
For more information, visit: DAY ONE POSTER
Understanding RIB Groups: RIB Group Syntax:
[Link] [Link] Using RIB Groups for Route
release-independent/solutions/information- junos/topics/reference/configuration-statement/ Sharing in the Junos OS®
products/pathway-pages/[Link] [Link]
Juniper Networks Information
Poster concept: Kieran Milne and Learning Experience (iLX)
©2017 by Juniper Networks, Inc. All rights reserved. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change,
modify, transfer, or otherwise revise this publication without notice. [Link]/posters