Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Configuring Solaris DHCP Server

News

DHCP Protocol

Solaris books Recommended Links DHCP Client Selected Solaris man pages Reference Solaris DHCP Server
dhcpsvc.conf dhcpconfig Utility pntadm Utility dhtadm Utility dhcp_network File DHCP security Humor Etc

Solaris has separate daemons for DHCP client ( dhcpagent ) and DHCP server (in.dhcpd ).

Solaris DHCP  daemon is started automatically during  bootup if file /etc/dhcp.interface  exists for at lest one interface  Only interfaces  with a corresponding  /etc/dhcp.interface file are automatically configured during boot.

Like DNS there can be primary and secondary DHCP servers but secondary DHCP servers are not a requirement and they are not that common.  Primary and secondary DHCP servers must have access to the exact same data. Copies cannot be used. This can be achieved by via NIS and NFS.  Both run in.dhcpd daemon:

There are two alterative ways (command line based and GUI-based) to configure DHCP servers (and BOOTP relay servers):

Both utilities permit setting of startup options, configure the DHCP service database type (binary or text) and location, as well as initialize the dhcptab and dhcp_network tables for the DHCP zone that the server controls.

/etc/inet/dhcpsvc.conf File

The /etc/inet/dhcpsvc.conf file contains configuration information and typically is populated using utilities that we mentioned above, although nothing prevents you for editing it manually. It the configuration file is not present, then the server does not run DHCP daemon. The content is a typical Unix-style configuration file with keyword-value pairs:

cat /etc/inet/dhcpsvc.conf

DAEMON_ENABLED=TRUE
RUN_MODE=server
RESOURCE=SUNWfiles
PATH=/var/dhcp
CONVER=1
VERBOSE=TRUE
ICMP_VERIFY=TRUE
INTERFACES=hme0,qfe0
UPDATE_TIMEOUT=15
LOGGING_FACILITY=7
BOOTP_COMPAT=automatic
 

dhcpconfig Utility

Use the dhcpconfig utility can:

The initial configuration is performed by command:

/usr/sbin/dhcpconfig -D -r datastore -p location

where:

The dhcpconfig utility uses the appropriate system and network files, such as hosts, netmasks, and so on, on the DHCP server to determine values that are not provided on the command line.

Configuration is done in two steps:

First we need to provide type of storage and path to DHCP tables: 

/usr/sbin/dhcpconfig -D -r SUNWfiles -p /var/dhcp
Created DHCP configuration file.
Created dhcptab.
Added "Locale" macro to dhcptab.
Added server macro to dhcptab - mydhcpsrv
DHCP server started.

Second we specify IP range for which DHCP services should be performed.  For example:

/usr/sbin/dhcpconfig -N 10.10.1.0 -t 10.10.1.1
Added network macro to dhcptab - 10.10.1.0.
Created network table.

Here we configured the system to provide DHCP services for the network 10.10.1.0/24  (option -N) with the router 10.10.1.1 (option -t). As a result the dhcp_network file will be created.

dhcp_network File

A separate dhcp_network file exists for each network that is served by the DHCP server. It contains the range of IP addresses that the DHCP server assigns (DHCP zone). The file  also maps the associated configuration parameters for each IP address assigned to the clients.

Each dhcp_network file is named using the IP address of the network it supports with the either SUNWbinfiles prefix (binary files format) or SUNWfiles prefix (text files format). For example, SUNWfiles1_10_10_1_0 is a text format file for network 10.10.1.0/24. You can view it using command:

cat SUNWfiles1_10_10_1_0 command

pntadm Utility

 The pntadm utility performs three main functions: :

Options include: 

Typical operations:

  1. To create a table for the 10.10.10.0 network, perform the command: pntadm -C 10.10.10.0

    To verify that the network table was created, perform the command: ls /var/dhcp | grep 10.10.10

    Note – You can use an alias name for this network in place of the network number if the alias is defined in the networks(4) file.
     

  2. To view the initial contents of the new table, or iew the changes using the table, perform the command: cat  /var/dhcp/SUNWfiles1_10_10_10_0
     
  3. To add an entry to the SUNWfiles1_10.10.10.0 table located in the /var/dhcp directory, perform the command:

    pntadm -r SUNWfiles -p /var/dhcp -A 10.10.10.1 10.10.10.0

  4. To modify the 10.10.10.1 entry of the SUNWfiles1_10.10.10.0 table, change the macro name (-m) to mymacro, and set the flags field to MANUAL and PERMANENT, perform the command:

    pntadm -M 10.10.10.1 -m mymacro -f ’PERMANENT+MANUAL’ 10.10.10.0
     

  5. To change the 10.10.10.1 entry to 10.10.10.2 (-n), perform the command: pntadm -M 10.10.10.1 -n 10.10.10.2 10.10.10.0 To verify the changes, perform the command: pntadm -P 10.10.10.0
     
  6. To delete the 10.10.10.2 entry from the 10.10.10.0 table, perform the command: pntadm -D 10.10.10.2 10.10.10.0 To verify the changes, perform the command: pntadm -P 10.10.10.0
     
  7. To list the existing DHCP tables, perform the command: pntadm -L

To view the table and observe the changes made by the pntadm command, perform the command:

cat /var/dhcp/SUNWfiles1_10_10_10_0
# SUNWfiles1_10_10_10_0
#
# Do NOT edit this file by hand -- use pntadm(1M) or dhcpmgr(1M) instead
10.10.10.1|00|00|10.10.1.1|0|8214847195300495361|UNKNOWN|

To view the changes, again use  pntadm -P 10.10.10.0

Notes:

dhtadm Utility

Use the dhtadm utility to manage the DHCP service configuration table,  dhcptab. You can specify one of the following option flags:

Lease Policy

A lease specifies the amount of time the DHCP server grants permission to a DHCP client to use a particular IP address. During the initial server configuration, you must specify a site-wide lease policy, indicating the lease time and whether clients can renew their leases. The server uses the information you supply to set option values in the default macros it creates during configuration. You can set different lease policies for specific clients or type of clients, by setting options in configuration macros you create.

The lease time is specified as a number of hours, days, or weeks for which the lease is valid. When a client is assigned an IP address (or renegotiates a lease on an IP address it is already assigned), the lease expiration date and time is calculated by adding the number of hours in the lease time to the timestamp on the client’s DHCP acknowledgment. For example, if the timestamp of the DHCP acknowledgment is September 16, 1999 9:15 A.M., and the lease time is 24 hours, the lease expiration time is September 17, 1999 9:15 A.M.

The lease expiration time is stored in the client’s DHCP network record, viewable in the DHCP Manager or using pntadm .

The lease time value should be relatively small, so that expired addresses are reclaimed quickly, but large enough so that if your DHCP service becomes unavailable, the clients continue to function until the machine(s) running the DHCP service can be repaired. A rule of thumb is to specify a time that is two times the predicted down time of a server. For example, if it generally takes four hours to obtain and replace a defective part and reboot the server, you should specify a lease time of eight hours.

The lease negotiation option determines whether or not a client can renegotiate its lease with the server before the lease expires. If lease negotiation is allowed, the client tracks the time remaining in its lease, and when half the lease time is used, the client requests the DHCP server to extend its lease to the original lease time. Disallowing lease negotiation is useful for environments where there are more machines than IP addresses, so the time limit is enforced on the use of IP addresses. If there are enough IP addresses, lease negotiation should be permitted to avoid forcing a client to take down its network interface and obtain a new lease, possibly interrupting their TCP connections (such as NFS and telnet sessions). Lease negotiation can be set site-wide during the server configuration, and for particular clients or types of clients through the use of the LeaseNeg option in configuration macros.

Note - Systems providing services on the network should retain their IP addresses, and should not be subject to short-term leases. You can use DHCP with such machines by assigning them reserved (manual) IP addresses, rather than IP addresses with permanent leases.


Top updates

Bulletin Latest Past week Past month
Google Search


NEWS CONTENTS

Old News ;-)

[Nov 22, 2006] SUMMARY (incomplete) Sun Solaris DHCP Server v. ISC DHCP Server

Bryan J. Smith b.j.smith at ieee.org
Sat Jul 20 18:14:32 EDT 2002
I received messages from people running both Solaris' built-in (or
unbundled) DHCP server as well as ISC's DHCP server on Solaris 2.5.1+. 
This summary is largely incomplete, as the responses given did _not_
show Sun's included Solaris DHCP Server has anything to offer over ISC's
DHCP Server.  Some people "guessed" that there might be some ONC+/NIS+
failover options, but no one confirmed this.

However, I still received a lot of good information.

- AVOID:  Solaris version 2.6 (and earlier unbundled) DHCP servers

Several people confirmed that pre-Solaris version 2.7 DHCP servers were
buggy.

- RECOMMEND:  Solaris version 2.8 10/01 (and later) DHCP servers

Several people confirmed that Solaris 2.8 10/01 and later are working
flawlessly for them.  Installing all post-10/01 DHCP patches is also
recommended.

Most are impressed with the GUI administration tools in these late DHCP
server releases which seem to make administration easier than ISC's DHCP
server "single, flat config file" setup.

- SCNA Note:  Study up on the Solaris DHCP server, it's 10% of the exam

As I mentioned before, if you plan on taking the Sun Certified Network
Administrator (SCNA) exam, be sure you know the bundled Solaris DHCP
_server_ in and out.  It's _nothing_ like the ISC server, and most of
the books (including Sun's SCNA Study Guide), and even the on-line Sun
Docs, are _dead_wrong_ in many areas.  Learn it from a working system
(which we should all be doing anyway, right? ;-).

-- Bryan

P.S.  I feel I must add this, so my apologize in advance:

In responses, several people accused me of "cheating" on the SCNA by
using some of the available "training/study guides."  I think people
forget that "computer-administered" examinations are _not_ about what
you know (let alone any extensive SunOS/Solaris experience -- I have 10
years, 6 _very_heavy_!), but if you can pass the objectives on the
examination which are usually _not_ "real-world" situations.  Most
"computer-administered" examinations try to be "hard" by either A)
making you memorize things that you usually hit the man pages for (this
is the Sun approach) or B) being very ambiguous in an attempt to confuse
the test taker (this is the Microsoft approach).  I agree that _neither_
is a good test for experienced administrators -- hence the "paper
certification" moniker (which I _do_ believe is an adequate
description).  Yes, it is possible that an experienced admin will pass
them "straight up," but if you want to get 90%+ (like I do), you use the
books to "brush up" on areas where you are weak.

Only "performance-based" laboratory/peer-reviewed examinations -- like
select Cisco certifications (and those modeled after them -- e.g.,
RedHat RHCE) test for "real world" experience where study guides are
useless (e.g., the RHCE passing rate went down drastically after
Syngress released its RHCE Study Guide).  While I would love to see
_all_ certifications follow the "performance-based" path (possibly with
background/experience checks like the CISSP), many HR departments are
using "paper certifications" right now to "filter out" candidates. 
Hence why I started sucking up certifications last month, because I'm
currently unemployed and I cannot find self-employment without these
little bits of paper that prospective clients want.  So cut me some
slack on the certs please, I'm even a degreed engineer (and _hate_ the
vendor "engineer" crap too ;-).

-- 
Bryan J. Smith, E.I.   mailto:b.j.smith at ieee.org   (407)489-7013
CompTIA A+ i-Net+ Linux+ Network+ Server+          Sun SCSA SCNA
----------------------------------------------------------------
SmithConcepts, Inc. -- http://www.SmithConcepts.com
Consulting Engineers and IT Professionals
_______________________________________________
sunmanagers mailing list
sunmanagers at sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Recommended Links

Softpanorama hot topic of the month

Softpanorama Recommended

[PDF] Solaris DHCP Administration Guide (806-5529)

System Administration Guide IP Services

Solaris DHCP Service Developer's Guide also at AnswerBook2 Solaris DHCP Service Developer's Guide

Solaris DHCP Solaris DHCP Service Developer's Guide BigAdmin Description: Solaris DHCP and PXE boot

HOW-TO Installing Solaris with PXE-DHCP - Solaris 10 tips and tricks for system administration

Solaris unattended installation (PXE and custom JumpStart) with ...

Setting Up a Solaris DHCP Client

DHCP FAQ

Reference

dhcpagent(1M) – Dynamic Host Configuration Protocol (DHCP) client daemon

dhcpconfig(1M) – DHCP service configuration utility

dhcpmgr(1M) – graphical interface for managing DHCP service

dhtadm(1M) – DHCP configuration table management utility

pntadm(1M) – DHCP network table management utility



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last Modified: October 20, 2015