Question Locked

Assigning IP Address ranges - is there a "Best Practices" document?

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I feel like I am trying to herd cats at work - I would really like to standardize how we assign IP addresses within DHCP and the subnets, but each administrator has his or her own "Best Practices" ideas about IP Address schemes - one person uses x.x.x.1 as the gateway/router, while another uses x.x.x.254, and yet another will use x.x.x.2. One administrator will use x.x.x.30 through x.x.x.100 as the DHCP range, while another will use x.x.x.100 through x.x.x.200 and so on. One administrator even used a range in the middle of his DHCP scope for switches, routers, and servers!

I want to do something like this:
x.x.x.1 = default gateway (assuming /24)
2-20 = network access devices
21-40 = server devices
41-60 = network peripherals (printers, etc.)
61-80 = reserved for special devices
81-100 = static addressed workstations
101-200 = standard DHCP pool of addresses
201-254 = VOIP devices (switch, adapters, etc.)

BUT ~ I can't convince everyone to do it the same way. They want to see a "Best Practices" document from an authoritative source, and I don't blame them, I do too. This has led into some heated but healthy discussions about ITIL and IT Service Management, areas in which I am still learning more.

Any feedback? Does such a document exist?

Thanks in advance!

7 replies

by fregeus

...and i doubt there is one. DHCP range assignment is very situation specific. Some networks don't have VioP devices, some don't have servers, some don't have printer or workstations.

I think your best bet is to get everyone involved in a conference room and hammer out your own standard.

TCB
edited for typos

by cg it

I don't think designing a network by IP address is considered SOP, though, it's a factor in design.

Also, assigning addresses isn't just a matter of wanting to be able to identify what host is what address.

There are many factors to use in the design process which effects what addresses to use. # of hosts needed. Security required, delegation of administration, any growth plans.

Besides, you will have to use MAC filtering in DHCP to ensure that hosts get the correct pool addresses. Not a monumental task but does tend to create more administrative effort when you retire older equipment, replace broken equipment, upgrade equipment, replace faulty NICs, blah blah blah.

by michael kassner

There are two schools of thought when it comes to this subject. There are those who like to compartmentalize the IP addrs and obviously those that do not.

The first approach is a great idea, but then you run into devices that do not fit into compartments and what do you do with them? There are other problems as well, what if you run out of IP addrs for a specific group?

I subscribe to the second approach for most of my clients and then immediately mention that they need to get a good inventory documentation application that will automatically provide all of the pertinent information about any given device.

Cisco has a great article about all of this and might be helpful to you.

http://www.cisco.com/en/US/tech/tk869/tk769/technologies_white_paper09186a008014f924.shtml#topic4

by wfairley

Thanks Michael! This Cisco document actually presents some "core" address assignments within subnets, such as suggested address assignments for gateways, special devices, and standard DHCP ranges, as well as naming conventions, etc. It is very helpful!

To put my request in context, I currently work for a small telecom company that occasionally gets a network consultant type sell for small firms in my city, predominantly law firms and doctor offices, with fewer than 20 people, so VLANs and subnetting are rarely necessary. By defining some standard practices regarding address ranges and assignments, we can improve our response times for outages, improve our documentation efficiency, even improve our install lead times and install process times.

This document takes me in the right direction, but I will continue my search, then publish my own "Best Practices" document in the TechRepublic forums and look for feedback.

Thanks again Michael!

-Woody

by michael kassner

Well, Cisco did all of the work. I would very much appreciate hearing about the final plan that you come up with. For the most part it is very specific to the situation being discussed, but I have never been led astray by Cisco.

by dumphrey

from a standards and procedures vector. Since this is mostly a pet peeve of yours, its your responsibility to show what financial, management, and security benefits are to be had by developing an internal standard.

This discussion is closed to new replies.