From: John Matijevic (matijevi@bellsouth.net)
Date: Wed Jul 09 2003 - 16:39:27 GMT-3
Adam,
I dont believe he needs to do that, the ospf network is on another network
than the rip network, he has connectivity to R1, and I dont believe he wants
to add the network to ospf, although that could certainly solve the issue,
then you would need to add the rip router to the ospf process. Jeongwoo, do
me a favor and run a clear ip ospf process on R1.
Sincerely,
Matijevic
----- Original Message -----
From: "Adam Asay" <aasay@cwfservice.net>
To: "Jeongwoo Park" <jpark@wams.com>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, July 09, 2003 3:27 PM
Subject: RE: Gotcha on Redistribute Connected
> Add network 170.100.23.0 0.0.0.255 area X to the OSPF process on router
> 2. Without this command on the network to reach the RIP router is
> unavailable.
>
> Thanks
> Adam
>
>
>
> On Wed, 2003-07-09 at 13:07, Jeongwoo Park wrote:
> > As you recommend, I added the route-map.
> > R1 is still not seeing the rip network.
> >
> >
> > router ospf 1
> > router-id 2.2.2.2
> > log-adjacency-changes
> > summary-address 170.100.20.0 255.255.255.0
> > redistribute connected subnets route-map c2o
> > redistribute rip subnets route-map r2o
> > network 170.100.12.0 0.0.0.255 area 0
> > network 170.100.124.0 0.0.0.255 area 0
> > !
> > router rip
> > redistribute ospf 1 metric 3
> > passive-interface default
> > no passive-interface Serial0/0.23
> > network 170.100.0.0
> > !
> > ip classless
> > ip http server
> > !
> > access-list 1 permit 170.100.20.0 0.0.0.7
> > access-list 2 permit 170.100.23.0 0.0.0.255
> > access-list 2 permit 170.100.51.0 0.0.0.255
> > dialer watch-list 1 ip 170.100.30.1 255.255.255.255
> > dialer-list 1 protocol ip permit
> > route-map r2o permit 10
> > match ip address 2
> > !
> > route-map c2o permit 10
> > match ip address 1
> >
> >
> > R1's routing table
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mo
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA exter
> > E1 - OSPF external type 1, E2 - OSPF external type 2
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, i
> > * - candidate default, U - per-user static route, o
> > P - periodic downloaded static route
> >
> > Gateway of last resort is 0.0.0.0 to network 0.0.0.0
> >
> > 170.200.0.0/24 is subnetted, 1 subnets
> > O E2 170.200.212.0 [110/20] via 170.100.15.5, 04:25:37,
> > 170.100.0.0/16 is variably subnetted, 10 subnets, 3 ma
> > O 170.100.124.2/32 [110/64] via 170.100.124.2, 04:25:
> > C 170.100.124.0/24 is directly connected, Serial0/0
> > O 170.100.124.4/32 [110/128] via 170.100.124.2, 04:25
> > C 170.100.15.0/24 is directly connected, Ethernet0/0
> > O 170.100.12.0/28 [110/1626] via 170.100.124.2, 04:25
> > C 170.100.30.0/24 is directly connected, Ethernet0/1
> > O E2 170.100.20.0/24 [110/20] via 170.100.124.2, 00:47:4
> > O E2 170.100.40.0/24 [110/20] via 170.100.30.4, 04:25:38
> > O IA 170.100.55.0/24 [110/11] via 170.100.15.5, 04:25:48
> > O E2 170.100.51.0/24 [110/20] via 170.100.124.2, 04:05:4
> > S* 0.0.0.0/0 is directly connected, Ethernet0/1
>
> -------------------------------------------------------------------------
> > FIGHT BACK AGAINST SPAM!
> > Download Spam Inspector, the Award Winning Anti-Spam Filter
> > http://mail.giantcompany.com
> >
> >
> > -----Original Message-----
> > From: John Matijevic [mailto:matijevi@bellsouth.net]
> > Sent: Wednesday, July 09, 2003 11:56 AM
> > To: Jeongwoo Park; Brian Dennis; 'Badger'
> > Cc: 'Ram Shummoogum'; ccielab@groupstudy.com
> > Subject: Re: Gotcha on Redistribute Connected
> >
> > Hello Jeongwoo,
> > I am working on a similar type of scenerio.
> > I am going to recommend that you make the following change:
> > > redistribute rip subnets route-map r2o
> > scroll down to config to view my recommended change on R2,
> > Please test and let us know results.
> > Sincerely,
> > Matijevic
> >
> > ----- Original Message -----
> > From: "Jeongwoo Park" <jpark@wams.com>
> > To: "'John Matijevic'" <matijevi@bellsouth.net>; "Brian Dennis"
> > <brian@labforge.com>; "'Badger'" <badger@pongo.org>
> > Cc: "'Ram Shummoogum'" <rshummoo@ca.ibm.com>; <ccielab@groupstudy.com>
> > Sent: Wednesday, July 09, 2003 2:12 PM
> > Subject: RE: Gotcha on Redistribute Connected
> >
> >
> > > Here you go;
> > >
> > > R1;
> > > hostname r1
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > no ip domain-lookup
> > > !
> > > isdn switch-type basic-ni
> > > !
> > > !
> > > !
> > > !
> > > !
> > > interface Ethernet0/0
> > > ip address 170.100.15.1 255.255.255.0
> > > !
> > > interface Serial0/0
> > > backup interface BRI0/0
> > > ip address 170.100.124.1 255.255.255.0
> > > encapsulation frame-relay
> > > ip ospf network point-to-multipoint
> > > frame-relay map ip 170.100.124.2 102 broadcast
> > > no frame-relay inverse-arp
> > > !
> > > interface BRI0/0
> > > ip address 170.100.12.1 255.255.255.240
> > > encapsulation ppp
> > > dialer map ip 170.100.12.2 broadcast 8358661
> > > dialer-group 1
> > > isdn switch-type basic-ni
> > > isdn spid1 0835866201 08358662
> > > isdn spid2 0835866401 08358664
> > > no peer neighbor-route
> > > !
> > > interface Ethernet0/1
> > > ip address 170.100.30.1 255.255.255.0
> > > !
> > > router ospf 1
> > > router-id 1.1.1.1
> > > log-adjacency-changes
> > > area 2 virtual-link 5.5.5.5
> > > network 170.100.12.0 0.0.0.255 area 0
> > > network 170.100.15.0 0.0.0.255 area 2
> > > network 170.100.30.0 0.0.0.255 area 3
> > > network 170.100.124.0 0.0.0.255 area 0
> > > !
> > >
> > > r2;
> > > hostname R2
> > > !
> > > !
> > > username all
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > no ip domain-lookup
> > > !
> > > isdn switch-type basic-ni
> > > !
> > > !
> > > voice-port 1/0/0
> > > !
> > > voice-port 1/0/1
> > > !
> > > !
> > > !
> > > !
> > > interface Ethernet0/0
> > > ip address 170.100.20.2 255.255.255.248
> > > !
> > > interface Serial0/0
> > > no ip address
> > > encapsulation frame-relay
> > > no fair-queue
> > > !
> > > interface Serial0/0.23 point-to-point
> > > ip address 170.100.23.2 255.255.255.0
> > > frame-relay interface-dlci 203
> > > !
> > > interface Serial0/0.124 multipoint
> > > ip address 170.100.124.2 255.255.255.0
> > > ip ospf network point-to-multipoint
> > > frame-relay interface-dlci 201
> > > frame-relay interface-dlci 204
> > > !
> > > interface BRI0/0
> > > ip address 170.100.12.2 255.255.255.240
> > > encapsulation ppp
> > > dialer map ip 170.100.12.1 broadcast 8358662
> > > dialer map ip 170.100.30.1 broadcast 8358662
> > > dialer watch-group 1
> > > dialer-group 1
> > > isdn switch-type basic-ni
> > > isdn spid1 0835866101 8358661
> > > isdn spid2 0835866301 8358663
> > > no peer neighbor-route
> > > !
> > > interface Ethernet0/1
> > > no ip address
> > > shutdown
> > > !
> > > router ospf 1
> > > router-id 2.2.2.2
> > > log-adjacency-changes
> > > summary-address 170.100.20.0 255.255.255.0
> > > redistribute connected subnets route-map c2o
> > > redistribute rip subnets
> > **Add here route-map r2o
> > > network 170.100.12.0 0.0.0.255 area 0
> > > network 170.100.124.0 0.0.0.255 area 0
> > > !
> > > router rip
> > > redistribute ospf 1 metric 3
> > > passive-interface default
> > > no passive-interface Serial0/0.23
> > > network 170.100.0.0
> > > !
> > > ip classless
> > > ip http server
> > > !
> > > access-list 1 permit 170.100.20.0 0.0.0.7
> > > access-list 2 permit 170.100.23.0 0.0.0.255
> > > access-list 2 permit 170.100.51.0 0.0.0.255
> > > dialer watch-list 1 ip 170.100.30.1 255.255.255.255
> > > dialer-list 1 protocol ip permit
> > > route-map r2o permit 10
> > > match ip address 2
> > > !
> > > route-map c2o permit 10
> > > match ip address 1
> > > !
> > >
> > > r3;
> > > hostname r3
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > no ip domain-lookup
> > > ip host r7 2007 10.0.136.1
> > > ip host pix3 2008 10.0.136.1
> > > ip host r5 2005 10.0.136.1
> > > ip host r4 2004 10.0.136.1
> > > ip host r3 2003 10.0.136.1
> > > ip host r6 2006 10.0.136.1
> > > ip host r2 2002 10.0.136.1
> > > !
> > > !
> > > !
> > > !
> > > interface Loopback0
> > > ip address 170.100.51.3 255.255.255.0
> > > !
> > > interface Ethernet0
> > > ip address 10.0.136.1 255.255.255.0
> > > !
> > > interface Ethernet0.12
> > > !
> > > interface Serial0
> > > ip address 170.100.23.3 255.255.255.0
> > > encapsulation frame-relay
> > > no fair-queue
> > > frame-relay map ip 170.100.23.2 302 broadcast
> > > no frame-relay inverse-arp
> > > !
> > > interface Serial1
> > > no ip address
> > > shutdown
> > > !
> > > router rip
> > > passive-interface default
> > > no passive-interface Serial0
> > > network 170.100.0.0
> > > !
> > >
> > >
> > >
> >
> -------------------------------------------------------------------------
> > > FIGHT BACK AGAINST SPAM!
> > > Download Spam Inspector, the Award Winning Anti-Spam Filter
> > > http://mail.giantcompany.com
> > >
> > >
> > > -----Original Message-----
> > > From: John Matijevic [mailto:matijevi@bellsouth.net]
> > > Sent: Wednesday, July 09, 2003 10:26 AM
> > > To: Brian Dennis; 'Badger'
> > > Cc: 'Ram Shummoogum'; park@wams.com; ccielab@groupstudy.com
> > > Subject: Re: Gotcha on Redistribute Connected
> > >
> > > Jeongwoo,
> > > I am a little confused about which interfaces and ips are in what
protocol
> > > processes. I believe this may have been mentioned earlier, but could
you
> > > please post full configs so we can have a better idea of whats going
on.
> > > Sincerley,
> > > Matijevic
> > > ----- Original Message -----
> > > From: "Brian Dennis" <brian@labforge.com>
> > > To: "'Badger'" <badger@pongo.org>
> > > Cc: "'Ram Shummoogum'" <rshummoo@ca.ibm.com>; <park@wams.com>;
> > > <ccielab@groupstudy.com>
> > > Sent: Wednesday, July 09, 2003 1:15 PM
> > > Subject: RE: Gotcha on Redistribute Connected
> > >
> > >
> > > > How could adding the RIP interfaces to the route-map that is used
for
> > > > redistribute connected affect the requirements?
> > > >
> > > > Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> > > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> > > > Badger
> > > > Sent: Wednesday, July 09, 2003 9:55 AM
> > > > To: Brian Dennis
> > > > Cc: 'Ram Shummoogum'; park@wams.com; ccielab@groupstudy.com
> > > > Subject: RE: Gotcha on Redistribute Connected
> > > >
> > > > Hi Brian,
> > > >
> > > > I tried that too, but it seems that in a lab environtment that that
> > > > solution
> > > > would violate the rule of only placing an interface under the
routing
> > > > process
> > > > that is specified in the requirements...I grabbing straws here,
because
> > > > I'm
> > > > afraid of losing points on the exam for doig this.
> > > >
> > > >
> > > >
> > > > Quoting Brian Dennis <brian@labforge.com>:
> > > >
> > > > > It still happens in 12.3. The solution is of course to add the
> > > > > interfaces that are running RIP to the route-map that is used for
the
> > > > > redistribution of the connected routes.
> > > > >
> > > > > Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> > > > >
> > > > > -----Original Message-----
> > > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf
> > > > Of
> > > > > Badger
> > > > > Sent: Wednesday, July 09, 2003 9:14 AM
> > > > > To: Ram Shummoogum
> > > > > Cc: park@wams.com; ccielab@groupstudy.com
> > > > > Subject: Re: Gotcha on Redistribute Connected
> > > > >
> > > > > I posted a similar problem "Subject OSPF <-> EIGRP
redistribution."
> > > > > I'm
> > > > > experiencing this not only with rip/ospf, but also ospf/eigrp. I
have
> > > > > found a
> > > > > cause/reason/solution yet. I use 12.1.5(14)T and plan to just
flash
> > > > > 12.2x to
> > > > > see if it fixes the rpoblem.
> > > > >
> > > > >
> > > > > Quoting Ram Shummoogum <rshummoo@ca.ibm.com>:
> > > > >
> > > > > > I don't think you are tripping. I have been observing this too
in
> > > > few
> > > > > > ipexpert labs and I always keep any eye on this.
> > > > > >
> > > > > > RAM
> > > > > >
> > > > > >
> > > > > > Jeongwoo Park <jpark@wams.com>@groupstudy.com on 07/09/2003
11:28:26
> > > > > AM
> > > > > >
> > > > > > Please respond to Jeongwoo Park <jpark@wams.com>
> > > > > >
> > > > > > Sent by: nobody@groupstudy.com
> > > > > >
> > > > > >
> > > > > > To: lab <ccielab@groupstudy.com>
> > > > > > cc:
> > > > > > Subject: Gotcha on Redistribute Connected
> > > > > >
> > > > > >
> > > > > > Hi, all
> > > > > > Here is the layout where the "redistribute connected" got me.
> > > > > >
> > > > > > R1-----ospf------R2-lo 0
> > > > > > |
> > > > > > rip
> > > > > > |
> > > > > > R3
> > > > > >
> > > > > > What I did was that I redistributed the connected network
(loopback
> > > > > > network)
> > > > > > into ospf with route-map only for the loopback network like
this.
> > > > > > router ospf 1
> > > > > > router-id 2.2.2.2
> > > > > > log-adjacency-changes
> > > > > > summary-address 170.100.20.0 255.255.255.0
> > > > > > redistribute connected subnets route-map c2o
> > > > > > redistribute rip subnets
> > > > > > network 170.100.124.0 0.0.0.255 area 0
> > > > > > !
> > > > > > route-map c2o permit 10
> > > > > > match ip address 1
> > > > > > !
> > > > > > access-list 1 permit 170.100.20.0 0.0.0.7
> > > > > >
> > > > > > Now, I redistribute rip into ospf on R2.
> > > > > >
> > > > > > The problem is that R1 can't see the rip network.
> > > > > >
> > > > > > What I think is the gotcha is that when R2 redistribute
"Connected"
> > > > > with
> > > > > > route-map, it filtered the rip network, because the rip network
is
> > > > the
> > > > > > connected network as well from the R2's stand point.
> > > > > >
> > > > > > Am I saying right or I am tripping?
> > > > > >
> > > > > > Please let me know what I am doing wrong here.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > JP
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:32 GMT-3