> > I know, I know... from time to time, someone asks here for help on OSPF.
> > Nevertheless, I don't think you can just point me to the FAQ
> and dismiss me
> > easily...
> > What is different here is:
> >
> > 1- E1 PRI, which means I can't just start recycle email about US setups;
>
> This is completely unimportant to configuring OSPF.
Well, yeah it wasn't very clear... what I really meant was, it's easier to
fit multiple 48 address ranges without trouble with .0 and .255... i.e the
usual setup starting from .16 for the first PM3 etc.
> The only address range that is important is the network that the devices
> that are talking OSPF to each other over. I think this is the
> 10.10.0.0/25 network in your example.
>
> add ospf area 0
> set ospf area 0 range 10.10.0.0/25
>
> And this is the only range entry you need.
OK.
> portions for commercial networks. But there is nothing at all wrong with
> the PM's spitting out a /27, /28, /29, and /30 for each assigned space.
> It doesn't take a lot of memory to store these and it only updates these
> very infrequently so it doesn't waste a lot of bandwidth either.
What I left out of the pictures are those customers with static IP, anything
from a /32 to a /28, which could connect to any of the PM3. They generate
more OSPF traffic. And then there are the dial-on-demand customers...
I will try to assess how much traffic is OPSF generating...
> You only want a range on the Livingstons for those interfaces that are
> talking OSPF. For the ciscos you need a range for every interface but you
> need to specify that the interface is passive if you are not talking OSPF
> to any device on it. You certainly don't need a range for address space
> that is not connected to that device. It will learn about it from those
> devices it is speaking OSPF with.
OK.
Thanks for your help!
Andrea
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>