RIP Configuration on Juniper

Juniper-RIP-configuration-example

RIP Configuration on Juniper

In this lesson, we will configure Juniper routers for RIPv2. RIP is the simplest Routing Protocol and configuring RIP on Juniper Routers need a couple of simple steps. We will see each of these steps one by one.
For our Juniper RIP Configuration Example, we will use the below topology.


Juniper-RIP-configuration-example

Now, let’s focus on the Juniper RIP Configuration steps and start our RIP configuration.

Step 1 – IP Address Configuration

Firstly, we need to configure all the interface addresses as given above. The IP connectivity is the first must, to configure RIP or any other Routing Protocol.

We can do IP configuration with the below command set:

Router 1

Juniper-Router1@Kosem> configure
Juniper-Router1@Kosem# set interfaces ge-1/1/1 unit 0 family inet address 10.0.10.1/30
Juniper-Router1@Kosem# set interfaces ge-1/1/2 unit 0 family inet address 10.0.20.1/30

Router 2

Juniper-Router2@Kosem> configure
Juniper-Router2@Kosem# set interfaces ge-1/1/1 unit 0 family inet address 10.0.30.1/30
Juniper-Router2@Kosem# set interfaces ge-1/1/2 unit 0 family inet address 10.0.10.2/30

Router 3

Juniper-Router3@Kosem> configure

Juniper-Router3@Kosem# set interfaces ge-1/1/1 unit 0 family inet address 10.0.20.2/30
Juniper-Router3@Kosem# set interfaces ge-1/1/2 unit 0 family inet address 10.0.30.2/30

Step 2 – Routing Policy Configuration

Here, we will configure a Routing Policy that will accept RIP learned and Directly connected Networks. Our Policy name will be RIPPolicy.

To configure Routing Policy, we will use the below commands. On each router, we will add this configuration.

Juniper-Router3@Kosem# set policy-options policy-statement RIPPolicy term 1 from protocol direct
Juniper-Router3@Kosem# set policy-options policy-statement RIPPolicy term 1 from protocol rip
Juniper-Router3@Kosem# set policy-options policy-statement RIPPolicy term 1 then accept

Step 3 – RIP Configuration

Our exact Juniper RIP Configuration will be in this step. Here, we will add the networks under RIP and we will also add the Routing Policy that we have created for RIP.

Router 1
set protocols rip group rip-group export RIPPolicy
set protocols rip group rip-group neighbor ge-1/1/1
set protocols rip group rip-group neighbor ge-1/1/2

Router 2
set protocols rip group rip-group export RIPPolicy
set protocols rip group rip-group neighbor ge-1/1/1
set protocols rip group rip-group neighbor ge-1/1/2

Router 3
set protocols rip group rip-group export RIPPolicy
set protocols rip group rip-group neighbor ge-1/1/1
set protocols rip group rip-group neighbor ge-1/1/2

The RIP configurations commands seem similar here even the interface. This is because all the router in RIP network are using the same interfaces (ge-1/1/1, ge-1/1/2).

Step 4 – RIP Configuration Commit

After the ROP Configuration, we need to commit all the configurations to take place. To do this, we use “commit” command on each router.

As a bect practice, where can i buy phentermine hcl online before “commit”, always use “commit check”. This will show you the configuration mistakes if are there any before affecting the network.

Use the below commands on each router that you configured.

Juniper-Router1@Kosem# Commit check
configuration check succeeds

Juniper-Router1@Kosem# Commit
commit completed

Step 5 – RIP Configuration Verification

After our configuration finishes, then we will verify our RIP Configuration with some verification commands. We will use the below commands to verify our Juniper RIP Configuration Example:

• show protocols
• show policy-options
• show route
• show route protocol rip

Let’s check Router 1’s configuration with this commands. The outputs of other routers will also be similar. Only, Routing Table will be a little different.

Juniper-Router1@Kosem# show protocols
rip {
group rip-group {
export RIPPolicy;
neighbor ge-1/1/1;
neighbor ge-1/1/2;
}
}

Juniper-Router1@Kosem# show policy-options
policy-statement RIPPolicy {
term 1 {
from protocol [ direct rip ];
then accept;
}
}

Juniper-Router1@Kosem# show route
inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.10.0/30 *[Direct/0] 00:40:11, metric 2, tag 0
> to 10.0.10.1 via ge-1/1/1
10.0.20.0/30 *[Direct/0] 00:40:11, metric 2, tag 0
> to 10.0.10.1 via ge-1/1/2
10.0.30.0/30 *[RIP/100] 00:40:11, metric 2, tag 0
> to 10.0.10.1 via ge-1/1/1
224.0.0.9/32 *[RIP/100] 00:42:13, metric 1
MultiRecv

Juniper-Router1@Kosem# show route protocol rip
inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, – = Last Active, * = Both

10.0.30.0/30 *[RIP/100] 00:40:11, metric 2, tag 0
> to 10.0.10.1 via ge-1/1/1
224.0.0.9/32 *[RIP/100] 00:42:13, metric 1
MultiRecv

Leave a Reply