jumpstart:
   OK>  boot net:dhcp - install

dhcp
      /etc/inet/dhcpsvc.conf
      /etc/dhcptap
      /var/dhcp/dhcptab
      /var/dhcp/dhcp_network

      pntadm -C 192.168.30.0
      pntadm -P  #show dhcptab
      pntamd -L  #list networks
      pntadm -P network#
      dhcpmgr
      dhcpconfig
      dhtadm
      pntadm
      dhcpinfo
      dhcpagent


================================================================================
Troubleshoot a DHCP server

IP address allocation errors are reported using the syslog facility or as server debug
output. This type of problem can occur when a client attempts to obtain or verify an
IP address.

The following are possible IP address allocation errors and solutions:

    * There is no n.n.n.n dhcp-network table for DHCP client's network

This error message means that a client requests a specific IP address or seeks to
extend a lease on its current IP address, but the DHCP server cannot find the DHCP
network table for that address.

The DHCP network table might have been deleted by mistake. Recreate the DHCP network
table by adding the network again using the dhcpmgr utility or the pntadm command.

    * ICMP ECHO reply to the OFFER candidate is n.n.n.n, disabling

The IP address considered for a DHCP client is already in use. This might occur if
more than one DHCP server owns the address or if an address is manually configured for
a non-DHCP network client.

Determine the correct ownership of the address, and correct either the DHCP server
database or the host's network configuration.

    * ICMP ECHO reply to OFFER candidate n.n.n.n. No corresponding dhcp network record

The IP address considered for a DHCP client does not have a record in a network table.
This might occur if the IP address record is deleted from the DHCP network table after
the address is selected, but before the duplicate address check is complete.

Use the dhcpmgr utility or the pntadm command to view the DHCP network table. If the
IP address is missing, create it with the DHCP Manager (select Create from the Edit
menu on the Address tab) or use the pntadm command.

    * DHCP network record for n.n.n.n is unavailable, ignoring request

The record for the requested IP address is not in the DHCP network table; therefore,
the server drops the request.

Use the dhcpmgr utility or the pntadm command to view the DHCP network table and, if
the IP address is missing, create it with the dhcpmgr utility (select Create from the
Edit menu on the Address tab) or use the pntadm command.

    * n.n.n.n currently marked as unusable

The requested IP address cannot be offered because it is marked unusable in the
network table.

Use the DHCP Manager or the pntadm command to make the address usable.

    * n.n.n.n was manually allocated. No dynamic address will be allocated.

The client's ID is assigned a manually allocated address, and that address is marked
"unusable." The server cannot allocate a different address to this client.

Use the DHCP Manager or the pntadm command to make the address usable, or manually
allocate a different address to the client.

    * Manual allocation (n.n.n.n, client ID has n other records). Should have 0.

The client that has the specified client ID is manually assigned more than one IP
address. There should be only one address. The server selects the last manually
assigned address it finds in the network table.

Use the DHCP Manager or the pntadm command to modify IP addresses to remove the
additional manual allocations.

    * No more IP addresses on n.n.n.n network.

All IP addresses that are currently managed by DHCP on the specified network are
allocated.

Use the DHCP Manager or the pntadm command to create new IP addresses for this
network.

    * Client: clientID lease for n.n.n.n expired.

The lease was not negotiable, and it has timed out.

The client restarts the protocol to obtain a new lease.

    * Offer expired for client: n.n.n.n

The server made an IP address offer to the client, but the client took too long to
respond, and the offer expired.

The client issues another discover message. If this request times out, increase the
cache-offer timeout for the DHCP server. In the DHCP Manager, select Modify from the
Service menu.

    * Client: clientID REQUEST is missing requested IP option.

The client's request did not specify the offered IP address, so the DHCP server
ignores the request. This problem might occur if the client is not compliant with the
updated DHCP, RFC 2131.

Update the client software.

    * Client: clientID is trying to renew n.n.n.n, an IP address it has not leased.

The IP address recorded in the DHCP network table for this client does not match the
IP address that the client specified in its renewal request. The DHCP server does not
renew the lease.

This problem occurs if you delete a client's record while the client is still using
the IP address.

Use the DHCP Manager or the pntadm command to examine the network table, and correct
if necessary. The client's ID should be bound to the specified IP address. If it is
not, edit the address properties to add the client ID.

To enable the client to receive a new lease immediately, restart the DHCP agent on the
client by typing the commands:

# ifconfig interface dhcp release
# ifconfig interface dhcp start

================================================================================
Troubleshoot a DHCP client

The problems you might encounter with a DHCP client fall into the following categories:

    * Problems communicating with the DHCP server
    * Problems with inaccurate DHCP configuration information

After you enable the client software and reboot the system, the client tries to reach
the DHCP server to obtain its network configuration. If the client fails to reach the
server or if the client does not receive correct information, you can see error
messages, such as:

DHCP or BOOTP server not responding 
Need router-ip to communicate with TFTP server
TFTP server's IP address not known!

Before you determine the problem, you must gather diagnostic information from both the
client and the server, and analyze this information. To gather information, you can:

    * Run the client in debug mode.
    * Run the server in debug mode.
    * Start the snoop utility to monitor network traffic.

You can perform these tasks separately or concurrently.

The information you gather can help you determine if the problem is with the client,
server, or a relay agent.
================================================================================
================================================================================