Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Example: Redistributing Routes Among RIP Instances

Understanding Route Redistribution Among 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.

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.

Example: Redistributing Routes Between Two RIP Instances

This example shows how to configure a RIP routing instance and control the redistribution of RIP routes between the routing instance and the master instance.

• Requirements
• Overview
• Configuration
• Verification

Requirements

No special configuration beyond device initialization is required before configuring this example.

Overview

When you create a routing instance called voice, Junos OS creates a routing table called voice.inet.0. The example shows how to install routes learned through the master RIP instance into the voice.inet.0 routing table. The example also shows how to install routes learned through the voice routing instance into inet.0. This is done by configuring routing table groups. RIP routes are installed into each routing table that belongs to a routing table group.

Figure 1 shows the topology used in this example.

Figure 1: Redistributing Routes Between RIP Instances Network Topology

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. The section Step-by-Step Procedure describes the steps on Device R2.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

1. Configure the network interfaces.
   [edit interfaces]user@R2# set fe-1/2/0 unit 2 family inet address 10.0.0.2/30
   user@R2# set fe-1/2/1 unit 5 family inet address 10.0.0.5/30
   user@R2# set lo0 unit 2 family inet address 192.168.2.2/32user@R2# set lo0 unit 2 family inet address 172.16.2.2/32
2. Create the routing instance, and add one or more interfaces to the routing instance.
   [edit routing-instances voice]user@R2# set interface fe-1/2/0.2
3. Create the RIP groups and add the interfaces.
   [edit protocols rip group to-R3]user@R2# set neighbor fe-1/2/1.5
   [edit routing-instances voice protocols rip group to-R1]user@R2# set neighbor fe-1/2/0.2
4. Create the routing table groups.
   [edit routing-options rib-groups]user@R2# set inet-to-voice import-rib inet.0user@R2# set inet-to-voice import-rib voice.inet.0
   user@R2# set voice-to-inet import-rib voice.inet.0user@R2# set voice-to-inet import-rib inet.0
5. Apply the routing table groups.
   [edit protocols rip]user@R2# set rib-group inet-to-voice
   [edit routing-instances voice protocols rip]user@R2# set rib-group voice-to-inet
6. Create the routing policy to advertise both direct and RIP-learned routes.
   [edit policy-options policy-statement advertise-routes-through-rip term 1]user@R2# set from protocol directuser@R2# set from protocol ripuser@R2# set then accept
7. Apply the routing policy.

   In Junos OS, you can only apply RIP export policies at the group level.

   [edit protocols rip group to-R3]user@R2# set export advertise-routes-through-rip
   [edit routing-instances voice protocols rip group to-R1]user@R2# set export advertise-routes-through-rip

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, show policy-options, show routing-instances, and show routing-options commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly.

Checking the Routing Tables

Purpose

Make sure that the routing tables contain the expected routes.

Action

From operational mode, enter the show route protocol rip command.

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.16.0.1/32      *[RIP/100] 01:58:14, metric 2, tag 0
                    > to 10.0.0.1 via fe-1/2/0.2
172.16.3.3/32      *[RIP/100] 02:06:03, metric 2, tag 0
                    > to 10.0.0.6 via fe-1/2/0.5
192.168.1.1/32     *[RIP/100] 01:58:14, metric 2, tag 0
                    > to 10.0.0.1 via fe-1/2/0.2
192.168.3.3/32     *[RIP/100] 02:06:03, metric 2, tag 0
                    > to 10.0.0.6 via fe-1/2/0.5
224.0.0.9/32       *[RIP/100] 01:44:13, metric 1
                         MultiRecv

voice.inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.16.0.1/32      *[RIP/100] 02:06:03, metric 2, tag 0
                    > to 10.0.0.1 via fe-1/2/0.2
172.16.3.3/32      *[RIP/100] 01:58:14, metric 2, tag 0
                    > to 10.0.0.6 via fe-1/2/0.5
192.168.1.1/32     *[RIP/100] 02:06:03, metric 2, tag 0
                    > to 10.0.0.1 via fe-1/2/0.2
192.168.3.3/32     *[RIP/100] 01:58:14, metric 2, tag 0
                    > to 10.0.0.6 via fe-1/2/0.5
224.0.0.9/32       *[RIP/100] 01:44:13, metric 1
                         MultiRecv

Meaning

The output shows that both routing tables contain all of the RIP routes.