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> </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 <A HREF="#store"><EM>Data Store</EM></A><BR> 62 <A HREF="#dspath"><EM>Path</EM></A><BR> 63 <A HREF="#hostnmserv"><EM>Hosts Name Service</EM></A><BR> 64 <A HREF="#lease"><EM>Lease Policy</EM></A><BR> 65 <A HREF="#dns"><EM>DNS Domain/Server</EM></A><BR> 66 <A HREF="#net"><EM>Network</EM></A><BR> 67 <A HREF="#router"><EM>Router</EM></A><BR> 68 <A HREF="#nis"><EM>NIS</EM></A><BR> 69 <A HREF="dhcp_relay_config.html">Relay Config</A><BR> 70 <A HREF="dhcp_net_wiz.html">Network Config</A><BR> 71 <A HREF="dhcp_server_serv.html">DHCP Services</A><BR> 72 <A HREF="dhcp_relay_serv.html">Relay Services</A><P> 73 <A HREF="dhcp_addr_ref.html"><STRONG>Addresses</STRONG></A><P> 74 <A HREF="dhcp_macro_ref.html"><STRONG>Macros</STRONG></A><P> 75 <A HREF="dhcp_option_ref.html"><STRONG>Options</STRONG></A><P> 76 <A HREF="dhcp_main_how.html"><STRONG>How To..</STRONG></A><P> 77 <A HREF="dhcp_main_menus.html"><STRONG>Menus</STRONG></A><P> 78<A HREF="dhcp_main_idx.html"><STRONG>Index</STRONG></A> 79 80 </td> 81 82<!-- End contents block --> 83 84<!-- Start column rule --> 85 86 <td colspan=1 width=5 bgcolor="#CCCCCC"> </td> 87 88<!-- End column spacer --> 89 90<!-- Start column spacer --> 91 92 <td colspan=1 width=10 bgcolor="#FFFFFF"> </td> 93 94<!-- End column spacer --> 95 96 97 98<!-- Start topic block --> 99 100<td colspan=1 valign="top" bgcolor="#ffffff" width="495"> 101<P> </P> 102 103 104<H1>DHCP Configuration Wizard</H1> 105 106The DHCP Configuration Wizard helps you configure a Solaris<small><sup>TM</sup></small> 107system to be a DHCP server and configures the first network. <P> 108<TABLE WIDTH="500" BORDER="1" CELLSPACING="2" CELLPADDING="2" VALIGN="TOP" BORDERCOLOR="#CCCCCC" BGCOLOR="#DEDEDE"> 109<TR> 110<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. 111</TD></TR> 112</TABLE> 113<P> 114After initial configuration, use the Modify option in the <A HREF="dhcp_server_serv.html">Services</A> 115menu to configure services such as BOOTP compatibility, duplicate address detection, 116and which interfaces to monitor.<P> 117To enter information in the wizard, double-click in the field, enter the desired value, and then press Enter.<P> 118The DHCP Configuration Wizard, asks you to supply the following information. 119<P><HR NOSHADE><P> 120 121<table border=0 cellspacing=4 cellpadding=3 width=490> 122 <tr> 123 <td width=125 valign="top"><A NAME="store"><STRONG>Data Store </STRONG></A><br> 124 </td> 125 <td valign="top">Select the type of data store the DHCP server will use to 126 store configuration data. The choices are: 127 128<table cellspacing=3 cellpadding=3> 129 <tr> 130 <td width=90 valign="top"><em>Text files</em></td> 131 <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> 132 </tr> 133<tr> 134 <td width=90 valign="top"><em>Binary files</em></td> 135 <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> 136 </tr> 137</table> 138</td> 139</tr> 140<!-- end data store row --> 141 <tr> 142<td width=125 valign="top"><A NAME="dspath"><STRONG>Data store path</STRONG></A><br> 143</td> 144<td>If you chose text files or binary files as your data store, enter the path to the 145 data (default=<tt>/var/dhcp</tt>).<p> 146 <P> </td></tr> 147 148 149<tr> 150 <td width=125 valign="top"><A NAME="hostnmserv"><STRONG>Hosts name service</STRONG></A><br> 151 </td> 152 <td valign="top">Select the name service that the DHCP server should use to register host names associated with IP addresses that it allocates to clients. 153 <table cellspacing=3 cellpadding=3> 154 <tr> 155 <td width=90 valign="top"><em>Do not manage hosts records</em></td> 156 <td valign="top">The DHCP server will not attempt to add host name entries to any name service. An administrator should add the names manually to a name service. </td> 157 </tr> 158<tr> 159 <td width=90 valign="top"><em>/etc/hosts</em></td> 160 <td valign="top">The DHCP server will add host name entries to the servers /etc/hosts table. </td> 161 </tr> 162<tr> 163 <td width=90 valign="top"><em>DNS</em></td> 164 <td valign="top">The DHCP server will add host name entries to DNS if the DHCP daemon and DNS daemon are running on the same system. You must supply the DNS domain name. </td> 165 </tr> 166</table> 167 168 </td> 169 </tr> 170<!-- End of Hosts name service row --> 171 <tr> 172 <td width=125 valign="top"><A NAME="lease"><STRONG>Lease Policy</STRONG></A><br> 173 </td> 174 <td valign="top">Enter the length of time before a lease expires. 175 The lease is the amount of time a DHCP server grants 176 permission to a DHCP client to use a particular address. 177 You can enter from 1 hour to 3550 weeks. <P> 178 The lease time value should be relatively small, so that expired addresses 179are reclaimed quickly, but large enough so that if your DHCP service becomes 180unavailable, the clients continue to function until the machine(s) running 181the DHCP service can be repaired. A rule of thumb is to specify a time that 182is two times the predicted down time of a server. For example, if it generally 183takes four hours to obtain and replace a defective part and reboot the server, 184you should specify a lease time of eight hours. <P> 185 The default is to allow a client to renegotiate the lease before it expires. 186 A Solaris DHCP client will try to renew the lease when it is halfway 187 through the lease period. <P> 188 If not allowed to renegotiate, clients must issue a new DHCP request 189 in order to obtain a 190 new address when the lease expires. You may choose this option 191 in an environment where there are more clients than there are 192 addresses, and you need to enforce a time limit on the use of an IP 193 address. 194 </td> 195 </tr> 196 197 <tr> 198 <td width=125 valign="top"><A NAME="dns"><STRONG>DNS Domain</STRONG></A></td> 199 <td valign="top">The domain server resolves host names to host 200 addresses. If the server is configured to use DNS, the domain name and address 201 of the DNS server will be displayed. 202 If the fields are empty, you can enter the domain name and address of a 203 DNS domain server. <p> 204 You can enter the address of more than one server. The order in the list 205 determines the order in which the servers are queried. 206 </td> 207 208 </tr> 209 <TR><TD COLSPAN="2"> <A HREF="#top"><small>return to top</small></A></TD></TR> 210 211 </table> 212 213<HR noshade size=2> 214 215 216<strong><A NAME="net"><big>Network Configuration</big></A></STRONG><P> 217This section begins the network configuration. 218You can configure the first network using the DHCP Configuration Wizard. Once 219the 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> 220 221 <table border=0 cellspacing=4 cellpadding=3 width=490> 222 <tr> 223 <td width=125 valign="top"><A NAME="addr"><STRONG>Network Address</STRONG></A></td> 224 <td valign="top"> 225 Enter the IP address of the network you are configuring.<p> 226 </td> 227 </tr> 228 229 <tr> 230 <td width=125 valign="top"><A NAME="info"><STRONG>Subnet Mask</STRONG></A><br></td> 231 <td valign="top"> 232 Enter the subnet mask for this network. A subnet mask is a way of dividing 233 up the host portion of an Internet address to form local subnetworks. 234 </TD></TR> 235 236 <tr> 237 <td width=125 valign="top"><A NAME="info"><STRONG>Network Type</STRONG></A><br></td> 238 <td valign="top"> 239 Specify whether the network is a local area network (LAN) or point-to-point (PPP).<p> 240 241 242 </TD> 243 </tr> 244 245 <tr> 246 <td width=125 valign="top"><A NAME="router"><STRONG>Routing</STRONG></A></td> 247 <td valign="top">A router is a machine with multiple network 248 interfaces that can forward IP packets from one network to 249 another. In most cases, your clients should use router discovery to 250 connect to a router. If you have clients in your network that cannot 251 use router discovery, enter the IP address of a router which 252 they can use to communicate with systems on another network. 253 </td> 254 </tr> 255 256 257 <tr> 258 <td width=125 valign="top"><A NAME="nis"><STRONG>NIS Domain Name</STRONG></A><br> 259 <STRONG>NIS Server Address</STRONG></td> 260 <td valign="top">If the server is configured to use NIS naming service, 261 the NIS server information will be filled in. If not, you can enter the domain 262 name and IP address of one or more NIS name servers.<P> 263 264 The order in which the address appears in the list determines the order in 265 which the servers are queried. 266 </td> 267 </tr> 268 269</table> 270 <A HREF="#top"><small>return to top</small></A> 271 272 273 274<p> </p> 275 276 277<!-- Don't go past this line! --> 278 279 </td> 280 281<!-- End topic block --> 282 283</tr> 284 285</table> 286 287<!-- End topic table --> 288 289</body> 290</html> 291
