RIP Configuration between Cisco and Juniper Routers on Gns3 1.1

How to Configure RIP among different vendor routers:

This article is about configuration of RIP routing protocol between Cisco and juniper. RIP is an open standard protocol that's mean you can configure it among different vendors router. RIP have two versions i.e. version 1 & version 2 (which the most advance & standard version of routing information protocol). On Cisco when you enable RIP, by default its run the version 1 and you manually have to configure the version 2. On the other hand junOS enables the version 2 by default.

Lab details:

Gns3: Gns3 version 1.1.X
VitualBox: 4.2.4 
Cisco IOS: Cisco 7200 series
Junos version=  JunOS Olive 12.1 VM image

Beginner and want to learn about JunOS then you can see how to configure junos on gns3 and Juniper commands.

In our topology we have three router j2, j4 & R1, junos2 & junos4 are juniper routers and R1 is Cisco router.
Lab objective:
Configure RIP on all the routers so that they can communicate with each other.
Lab configurations:
You need to perform the following configurations for achieving the above objective.
JUNOS 2 Configuration:
On JUNOS 2 device, both interfaces em0 and lo0 will be configured for RIP. They will be in the same RIP group called rip-routes.
set interface em0 unit 0 family inet 172.16.1.1/24
set interface lo0 unit 0 family inet 111.0.0.1/32
set protocols rip group rip-routes neighbor em0
set policy-option policy-statement advertise-RIProutes from protocol direct
set policy-option policy-statement advertise-RIProutes from protocol rip
set policy-option policy-statement advertise-RIProutes then accept  

set protocols rip group rip-routes export advertise-RIProutes
 "advertise-RIProutes" is the name of policy for RIP, you can learn more about the configuration of RIP on juniper.

Output of run show configuration | display set on JunOS 2:



JUNOS 4 Configuration:
Similarly you will be configure both interfaces em0 & lo0 for RIP with similar RIP group i.e. rip-routes.
set interface em0 unit 0 family inet 192.168.1.2/24
set interface lo0 unit 0 family inet 222.0.0.1/32
set protocols rip group rip-routes neighbor em0
set policy-option policy-statement advertise-RIProutes from protocol direct
set policy-option policy-statement advertise-RIProutes from protocol rip
set policy-option policy-statement advertise-RIProutes then accept  

set protocols rip group rip-routes export advertise-RIProutes

Output of run show configuration | display set on JunOS 4:

R1 Configuration:
On cisco router you need to advertise both network 192.168.1.0 & 172.16.1.0 In RIP routing

interface FastEthernet0/0
 ip address 172.16.1.2 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 ip address 192.168.1.1 255.255.255.0
 duplex auto
 speed auto
!
router rip
 version 2
 network 172.16.0.0
 network 192.168.1.0
 no auto-summary

How to test your configurations:
After the correct configuration ping from JunOS2 to 222.0.0.1 should be successful.

Output of Cisco Routing Table:



Output of Routing Table on JunOS 2:



3 comments:

  1. I've always used GNS3 to configure Cisco routers and Qemu for Juniper routers. But having both interconnected with RIP is nice.

    ReplyDelete
  2. Very Good example... Thanks a lot

    ReplyDelete
  3. Great example. How do you stop the Juniper routes from being summarized? There appears to be no 'no-summary' equivalent in Juniper and all my routes are being summarized as shown below:

    rtodhunter@4200-7> show route receive-protocol rip 192.168.20.5

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

    1.0.0.0/8 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    2.0.0.0/8 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    10.0.0.0/8 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    172.128.0.0/16 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.1.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.2.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.3.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.4.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.10.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.128.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.132.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.133.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31
    192.168.134.0/24 *[RIP/100] 00:24:20, metric 2, tag 0
    > to 192.168.20.5 via vlan.31

    ReplyDelete

UA-23728446-1