dhcp_modules(5)

1dhcp_modules(5)       Standards, Environments, and Macros      dhcp_modules(5)
2
3
4

NAME

6       dhcp_modules - data storage modules for the DHCP service
7

DESCRIPTION

9       This  man  page  describes  the characteristics of data storage modules
10       (public modules) for use by the Solaris Dynamic Host Configuration Pro‐
11       tocol (DHCP) service.
12
13
14       Public  modules  are  the  part  of  the DHCP service architecture that
15       encapsulate the details of storing DHCP service data in a data  storage
16       service.  Examples  of  data storage services are NIS+, Oracle, and ufs
17       file systems.
18
19
20       Public modules are dynamic objects which can be shipped separately from
21       the Solaris DHCP service. Once installed, a public module is visible to
22       the DHCP service, and can be selected for use by  the  service  through
23       the  DHCP  service  management interfaces (dhcpmgr(1M), dhcpconfig(1M),
24       dhtadm(1M), and pntadm(1M)).
25
26
27       Public modules may be provided by Sun Microsystems,  Inc  or  by  third
28       parties.
29
30
31       The  Solaris  DHCP service management architecture provides a mechanism
32       for plugging in  public  module-specific  administration  functionality
33       into  the  dhcpmgr(1M) and dhcpconfig(1M) utilities. This functionality
34       is in the form of a Java Bean, which is provided by the  public  module
35       vendor.  This  Java  Bean collects public module-specific configuration
36       from the user (you) and provides it to the Solaris DHCP service.
37
38
39       The Solaris DHCP service bundles three modules with the service,  which
40       are  described below. There are three dhcpsvc.conf(4) DHCP service con‐
41       figuration parameters pertaining to public modules: RESOURCE, PATH, and
42       RESOURCE_CONFIG.  See  dhcpsvc.conf(4) for more information about these
43       parameters.
44
45   SUNWfiles
46       This module stores its data in ASCII  files.  Although  the  format  is
47       ASCII, hand-editing is discouraged. It is useful for DHCP service envi‐
48       ronments that support several hundred to a couple thousand  of  clients
49       and lease times are a few hours or more.
50
51
52       This  module's  data may be shared between DHCP servers through the use
53       of NFS.
54
55   SUNWbinfiles
56       This module stores its data in binary files. It is useful for DHCP ser‐
57       vice  environments  with  many  networks and many thousands of clients.
58       This module provides an order of magnitude increase in performance  and
59       capacity over SUNWfiles.
60
61
62       This module's data cannot be shared between DHCP servers.
63
64   SUNWnisplus
65       This module stores its data within a NIS+ domain. It is useful in envi‐
66       ronments where NIS+ is already deployed and facilitates  sharing  among
67       multiple  DHCP  servers.  This  module suports several hundred to a few
68       thousand clients with lease times of several hours or more.
69
70
71       The NIS+ service should be hosted on a machine with  ample  CPU  power,
72       memory,  and  disk space, as the load on NIS+ is significant when it is
73       used to store DHCP data. Periodic checkpointing of the NIS+ service  is
74       necessary  in order to roll the transaction logs and keep the NIS+ ser‐
75       vice  operating  at  its  highest  efficiency.  See   nisping(1M)   and
76       crontab(1) for more information.
77

NAME

DESCRIPTION

SEE ALSO