Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Splitting DHCP scope

Status
Not open for further replies.

mojo31

IS-IT--Management
Aug 19, 2003
74
GB
I have all the eggs in one basket at the moment as far as DHCP goes, and want to split the scopes in a 50/50 manner. I know normally its 80/20....
Whats the easiest way to move a single scope and db from one server to another. Am I right in thinking that we set the same scope on both servers, and then set opposite exclusions on each server so they dish out different ranges of the scope?
My main concern is the effect this will have on machines which have a lease from a machine, then the address is now available on a different server. Or would it be easier to change the lease time? Obviously its out of hours task, but anyone been there and got the t shirt and have any ideas to pass along?

cheers
 
DHCP import/export tool will allow you to export all the settings (and the database) from 1 server and then import all this onto your 2ndary.

You can then exclude ranges however you feel is best (80/20 - 50/50).

Remember: Backups save jobs!!!
;-)
 
My answer assume DHCP is running on a Windows environment !!

Remember: Backups save jobs!!!
;-)
 
I used DHCPexim.exe to move the the database to a new server, but now wish to split the scopes onto 2 servers. We can use it to get the db to the new server again. But as I said i am concerned with leases that have been obtained from one server but then are moved to another, will it cause problems with clients renewing that lease?
 
As you have a copy of the current database the impact should be minimal.

We had a very short lease time running when we carried out our DHCP split (30 mins) so the leases were renewed quickly onto the 2ndary.

In essence all those workstations that can still talk to the original DHCP server (and are in the 'live' scope) will continue to lease ones from that server.
As the other workstations release and then find the new DHCP server there may be the chance of a duplicate, however there is a collision detection option which you can set.

If you can set the scope lease very low then the impact is limited to minutes and not days!

*if I'm wrong on any points then peeps please correct :)



Remember: Backups save jobs!!!
;-)
 
thanks techlad, that was what i had in mind as well- to set the scope to a low renew time. Either that or send a batch script out via sms with ipconfig /release, /renew.
Am interesetd in this collision detection option though. Where is that located and is it only available on w2k?
 
It is available in W2K, on checking an NT4 box the option appears to be greyed out so this option probably only applies to W2K...though I am not 100% sure...

The option is located under the properties of the server itself within DHCP manager (am using Windows XP tools to manage).


Remember: Backups save jobs!!!
;-)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top