networking-forum.com
Community BlogCommunity Wiki * Register  * Search  * Login
View unanswered postsView active topics

All times are UTC - 6 hours [ DST ]



Post new topic Reply to topic  [ 12 posts ] 
Author Message
PostPosted: Thu Feb 17, 2011 5:47 pm 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Hey guys, I was just wondering if I could get some help with this.

I'm in the final stretch of my CCNA studies and I decided to setup an all-in-one network in packet tracer. A big series of networks that pretty much just revises all the mentioned content. At any rate, after setting up a static route network and a separate RIPv2 network, I wanted to enable communication between the networks and I have been unsuccessful at redistributing the routes.

Here is the network layout (there is no "logical" layout... I'm just adding features as I revise the topics in the curriculum):
Image

R4, R5, and R6 are all running rip and R1, R2, and R3 are all communicating via static routes. I was trying to use R4 to run redistribution, but I have been unsuccessful at completing the task. As of right now, R4 can communicate with everybody, but the other rip routers can't cross over and vice versa. All cross traffic seems to be getting cut off at R4 (obviously).

Here are the router configurations (the parts that matter anyway and I've attached the packet tracer sim):

R1
Quote:
ip route 192.168.2.0 255.255.255.0 192.168.1.2
ip route 192.168.3.0 255.255.255.0 192.168.1.2
interface Serial0/1/0
ip address 192.168.4.2 255.255.255.0


R2
Quote:
ip route 192.168.3.0 255.255.255.0 192.168.2.2
ip route 192.168.0.0 255.255.255.0 192.168.1.1
ip route 192.168.4.0 255.255.255.0 192.168.1.1


R3
Quote:
ip route 192.168.1.0 255.255.255.0 192.168.2.1
ip route 192.168.0.0 255.255.255.0 192.168.2.1
ip route 192.168.4.0 255.255.255.0 192.168.2.1


R4
Quote:
interface Serial0/0/0
ip address 192.168.4.1 255.255.255.0
clock rate 800000
router rip
version 2
redistribute static metric 1
network 10.0.0.0
no auto-summary
ip route 192.168.0.0 255.255.255.0 192.168.4.2
ip route 192.168.1.0 255.255.255.0 192.168.4.2
ip route 192.168.2.0 255.255.255.0 192.168.4.2
ip route 192.168.3.0 255.255.255.0 192.168.4.2


R4 show ip rip database
Quote:
R4#sh ip rip database
10.0.1.0/24 auto-summary
10.0.1.0/24 directly connected, Serial0/3/0
10.0.2.0/24 auto-summary
10.0.2.0/24
[1] via 10.0.1.2, 00:00:05, Serial0/3/0 [1] via 10.0.3.2, 00:00:19, Serial0/3/1
10.0.3.0/24 auto-summary
10.0.3.0/24 directly connected, Serial0/3/1
10.0.4.0/24 auto-summary
10.0.4.0/24
[1] via 10.0.1.2, 00:00:05, Serial0/3/0
10.0.5.0/24 auto-summary
10.0.5.0/24
[1] via 10.0.1.2, 00:00:05, Serial0/3/0
192.168.0.0/24 auto-summary
192.168.0.0/24
[1] via 192.168.4.2, 00:00:07
192.168.1.0/24 auto-summary
192.168.1.0/24
[1] via 192.168.4.2, 00:00:07
192.168.2.0/24 auto-summary
192.168.2.0/24
[1] via 192.168.4.2, 00:00:07
192.168.3.0/24 auto-summary
192.168.3.0/24
[1] via 192.168.4.2, 00:00:07


R5
Quote:
router rip
version 2
network 10.0.0.0
no auto-summary


R6
Quote:
router rip
version 2
network 10.0.0.0
no auto-summary


Sorry for the long post, I'm just really baffled by this. I have no idea whether I'm forgetting a small command or if I've missed the boat completely. Any help would be appreciated, thanks in advance.

By the way, I'm a first time poster (long time reader) and I really like your forum.


Attachments:
ccna lab.zip [18.84 KiB]
Downloaded 75 times
Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 9:12 am 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Anybody? I'd really appreciate some help. I've read over my Cisco IOS cookbook and I followed the steps, but I still can't get it to work.


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 9:38 am 
Offline
Post Whore
Post Whore
User avatar

Joined: Thu Oct 14, 2010 4:39 am
Posts: 1007
Certs: CCNP (R&S, Security), ITILv3 Foundation
How about a bit more information:
show ip route
show ip protocols
both from R4.
I'm presuming that you've got a packet tracer file attached so if I have the time tonight / tomorrow morning I'll download it and take a looksee. Presuming, of course, that no-one else comes up with an elegant solution in the meantime.


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 9:41 am 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Halo wrote:
How about a bit more information:
show ip route
show ip protocols
both from R4.
I'm presuming that you've got a packet tracer file attached so if I have the time tonight / tomorrow morning I'll download it and take a looksee. Presuming, of course, that no-one else comes up with an elegant solution in the meantime.


No problem!

R4 show ip route
Quote:
R4#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/24 is subnetted, 5 subnets
C 10.0.1.0 is directly connected, Serial0/3/0
R 10.0.2.0 [120/1] via 10.0.1.2, 00:00:26, Serial0/3/0
[120/1] via 10.0.3.2, 00:00:24, Serial0/3/1
C 10.0.3.0 is directly connected, Serial0/3/1
R 10.0.4.0 [120/1] via 10.0.1.2, 00:00:26, Serial0/3/0
R 10.0.5.0 [120/1] via 10.0.1.2, 00:00:26, Serial0/3/0
S 192.168.0.0/24 [1/0] via 192.168.4.2
S 192.168.1.0/24 [1/0] via 192.168.4.2
S 192.168.2.0/24 [1/0] via 192.168.4.2
S 192.168.3.0/24 [1/0] via 192.168.4.2
C 192.168.4.0/24 is directly connected, Serial0/0/0


R4 show ip protocol
Quote:
R4#show ip protocol
Routing Protocol is "rip"
Sending updates every 30 seconds, next due in 17 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip, static
Default version control: send version 2, receive 2
Interface Send Recv Triggered RIP Key-chain
Serial0/3/0 2 2
Serial0/3/1 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
10.0.1.2 120 00:00:09
10.0.3.2 120 00:00:10
Distance: (default is 120)


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 10:08 am 
Offline
Post Whore
Post Whore
User avatar

Joined: Thu Oct 14, 2010 4:39 am
Posts: 1007
Certs: CCNP (R&S, Security), ITILv3 Foundation
Well from reading your diagram, you have a serial connection between R4's s0/0/0 and R1's s0/0/0.
The interface on R4 has an IP address of 192.168.4.1 /24
The RIP process on R4 does not, however, include the 192.168.4.1 interface.
Which means that the other routers running RIP (R5 and R6) won't have this network in their routing tables as they won't have been told about it.

That's the first thing that came to mind. The second one was a little more pernicious. When you say redistribute, do you mean it in a specifically networking sense, or in a more general 'this is where my statically-addressed network meets my dynamically-addressed network'. There's quite a difference.
In theory in can be solved by entering the following commands on R4
router rip
redistribute static
But I think it's best if you hang fire on entering those commands (or save your topology before you do). Redistribution isn't something that's tackled in the CCNA syllabus, nor do I have any notable experience in its behaviour in packet tracer.


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 10:21 am 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Halo wrote:
Well from reading your diagram, you have a serial connection between R4's s0/0/0 and R1's s0/0/0.
The interface on R4 has an IP address of 192.168.4.1 /24
The RIP process on R4 does not, however, include the 192.168.4.1 interface.
Which means that the other routers running RIP (R5 and R6) won't have this network in their routing tables as they won't have been told about it.


Good observation! So I ran the command (network 192.168.4.1) in R4 and now that network is being advertised:

R5 show ip route
Quote:
R5#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
C 10.0.1.0/24 is directly connected, Serial0/0/0
C 10.0.2.0/24 is directly connected, Serial0/0/1
C 10.0.2.2/32 is directly connected, Serial0/0/1
R 10.0.3.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0
[120/1] via 10.0.2.2, 00:00:24, Serial0/0/1
C 10.0.4.0/24 is directly connected, Loopback0
C 10.0.5.0/24 is directly connected, Loopback1
R 192.168.0.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0
R 192.168.1.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0
R 192.168.2.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0
R 192.168.3.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0
R 192.168.4.0/24 [120/1] via 10.0.1.1, 00:00:15, Serial0/0/0


R6 show ip route
Quote:
R6#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
R 10.0.1.0/24 [120/1] via 10.0.2.1, 00:00:27, Serial0/0/1
[120/1] via 10.0.3.1, 00:00:22, Serial0/0/0
C 10.0.2.0/24 is directly connected, Serial0/0/1
C 10.0.2.1/32 is directly connected, Serial0/0/1
C 10.0.3.0/24 is directly connected, Serial0/0/0
R 10.0.4.0/24 [120/1] via 10.0.2.1, 00:00:27, Serial0/0/1
R 10.0.5.0/24 [120/1] via 10.0.2.1, 00:00:27, Serial0/0/1
R 192.168.0.0/24 [120/1] via 10.0.3.1, 00:00:22, Serial0/0/0
R 192.168.1.0/24 [120/1] via 10.0.3.1, 00:00:22, Serial0/0/0
R 192.168.2.0/24 [120/1] via 10.0.3.1, 00:00:22, Serial0/0/0
R 192.168.3.0/24 [120/1] via 10.0.3.1, 00:00:22, Serial0/0/0
R 192.168.4.0/24 [120/1] via 10.0.3.1, 00:00:22, Serial0/0/0


R5 and R6 are now able to ping 192.168.4.1 (serial interface on R4) however they cannot ping 192.168.4.2 (serial interface on R1). Seeing as how R4 is advertising all my 192.168 networks, would I be wrong to assume that the packets can reach those networks, but cannot find their way back?

Halo wrote:
That's the first thing that came to mind. The second one was a little more pernicious. When you say redistribute, do you mean it in a specifically networking sense, or in a more general 'this is where my statically-addressed network meets my dynamically-addressed network'. There's quite a difference.
In theory in can be solved by entering the following commands on R4
router rip
redistribute static
But I think it's best if you hang fire on entering those commands (or save your topology before you do). Redistribution isn't something that's tackled in the CCNA syllabus, nor do I have any notable experience in its behaviour in packet tracer.


Like you said, this is out of my CCNA scope. I was literally just building a large packet tracer simulation with all the necessary elements for my CCNA studies, and I figured why not enable communication between all the different network types (instead of having a bunch of standalone networks). With that said, I guess I meant it in a general sense, where my static network meets my dynamic one.

Thanks for your answers so far!


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 10:25 am 
Offline
New Member
New Member
User avatar

Joined: Sun May 16, 2010 12:32 pm
Posts: 33
Location: London, UK
Certs: CCNA
like you said, the R1,R2 and R3 don't know where to respond.
something like adding R4 as the gateway of last resort for said routers will make it work..


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 10:48 am 
Offline
Post Whore
Post Whore
User avatar

Joined: Thu Oct 14, 2010 4:39 am
Posts: 1007
Certs: CCNP (R&S, Security), ITILv3 Foundation
osiris wrote:
like you said, the R1,R2 and R3 don't know where to respond.
something like adding R4 as the gateway of last resort for said routers will make it work..


The easiest way of doing this would be to issue one of the following:
ip route 0.0.0.0 0.0.0.0 192.168.4.1
ip default-network 192.168.4.1

This would mean that when one of those routers doesn't know where to send something it gets directed towards R4's S0/0/0 interface. Presuming, of course, that they have a route to 192.168.4.1


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 10:53 am 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Halo wrote:
osiris wrote:
like you said, the R1,R2 and R3 don't know where to respond.
something like adding R4 as the gateway of last resort for said routers will make it work..


The easiest way of doing this would be to issue one of the following:
ip route 0.0.0.0 0.0.0.0 192.168.4.1
ip default-network 192.168.4.1

This would mean that when one of those routers doesn't know where to send something it gets directed towards R4's S0/0/0 interface. Presuming, of course, that they have a route to 192.168.4.1


Yup right after I posted my updated RIP route advertisements I tried using a default gateway (ip route 0.0.0.0 0.0.0.0) and it worked like a charm. Although I had to create a gateway of last resort on each router in my statically assigned network (is this normal?).

Also, is this the best way to complete the redistribution? I mean, had this been a real RIP <----> Static environment, I doubt I'd be using a gateway of last resort to enable communication, right?


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 11:00 am 
Offline
Post Whore
Post Whore
User avatar

Joined: Thu Oct 14, 2010 4:39 am
Posts: 1007
Certs: CCNP (R&S, Security), ITILv3 Foundation
I'd have gone with a different design on the network, personally ;)
Although other acceptable answers could be:
Quote:
I'd have used a different routing protocol

Quote:
I'd have used some summarisation with my static routes

Quote:
Well we've still got a lot of spare carrier pigeons, so how about them?


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 11:03 am 
Offline
Ultimate Member
Ultimate Member

Joined: Thu Nov 18, 2010 3:54 pm
Posts: 757
Location: Canada
Certs: CCIE R&S
Halo wrote:
I'd have gone with a different design on the network, personally ;)
Although other acceptable answers could be:
Quote:
I'd have used a different routing protocol

Quote:
I'd have used some summarisation with my static routes

Quote:
Well we've still got a lot of spare carrier pigeons, so how about them?


LOL really there was no design in mind... it was just for studying/fun.

Thanks for your answers.


Top
 Profile  
 
PostPosted: Fri Feb 18, 2011 1:14 pm 
Offline
Post Whore
Post Whore
User avatar

Joined: Tue Aug 21, 2007 2:15 pm
Posts: 8457
Location: Frederick MD
Certs: Instanity
just to be clear
you can't redistribute RIP routes into static routes.
redistribution occurs between 2 different routing protocols.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: Bing [Bot], Otanx, OverComplicated, Simpleman123, Steven King and 24 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group