Re: Load testing a DHCP server

A few recommendations:

Error-check object creation and method calls
Use Net::Address::Ethernet to get MAC address
Try /sbin/pump , or /sbin/dhclient to release/renew DHCP-assigned address (Not familiar with these - I would use "ipconfig/release /renew" on Win32)

I think you are using the wrong approach to justify improving the server. A 386 will work fine to serve DHCP to ~250 client machines - maybe more, depending on lease time.

You should approach this more from the angle of RELIABILITY of an aging machine.

Earth first! (We'll rob the other planets later)

Comment on Re: Load testing a DHCP server

Replies are listed 'Best First'.
Re^2: Load testing a DHCP server by waswas-fng (Curate) on Nov 05, 2004 at 20:29 UTC
Sorry but a 386 with ISC dhcpd with a > 2 day lease can support normal load on way over 8k leases. If a power outage happens and you have all clients hitting at the same relative time it just takes a little longer to feed all of the requests. I would still upgrade and replace the hardware with newer supported hardware and setup failover pools on more than one server -- no need to have all your eggs in a basket. -Waswas	[reply]

Replies are listed 'Best First'.

Re^2: Load testing a DHCP server
by waswas-fng (Curate) on Nov 05, 2004 at 20:29 UTC

-Waswas

[reply]