New IP Scheme for a client

Kevin Melton · ‎04-22-2010

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			LOCATION	USE
Glen Allen /19 Block
192.168.	0	/19	Glen Allen
192.168.	0	/24
192.168.	1	/24		Servers - includes Servers, VM Hardware and FTP
192.168.	2	/24		Firewall Transit
192.168.	3	/24		SCADA A
192.168.	4	/24		SCADA B
192.168.	5	/24		SAN
192.168.	6	/24		Loopbacks
192.168.	7	/24		Users
192.168.	8	/24		DMZ
192.168.	9	/24
192.168.	10	/24		GA Frame
	10.0-10.252	/30's		Member Sites
192.168.	11	/24		Wireless
192.168.	12	/24		Diesel Generators
192.168.	13	/24
192.168.	14	/24		ISDN
192.168.	15	/24		WAN
192.168.	16 - 31	/24		Reserved for Future
Louisa /20 Block
192.168	32	/20	Louisa
192.168.	32	/24		Servers - includes Servers, VM Hardware and FTP
192.168.	33	/24		Users
192.168.	34	/24		SAN
192.168.	35	/24		LO Frame
	35.0 - 35.252	/30's
192.168.	36	/24		WAN
192.168.	37	/24		Transient Networks (Former 172.16.132.9/30, 172.16.132.3/29)
		/27's
192.168.	38	/24		Loopbacks
192.168.	39	/24		SCADA A
192.168.	40	/24		SCADA B
192.168.	41 - 47	/24		Reserved for Future
Marsh Run /20 Block
192.168	48	/21	Marsh Run
192.168.	48	/24
192.168.	49	/24		MPLS net
192.168.	50	/24		SCADA
192.168.	51	/24		Dominion Va Power
192.168.	52	/24		PJM
192.168.	53	/24		user
192.168.	54	/32		loopbacks
192.168.	55	/24		DMZ
192.168.	56	/24		WiFi
192.168.	57 - 63	/24		Reserved for Future
Rock Springs /20 Block
192.168	64	/21	Rock Springs
192.168.	64	/24		user
192.168.	65	/24		SCADA
192.168.	66	/24		DMZ
192.168.	67	/24		WiFi
192.168.	68	/24
192.168.	69	/32		Loopbacks
192.168.	70-79	/24		Reserved for Future

Giuseppe Larosa · ‎04-22-2010

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 · ‎04-22-2010

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 · ‎04-22-2010

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 · ‎04-22-2010

Thanks for your response Jon. Hope you are well.

Kevin

Kevin Melton · ‎06-09-2010

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			LOCATION	USE
Glen Allen /16 Block
172.16.	0	/16	Glen Allen
172.16.	0	/24
172.16.	1	/24		Servers - includes Servers, VM Hardware and FTP
172.16.	2	/24		Firewall Transit
172.16.	3	/24		SCADA A
172.16.	4	/24		SCADA B
172.16.	5	/24		SAN
172.16.	6	/24		Loopbacks
172.16.	7	/24		Users
172.16.	8	/24		DMZ
172.16.	9	/24
172.16.	10	/24		GA Frame
	10.0-10.252	/30's		Member Sites
172.16.	11	/24		Wireless
172.16.	12	/24		Diesel Generators
172.16.	13	/24
172.16.	14	/24		ISDN
172.16.	15	/24		WAN
172.16.	16	/24		VPN networks
		/27's or /28's as necessary
	17			VPN networks
		/27's or /28's as necessary
	18-255			Reserved for Future
Louisa /16 Block
172.17	0	/16	Louisa
172.17.	1	/24		Servers - includes Servers, VM Hardware and FTP
172.17.	2	/24		Users
	3	/24		Wireless
172.17.	4	/24		SAN
172.17.	5	/24		LO Frame
	6	/30's
172.17.	7	/24		WAN
172.17.	8	/24		Transient Networks (Former 172.16.132.9/30, 172.16.132.3/29)
	9	/27's
172.17.	10	/24		Loopbacks
172.17.	11	/24		SCADA A
172.17.	12	/24		SCADA B
172.17.	13	/24		VPN
172.17.	14	/24		DMZ
172.17.	15-255	/24		Reserved for Future
Marsh Run /17 Block
172.18	0	/17	Marsh Run
172.18.	1	/24
172.18.	2	/24		MPLS net
172.18.	3	/24		SCADA
172.18.	4	/24		Dominion Va Power
172.18.	5	/24		PJM
172.18.	6	/24		user
	7	/24		Wireless
172.18.	8	/24		loopbacks
172.18.	9	/24		DMZ
172.18.	10	/24
172.18.	11	/24		VPN - DAHS
172.18.	12-127	/24		Reserved for Future
Rock Springs /17 Block
172.18	128	/17	Rock Springs
172.18.	129	/24		user
172.18.	130	/24		SCADA
172.18.	131	/24		DMZ
172.18.	132	/24		Loopbacks
172.18.	133-255	/24		Reserved for Future


RESERVED
	172.19.1.0	-	172.31.254.255