New IP Scheme for a client

Unanswered Question
Apr 22nd, 2010
User Badges:

To the Forum


I have been tasked with developing an efficient and summarizable IP address scheme for one of my clients. Within the scheme, I want to have efficient use of IP address space.


The clients current configuration is basically a hodge podge of different IP addresses and networks all thrown together.


There are 4 Main sites that the company uses.  My idea was to summarize at these 4 MPLS connections for all of the networks at each site.


I am attaching the spreadsheet I have developed and was hoping one of you with IP address design experience would evaluate my plan as it is layed out and let me know if this would work.


My main question centers around the /19 mask I am using at the main Site vs. the /20 and /21 masks I am using at the other sites.  Will the networks be routable based upon what I have layed out?


Please take a look and let me know


Thank You


Kevin



NEW
NET LOCATIONUSE
Glen Allen  /19 Block
192.168.0/19Glen Allen
192.168.0/24
192.168.1/24Servers - includes Servers, VM Hardware and FTP
192.168.2/24Firewall Transit
192.168.3/24SCADA A
192.168.4/24SCADA B
192.168.5/24SAN
192.168.6/24Loopbacks
192.168.7/24Users
192.168.8/24DMZ
192.168.9/24
192.168.10/24GA Frame
10.0-10.252/30'sMember Sites
192.168.11/24Wireless
192.168.12/24Diesel Generators
192.168.13/24
192.168.14/24ISDN
192.168.15/24WAN 
192.168.16 - 31/24Reserved for Future
Louisa  /20 Block
192.16832/20Louisa
192.168.32/24Servers - includes Servers, VM Hardware and FTP
192.168.33/24Users
192.168.34/24SAN
192.168.35/24LO Frame
35.0 - 35.252/30's
192.168.36/24WAN
192.168.37/24Transient Networks (Former 172.16.132.9/30, 172.16.132.3/29)
/27's
192.168.38/24Loopbacks
192.168.39/24SCADA A
192.168.40/24SCADA B
192.168.41 - 47/24Reserved for Future
Marsh Run  /20 Block
192.16848/21Marsh Run
192.168.48/24
192.168.49/24MPLS net
192.168.50/24SCADA
192.168.51/24Dominion Va Power
192.168.52/24PJM
192.168.53/24user
192.168.54/32loopbacks
192.168.55/24DMZ
192.168.56/24WiFi
192.168.57 - 63/24Reserved for Future
Rock Springs /20 Block
192.16864/21Rock Springs
192.168.64/24user
192.168.65/24SCADA
192.168.66/24DMZ
192.168.67/24WiFi
192.168.68/24
192.168.69/32Loopbacks
192.168.70-79/24Reserved for Future
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Giuseppe Larosa Thu, 04/22/2010 - 06:12
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Kevin,

your address plan and the summary routes are correct and should not create routing problems.


only note: if you dedicate a /24 block for Loopbacks you should indicate it as a /24, then as a note you can add that you will further subnet it using /32 as you did before for 192.168.10.0/24


Hope to help

Giuseppe

Kevin Melton Thu, 04/22/2010 - 07:44
User Badges:

thanks for the quick reply

Giuseppe


I am to pitch this to Management today.  I will let you know what they say.


Thanks

Kevin

Jon Marshall Thu, 04/22/2010 - 06:18
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Kevin


Looks fine. Key things to bear in mind when doing this sort of thing are -


1) always leave adequate room for growth within the address space for each site

2) loopbacks etc. used for management should still fall within the site allocated range(s)

3) always summarise as much as possible between sites.


With a new addressing scheme such as the one you are doing 1) + 3) means you should only have to advertise one IP block from each site.


Jon

Kevin Melton Wed, 06/09/2010 - 08:13
User Badges:

Jon


The client asked me to develop a Class B range for consideration in addtion to the formerly proposed Class C range.


I came up with the following and wanted you to look it over and make sure that it is summarizable at each route point (location - glen Allen, Louisa, Marsh Run, Rock Springs).


Thanks for your input.


Kevin



NEW
NET LOCATIONUSE
Glen Allen  /16 Block
172.16.0/16Glen Allen
172.16.0/24
172.16.1/24Servers - includes Servers, VM Hardware and FTP
172.16.2/24Firewall Transit
172.16.3/24SCADA A
172.16.4/24SCADA B
172.16.5/24SAN
172.16.6/24Loopbacks
172.16.7/24Users
172.16.8/24DMZ
172.16.9/24
172.16.10/24GA Frame
10.0-10.252/30'sMember Sites
172.16.11/24Wireless
172.16.12/24Diesel Generators
172.16.13/24
172.16.14/24ISDN
172.16.15/24WAN 
172.16.16/24VPN networks
/27's or /28's as necessary
17VPN networks
/27's or /28's as necessary
18-255Reserved for Future
Louisa  /16 Block
172.170/16Louisa
172.17.1/24Servers - includes Servers, VM Hardware and FTP
172.17.2/24Users
3/24Wireless
172.17.4/24SAN
172.17.5/24LO Frame
6/30's
172.17.7/24WAN
172.17.8/24Transient Networks (Former 172.16.132.9/30, 172.16.132.3/29)
9/27's
172.17.10/24Loopbacks
172.17.11/24SCADA A
172.17.12/24SCADA B
172.17.13/24VPN
172.17.14/24DMZ
172.17.15-255/24Reserved for Future
Marsh Run  /17 Block
172.180/17Marsh Run
172.18.1/24
172.18.2/24MPLS net
172.18.3/24SCADA
172.18.4/24Dominion Va Power
172.18.5/24PJM
172.18.6/24user
7/24Wireless
172.18.8/24loopbacks
172.18.9/24DMZ
172.18.10/24
172.18.11/24VPN - DAHS
172.18.12-127/24Reserved for Future
Rock Springs /17 Block
172.18128/17Rock Springs
172.18.129/24user
172.18.130/24SCADA
172.18.131/24DMZ
172.18.132/24Loopbacks
172.18.133-255/24Reserved for Future
RESERVED
172.19.1.0-172.31.254.255

Actions

This Discussion