(PM) Ospf Area Range

Jason Hatch (zone@berkshire.net)
Tue, 27 Jan 1998 05:13:17 -0500 (EST)

ComOS 3.7.2, IRX-114 and PM2e30s

I basically have a simple network with several machines (including my
IRX-114, pm2e30's, sparc) interconnected via a switch. All machines'
ethernet interfaces are on network A, and I have dialups (four
portmasters worth) in network B, and some other larger subnets being used
in network C (A B and C are /24s).

I finally made the jump to OSPF, and everything seems to be running
smoothly. I realize my config probably isn't optimal, but it fixed my
problem with the kludged dialup configuration and problems with RIP
writing over dialup routes. I had a couple of questions about OSPF areas.

When carving out my sole area 0, I initially tried adding a range for
every network block (/24) that I have, about 12 or so. I was then reminded
about the limitation of 8 ranges, so, since I only needed it for my
dialups that were on a /24 other than my ethernet network, I created a
small area with 3 ranges: A (my ethernet), B (my dialups) and C (reserved
for large dialup customers who get subnets routed). I noticed that my IRX
ended up injecting its other routes (other /24's that I use for dedicated
customers and virtual hosts), basically passing my complete routing table
to all the portmasters, which is fine, but I was wondering how the
"range" keyword played into this, since it's injecting routes outside of
the 3 ranges I configed in. Do I really only need one range, with my
ethernet backbone address?

I also had a question about router priority. I configured my Internet
Router (IRX-114) with a priority of 10, and my pm2e's with a priority of
1. In "show ospf nei", it shows my IRX as the DR, and the rest as "Full"
(at one time, it showed my first portmaster as a BDR). Should I really be
setting the priority of my portmasters to 1, as if they go down, or if the
main router goes down, there is nothing they can really do to assume
responsibility for the eachother. Or am I missing something?

TIA

-Jason

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.