First, some assumptions:
1. You are starting with a single /24 subnet of major network 10.0.0.0
(10.100.1.0/24) and creating 64 2-host subnets.
2. Since you are now variably subnetting, you must be using a classless
routing protocol supporting VLSM (OSPF, EIGRP, etc.).
3. This is for INTERNAL deployment (i.e., behind a NAT) or across private
circuits not directly accessing the internet.
These 2-host subnets are generally created to provision point-to-point
circuits like Frame Relay PVCs.
The general rule of thumb is to cluster your network numbers as
geographically (wierd looking word!) as possible to permit aggregation
/summarization. In other words, make the subnets contiguous.
If you are creating a hub and spoke cloud, these subnets would appear
contiguous at the hub, and spoke to spoke traffic would also see the cloud
as a contiguous block. If you are creating a full mesh arrangement the
interconnecting circuits are still contiguous within the cloud. In a
partial mesh, be careful to cluster the subnets into common regions so
summarization can be achieved. The issue is also how the other subnets are
disbursed. You want to keep the numbers as contiguous as possible. Your
sites may have the /24 subnets spread around as well so check to see that
connected sites reachable via a common path share contiguous networks if
possible.
All this contiguous-ness facilitates reducing the size of routing tables
(efficiency) and enhancing stability of the routing process via summarization.
I'm sure there are other issues not addressed here, but check around for
articles on VLSM and WAN design, maybe Caslow's book, or a BSCN or BCRAN
Study guide, etc., and look for other suggestions.
Hope this is helpful...
Dennis
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=9515&t=9509
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
