1 <!--
   2   --
   3     CDDL HEADER START
   4 
   5     The contents of this file are subject to the terms of the
   6     Common Development and Distribution License (the "License").
   7     You may not use this file except in compliance with the License.
   8 
   9     You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
  10     or http://www.opensolaris.org/os/licensing.
  11     See the License for the specific language governing permissions
  12     and limitations under the License.
  13 
  14     When distributing Covered Code, include this CDDL HEADER in each
  15     file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  16     If applicable, add the following below this CDDL HEADER, with the
  17     fields enclosed by brackets "[]" replaced with your own identifying
  18     information: Portions Copyright [yyyy] [name of copyright owner]
  19 
  20     CDDL HEADER END
  21 
  22  -- Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
  23  -- Use is subject to license terms.
  24   -->
  25 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  26 <html>
  27 
  28 <head>
  29 <title>DHCP Manager Help: Configuring DHCP Server</title>
  30 <meta NAME="AUTHOR" CONTENT="smorgan">
  31 <meta NAME="KEYWORDS" CONTENT="DHCP">
  32 
  33 </head>
  34 
  35 <body bgcolor="#ffffff">
  36 
  37 <a name="top"></a>
  38 
  39 <table border=0 cellspacing=0 cellpadding=0 width=625>
  40 
  41 
  42 <!-- Start navigation banner -->
  43 
  44 <tr><td colspan=4  WIDTH="615" align="left" valign="top"><IMG SRC="art/bannersmc.gif" WIDTH=615 BORDER=0 ALT="DHCP Manager Help">
  45 
  46         </td>
  47         </tr>
  48 
  49 <!-- End navigation banner -->
  50 
  51 
  52 <tr>
  53 
  54 <!-- Start contents block -->
  55 
  56         <td colspan=1 valign="top" WIDTH="105">
  57         <P>&nbsp;</P>
  58         <STRONG><A HREF="dhcp_main_top.html">Overview</A></STRONG><P>
  59         <STRONG><A HREF="dhcp_relay_ref.html">Servers and Relays</A></STRONG><BR>
  60         <IMG SRC="art/tip2.gif" WIDTH=12 HEIGHT=10 BORDER=0 ALT="">DHCP Config<BR>
  61         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#store"><EM>Data Store</EM></A><BR>
  62    &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#hostnmserv"><EM>Hosts Name Service</EM></A><BR>
  63         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#lease"><EM>Lease Policy</EM></A><BR>
  64         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#dns"><EM>DNS Domain/Server</EM></A><BR>
  65         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#net"><EM>Network</EM></A><BR>
  66         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#router"><EM>Router</EM></A><BR>
  67         &nbsp;&nbsp;&nbsp;&nbsp;<A HREF="#nis"><EM>NIS</EM></A><BR>
  68         &nbsp;&nbsp;<A HREF="dhcp_relay_config.html">Relay Config</A><BR>
  69         &nbsp;&nbsp;<A HREF="dhcp_net_wiz.html">Network Config</A><BR>
  70         &nbsp;&nbsp;<A HREF="dhcp_server_serv.html">DHCP Services</A><BR>
  71         &nbsp;&nbsp;<A HREF="dhcp_relay_serv.html">Relay Services</A><P>
  72         <A HREF="dhcp_addr_ref.html"><STRONG>Addresses</STRONG></A><P>
  73         <A HREF="dhcp_macro_ref.html"><STRONG>Macros</STRONG></A><P>
  74         <A HREF="dhcp_option_ref.html"><STRONG>Options</STRONG></A><P>            
  75         <A HREF="dhcp_main_how.html"><STRONG>How To..</STRONG></A><P>
  76         <A HREF="dhcp_main_menus.html"><STRONG>Menus</STRONG></A><P>
  77 <A HREF="dhcp_main_idx.html"><STRONG>Index</STRONG></A>
  78         
  79                 </td>
  80         
  81 <!-- End contents block -->
  82 
  83 <!-- Start column rule -->
  84 
  85         <td colspan=1 width=5 bgcolor="#CCCCCC">&nbsp;</td>
  86 
  87 <!-- End column spacer -->
  88 
  89 <!-- Start column spacer -->
  90 
  91         <td colspan=1 width=10 bgcolor="#FFFFFF">&nbsp;</td>
  92 
  93 <!-- End column spacer -->
  94 
  95 
  96 
  97 <!-- Start topic block -->
  98 
  99 <td colspan=1 valign="top" bgcolor="#ffffff" width="495">
 100 <P>&nbsp;</P>
 101 
 102 
 103 <H1>DHCP Configuration Wizard</H1>
 104 
 105 The DHCP Configuration Wizard helps you configure a Solaris<small><sup>TM</sup></small>
 106 system to be a DHCP server and configures the first network.  <P>
 107 <TABLE WIDTH="500" BORDER="1" CELLSPACING="2" CELLPADDING="2" VALIGN="TOP" BORDERCOLOR="#CCCCCC" BGCOLOR="#DEDEDE">
 108 <TR>
 109 <TD><STRONG>Note: </STRONG>Please read the "Planning for DHCP Service" chapter in the Solaris <em>DHCP Administration Guide, </em> before configuring a DHCP server.  
 110 </TD></TR>
 111 </TABLE>
 112 <P>
 113 After initial configuration, use the Modify option in the <A HREF="dhcp_server_serv.html">Services</A>
 114 menu to configure services such as BOOTP compatibility, duplicate address detection,
 115 and which interfaces to monitor.<P>
 116 To enter information in the wizard, double-click in the field, enter the desired value, and then press Enter.<P>
 117 The DHCP Configuration Wizard, asks you to supply the following information.
 118 <P><HR NOSHADE><P>
 119 
 120 <table border=0 cellspacing=4 cellpadding=3 width=490>
 121         <tr>
 122         <td width=125 valign="top"><A NAME="store"><STRONG>Data Store </STRONG></A><br>
 123         </td>
 124         <td valign="top">Select the type of data store the DHCP server will use to 
 125         store configuration data. The choices are:
 126 
 127 <table cellspacing=3 cellpadding=3>
 128                 <tr>
 129                 <td width=90 valign="top"><em>Text files</em></td>
 130                 <td valign="top">Data is stored in clear text ASCII files. Suitable for small number of clients, up to 10,000. Data can be shared through NFS among several DHCP servers.</td>
 131                 </tr>
 132 <tr>
 133                 <td width=90 valign="top"><em>Binary files</em></td>
 134                 <td valign="top">Data is stored in binary text files. Suitable for large numbers of clients up to 100,000. Data can <em>not</em> be shared among several DHCP servers. </td>
 135                 </tr>
 136 </table>
 137 </td>
 138 </tr>
 139 <!-- end data store row -->
 140         <tr>
 141         <td width=125 valign="top"><A NAME="lease"><STRONG>Lease Policy</STRONG></A><br>
 142         </td>
 143         <td valign="top">Enter the length of time before a lease expires. 
 144         The lease is the amount of time a DHCP server grants
 145         permission to a DHCP client to use a particular address. 
 146         You can enter from 1 hour to 3550 weeks. <P>
 147         The lease time value should be relatively small, so that expired addresses
 148 are reclaimed quickly, but large enough so that if your DHCP service becomes
 149 unavailable, the clients continue to function until the machine(s) running
 150 the DHCP service can be repaired.  A rule of thumb is to specify a time that
 151 is two times the predicted down time of a server. For example, if it generally
 152 takes four hours to obtain and replace a defective part and reboot the server,
 153 you should specify a lease time of eight hours. <P> 
 154         The default is to allow a client to renegotiate the lease before it expires.
 155         A Solaris DHCP client will try to renew the lease when it is halfway
 156         through the lease period. <P> 
 157         If not allowed to renegotiate, clients must issue a new DHCP request 
 158     in order to obtain a
 159         new address when the lease expires. You may choose this option
 160         in an environment where there are more clients than there are
 161         addresses, and you need to enforce a time limit on the use of an IP
 162         address.  
 163         </td> 
 164         </tr>
 165         
 166         <tr>
 167         <td width=125 valign="top"><A NAME="dns"><STRONG>DNS Domain</STRONG></A></td>
 168         <td valign="top">The domain server resolves host names to host 
 169         addresses. If the server is configured to use DNS, the domain name and address 
 170         of the DNS server will be displayed.
 171         If the fields are empty, you can enter the domain name and address of a
 172         DNS domain server. <p>
 173         You can enter the address of more than one server. The order in the list 
 174         determines the order in which the servers are queried.
 175         </td>     
 176 
 177         </tr>
 178         <TR><TD COLSPAN="2">&nbsp;&nbsp;&nbsp;<A HREF="#top"><small>return to top</small></A></TD></TR>
 179 
 180         </table>
 181 
 182 <HR noshade size=2>
 183         
 184 
 185 <strong><A NAME="net"><big>Network Configuration</big></A></STRONG><P>
 186 This section begins the network configuration.
 187 You can configure the first network using the DHCP Configuration Wizard. Once
 188 the DHCP server is configured, you can add additional networks using the Network Wizard, which is available from the Edit menu, when the Address view is displayed.<P>
 189 
 190         <table border=0 cellspacing=4 cellpadding=3 width=490>
 191         <tr>
 192         <td width=125 valign="top"><A NAME="addr"><STRONG>Network Address</STRONG></A></td>
 193         <td valign="top">
 194         Enter the IP address of the network you are configuring.<p>
 195         </td>
 196         </tr>
 197         
 198                 <tr>
 199         <td width=125 valign="top"><A NAME="info"><STRONG>Subnet Mask</STRONG></A><br></td>
 200         <td valign="top">
 201                 Enter the subnet mask for this network. A subnet mask is a way of dividing 
 202         up the host portion of an Internet address to form local subnetworks.
 203         </TD></TR>
 204 
 205         <tr>
 206         <td width=125 valign="top"><A NAME="info"><STRONG>Network Type</STRONG></A><br></td>
 207         <td valign="top">
 208         Specify whether the network is a local area network (LAN) or point-to-point (PPP).<p>
 209 
 210 
 211         </TD>
 212         </tr>
 213 
 214         <tr>
 215         <td width=125 valign="top"><A NAME="router"><STRONG>Routing</STRONG></A></td>
 216         <td valign="top">A router is a machine with multiple network 
 217         interfaces that can forward IP packets from one network to
 218         another. In most cases, your clients should use router discovery to 
 219         connect to a router. If you have clients in your network that cannot 
 220         use router discovery, enter the IP address of a router which
 221         they can use to communicate with systems on another network.
 222         </td>
 223         </tr>
 224 
 225         
 226         <tr>
 227         <td width=125 valign="top"><A NAME="nis"><STRONG>NIS Domain Name</STRONG></A><br>
 228         <STRONG>NIS Server Address</STRONG></td>
 229         <td valign="top">If the server is configured to use NIS naming service, 
 230         the NIS server information will be filled in.  If not, you can enter the domain 
 231         name and IP address of one or more NIS name servers.<P>
 232 
 233         The order in which the address appears in the list determines the order in
 234         which the servers are queried.
 235         </td> 
 236         </tr>
 237 
 238 </table>
 239 &nbsp;&nbsp;&nbsp;<A HREF="#top"><small>return to top</small></A>
 240 
 241 
 242 
 243 <p>&nbsp;</p>
 244 
 245 
 246 <!-- Don't go past this line! -->
 247 
 248         </td>
 249 
 250 <!-- End topic block -->
 251 
 252 </tr>
 253 
 254 </table>
 255 
 256 <!-- End topic table -->
 257 
 258 </body>
 259 </html>