CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

A Cisco router can function either as a local Dynamic Host Configuration Protocol (DHCP) server managing subnet scopes or as a DHCP relay agent forwarding client requests to a centralized server. When network endpoints encounter addressing failures or IP lease renewal errors, verifying the router’s running DHCP parameters, active leases, and interface relay settings is the primary troubleshooting action. Inspecting these states directly in Cisco IOS enables network administrators to confirm address pool allocations, analyze active bindings, and identify configuration discrepancies before they disrupt host connectivity.

Step-by-Step Guide to Verifying DHCP Pools and Active Leases

To confirm that a Cisco router is actively serving network endpoints, use Privileged EXEC mode (#) commands to audit the configuration, pool capacity, and client bindings.

Step 1: Verify DHCP Service State and Configuration

Before inspecting dynamic pools, verify that the router has the DHCP daemon enabled and review the assigned scope parameters:

Router# show running-config | section dhcp

Look for service dhcp in the global configuration (this feature is enabled by default in modern IOS versions). Verify that the excluded address ranges (ip dhcp excluded-address) and pool definitions match the intended subnet design:

ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp pool LAN_POOL
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1
 dns-server 8.8.8.8 8.8.4.4
 lease 1 0 0

Step 2: Check Configured Pool Capacity and Subnet Scope

Execute show ip dhcp pool to review the operational status of all configured pools or append a specific pool name:

Router# show ip dhcp pool LAN_POOL
Pool LAN_POOL :
 Utilization mark (high/low)    : 100 / 0
 Subnet size (to/from/count)    : 254 / 1 / 254
 Total addresses                : 254
 Leased addresses               : 14
 Excluded addresses             : 10
 Pending addresses              : 0
 Subnet prefix                  : 192.168.10.0/24

This output displays the available address space, active leases, and excluded blocks. Verify that Total addresses matches your subnet size and that Leased addresses has not reached the pool’s maximum usable capacity.

Step 3: Inspect Active DHCP Client Bindings

Display all current IP leases provided to connected hosts:

Router# show ip dhcp binding
Bindings from all pools :
IP address      Client-ID/              Lease expiration        Type
                Hardware address/
                User name
192.168.10.11   0100.5079.6668.00       Mar 15 2026 10:45 AM    Automatic
192.168.10.12   0114.dae9.55ab.cd       Mar 15 2026 11:02 AM    Automatic

Inspect this list to verify that hosts receive IPs from the expected subnet and that lease durations match administrative policies.

Step 4: Review DHCP Server Message Statistics

Examine transaction traffic to ensure the router processes client discoveries, offers, requests, and acknowledgments without packet drops:

Router# show ip dhcp server statistics

Confirm that the counters for DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, and DHCPACK increment when new clients join the network.

Interpreting DHCP Output: Leases, MAC Identifiers, and Pool Utilization

Why does the hardware address in show ip dhcp binding contain a leading “01”?

In Cisco IOS, the Client-ID field represents the DHCP Option 61 identifier sent by the client. For standard Ethernet interfaces, Cisco IOS prepends 01—the standard ARP hardware type for Ethernet defined in RFC 1700—to the device’s 48-bit MAC address.

For example, a binding displaying 0100.5079.6668.00 corresponds to a physical MAC address of 00:50:79:66:68:00. If a client submits an ASCII-based or DUID-based identifier (common with Windows or Linux operating systems requesting IPv6/IPv4 options), the string appears longer and will not follow standard MAC formatting.

What do the lease expiration timestamps mean, and why are some marked “Infinite”?

The Lease expiration column displays when a dynamic lease must be renewed by the client. If an expiration date and time appear, the lease is dynamic (“Automatic”) and calculated from the router’s internal clock.

If the expiration is listed as Infinite, one of two conditions applies:
1. The pool has been configured with the lease infinite command.
2. The address assignment is a static manual reservation configured using a dedicated host pool mapping a specific hardware-address or client-identifier.

How is pool utilization calculated in show ip dhcp pool?

Cisco IOS tracks pool capacity using the following relationship:

$$\text{Usable Addresses} = \text{Total addresses} – \text{Excluded addresses}$$

$$\text{Pool Utilization \%} = \left(\frac{\text{Leased addresses}}{\text{Usable Addresses}}\right) \times 100$$

A high pool utilization (approaching 100%) indicates that new clients cannot obtain an IP address until existing leases expire or the scope is expanded.

What causes an address assignment to be listed as “Pending”?

An address appears as Pending when the router offers an IP address (DHCPOFFER) to a client but has not yet received a confirmation request (DHCPREQUEST) and completed the transaction (DHCPACK). Cisco IOS reserves this address temporarily (typically for a few seconds) to prevent issuing the same address to multiple competing hosts during concurrent boot events.

How to Verify DHCP Relay (IP Helper-Address) Configuration

When a Cisco router does not serve DHCP locally, it forwards broadcast discovery packets across routed boundaries to an upstream DHCP server. This is configured on the client-facing Layer 3 interface.

Step 1: Identify Ingress Relay Configuration on Client Interfaces

Confirm that the client-facing interface has an ip helper-address assigned and is in an up/up operational state:

Router# show running-config interface GigabitEthernet0/0/1
interface GigabitEthernet0/0/1
 ip address 10.10.10.1 255.255.255.0
 ip helper-address 172.16.1.100

Verify that the target IP (172.16.1.100) matches the active IP address of the upstream DHCP server.

Step 2: Check Interface Forwarding Parameters

Confirm that the interface has UDP broadcast forwarding active:

Router# show ip interface GigabitEthernet0/0/1
GigabitEthernet0/0/1 is up, line protocol is up
  Internet address is 10.10.10.1/24
  Broadcast address is 255.255.255.255
  Address determined by setup command
  Helper address is 172.16.1.100
  Directed-broadcast forwarding is disabled

Ensure the Helper address line reflects the target server. If multiple DHCP servers provide redundancy, confirm that each server IP appears as an independent helper address entry.

Step 3: Validate Upstream Routing Reachability

Confirm that the router can route packets to the upstream DHCP server through its routing table:

Router# show ip route 172.16.1.100
Routing entry for 172.16.1.0/24
  Known via "ospf 1", distance 110, metric 20
  Routing Descriptor Blocks:
  * 10.0.0.2, from 172.16.1.100, via GigabitEthernet0/0/0

If the route is missing or pointing to a non-functional interface, relayed unicast packets will be discarded before reaching the server.

Step 4: Inspect UDP Forwarding Statistics

Verify that broadcast DHCP requests (UDP ports 67 and 68) are being converted to unicast and forwarded upstream:

Router# show ip forward interface GigabitEthernet0/0/1

Confirm that the forwarding counters increment when client devices transmit broadcast discover packets on that segment.

Troubleshooting DHCP Failures: Exhaustion, Conflicts, and Packet Drops

When clients report missing IP addresses or receive Automatic Private IP Addressing (APIPA) coordinates (169.254.x.x), execute these diagnostic steps to identify the root cause.

Step 1: Identify and Resolve IP Conflicts

A conflict occurs when the router detects an address is already in use (via ICMP ping before assignment) or when a host transmits a gratuitous ARP rejecting an assigned IP.

Router# show ip dhcp conflict
IP address        Detection method   Detection time          VRF
192.168.10.25     Ping               Mar 14 2026 08:12 AM    --
192.168.10.42     Gratuitous ARP     Mar 14 2026 09:30 AM    --

When an address is flagged as conflicted, the router removes it from the usable pool. To resolve the conflict:
1. Locate the rogue or statically configured device on the network holding that IP address.
2. Clear the router conflict entry so the IP can re-enter service:

Router# clear ip dhcp conflict 192.168.10.25
! Or clear all recorded conflicts:
Router# clear ip dhcp conflict *

Step 2: Mitigate Pool Exhaustion

If show ip dhcp pool shows high utilization with zero free addresses, new clients will be rejected. Resolve pool exhaustion using one of the following methods:

  • Shorten Lease Times: Free up inactive leases faster for transient devices:
    text
    Router(config)# ip dhcp pool LAN_POOL
    Router(dhcp-config)# lease 0 4 0 ! Sets lease duration to 4 hours
  • Reclaim Excluded Addresses: Audit the ip dhcp excluded-address range to confirm reserved addresses are truly required for static hosts.
  • Clear Expired or Stale Bindings: Manually remove an obsolete binding to free an address immediately:
    text
    Router# clear ip dhcp binding 192.168.10.15

Step 3: Monitor Real-Time DHCP Transactions

To isolate dropped packets, misconfigured option parameters, or client transmission timeouts, activate real-time packet debugging in Privileged EXEC mode:

Router# terminal monitor
Router# debug ip dhcp server packet
Router# debug ip dhcp server events

Observe the console for the four-way DORA handshake:

*Mar 15 11:20:01.102: DHCPD: DHCPDISCOVER received from client 0100.5079.6668.00 on interface GigabitEthernet0/0/1.
*Mar 15 11:20:01.103: DHCPD: Sending DHCPOFFER of IP address 192.168.10.15.
*Mar 15 11:20:01.108: DHCPD: DHCPREQUEST received from client 0100.5079.6668.00.
*Mar 15 11:20:01.109: DHCPD: Sending DHCPACK to client 0100.5079.6668.00.

If the router logs DHCPDISCOVER but does not reply with DHCPOFFER, confirm that the ingress interface IP falls within the defined network pool and that usable addresses remain.

Always terminate debugging sessions once diagnostics are complete:

Router# undebug all

Cisco IOS IP Addressing Services Command Reference

The following operational commands are documented under the official Cisco IOS IP Addressing Services Command Reference. These commands are run from Privileged EXEC mode (Router#) unless otherwise specified.

show ip dhcp binding

  • Syntax: show ip dhcp binding [ip-address]
  • Mode: Privileged EXEC
  • Purpose: Displays address-to-hardware binding associations maintained by the local server.
  • Parameters:
  • ip-address (Optional): Restricts output to a single client binding.

show ip dhcp pool

  • Syntax: show ip dhcp pool [pool-name]
  • Mode: Privileged EXEC
  • Purpose: Displays capacity, utilization thresholds, dynamic range metrics, and excluded address blocks for dynamic scopes.
  • Parameters:
  • pool-name (Optional): Specifies the target pool name. If omitted, statistics for all active pools are displayed.

show ip dhcp conflict

  • Syntax: show ip dhcp conflict [ip-address]
  • Mode: Privileged EXEC
  • Purpose: Displays IP addresses detected as duplicates and isolated from assignment pools.
  • Parameters:
  • ip-address (Optional): Filters conflict output for an individual IP.

show ip dhcp server statistics

  • Syntax: show ip dhcp server statistics
  • Mode: Privileged EXEC
  • Purpose: Displays global message traffic counters for protocol transactions (DISCOVER, OFFER, REQUEST, ACK, NAK, DECLINE).
  • Parameters: None.

clear ip dhcp binding

  • Syntax: clear ip dhcp binding {* | ip-address}
  • Mode: Privileged EXEC
  • Purpose: Releases one or all active dynamic address leases from the database.
  • Parameters:
  • *: Clears all active bindings across all pools.
  • ip-address: Clears the specific host lease.

clear ip dhcp conflict

  • Syntax: clear ip dhcp conflict {* | ip-address}
  • Mode: Privileged EXEC
  • Purpose: Restores addresses flagged as conflicting back to the usable dynamic scope.
  • Parameters:
  • *: Clears all recorded conflicts.
  • ip-address: Clears the specific conflict record.

Cisco Router DHCP Verification Commands Cheat Sheet

Use the following CLI template as a ready-reference script for configuration, validation, and troubleshooting sessions:

! ==============================================================================
! 1. CONFIGURATION TEMPLATE: DHCP SERVER & RELAY
! ==============================================================================
configure terminal

 ! --- Local DHCP Server Configuration ---
 service dhcp
 ip dhcp excluded-address 192.168.20.1 192.168.20.10
 !
 ip dhcp pool BRANCH_OFFICE
  network 192.168.20.0 255.255.255.0
  default-router 192.168.20.1
  dns-server 1.1.1.1 8.8.8.8
  domain-name enterprise.local
  lease 0 8 0
 exit

 ! --- DHCP Relay Configuration (Interface Level) ---
 interface GigabitEthernet0/0/2
  description Client_Access_VLAN
  ip address 192.168.30.1 255.255.255.0
  ip helper-address 10.100.1.50
  no shutdown
 exit
end

! ==============================================================================
! 2. PRIMARY VERIFICATION COMMANDS
! ==============================================================================
! View running DHCP configuration lines
show running-config | section dhcp

! View pool allocation and utilization metrics
show ip dhcp pool
show ip dhcp pool BRANCH_OFFICE

! View all active client IP leases
show ip dhcp binding

! View interface helper address configuration
show ip interface GigabitEthernet0/0/2 | include (Helper|Internet address)

! View global server transaction statistics
show ip dhcp server statistics

! ==============================================================================
! 3. TROUBLESHOOTING & RESET COMMANDS
! ==============================================================================
! Inspect detected IP conflicts
show ip dhcp conflict

! Clear conflict state for an address or entire conflict log
clear ip dhcp conflict 192.168.20.15
clear ip dhcp conflict *

! Release active leases
clear ip dhcp binding 192.168.20.25
clear ip dhcp binding *

! Real-time debugging (Disable immediately after capturing packets)
terminal monitor
debug ip dhcp server packet
debug ip dhcp server events
undebug all

Validating DHCP operations on a Cisco router requires examining the router’s role in the network architecture. When functioning as a DHCP server, regular inspection of pool utilization, active client bindings, and conflict lists helps prevent address exhaustion and IP overlaps. When operating as a relay agent, checking interface helper assignments, forwarder counters, and upstream routing ensures discovery broadcasts reach the central server. Integrating these verification routines into standard operational checks maintains predictable dynamic addressing across all connected network segments.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.