OSPF router-id and IP addressing best practice ??

Hi,

I'm doing large enterprise network which includes new IP addressing
and OSPF as routing protocol. I took 10.0.0.0/8 for clients, servers
and other stuff in network and divided it hierarchically so that I can
do summarizing later on. My WAN connections are all metro ethernet L2.
For WAN IP addresses I took 192.168.0.0, simply for easier distinguish
between WAN IPs and other IPs. WAN addresses I will be able to
summarize. My dilemma is router loopback's IP addresses. I'm planning
to use 192.168.255.0, 192.168.254.0, 192.168.253.0, etc, for all
loopbacks in my network and those subnet will not be included in
summarization. Reason for that is also easier distinguishing so I know
that those subnets are my loopbacks.
At the end, one day, I could have almost 1200 routers in all OSPF
areas. Is it good idea to put loopbacks like that? I will have 1000
lines in routing table without summarization, just from loopbacks .
If I use loopback from C classes which can be summarized, I won't be
able to easly recognize loopbacks in my routing table. That loopbacks
will be management addresses and used for accessing and for mgmt
tools.
What is best practice for loopbacks globally in enterprise network?

Another question is about OSPF router id. Is it smart to assign router
ids like, lets say, 1.1.1.1, 5.5.5.5, since those addresses won't
exist in my network? Or, is it better to use Loopback IP address?

Thanks.

Blogs and organic groups at http://www.ccie.net
Received on Mon Aug 02 2010 - 16:50:59 ART