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