1 '\" te
   2 .\" Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved.
   3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6 .TH DHCP_MODULES 5 "Jan 24, 2003"
   7 .SH NAME
   8 dhcp_modules \- data storage modules for the DHCP service
   9 .SH DESCRIPTION
  10 .sp
  11 .LP
  12 This man page describes the characteristics of data storage modules (public
  13 modules) for use by the Solaris Dynamic Host Configuration Protocol
  14 (\fBDHCP\fR) service.
  15 .sp
  16 .LP
  17 Public modules are the part of the \fBDHCP\fR service architecture that
  18 encapsulate the details of storing \fBDHCP\fR service data in a data storage
  19 service. Examples of data storage services are \fBNIS+\fR, Oracle, and
  20 \fBufs\fR file systems.
  21 .sp
  22 .LP
  23 Public modules are dynamic objects which can be shipped separately from the
  24 Solaris \fBDHCP\fR service. Once installed, a public module is visible to the
  25 \fBDHCP\fR service, and can be selected for use by the service through the
  26 \fBDHCP\fR service management interfaces (\fBdhcpmgr\fR(1M),
  27 \fBdhcpconfig\fR(1M), \fBdhtadm\fR(1M), and \fBpntadm\fR(1M)).
  28 .sp
  29 .LP
  30 Public modules may be provided by Sun Microsystems, Inc or by third parties.
  31 .sp
  32 .LP
  33 The Solaris \fBDHCP\fR service management architecture provides a mechanism for
  34 plugging in public module-specific administration functionality into the
  35 \fBdhcpmgr\fR(1M) and \fBdhcpconfig\fR(1M) utilities. This functionality is in
  36 the form of a Java Bean, which is provided by the public module vendor. This
  37 Java Bean collects public module-specific configuration from the user (you) and
  38 provides it to the Solaris \fBDHCP\fR service.
  39 .sp
  40 .LP
  41 The Solaris \fBDHCP\fR service bundles three modules with the service, which
  42 are described below. There are three \fBdhcpsvc.conf\fR(4) \fBDHCP\fR service
  43 configuration parameters pertaining to public modules: \fBRESOURCE\fR,
  44 \fBPATH\fR, and \fBRESOURCE_CONFIG\fR. See \fBdhcpsvc.conf\fR(4) for more
  45 information about these parameters.
  46 .SS "SUNWfiles"
  47 .sp
  48 .LP
  49 This module stores its data in \fBASCII\fR files. Although the format is
  50 \fBASCII\fR, hand-editing is discouraged. It is useful for \fBDHCP\fR service
  51 environments that support several hundred to a couple thousand of clients and
  52 lease times are a few hours or more.
  53 .sp
  54 .LP
  55 This module's data may be shared between \fBDHCP\fR servers through the use of
  56 \fBNFS\fR.
  57 .SS "SUNWbinfiles"
  58 .sp
  59 .LP
  60 This module stores its data in binary files. It is useful for \fBDHCP\fR
  61 service environments with many networks and many thousands of clients. This
  62 module provides an order of magnitude increase in performance and capacity over
  63 SUNWfiles.
  64 .sp
  65 .LP
  66 This module's data cannot be shared between \fBDHCP\fR servers.
  67 .SS "SUNWnisplus"
  68 .sp
  69 .LP
  70 This module stores its data within a \fBNIS+\fR domain. It is useful in
  71 environments where \fBNIS+\fR is already deployed and facilitates sharing among
  72 multiple \fBDHCP\fR servers. This module suports several hundred to a few
  73 thousand clients with lease times of several hours or more.
  74 .sp
  75 .LP
  76 The \fBNIS+\fR service should be hosted on a machine with ample \fBCPU\fR
  77 power, memory, and disk space, as the load on \fBNIS+\fR is significant when it
  78 is used to store \fBDHCP\fR data. Periodic checkpointing of the \fBNIS+\fR
  79 service is necessary in order to roll the transaction logs and keep the
  80 \fBNIS+\fR service operating at its highest efficiency. See \fBnisping\fR(1M)
  81 and \fBcrontab\fR(1) for more information.
  82 .SH SEE ALSO
  83 .sp
  84 .LP
  85 \fBcrontab\fR(1), \fBdhcpconfig\fR(1M), \fBdhcpmgr\fR(1M), \fBdhtadm\fR(1M),
  86 \fBnisping\fR(1M), \fBpntadm\fR(1M), \fBdhcpsvc.conf\fR(4), \fBdhcp\fR(5)
  87 .sp
  88 .LP
  89 \fISolaris DHCP Service Developer\&'s Guide\fR