From: Bola Adegbonmire (BolaAD@xxxxxxxxxxxxxxxxx)
Date: Fri May 31 2002 - 15:06:52 GMT-3
Kym,
Thanks a zillion for pointing out my assumptions. I do agree with you
that the interface will not advertise OSPF domain routes with anything
other than /24, so whereas it works here, it won't always. But the part
where you pointed out other routes with a diferent address other than
10.1.1.x won't work I am not so clear on.If I had a 10.1.2.x/24 you say
it won't be pingable, but it was pingable in the ospf domain. I did have
10.1.5.0/24, 10.1.2.0/24 , 10.1.3.0/24 in the ospf domain and they were
all pingable form anywhere in the internetwork. What will not be
pingable from the RIP domain are addresses on any reachable network that
is outside of the /20 subnet for that range.that is if I had a 10.1.4.19
on the R-ospf e0/1 int, it will be reachable from anywhere in the
internetwork save the RIP domain. Why? - the RIP domain will still
calculate the reachable networks as /20 and as this falls out of the
reachable 10.1.4.0/20 that it calculates, it will return an
adminstrative message of unroutable to the administrator. This happens
even though the host is a legitimate host on the ospf 10.1.4.0/24
subnet. At the same time a host with 10.1.4.10 will be reacheble from
the same location. This is my understanding. Am I missing out something?
I really want to learn.
These things tell me I am in the right group.
Thanks for pointing out my assumptions and giving me a solution. Your
soluion is dead right!! Just never thought of it. I guess that's' why I
am not yet a CCIE. Right?
-----Original Message-----
From: kym blair [mailto:kymblair@hotmail.com]
Sent: Friday, May 31, 2002 11:19 AM
To: osindero@lagos.sns.slb.com; ccielab@groupstudy.com
Subject: RE: [OSPF & RIP Red. With rip longer mask]
Bola and Ademola,
Setting the redistribution router's E0 mask to /24 won't do what you
want.
First, all of your RIP routes arrived in OSPF with /32 masks, so your
pings
only worked because they started with 10.1.1.X, which is the same as the
valid 10.1.1.0 /24 on E0. Any network with some different address
(e.g.,
10.1.2.X /24) wouldn't work. Second, this approach will only allow
redistribution of interfaces with the same mask (/24); it won't
redistribute
routes with other masks.
SOLUTION: You should be allowed to add the following even if your
instructions say to only use RIP version 1 (but better verify with the
proctor):
Router R-RED (running RIP Version 1)
int e 0
ip rip send version 2
ip rip rece version 2
Router R-RIP (running RIP Version 1)
int e 0
ip rip send version 2
ip rip rece version 2
Regards, Kym
>>-----Original Message-----
>>From: Bola Adegbonmire
>>Sent: Thursday, May 30, 2002 4:25 PM
>>To: 'Ademola Osindero'
>>Cc: 'ccielab@studygroup.com'
>>Subject: RE: OSPF & RIP Red. With rip longer mask
>>
>>
>>I will try to see if I can get a solution to the caveat you
>>introduced,
>>off
>>the cuff now I don't have a solution, But I guess it will make an
>>interesting
>>search. I tried everything before this solution but it wouldn't work.
I
>>believe it still stands, no static routes?
>>
>>-----Original Message-----
>>From: Ademola Osindero [mailto:osindero@lagos.sns.slb.com]
>>Sent: Thursday, May 30, 2002 4:07 PM
>>To: Bola Adegbonmire; ccielab@groupstudy.com
>>Subject: RE:OSPF & RIP Red. With rip longer mask
>>
>>
>>Hi Bola,
>>
>>"The solution is to change the mask of the router connecting to the
>>RIP domain on the redristributing router to match that of the ospf
>>domain."
>>
>>What if you are not permitted to change the mask and things are still
>>expected to work, can there be another way around it?
>>
>>Ademola
>>
>>At 02:07 PM 5/30/2002 +0100, Bola Adegbonmire wrote:
>>
>>
>>Hi,
>>Somebody posted this scenario earlier. Here is what I came up with in
>>the lab.
>>
>>This are configs from three 2611 routers used to simulate this
>>scenario. I didn't post this earlier 'cos I wanted to be sure that if
>>I actuall had a PC behind one of the networks I will be able to get to
>>it. Which works.
>>
>>The solution is to change the mask of the router connecting to the RIP
>>domain on the redristributing router to match that of the ospf domain.
>>That way the ospf routers learn the RIP routes with a /32 mask, but
>>since the routers have ip classless configured packtets get routed
>>with longest match rule. There should be no conflitcs as long as the
>>rip networks major networks if the ospf mask were used on the RIP
>>domian are not duplicated in the ospf domain. The ping outputs to
>>10.1.1.18 for the PC attached to the R-RIP int e0/1.
>>
>>Rip domain uses /28 mask while OSPF uses /24 mask. All are of the
>>10.0.0.0 major network.
>>
>>If there are any assumptions anybody knows of I have made, pls let me
>>know. I want to learn. Or nay other way without using static routes.
>>
>>Have fun
>>
>>Network illustration.
>>R-ospf--------------------------------R-Red---------------------------
>>--
>>----------R-RIP
>>
>>Here are the configs.
>>
>>For R-ospf
>>
>>sh run
>>Building configuration...
>>
>>Current configuration : 788 bytes
>>!
>>version 12.1
>>service timestamps debug uptime
>>service timestamps log uptime
>>no service password-encryption
>>!
>>hostname R-ospf
>>!
>>!
>>!
>>!
>>!
>>!
>>memory-size iomem 10
>>ip subnet-zero
>>no ip finger
>>!
>>ip audit notify log
>>ip audit po max-events 100
>>!
>>!
>> --More-- !
>>!
>>!
>>!
>>!
>>!
>>interface Loopback0
>> ip address 10.1.3.1 255.255.255.0
>> ip ospf network point-to-point
>>!
>>interface Loopback2
>> ip address 10.1.5.1 255.255.255.0
>> ip ospf network point-to-point
>>!
>>interface Ethernet0/0
>> ip address 10.1.2.2 255.255.255.0
>>!
>>interface Ethernet0/1
>> ip address 10.1.4.1 255.255.255.0
>> no keepalive
>>!
>>router ospf 2
>> log-adjacency-changes
>> --More--
>> network 10.1.0.0 0.0.255.255 area 0
>>!
>>ip classless
>>no ip http server
>>!
>>!
>>line con 0
>> exec-timeout 0 0
>> transport input none
>>line 33 40
>>line aux 0
>>line vty 0 4
>>!
>>no scheduler allocate
>>end
>>
>>R-ospf#sh ip ro
>>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, 8 subnets, 2 masks
>>C 10.1.3.0/24 is directly connected, Loopback0
>>C 10.1.2.0/24 is directly connected, Ethernet0/0
>>O E1 10.1.1.0/24 [110/75] via 10.1.2.1, 00:15:41, Ethernet0/0
>>C 10.1.5.0/24 is directly connected, Loopback2
>>C 10.1.4.0/24 is directly connected, Ethernet0/1
>>O E1 10.1.1.16/32 [110/75] via 10.1.2.1, 00:06:35, Ethernet0/0
>>O E1 10.1.1.32/32 [110/75] via 10.1.2.1, 00:05:57, Ethernet0/0
>>O E1 10.1.1.48/32 [110/75] via 10.1.2.1, 00:05:58, Ethernet0/0
>>R-ospf#ping 10.1.1.17
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.17, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-ospf#ping 10.1.1.18
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.18, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-ospf#ping 10.1.1.33
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.33, timeout is 2 seconds:
>>.!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/3/4
>>ms R-ospf#ping 10.1.1.1
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
>>.!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/2/4
>>ms R-ospf#trace 10.1.1.18
>>
>>Type escape sequence to abort.
>>Tracing the route to 10.1.1.18
>>
>> 1 10.1.2.1 0 msec 0 msec 4 msec
>> 2 10.1.1.18 4 msec 0 msec 4 msec
>>R-ospf#ping 10.1.1.49
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.49, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>4/4/4 ms R-ospf#
>>
>>For R-RIP
>>
>>sh run
>>Building configuration...
>>
>>Current configuration : 740 bytes
>>!
>>version 12.1
>>service timestamps debug uptime
>>service timestamps log uptime
>>no service password-encryption
>>!
>>hostname R-RIP
>>!
>>!
>>!
>>!
>>!
>>!
>>memory-size iomem 10
>>ip subnet-zero
>>no ip finger
>>!
>>ip audit notify log
>>ip audit po max-events 100
>>!
>>!
>> --More--!
>>!
>>!
>>voice-port 1/0/0
>>!
>>voice-port 1/0/1
>>!
>>voice-port 1/1/0
>>!
>>voice-port 1/1/1
>>!
>>!
>>!
>>!
>>interface Loopback0
>> ip address 10.1.1.1 255.255.255.240
>>!
>>interface Loopback2
>> ip address 10.1.1.33 255.255.255.240
>>!
>>interface Ethernet0/0
>> ip address 10.1.1.49 255.255.255.240
>>!
>> --More--
>>interface Ethernet0/1
>> ip address 10.1.1.17 255.255.255.240
>>!
>>router rip
>> network 10.0.0.0
>>!
>>ip classless
>>no ip http server
>>!
>>!
>>line con 0
>> exec-timeout 0 0
>> transport input none
>>line aux 0
>>line vty 0 4
>>!
>>no scheduler allocate
>>end
>>
>>R-RIP#sh ip ro
>>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/28 is subnetted, 8 subnets
>>R 10.1.3.0 [120/3] via 10.1.1.50, 00:00:02, Ethernet0/0
>>R 10.1.2.0 [120/1] via 10.1.1.50, 00:00:02, Ethernet0/0
>>C 10.1.1.0 is directly connected, Loopback0
>>R 10.1.5.0 [120/3] via 10.1.1.50, 00:00:02, Ethernet0/0
>>R 10.1.4.0 [120/3] via 10.1.1.50, 00:00:02, Ethernet0/0
>>C 10.1.1.16 is directly connected, Ethernet0/1
>>C 10.1.1.32 is directly connected, Loopback2
>>C 10.1.1.48 is directly connected, Ethernet0/0
>>R-RIP#ping 10.1.3.1
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.3.1, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/3/4 ms R-RIP#ping 10.1.4.1
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.4.1, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-RIP#ping 10.1.5.1
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.5.1, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-RIP#
>>
>>For R-Red
>>
>>
>>sh run
>>Building configuration...
>>
>>Current configuration:
>>!
>>version 12.0
>>service timestamps debug uptime
>>service timestamps log uptime
>>no service password-encryption
>>!
>>hostname R-Red
>>!
>>!
>>!
>>!
>>!
>>!
>>memory-size iomem 10
>>ip subnet-zero
>>!
>>ip audit notify log
>>ip audit po max-events 100
>>cns event-service server
>>!
>>!
>> --More---
>>!
>>!
>>!
>>voice-port 1/0/0
>>!
>>voice-port 1/0/1
>>!
>>voice-port 1/1/0
>>!
>>voice-port 1/1/1
>>!
>>process-max-time 200
>>!
>>interface Ethernet0/0
>> ip address 10.1.1.50 255.255.255.0
>> no ip directed-broadcast
>>!
>>interface Ethernet0/1
>> ip address 10.1.2.1 255.255.255.0
>> no ip directed-broadcast
>>!
>>router ospf 2
>> redistribute rip metric 65 metric-type 1 subnets
>> --More--
>>network 10.1.2.0 0.0.0.255 area 0
>>!
>>router rip
>> redistribute ospf 2 metric 3
>> network 10.0.0.0
>>!
>>ip classless
>>no ip http server
>>!
>>!
>>!
>>line con 0
>> exec-timeout 0 0
>> transport input none
>>line aux 0
>>line vty 0 4
>>!
>>!
>>no scheduler allocate
>>end
>>
>>R-Red#sh ip ro
>>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, 8 subnets, 2 masks
>>O 10.1.3.0/24 [110/11] via 10.1.2.2, 00:26:33, Ethernet0/1
>>C 10.1.2.0/24 is directly connected, Ethernet0/1
>>C 10.1.1.0/24 is directly connected, Ethernet0/0
>>O 10.1.5.0/24 [110/11] via 10.1.2.2, 00:26:33, Ethernet0/1
>>O 10.1.4.0/24 [110/20] via 10.1.2.2, 00:26:33, Ethernet0/1
>>R 10.1.1.16/32 [120/1] via 10.1.1.49, 00:00:27, Ethernet0/0
>>R 10.1.1.32/32 [120/1] via 10.1.1.49, 00:00:27, Ethernet0/0
>> [120/1] via 10.1.1.17, 00:00:27, Ethernet0/0
>>R 10.1.1.48/32 [120/1] via 10.1.1.17, 00:00:28, Ethernet0/0
>>R-Red#ping 10.1.1.1
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-Red#ping 10.1.1.18
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.18, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-Red#ping 10.1.1.17
>>
>>Type escape sequence to abort.
>>Sending 5, 100-byte ICMP Echos to 10.1.1.17, timeout is 2 seconds:
>>!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max =
>>1/2/4 ms R-Red#
>>
>>Bola Adegbonmire
>>WAN, Security and Network management
>>Resourcery Limited
>>18 Adeola Hopewell, Victoria Island.Lagos-Nigeria. Tel:234-1-3200301,
>>4618281, 7740711-2
>>
>>*************************************************Disclaimer***********
>>**
>>***************************************************
>>"The information contained in this email and any attached files is
>>strictly private and confidential. This email should be read by the
>>intended addressee only. If the recipient of this message is not the
>>intended addressee, please call Resourcery limited Lagos Nigeria, on
>>+234 1 7740711 and promptly delete this email and any attachments. The
>>intended recipient of this email may only use, reproduce, disclose or
>>distribute the information contained in this email and any attached
>>files with Resourcery's permission. If you are not the intended
>>addressee, you are strictly prohibited from using, reproducing,
>>disclosing or distributing the information contained in this email and
>>any attached files. Resourcery advises that this email and any
>>attached files should be scanned to detect viruses. Resourcery accepts
>>no liability for loss or damage (whether caused by negligence or not)
>>resulting from the use of any attached files."
>>**********************************************************************
>>**
>>***************************************************
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:13 GMT-3