IP Allocation Plan

Ip schema is the heart of any organisation. If ip schema is not maintained then it can come up with the massive problem in future. I faced a problem during allocation of ip schema. So I decided to revamp the schema with future scalability. Currently for an ISP network we are allocating a /16 pool for a particular region and a summary is being originated for that pool. But have you ever think about that what will be happened if that network will expand exponentially. Definitely you will answer that’s why we reserve the /16 pool for that region. But as per me instead of allocating a /16 pool further divide the pool into multiples of small pool of /22. It means /22 will cover approx 64 number of subnets. Now divide the main region into logically four regions and assign the /22 pool to each region. In future down the line if the region routers need to be increased and a aggregation point is required in that time we need to change the area instead of changing the whole ip schema. This will bring the scalability and future expansion of ip addresses. A summary router of /22 will be originated from that aggregation point.
So the new schema would like cite below:-
Main Pool
10.0.0.0/8
Pool divided into smaller pools
10.1.0.0/16
10.2.0.0/16
10.3.0.0/16
10.4.0.0/16
::::::::::::::::
::::::::::::::::
10.255.0.0/16

-----------------------------------------------------------------------------------
Further divide the /16 pool to multiple logical pools of /22
10.1.0.0/16
-------------------------
10.1.1.0/24
to
10.1.63.0/24
Summary route will look like 10.1.1.0/22

10.1.64.0/24
to
10.1.127.0/24
Summary route will look like 10.1.64.0/22

10.1.128.0/24
to
10.1.191.0/24
Summary route will look like 10.1.128.0/22

10.1.192.0/24
to
10.1.255.0/24
Summary route will look like 10.1.192.0/22

Regards
shivlu jain

People who read this post also read :