On Wed, 23 Jul 1997, Kelley Lingerfelt wrote:
>
> Here is our network, I would like, and think we need to do OSPF,but I am
> just too stupid to pull it off. Somebody care to suggest how they would
> program this, so I could at least have a starting point and maybe I will
> see the light. :)
>
> Remote Pop
> Pool xxx.yyy.243.97
> Internet Ser0+-------------+Ser1 T1 +-------------+
> <---------------+ Cisco 2501 +-------------+ PM-3A-2T +----PRI1
> +------+------+ +-----+-------+
> |.12 | Ether0
> | xxx.yyy.243.129
> |
> PRI1 PRI2 | PRI3 PRI4
> | | | +--+----+--+
> +-+-------+--+ | | PM-3A-2T |
> | PM-3A-2T | | +----+-----+
> +-------+----+ | |.5
> |.4 | Network xxx.yyy.242 |
> -----+--+-------------+------------+-----------------+--> Clients,
> |.8 |.2 WWW,NS,Mail,
> +-----+------+ +-----+-----------+ News,Radius
> | OR-HS | | PM-2E (Only using ISDN)
> +-----+------+ +--+----+------+--+
> |T1 |.1 |.33 |.65
> | <--------+ | | uuu.vvv.89.64/27
> +-----+------+ Full Class C Net | +--(DialUp 64K ISDN)--->
> | OR-HS | uuu.vvv.88 | uuu.vvv.89.32/27
> +-----+------+ Dedicated 128K ISDN +--(DialUp 64K ISDN)--->
> |.1
> |
> | Full Class C Net uuu.vvv.90
> +--------------------------
> Small ISP w/128K Bandwidth
> and DialUps on a PM2E
>
>
For ease of reading, your /24 (class C) networks are:
xxx.yyy.242.0/24 - "core" backbone for www,ns,etc, and some PM3s,
PM2s,OR-HSes
xxx.yyy.243.0/24 - remote pop and remote backbone
uuu.vvv.88.0/24 - completely given to ISDN-based client ISP
uuu.vvv.89.0/24 - broken into /27 subnets for dialup ISDN clients
uuu.vvv.90.0/24 - completely given to T1-based client ISP
The above network topology you have looks ok. You've probably decided
that xxx.yyy.242.0/24 is your backbone network and have assigned almost
all your equipment's IPs from there. But I noticed that your remote
POP's IP address is assigned from the xxx.yyy.243.0/24 network. This
would mean that you'll have to define 2 OSPF areas, and have the
cisco 2501 be the area border router (ABR). You might want to consider
changing that PM3's IP to be part of your core 242 network. It will still
be able to handle traffic for the 243 network. That way, you'll only need
to define 1 ospf area.
On CISCO:
--------
conf term
router ospf 101
network xxx.yyy.242.0 00.0.255 area 0
area 0 authentication (optional but strongly recommended)
network xxx.yyy.243.0 00.0.255 area 1
area 1 authentication (optional but strongly recommended)
redistribute rip (up to you, depending also on whether or not your
upstream needs to know your local routing info)
exit
interface eth 0
ip ospf authentication-key (yoursecret)
ip ospf priority 10
exit
interface ser 1
ip ospf authentication-key (yoursecret)
ip ospf priority 10
exit
copy run start
reboot
On all PMs except the one at your Remote POP:
--------------------------------------------
set ospf enable
save all
reboot
set opsf priority 1
add ospf area 0
set ospf area 0 range xxx.yyy.242.0/24 advertise
set ospf area 0 range uuu.vvv.89.0/24 advertise
set ospf area 0 range uuu.vvv.90.0/24 advertise
set ether0 ospf on
set ospf area 0 password (yoursecret)
On your Remote POP:
------------------
set ospf enable
save all
reboot
set opsf priority 1
add ospf area 1
set ospf area 1 range xxx.yyy.243.0/24 advertise
set ether0 ospf on
set ospf area 1 password (yoursecret)
Assuming you've set up your radius entries or location tables with proper
routes, the routing info should propagate properly then. You should
probably also use "show ospf area", "sho ospf nei", "sho route"
on your PMs, and "show ip route", and "show ip ospf" on your Cisco to
verify everything.
> We will be adding another PM3, on the local net, xxx.yyy.242 and will
soon
> be adding more modems and another PRI line to the PM3 at the Remote Pop,
> and therefore will be adding another router to replace the PM3 w24 on
> line1 as the router. We have a customer that wants a subnet off the PM3
> dialup at the remote location, so we will have to deal with that also.
Shouldn't be a problem.
> I really need to get the dialup 64K ISDNs on to the PM3s, so we can drop
> the ISDN lines that are coming in, if we need more dedicated ISDNs we
> can use the PM2E for that purpose.
Shouldn't be a problem. With OSPF, even though the subnet is different
from whichever the NAS is on, routing information will still propagate.
> I would attempt it, but sure as sh*t I would hose the whole network.
Bound to happen sometime :)
> Would make a good How-To, because I am sure there are very similar
> setups to this all over the place.
Well, hope that works for you. There's no warranties though :)
Good Luck,
Leonard.