Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Understanding Route Redistribution Among RIP instances

You can redistribute routes among RIP processes. Another way to say this is to export RIP routes from one RIP instance to other RIP instances.

In Junos OS, route redistribution among routing instances is accomplished by using routing table groups, also called RIB groups. Routing table groups allow you to import and export routes from a protocol within one routing table into another routing table.

Note: In contrast, the policy-based import and export functions allow you import and export routes between different protocols within the same routing table.

Consider the following partial example:

protocols {rip {rib-group inet-to-voice;}}
routing-instances {voice {protocols {rip {rib-group voice-to-inet;}}}}
routing-options {rib-groups {inet-to-voice {import-rib [ inet.0 voice.inet.0 ];}voice-to-inet {import-rib [ voice.inet.0 inet.0 ];}}}

The way to read the import-rib statement is as follows. Take the routes from the protocol (RIP, in this case), and import them into the primary (or local) routing table and also into any other routing tables listed after this. The primary routing table is the routing table where the routing table group is being used. That would be either inet.0 if used in the main routing instance or voice.inet.0 if used within the routing instance. In the inet-to-voice routing table group, inet.0 is listed first because this routing table group is used in the main routing instance. In the voice-to-inet routing table group, voice.inet.0 is listed first because this routing table group is used in the voice routing instance.

Published: 2013-08-15