HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

b
bootpd(1M) bootpd(1M)
order.
IP addresses must be specified in standard Internet ‘‘dot’’ notation, and can use decimal, octal, or hexade-
cimal numbers (octal numbers begin with 0, hexadecimal numbers begin with
0x or 0X). Certain tags
accept a list of one or more
IP
addresses (ip_address_list). When more than one
IP address is listed, they
must be separated by white space.
The currently recognized keywords are:
dhcp_pool_group
This keyword is followed by tags defining a group of IP addresses to give out to clients on the
same subnet, and the characteristics of that group. In addition to the tags defined for DHCP
groups, all of the two-letter tags for bootp entries may also be used (except for
ht, the
hardware type tag,
ha, the hardware address tag, or
ci, the client ID tag. Required tags are:
subnet-mask , addr-pool-start-address
, and addr-pool-last-address
.
dhcp_device_group
This keyword is used to define a group of IP addresses on a subnet much like
dhcp_pool_group
, but with one exception: all clients in a device group must have the same
client class (specified with tag
class-id). This allows different types of clients to receive
different parameters from the server. Required tags are: class-id, subnet-mask ,
addr-pool-start-address
, and addr-pool-last-address.
dhcp_default_client_settings
This keyword is followed by tags to be applied to all groups. These tag values can be overridden
for a specific group if that tag is defined for that specific group. This keyword simply saves one
from entering the same tag for every group. Thus most tags that may be used for
dhcp_pool_group, and
dhcp_device_group, may be used here. The tag descriptions
specify if a tag may not be used here.
dhcp_server_settings
This keyword is followed by tags that specify a few general behaviors for the dhcp server as a
whole.
The currently supported tags for
dhcp_server_settings
:
dhcpdb-write-perf=
This parameter takes a small integer (like 2 or 5) as input. If set, the write to the
/etc/dhcpdb file will be delayed by the server. This will increase performance for busy
servers. If set to a value greater than 2, the server will spawn a new process to do the writing,
which will be a considerable performance improvement.
callback-style=old
|new
Callbacks are a powerful feature that allow the system administrator to customize the opera-
tion of the server. A user-supplied executable file (typically a shell script) is executed each time
one of the main server actions is performed (example: granting a lease). An argument list is
passed in with information about the individual client and the lease. The
callback-style=
tag specifies whether the old (and confusing) argument list should be used with the
call-
on-
xxx feature described below. The new (and recommended) argument list is much simpler to
use, and is identical for all of the call-on-xxx functions. The new style simply inserts a
value of "00" for fields that are not sensible for a particular callback. The new argument list is:
filename
: client-id htype haddr ipaddr subnet-mask lease-expiration hostname gateway
The old argument list is described for each of the individual callbacks below.
call-on-unrequited=filename
This tag specifies an executable file filename that will be called when the server receives a
request to which it cannot send a response. Certain arguments will be passed in; the call exe-
cuted will be:
filename: client-id htype haddr [gateway]
where client-id is the client ID in hex if present, or 00 if there is no client ID. htype is the
hardware type as per the ARP section of the "Assigned Numbers" RFC. haddr is the hardware
address in hex. gateway is the IP address of the bootp relay agent. If the packet was not
relayed, then this field is absent.
call-on-assignment=filename
This tag specifies the fully qualified filename to be called when an IP address has been assigned
Section 1M−−112 Hewlett-Packard Company − 7 − HP-UX 11i Version 1: September 2005