Question

Locked

Does anybody have an IP Addressing Procedure or Policy?

By ant_bfaog ·
Hi All, I've been tasked to develop a procedure with regards to the management of assigning IP addresses on end-user machines. We assign static IP addresses to end-user machines. When we get conflicts we are at a loss. My question is how do you layout the process of assigning of new IP's, modify IP's, removing IP's, and handling IP conflicts.

Thanks
Anthony

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Request for Clarification

by Spitfire_Sysop In reply to Clarifications

Why are you doing this?

Collapse -

Depends

by cmiller5400 In reply to Does anybody have an IP A ...

You can use a spreadsheet or database for this, but this depends on everyone using and updating it (a "policy" that it must be followed to make sure that it is done).

You may also want to consider using DHCP and using reservations to control addresses. That way IP addresses are controlled in one place.

Just some food for thought.

Collapse -

Probably need more info

by IcebergTitanic In reply to Does anybody have an IP A ...

In a domain environment, it is usually handled on the domain controller. DHCP hands out addresses, and the workstations are authorized to update their record in DNS.

DHCP will handle all the problems with IP conflicts, removing unused IPs, etc. It is also used to hand out other information such as default gateway and DNS servers. Otherwise, if you change one of those, you have to go to EVERY workstation and update their config.

Frankly, if they're paying you even minimum wage, it would quickly become more cost-effective for them to buy some variety of server that does nothing more than DHCP.

=P

Generally speaking, I tend to do a couple things...

If you have the luxury of using a 16-bit netmask (255.255.0.0) you can use the 3rd octet to signify a group of devices, and the 4th to designate the individual devices.

Example:
192.168.0.xxx for network infrastructure like switches and routers
192.168.1.xxx for Servers
192.168.2.xxx for Printers
192.168.10.xxx through 192.168.15.xxx for workstations

Alternately, you can just decide on particular ranges in a subnet for use:

192.168.0.1 through 192.168.0.10 for network infrastructure
192.168.0.11 through 192.168.0.29 for Printers
192.168.0.200 through 192.168.0.254 for Servers
192.168.0.30 through 192.168.0.199 for Workstations

Personally, I prefer using a combination of DHCP with the first method. DHCP hands out the workstation IPs, and then you statically assign the Servers, Switches/Routers, and Printer groups.

Collapse -

IP settings

by Charles Bundy In reply to Does anybody have an IP A ...

First I would recommend using DHCP in conjunction with static IP addressing. Use DHCP for workstations if at all possible. Then breakout your static portion of addresses into printers, managed devices, servers. A while back I wrote a PHP/MySQL web DB which allowed central management of network devices. It was ok but I found a better system for managing assets. Check out OCSng at http://www.ocsinventory-ng.org/en/.

Back to IT Employment Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums