From: Scott F. Robohn (sfr@xxxxxxxx)
Date: Wed Apr 28 1999 - 22:20:41 GMT-3
Pamela,
Sorry for the vague initial description. Had to head out
for an appointment.
The RIP routes are not the concern here, it's the OSPF
routes from area 21. Here is some pretty bad line art to
talk to:
_________
| RIP |<192.168.100.0
| |<192.168.101.0
| fs | 172.30.0.0
| | | V 172.22.0.0 172.23.0.0
| ----- |-------- V V
| | ||OSPF | ------------ ---------------
---r11---|Area30| | r21 | | r31 r32 |
| | \ |vlink | | | \ | | | | |
| r12 r13------- | r22 r23 | | r33 r34 |
| / | | | | / | | | | / | | \ |
| | ----- | | | ----- | | | ------- | ------|
| | OSPF | | | OSPF | | | | | | OSPF |
| \ Area21| | | Area22| | | r35 r36 | Area23|
---\-------- --|--------- --|---------/--------
\ ^172.21.0.0 | | /
\-----------<<<<<<<FRAME SWITCH>>>>>>>
Area0: 192.168.15.0/24
The external RIP routes are 192.168.100.0/24 and
192.168.101.0/24.
Area 0 consists of Serial (encap frame relay) interfaces on
r12, r22, r33, and r34. r12, r22, and r34 use
point-to-point subinterfaces, while r33 uses a
point-to-multi subinterface. All subinterfaces are using
'ip ospf net point-to-multipoint'.
The intent here is to have each non-0 area advertise a
summary of 172.X.0.0/16, where X is the area number. Each
area has a handful of variably-subnetted subnets of the
corresponding major network. Area 22 is totally stubby, so
it sees no E2 routes. Area 21 internal routers see
summaries for 172.22.0.0/16 and 172.23.0.0/16, but area 23
internal routers see all the O-IA subnets of 172.21.0.0/16.
Each ABR has the appropriate 'area X range 172.X.0.0
255.255.0.0' statement.
I can send configs if you'd like. This isn't a
show-stopper, I just wondered if this is something simple
I'm missing, or if this is how it's intended to operate.
Any thoughts?
Thanks,
Scott
Pamela Forsyth wrote:
>
> Scott,
>
> It isn't really clear from your description (and my hasty reading of it,
> sorry) whether it's the RIP subnets you're trying to summarize. If it is,
> try the "summary-address" command instead of "area range" for external
> routes. ;-)
>
> Pamela
>
> On Wed, 28 Apr 1999, Scott F. Robohn wrote:
>
> > OK, here's a quickie: I have an OPSF area (21) with a single
> > ABR and the 'area 21 range 172.21.0.0 255.255.0.0' command.
> > Area 21 has a RIP process hanging off of it, as well as area
> > 30 that has a virtual link to the backbone area.
> >
> > Area 23 sees all of area 21's subnets, even though I'm using
> > the range command to advertise a summary out of area 21.
> > Area 23 has 2 ABRs connecting it two the backbone, both of
> > which are using the 'area 23 range 172.23.0.0 255.255.0.0'
> > command to summarize out of this area. Area 21 sees area
> > 23's summary, as expected.
> >
> > This must be something simple; any thoughts?
> >
> > BTW, there is also an area 22 and it's totally stubby.
> >
> > Thanks,
> > Scott
> >
> > --
> > >>Scott F. Robohn, CCNA, FLCE............sfr@ccci.com<<
> > >>Chesapeake Computer Consultants, Inc...703-623-3752<<
> >
-- >>Scott F. Robohn, CCNA, FLCE............sfr@ccci.com<< >>Chesapeake Computer Consultants, Inc...703-623-3752<<
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:36 GMT-3