Normal server debug output shows server configuration information followed by information about each network interface as the daemon starts. Thereafter, the debug output shows information about requests the daemon processes. The following examples show sample output for a DHCP server and a BOOTP relay agent. Example 12-3 shows debug output for a DHCP server that has just started and then extends the lease for a client using an address owned by another DHCP server that is not responding.
Daemon Version: 3.1 Maximum relay hops: 4 Transaction logging to console enabled. Run mode is: DHCP Server Mode. Datastore: nisplus Path: org_dir.dhcp.test..:dhcp.test..:$ DHCP offer TTL: 10 Ethers compatibility enabled. BOOTP compatibility enabled. ICMP validation timeout: 1000 milliseconds, Attempts: 2. Monitor (0005/hme0) started... Thread Id: 0005 - Monitoring Interface: hme0 ***** MTU: 1500 Type: DLPI Broadcast: 102.21.255.255 Netmask: 255.255.0.0 Address: 102.21.0.2 Monitor (0006/nf0) started... Thread Id: 0006 - Monitoring Interface: nf0 ***** MTU: 4352 Type: DLPI Broadcast: 102.22.255.255 Netmask: 255.255.0.0 Address: 102.22.0.1 Monitor (0007/qe0) started... Thread Id: 0007 - Monitoring Interface: qe0 ***** MTU: 1500 Type: DLPI Broadcast: 102.23.63.255 Netmask: 255.255.192.0 Address: 102.23.0.1 Read 33 entries from DHCP macro database on Tue Aug 10 15:10:27 1999 Datagram received on network device: qe0 Client: 0800201DBA3A is requesting verification of address owned by 102.21.0.4 Datagram received on network device: qe0 Client: 0800201DBA3A is requesting verification of address owned by 102.21.0.4 Datagram received on network device: qe0 Client: 0800201DBA3A is requesting verification of address owned by 102.21.0.4 Datagram received on network device: qe0 Client: 0800201DBA3A maps to IP: 102.23.3.233 Unicasting datagram to 102.23.3.233 address. Adding ARP entry: 102.23.3.233 == 0800201DBA3A DHCP EXTEND 0934312543 0934316143 102.23.3.233 102.21.0.2 0800201DBA3A SUNW.SPARCstation-10 0800201DBA3A |
The following example shows debug output from a DHCP daemon that starts up as a BOOTP relay agent and relays requests from a client to a DHCP server, and relays the servers responses to the client.
Relay destination: 102.21.0.4 (blue-servr2) network: 102.21.0.0 Daemon Version: 3.1 Maximum relay hops: 4 Transaction logging to console enabled. Run mode is: Relay Agent Mode. Monitor (0005/hme0) started... Thread Id: 0005 - Monitoring Interface: hme0 ***** MTU: 1500 Type: DLPI Broadcast: 102.21.255.255 Netmask: 255.255.0.0 Address: 102.21.0.2 Monitor (0006/nf0) started... Thread Id: 0006 - Monitoring Interface: nf0 ***** MTU: 4352 Type: DLPI Broadcast: 102.22.255.255 Netmask: 255.255.0.0 Address: 102.22.0.1 Monitor (0007/qe0) started... Thread Id: 0007 - Monitoring Interface: qe0 ***** MTU: 1500 Type: DLPI Broadcast: 102.23.63.255 Netmask: 255.255.192.0 Address: 102.23.0.1 Relaying request 0800201DBA3A to 102.21.0.4, server port. BOOTP RELAY-SRVR 0934297685 0000000000 0.0.0.0 102.21.0.4 0800201DBA3A N/A 0800201DBA3A Packet received from relay agent: 102.23.0.1 Relaying reply to client 0800201DBA3A Unicasting datagram to 102.23.3.233 address. Adding ARP entry: 102.23.3.233 == 0800201DBA3A BOOTP RELAY-CLNT 0934297688 0000000000 102.23.0.1 102.23.3.233 0800201DBA3A N/A 0800201DBA3A Relaying request 0800201DBA3A to 102.21.0.4, server port. BOOTP RELAY-SRVR 0934297689 0000000000 0.0.0.0 102.21.0.4 0800201DBA3A N/A 0800201DBA3A Packet received from relay agent: 102.23.0.1 Relaying reply to client 0800201DBA3A Unicasting datagram to 102.23.3.233 address. Adding ARP entry: 102.23.3.233 == 0800201DBA3A |
If there is a problem, the debug output might display warnings or error messages. Use the following table to find the error message or condition and find a solution.
Table 12-4 DHCP Server Error Messages
Message |
Explanation |
Solution |
---|---|---|
ICMP ECHO reply to OFFER candidate: ip_address disabling |
Before the DHCP server offers an IP address to a client, it verifies that the address is not in use by pinging the address. If a client replies, the address is in use. |
Make sure the addresses you configured are not already in use. |
No more IP addresses on network_address network. |
No available IP addresses in the client's per network table. |
Allocate more IP addresses using DHCP Manager or pntadm. If the DHCP daemon is monitoring multiple subnets, be sure the additional addresses are for the subnet where the client is located. |
No more IP addresses for network_address network when you are running the DHCP daemon in BOOTP compatibility mode (-b option). |
BOOTP does not use a lease time, so the DHCP server looks for free addresses with the BOOTP flag set to allocate to BOOTP clients. |
Use DHCP Manager to allocate BOOTP addresses. |
Request to access nonexistent per network database: database_name in datastore: datastore. |
During configuration of the DHCP server, a DHCP network table for a subnet was not created. |
Use DHCP Manager or the pntadm to create the DHCP network table and new IP addresses. |
There is no table_name dhcp-network table for DHCP client's network. |
During configuration of the DHCP server, a DHCP network table for a subnet was not created. |
Use DHCP Manager or the pntadm to create the DHCP network table and new IP addresses. |
Client using non_RFC1048 BOOTP cookie. |
A device on the network is trying to access an unsupported implementation of BOOTP. |
Ignore this message, unless you need to configure this device. |
Client client_id is trying to verify unrecorded address ip_address, ignored. |
The IP address and client ID in the /etc/dhcp/interface.dhc file on the client do not match the IP address and client ID in the DHCP network database that is checked by the DHCP server. This can happen when you use local files as the DHCP data store and have multiple DHCP servers (not sharing information) or have changed the DHCP network table |
Restart the DHCP protocol on the client by typing the following commands: ifconfig interface dhcp release ifconfig interface dhcp start |