cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
1544
Views
25
Helpful
11
Replies

RIP not working

Boda
Level 1
Level 1

Hello guys,

I'm still new here so, I apologize in advance if I posted the question incorrectly.
I'm trying to create a network that consists of 2 buildings. Each building has 3 floors and each floor has its own local network. Below is the IP table for the local networks (Network addresses):
Building 1:

Production floor - 128.0.0.0/20

Testing floor - 128.0.16.0/21

Quality control floor - 128.0.24.0/22

Building 2:

Design floor - 128.0.28.0/23

Management floor - 128.0.30.0/24

Safety floor - 128.0.31.0/26

For each floor, I have a couple of end device connected to a switch and a router connected to the switch. So for each building I have 3 routers that connect all the local areas together. I then added 2 routers to connect both buildings together.

My plan is that I want to create a 3 layer network with redundancies but I only created 2 layers to test the connections. I would like to use RIP as the routing protocol. The issue I am having is that I can ping the devices in the local network but I can't ping devices from different networks. When ever I try to do so in the command prompt, I get a message that says "Destination host unreachable". I set all routers to work with RIP and I added all the networks in each router but I still can't figure out what's the issue. I have attached 2 pictures, 1 showing an overview of the whole current network and another showing a close up of one of the local networks. 
Your help is much appreciated.

 

Update: I have made some changes based on the suggestions I have received so far. All the devices in one building are pinging each other successfully but the second building isn't working.

I have also attached the latest packet tracer project (Protocol used RIPv2)

 

1 Accepted Solution

Accepted Solutions

Hello Boda,

to make the two buildings to communicate you need a common IP subnet between the two routers on the top that interconnect with a serial line and to run RIPv2 over it.

RIPv1 does not support your network topology because you have used different subnet masks taken from major network 128.0.0.0

 

But RIPv2 should work .

If you use major network 128.1.0.0 for inter router links you need to disable auto summary under RIPv2

 

Hope to help

Giuseppe

 

View solution in original post

11 Replies 11

balaji.bandi
Hall of Fame
Hall of Fame

You need also show configuration example : Try use RIPv2

 

But i always suggest to use OSPF or EIGRP for the requirement, if this is Lab for testing. you can do as many as testing you want with different IGP

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

I am really sorry I don't think I fully understand what you mean. I used the router GUI to add the networks for RIP and this is exactly what is inside each router:

128.0.0.0 (the local areas network)

128.1.0.0 (The rest are connections between each router)

128.2.0.0

128.3.0.0

128.4.0.0

128.5.0.0

128.11.0.0

128.12.0.0

Is that right?

Hello Boda,

to make the two buildings to communicate you need a common IP subnet between the two routers on the top that interconnect with a serial line and to run RIPv2 over it.

RIPv1 does not support your network topology because you have used different subnet masks taken from major network 128.0.0.0

 

But RIPv2 should work .

If you use major network 128.1.0.0 for inter router links you need to disable auto summary under RIPv2

 

Hope to help

Giuseppe

 

Dear Giuseppe,

Thank you so much for your explanation, it helped a lot. The whole network works perfect now. This is my first time hearing about auto summary and I will definitely need to read more about it. 

Much appreciated,

Boda

If I remember correctly, Cisco's auto summary is related to classful addressing.  When on, it aggregates "real" subnets up into their class's address block.  When off, "real" subnets are classless networks (with routing protocols that support classless addressing).

Classful addressing isn't much used much any more, but you can enounter a few issues were it can still arise, as in the auto summary config statement.

BTW, if you follow the rules for classful addressing, RIP would work fine for you too, but routing with classful "real" subnets has its own special rules.

Hello Boda,

auto-summary is triggered by a change of major network when sending updates out an interface in  a different major network like 128.1.0.0 is when compared with 128.0.0.0, the auto-summary feature causes the router to send the classful 128.0.0.0/16 instead of the known subnets.

in your case you have a partitioned major network 128.0.0.0 as some subnets are in the first building and some are in the second building and the inter router link is in 128.1.0.0 major network.

Disabling auto-summary allows each router to send the known subnets of 128.0.0.0/16 to each other

 

Hope to help

Giuseppe

 

 

Dear Giuseppe,

That makes sense now. Thank you so much, you have helped me a lot. Your efforts are much appreciated.

Regards,

Boda

Joseph W. Doherty
Hall of Fame
Hall of Fame

Possibly you might be bumping into the issue that RIP is a classful routing protocol.  (NB: 128.x.x.x is a class B address block, i.e. /16.)

RIPv2 (suggested by Balaji) supports classless although it still embeds some classful features.

OSPF or EIGRP (as also suggested by Balaji) better support classless than RIPv2.

 

Boda
Level 1
Level 1

I tired RIPv2 like you guys said and I am successfully pinging some devices in the same building, however, I can't seem to ping devices from the other building. I'm trying to research about OSPF and EIGRP. But in the mean time, do you have any idea why this might be happening?

Hello,

 

this looks like a Packet Tracer project, if that is the case, post the zipped project (.pkt) file...

Yes sure. I have attached the zipped file.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card