Partner Down State
Glenn.Satchell at uniq.com.au
Tue Jun 6 10:27:40 UTC 2006
>Subject: Partner Down State
>Date: Mon, 5 Jun 2006 13:20:31 -0300
>From: "Kingston, Ken" <Ken.Kingston at aliant.ca>
>To: <dhcp-users at isc.org>
>I'm in the process of switching from the Sun Dhcp Server (lack of a
>particular functionality) to the ISC Dhcp server. I'm executing a
>serious of test cases. I cannot find a way to put my server into Partner
>Down State - I've tried omshell with some examples I've found but no
>luck. Anybody know how to do this (yes I've followed what documentation
>I could find). Also would appreciate any comments or experiences on
>performance and expected # of clients on a SUN 240.
There were some shell scripts posted on the list a while back that
purported to do this. I haven't looked at them in detail, but have a
plan to write a script taht will watch the partner dhcp server, and
switch to partner-down using omapi after a configurable delay, probably
There is lots of documentation, just not much on how to do specific
tasks. The omshell syntax to switch to partner down is not that
difficult but it is necessary to work it out. Man pages were never
really designed to be a procedural document but rather "here's all the
options". I assume you've looked at the omshell and omapi man pages?
As for the performance aspect, I look after a site with 3500 PCs and
4500 IP phones. They use two Sun Netra t1 servers (500MHz cpu, 256MB
ram) and they handle this number of clients as well as DNS without
going above a few percent CPU. I'd imagine your 240 could easily do 10
to 20 times that number of clients.
The load from a dhcp client is quite low, the main requirement
being how long the leases are. If leases are short then there
will be a correspondingly higher request rate to the server.
Long leases mean less work for the server. We run about 12 hours
for the PCs and 1 week for the phones.
More information about the dhcp-users