Escolar Documentos
Profissional Documentos
Cultura Documentos
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.
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
TEST.inet.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
TEST.inet.0.
Configuration
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 192.168.1.1/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 10.10.10.1/24; Master (inet.0) inet.0
} Import RIB 10.10.10.0/24 *[Direct/0] 00:00:33
}
192.168.1.1/24
} Interface
10.10.10.1/32 *[Local/0] 00:00:33
Local via et-0/0/1.0
Routes 192.168.1.0/24 *[Direct/0] 00:08:26
user@device# show routing-options > via et-0/0/0.0
interface-routes { 192.168.1.1/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 (TEST.inet.0) TEST.inet.0
rib-groups {
to-TEST { ## share Master int-routes with TEST 10.10.10.0/24 *[Direct/0] 00:08:26
import-rib [ inet.0 TEST.inet.0 ]; > via et-0/0/1.0
10.10.10.1/24