From: mcaplan.cs@xxxxxxxxxxxxxxx
Date: Fri May 04 2001 - 12:03:33 GMT-3
Raymond,
well I wasn't too serious about the 10.10.0.0 subnet, but the 10.3.0.0
subnet did have me baffled.
10.3.1.1/16 is configured on R3, and is part of area 0 ie
R3
router ospf 1
network 10.3.1.1 0.0.0.0 area 0
Is that they key ? Maybe 'redis conn sub' will only inject E2 routes related
to interfaces in a different area, or interfaces with no OSPF process
running on them ? Any references to this on CCO ? I cant find any.
Thanks for your attention
Mark
> ----------
> From: rsevier[SMTP:rsevier@zealousolutions.com]
> Sent: Freitag, 4. Mai 2001 17:02
> To: mcaplan.cs@clearstream.com; lkidd@netstarnetworks.com;
> ccielab@groupstudy.com
> Subject: RE: ccbootcamp lab 2
>
> Mark- I see what you are saying now. R1 and R3 share the network
> 10.10.0.0
> so it can't be an E2 route to R1 becuase it is directly connected. As for
> the 10.3.0.0, is there a routing process associated with that interface?
> That was my question when I did that lab.
>
> Raymond
>
> -----Original Message-----
> From: mcaplan.cs@clearstream.com [mailto:mcaplan.cs@clearstream.com]
> Sent: Friday, May 04, 2001 7:32 AM
> To: lkidd@netstarnetworks.com; mcaplan.cs@clearstream.com;
> ccielab@groupstudy.com; rsevier@zealousolutions.com
> Subject: RE: ccbootcamp lab 2
>
>
> Raymond,
>
> Yes, but my observation (and the routes shown in the answers from Marc's
> labs) show that some of the connected interfaces are redistributed as E2
> and
> some are not.
>
> R3----frame PVC-----R1
>
> This is from CCbootcamp lab 2 as a reminder
>
> Look at the routing table of R3 below:
>
> Gateway of last resort is 173.168.40.2 to network 0.0.0.0
>
> B 4.0.0.0/8 [200/0] via 173.168.40.2, 01:17:23
> 173.168.0.0/24 is subnetted, 1 subnets
> C 173.168.40.0 is directly connected, Serial1
> 10.0.0.0/8 is variably subnetted, 8 subnets, 3 masks
> O 10.10.1.1/32 [110/64] via 10.10.1.1, 02:03:35, Serial0
> C 10.10.0.0/16 is directly connected, Serial0
> O 10.10.1.5/32 [110/128] via 10.10.1.1, 02:03:35, Serial0
> C 10.3.0.0/16 is directly connected, TokenRing0
> O IA 10.1.0.0/16 [110/74] via 10.10.1.1, 02:03:35, Serial0
> O E1 10.20.0.0/16 [110/84] via 10.10.1.1, 02:03:35, Serial0
> C 10.33.2.0/24 is directly connected, Loopback1
> C 10.33.1.0/24 is directly connected, Loopback0
> 11.0.0.0/16 is subnetted, 1 subnets
> O 11.1.0.0 [110/138] via 10.10.1.1, 02:03:36, Serial0
> B 12.0.0.0/8 [20/0] via 10.10.1.1, 00:27:56
> B 41.0.0.0/8 [200/0] via 173.168.40.2, 01:17:26
> 44.0.0.0/24 is subnetted, 1 subnets
> B 44.1.1.0 [200/0] via 173.168.40.2, 01:17:26
> 137.20.0.0/24 is subnetted, 1 subnets
> O E1 137.20.20.0 [110/84] via 10.10.1.1, 02:03:37, Serial0
> B 177.1.0.0/16 [20/0] via 10.10.1.1, 00:27:56
> S* 0.0.0.0/0 [1/0] via 173.168.40.2
>
> There are 5 connected interfaces. The command 'redist connec subnet' on R3
> produces the following routing table on R1
>
> Gateway of last resort is 10.10.1.3 to network 0.0.0.0
>
> B 4.0.0.0/8 [20/0] via 10.10.1.3, 01:11:21
> 173.168.0.0/24 is subnetted, 1 subnets
> O E2 173.168.40.0 [110/20] via 10.10.1.3, 01:39:03, Serial0.2
> 10.0.0.0/8 is variably subnetted, 9 subnets, 3 masks
> C 10.10.0.0/16 is directly connected, Serial0.2
> O 10.10.1.3/32 [110/64] via 10.10.1.3, 02:00:39, Serial0.2
> O 10.10.1.5/32 [110/64] via 10.10.1.5, 02:00:39, Serial0.2
> O 10.3.0.0/16 [110/70] via 10.10.1.3, 02:00:39, Serial0.2
> C 10.1.0.0/16 is directly connected, Ethernet0
> C 10.20.0.0/16 is directly connected, Serial0.1
> O E2 10.33.2.0/24 [110/20] via 10.10.1.3, 01:39:04, Serial0.2
> O E2 10.33.1.0/24 [110/20] via 10.10.1.3, 01:39:04, Serial0.2
> O IA 10.33.0.0/16 [110/65] via 10.10.1.3, 02:00:40, Serial0.2
> 11.0.0.0/16 is subnetted, 1 subnets
> O 11.1.0.0 [110/74] via 10.10.1.5, 02:00:41, Serial0.2
> B 12.0.0.0/8 [200/0] via 11.1.1.6, 00:26:13
> B 41.0.0.0/8 [20/0] via 10.10.1.3, 01:11:23
> 44.0.0.0/24 is subnetted, 1 subnets
> B 44.1.1.0 [20/0] via 10.10.1.3, 01:11:23
> C 192.168.1.0/24 is directly connected, Loopback0
> 137.20.0.0/24 is subnetted, 1 subnets
> D 137.20.20.0 [90/2195456] via 10.20.1.1, 02:00:41, Serial0.1
> B 177.1.0.0/16 [200/0] via 11.1.1.6, 00:26:13
> O*E1 0.0.0.0/0 [110/564] via 10.10.1.3, 02:00:41, Serial0.2
>
>
> As you can see there are only 3 E2 routes. What about the other 2:
> ie 10.10.0.0/16 and 10.3.0.0/16 .
>
> Regards
>
> Mark
>
>
> > ----------
> > From: rsevier[SMTP:rsevier@zealousolutions.com]
> > Sent: Freitag, 4. Mai 2001 16:20
> > To: Lachlan Kidd; mcaplan.cs@clearstream.com;
> ccielab@groupstudy.com
> > Subject: RE: ccbootcamp lab 2
> >
> > Mark- You can use a route map to redistribute only the connected
> > interfaces
> > that you wish:
> >
> > redistribute connected subnets route-map muther
> >
> > access-list 1 permit 173.168.40.0 0.0.0.255
> > route-map muther permit 10
> > match ip address 1
> >
> > and Lachlan is right about it redistributing everything that is showing
> up
> > as connected in the route table.
> >
> > Raymond
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Lachlan Kidd
> > Sent: Thursday, May 03, 2001 1:53 AM
> > To: mcaplan.cs@clearstream.com; ccielab@groupstudy.com
> > Subject: RE: ccbootcamp lab 2
> >
> >
> > Hi Mark,
> > I think the answer goes something like this. The 'redistribute'
> > command
> > only works on what is in the route table. If you redistribute IGRP
> routes
> > then anything with an I next to it will get redistributed. The same
> > applies
> > to connected routes. If it's in the route table with a 'C' next to it,
> it
> > will get redistributed regardless of what protocol is running on that
> > interface. HTH, feel free to let me know if I've missed the point
> > completely.
> > Regards,
> > Lachlan
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > mcaplan.cs@clearstream.com
> > Sent: Thursday, 3 May 2001 6:12:PM
> > To: ccielab@groupstudy.com
> > Subject: FW: ccbootcamp lab 2
> >
> >
> > Has anybody got any advice with respect to this one - see thread below:
> >
> > The fundamental question is :
> >
> > Does 'redistribute connected subnets' put E2 routes into OSPF even for
> > interfaces that are part of the OSPF process ?
> >
> > Thanks
> >
> > Mark
> >
> > > ----------
> > > From: TCN CAPLAN Mark - Service Provider
> > > Sent: Mittwoch, 2. Mai 2001 16:11
> > > To: 'ccielab@groupstudy.com'
> > > Subject: ccbootcamp lab 2
> > >
> > > Hi,
> > >
> > > I've got a question about Marc's bootcamp lab2.
> > >
> > > The routing table for R1 shows two subnets advertised as E2 routes
> plus
> > > the summary:
> > >
> > > O E2 10.33.2.0/24 [110/20] via 10.10.1.3, 00:00:01, Serial0.2
> > > O E2 10.33.1.0/24 [110/20] via 10.10.1.3, 00:00:01, Serial0.2
> > > O IA 10.33.0.0/16 [110/65] via 10.10.1.3, 00:00:02, Serial0.2
> > >
> > > Now the IA route comes from the 'area 3 range 10.33.0.0 255.255.0.0'
> > > statement on R3. And the E2 routes evidently come from the
> 'redistribute
> > > connected subnets' command on R3.
> > >
> > > I dont really understand why the E2 routes are there. The loopback
> > > interfaces concerned are in Area3 and part of the OSPF process. Its
> not
> > as
> > > if the other connected interfaces are redistributed as E2 eg
> 10.3.1.1/16
> > > which is part of Area 0. So why these 2 subnets ? My understanding was
> > > that 'redistribute connected subnets' would only redistribute subnets
> on
> > > connected interfaces if they weren't part of the OSPF process. But the
> > > evidence shows otherwise. Is the rule that it redistributes any
> > interfaces
> > > in a different area as E2 aswell.
> > >
> > > Any help would be appreciated
> > >
> > > Thanks
> > >
> > > Mark
> > >
> >
> >
> > Visit us at http://www.clearstream.com
> > Check out current job vacancies at
> > http://www.clearstream.com/public/english/e_vacs.htm
> >
> > IMPORTANT MESSAGE
> >
> > Internet communications are not secure and therefore Clearstream
> > International does not
> > accept legal responsibility for the contents of this message.
> >
> > The information contained in this e-mail is confidential and may be
> > legally
> > privileged. It is
> > intended solely for the addressee. If you are not the intended
> recipient,
> > any disclosure,
> > copying, distribution or any action taken or omitted to be taken in
> > reliance
> > on it, is
> > prohibited and may be unlawful. Any views expressed in this e-mail are
> > those
> > of the
> > individual sender, except where the sender specifically states them to
> be
> > the views of
> > Clearstream International or of any of its affiliates or subsidiaries.
> >
> > END OF DISCLAIMER
> > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:33 GMT-3