From: Dan Lockwood (dlockwood@shastalink.k12.ca.us)
Date: Wed Feb 12 2003 - 19:10:15 GMT-3
Hi David,
We use private addresses and translate them to public via several PIXs.
We use 10.0.0.0/8 and 66.244.0.0/18. Basically every one of our
"customers", divisions, etc, is given a /16 out of the 10.0.0.0/8. We
use OSPF exclusively as our IGP and the /16 that is provided also
corresponds to the area ID. For example, the administrative group is at
a physical site and is administratively autonomous and therefore is
given the address space 10.32.0.0/16. The area ID for this group would
be 32. Following are the rules that I use when addressing
infrastructure equipment for our customers.
Taking our example a bit further, all links connecting the
Administrative group to our NOCs are addressed using 10.254.32.x/30.
What this tells me immediately is that the link is connecting area 32 to
one of our NOCs. The low number is always on the NOC side and the high
number on the customer side. Numbering sequentially it also tells you
the number of circuits in service for a particular customer as well.
As far as the customer equipment is concerned, all circuits that connect
customer sites and services but do not connect to our NOCs are addressed
as follows: 10.32.254.128+/30. Again, this tells me immediately that
the a) the network is a circuit, and b) it resides within area 32. All
routers are given a /32 loopback address of 10.32.254.1/32,
10.32.254.2/32, etc. all the way up to 127.
Looking further at subnetting 10.32.0.0/16 the following rules apply: If
the customer has 10 additional sites, such as in an extended star
topology, we would subnet with a /20 and give each of the extended sites
one of the /20s. Addressing at those sites would begin with the low
network assigned strictly for infrastructure equipment, the second
assigned strictly for servers and the third, four, five, etc assigned
for hosts as needed. A VLAN is also setup for each of these subnets.
As an example, the primary site for the admin folks would be assigned
10.32.0.0/24 for infrastructure equipment, 10.32.1.0/24 for servers,
10.32.2.0/24 for workstations, 10.32.3.0/24 for workstations, etc. At
the first extended site the addressing would be 10.32.32.0/24,
10.32.33.0/24, 10.32.34.0/24, etc.
If you like I can send you some of our diagrams to help clarify why we
do things this way. When I took this job I was forced to clean up the
predecessor's mess and found this to be the best way. Using OSPF it is
easy to summarize routes and minimize LSA flooding. With a little
creative thinking you can make all other areas of your netowrk reachable
with just one route per area! :) Let me know if I can clarify any
details for you.
Dan
-----Original Message-----
From: David Porta [mailto:David.Porta003@msd.govt.nz]
Sent: Wednesday, February 12, 2003 12:01
To: cgs
Subject: IP addressing strategies
Hi everyone,
I was hoping some of you would share what your strategies are with
respect to IP addressing.
How your IP addressing scheme makes your diagrams more easily readable,
and your troubleshooting more effective and efficient. Also do you label
your telnet windows with IP addresses or host names?
Thanks in advance.
DP
-------------------------------
This email message and any attachment(s) is intended only for the
person(s) or entity(entities) to whom it is addressed. The
information it contains may be classified as IN CONFIDENCE and may be
legally privileged. If you are not the intended recipient any use,
disclosure or copying of the message or attachment(s) is strictly
prohibited. If you have received this message in error please
notify us immediately and destroy it and any attachment(s). Thank you.
The Ministry of Social Development accepts no responsibility for
changes made to this message or to any
attachment(s) after transmission from the Ministry.
-------------------------------
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:20 GMT-3