Need your help here!
We're in a process of designing a Network for one of our client and we need to come up with a Scalable IP addressing design.
Overview- The client has a HQ with 500 users and 5 other remote sites with 200 users each and 5 branch offices with 30 users each.
The plan is to use a 10.0.0.0 address range. Also, the HQ will have 40 IDF closets (we're planning 1 VLAN per IDF) and other VLANS like management, wireless, Voice, Server/Applications, Printers etc. The remote offices will have 5 IDF's each and some other vlans.
Question- How would you design and allocate IP addresses for each location to meet the above requirement with scalability in mind and to also be cognizant about not wasting too many IP's.
Any help will be greatly appreciated.
|Name||Hosts Needed||Hosts Available||Unused Hosts||Network Address||Slash||Mask||Usable Range||Broadcast||Wildcard|
|Host1||500||510||10||10.0.0.0||/23||255.255.254.0||10.0.0.1 - 10.0.1.254||10.0.1.255||0.0.1.255|
|Host2||200||254||54||10.0.2.0||/24||255.255.255.0||10.0.2.1 - 10.0.2.254||10.0.2.255||0.0.0.255|
|Host3||200||254||54||10.0.3.0||/24||255.255.255.0||10.0.3.1 - 10.0.3.254||10.0.3.255||0.0.0.255|
|Host4||200||254||54||10.0.4.0||/24||255.255.255.0||10.0.4.1 - 10.0.4.254||10.0.4.255||0.0.0.255|
|Host5||200||254||54||10.0.5.0||/24||255.255.255.0||10.0.5.1 - 10.0.5.254||10.0.5.255||0.0.0.255|
|Host6||200||254||54||10.0.6.0||/24||255.255.255.0||10.0.6.1 - 10.0.6.254||10.0.6.255||0.0.0.255|
vlan have another design depend on your requirements.
hope that helps
Please rate helpful posts
By no means do I consider myself an expert, so take my opinion for what it's worth ...
The first thing I'd ask myself here is "if I'm using a /8 of RFC 1918 space, why be so conservative?". Given your requirements, unless the client goes through some seriously massive growth you have an *enormous* pool of address space to spare that can never leave the confines of their network. I'm not advocating being blatantly wasteful with the space, but simplifying the design will make management easier in the long run.
I'd consider allocating a /22, or even a /21 per site from day one and just keep it simple. Each office gets broken in a standard way ... i.e. first two /24's for employee access, last /24 for infrastructure, and whatever else in between. I'd also pick a random base point to reduce the likelihood off colliding with any other networks that I may need to interconnect later. Plus, if there's already a couple spare /24's per office, I won't need to modify the WAN's routing tables if I need to light them up and use them (not that this is a big deal, but the WAN routing always stays simple too).
I've inherited networks that were carved into pieces as small as /29's and /28's using 1918 space and I could never understand why those before me would artificially constrain themselves ... not to mention cursing them as I try to expand things (renumbering is a PITA no matter how small the block).
I save the brain power for efficient design when I'm dealing with direct allocations where every address needs to count ... in this case, I'd probably lean towards simplicity and scalability vs efficiency. But, by all means, feel free to be efficient if that's what you prefer.
An Internet Protocol address (IP address) is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: host or network interface identification and location addressing.
Recommend: 352-001: CCDE Design Written Exam (CCDE)