08-21-2019 09:59 PM
Will they ping (image is attached).
In my case it's not pinging.
And if pinging, how?
Ps : Using C7200(router) ios image in GNS3
Solved! Go to Solution.
08-21-2019 10:35 PM
Hello Yaman,
by default Cisco routers can run both versions of RIP v1 and v2.
So it depends on how you configure the routers.
if your configuration is
R1:
router rip
version 1
network 1.0.0.0
network 192.168.1.0
!
R2
router rip
version 2
network 2.0.0.0
network 192.168.1.0
!
This can lead to interoperability issues.
You can check the state of RIP communication by
show ip route rip
if this show output is empty the two routers are not considering each other RIP neighbors
Likely R1 does not accept the version 2 update sent by R2, R2 can accept R1's update.
R2 version 2 updates are sent to IPv4 multicast address 224.0.0.9 R1 version 1 update are sent to 255.255.255.255 broadcast address.
Hope to help
Giuseppe
08-21-2019 11:01 PM
Hi @YamanBelwal0505 ,
Try this:
Router RIPv1
Router#show ip protocols
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Loopback1 1 2 1
FastEthernet0/0 1 2 1
Router RIPv2
Router#show ip protocols
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Loopback2 2 2
FastEthernet0/0 2 2
If you see these results, the RIPv1 router is receiving updates from both versions, but, the RIPv2 router is only receiving updates from version 2.
Maybe it will be solved with this command:
On router RIPv2
Router(config)# interface g0/0
Router(config-if)# ip rip receive version 1 2
Then, check again with the show ip protocols command.
I hope that helps you.
Regards
08-22-2019 01:09 AM
Hello Yaman,
RIP both versions is legacy for its very slow convergence and the limited scalability caused by the limited metric (up to 15 router hops allowed).
some use cases are for :
interaction with devices with limited routing capabilites to give them a dynamic routing protocol default route
providing a default route to some Unix workstations that has the RIP daemon running on it.
So RIP usage is limited to special cases and only to some access sections of the network. RIP is used as an edge protocol.
The core routing protocol now can be OSPF, EIGRP (that has became public it is not Cisco proprietary anymore) and IS-IS (less frequent in enterprise environment but it is becoming more popular for dual stack IPv4/IPv6 environments)
Hope to help
Giuseppe
08-21-2019 10:35 PM
Hello Yaman,
by default Cisco routers can run both versions of RIP v1 and v2.
So it depends on how you configure the routers.
if your configuration is
R1:
router rip
version 1
network 1.0.0.0
network 192.168.1.0
!
R2
router rip
version 2
network 2.0.0.0
network 192.168.1.0
!
This can lead to interoperability issues.
You can check the state of RIP communication by
show ip route rip
if this show output is empty the two routers are not considering each other RIP neighbors
Likely R1 does not accept the version 2 update sent by R2, R2 can accept R1's update.
R2 version 2 updates are sent to IPv4 multicast address 224.0.0.9 R1 version 1 update are sent to 255.255.255.255 broadcast address.
Hope to help
Giuseppe
08-21-2019 10:49 PM - edited 08-21-2019 10:50 PM
08-21-2019 11:02 PM - edited 08-21-2019 11:07 PM
Hello Yaman,
the router configured for RIP version 2 R2 by listening to R1 version 1 updates will fallback to version 1 RIP updates.
This explains why both routers are able to ping the other router's loopback.
In show ip route rip you should have one entry for the classful network 1.0.0.0/8 or 2.0.0.0/8 on each router.
Edit:
as explained by Luis a Cisco router running RIP can be listening to both versions of RIP.
RIP has not neighbor state machine concept compared to more modern and complex protocols like EIGRP and OSPF so it is able to work in a mixed version 1 / version 2 scenario like yours.
Hope to help
Giuseppe
08-21-2019 11:01 PM
Hi @YamanBelwal0505 ,
Try this:
Router RIPv1
Router#show ip protocols
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
Loopback1 1 2 1
FastEthernet0/0 1 2 1
Router RIPv2
Router#show ip protocols
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Loopback2 2 2
FastEthernet0/0 2 2
If you see these results, the RIPv1 router is receiving updates from both versions, but, the RIPv2 router is only receiving updates from version 2.
Maybe it will be solved with this command:
On router RIPv2
Router(config)# interface g0/0
Router(config-if)# ip rip receive version 1 2
Then, check again with the show ip protocols command.
I hope that helps you.
Regards
08-22-2019 12:01 AM
08-22-2019 01:09 AM
Hello Yaman,
RIP both versions is legacy for its very slow convergence and the limited scalability caused by the limited metric (up to 15 router hops allowed).
some use cases are for :
interaction with devices with limited routing capabilites to give them a dynamic routing protocol default route
providing a default route to some Unix workstations that has the RIP daemon running on it.
So RIP usage is limited to special cases and only to some access sections of the network. RIP is used as an edge protocol.
The core routing protocol now can be OSPF, EIGRP (that has became public it is not Cisco proprietary anymore) and IS-IS (less frequent in enterprise environment but it is becoming more popular for dual stack IPv4/IPv6 environments)
Hope to help
Giuseppe
08-22-2019 01:16 AM
08-22-2019 01:18 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide