CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

When a Cisco Catalyst or Layer 3 switch acts as an internal DHCP server, monitoring pool capacity and lease allocations is essential for keeping client subnets online. Whether you are auditing available IP capacity, tracking down which device claimed a specific address, or diagnosing why new clients are failing to join the network, Cisco IOS and IOS XE provide a dedicated suite of show ip dhcp verification commands. This guide walks through the exact CLI templates, step-by-step verification workflows, multi-VLAN checks, and troubleshooting procedures needed to inspect a DHCP pool on a Cisco switch.

CLI Commands to Check DHCP Pool Configuration and Utilization

To immediately inspect the configured parameters and real-time capacity counters of all DHCP pools—or a single named pool—run the following commands in Privileged EXEC mode (#). Keep prose intervention minimal by copying and adapting the CLI templates below directly into your terminal session.

! 1. View utilization counters and subnet ranges for all DHCP pools
Switch# show ip dhcp pool

! 2. View utilization counters for a single specific DHCP pool
Switch# show ip dhcp pool <POOL_NAME>

! 3. View the running configuration for all DHCP pools and global DHCP parameters
Switch# show running-config | section ip dhcp

! 4. View only the network, gateway, DNS, and lease settings of a specific pool
Switch# show running-config | section ip dhcp pool <POOL_NAME>

Example Output Template and Counter Breakdown

Switch# show ip dhcp pool VLAN10_USERS

Pool VLAN10_USERS :
 Utilization mark (high/low)    : 100 / 0
 Subnet size (first/next)       : 0 / 0 
 Total addresses                : 254
 Leased addresses               : 142
 Excluded addresses             : 12
 Pending event                  : none
 1 subnet is currently in the pool :
 Current index        IP address range                    Leased/Excluded/Total
 192.168.10.155       192.168.10.1     - 192.168.10.254    142   / 12     / 254
Switch# show running-config | section ip dhcp pool VLAN10_USERS
ip dhcp pool VLAN10_USERS
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1 
 dns-server 192.168.10.10 192.168.10.11 
 domain-name corp.example.com
 lease 0 8

Key Takeaway: Always compare Total addresses against the sum of Leased addresses and Excluded addresses in show ip dhcp pool to calculate how many usable IPs remain before the subnet reaches exhaustion.


How to Check Active DHCP Leases and IP Bindings

While pool counters show overall capacity, they do not identify which endpoints hold specific IP addresses. To inspect individual client leases and MAC-to-IP mappings, follow these steps to query the switch’s DHCP binding database.

Step 1: Display the Full DHCP Binding Table

From Privileged EXEC mode, run the show ip dhcp binding command to list every active IP lease currently maintained by the switch:

Switch# show ip dhcp binding
Bindings from all pools not associated with VRF:
IP address          Client-ID/              Lease expiration        Type
                    Hardware address/
                    User name
192.168.10.21       0100.5056.9a3b.1c       Nov 18 2026 02:14 PM    Automatic
192.168.10.22       001b.6384.45e6          Nov 18 2026 03:40 PM    Automatic
192.168.10.50       01a4.83e7.1120.9f       Infinite                Manual

Step 2: Interpret the Client-ID vs. Hardware Address Format

Examine the second column carefully when matching a lease to a physical device:
* 14-character hex string (starting with 01): Indicates the client included a DHCP Option 61 Client-Identifier in its request. The leading 01 represents the Ethernet media type, and the remaining 12 hex characters (0050.569a.3b1c) represent the device’s actual MAC address.
* 12-character hex string: Indicates the client did not send a Client-ID option, so the switch recorded the raw Layer 2 Hardware (MAC) address directly.
* Type (Automatic vs. Manual): Automatic indicates a dynamically leased IP with a finite expiration timestamp, whereas Manual indicates a static DHCP reservation (host statement) with an Infinite lease.

Step 3: Filter Bindings by IP or MAC Address

On switches managing hundreds of endpoints, pipe the output or specify an IP address directly to isolate a single client:

! Check the binding details for one specific IP address
Switch# show ip dhcp binding 192.168.10.21

! Search for a lease using the last four hex digits of a client MAC address
Switch# show ip dhcp binding | include 3b.1c

Key Takeaway: When searching the binding table by MAC address, match the final four to six characters rather than the beginning of the string so that leading 01 Client-ID prefixes do not cause missed matches.


How to Inspect Excluded Addresses and DHCP IP Conflicts

In the show ip dhcp pool output covered earlier, the Excluded addresses counter often displays a number higher than the static range you manually configured. This happens because Cisco IOS groups both administrative exclusions and dynamically detected IP conflicts into that single counter. Follow these steps to separate intentional exclusions from duplicate-IP conflicts.

Step 1: Verify Administratively Excluded IP Ranges

Check the running configuration for ip dhcp excluded-address statements. These commands reserve static IP blocks (such as SVI gateways, printers, and servers) so the DHCP server never assigns them:

Switch# show running-config | include excluded-address
ip dhcp excluded-address 192.168.10.1 192.168.10.10
ip dhcp excluded-address 192.168.10.250 192.168.10.254

In this example, 15 addresses (1–10 and 250–254) are intentionally excluded by the administrator.

Step 2: Check the DHCP Conflict Log

If the Excluded addresses counter in show ip dhcp pool exceeds your configured static exclusions, inspect the DHCP conflict table:

Switch# show ip dhcp conflict
IP address        Detection method   Detection time          VRF
192.168.10.25     Ping               Nov 16 2026 09:12 AM
192.168.10.26     Gratuitous ARP     Nov 16 2026 11:45 AM

Step 3: Identify the Conflict Detection Method

Whenever the Cisco switch detects that an IP inside the pool is already in use by a statically configured host, it moves that IP into the conflict table and withholds it from future allocation until an administrator clears it:
* Ping: Before offering an IP address to a client, the Cisco DHCP server sends ICMP echo requests to that IP. If any host replies, the switch logs a Ping conflict.
* Gratuitous ARP: After receiving a lease offer, the client broadcasts an ARP check for its assigned IP. If another device on the VLAN responds, the client sends a DHCPDECLINE packet back to the switch, which logs a Gratuitous ARP conflict.

Key Takeaway: Any IP listed in show ip dhcp conflict is permanently withheld from the available DHCP pool until the underlying duplicate IP is fixed and the conflict entry is manually cleared or the switch reloads.


Verifying DHCP Pools Across Multiple VLANs and VRFs

On Layer 3 Catalyst switches routing across multiple subnets or Virtual Routing and Forwarding (VRF) instances, verifying how pools map to specific interfaces requires checking both Layer 3 Switched Virtual Interfaces (SVIs) and VRF-aware DHCP tables.

How does a Cisco Layer 3 switch match a DHCP pool to a specific VLAN?

A Cisco switch does not bind a DHCP pool to a VLAN ID by name. Instead, it automatically matches the IP address and subnet mask of the incoming SVI (interface Vlan<ID>) against the network statement configured inside each ip dhcp pool. To verify which VLAN a pool serves, compare show ip interface brief against the pool’s network range:

Switch# show ip interface Vlan10 | include Internet address
  Internet address is 192.168.10.1/24

Because Vlan10 uses 192.168.10.1/24, any DHCP broadcast arriving on VLAN 10 is automatically served by the pool configured with network 192.168.10.0 255.255.255.0.

How do I check DHCP bindings and conflicts for a specific VRF?

If your DHCP pools are segmented across VRFs, the standard show ip dhcp binding command only displays non-VRF (global routing table) leases. Append the vrf keyword to inspect leases or conflicts inside a specific VRF instance:

! View active DHCP bindings inside a specific VRF
Switch# show ip dhcp binding vrf GUEST_VRF

! View IP conflicts recorded inside a specific VRF
Switch# show ip dhcp conflict vrf GUEST_VRF

How do I tell if a VLAN is using a local switch DHCP pool or an external DHCP server?

Inspect the SVI configuration for a DHCP relay agent (ip helper-address). Run show ip interface Vlan<ID> | include Helper to check:

Switch# show ip interface Vlan20 | include Helper
  Helper address is 10.100.1.50

If a Helper address is present and no local ip dhcp pool matches that SVI’s subnet, the switch is relaying DHCP broadcasts to the external server rather than allocating addresses locally.

Key Takeaway: Always confirm that the SVI IP address falls within the exact subnet defined in the pool’s network statement, and use the vrf <VRF_NAME> flag whenever auditing multi-tenant Layer 3 switches.


Troubleshooting an Exhausted or Non-Responding DHCP Pool

When endpoints fall back to APIPA addresses (169.254.x.x) despite an active DHCP configuration on the switch, follow this diagnostic sequence to identify bottlenecks and restore IP allocation.

Step 1: Audit DHCP Server Packet and Memory Statistics

Verify whether client requests are actually reaching the switch CPU and whether the switch is attempting to respond by checking the global server statistics:

Switch# show ip dhcp server statistics
Memory usage         42912
Address pools        3
Database agents      0
Automatic bindings   142
Manual bindings      1
Expired bindings     8
Malformed messages   0
Secure arp entries   0

Message              Received
BOOTREQUEST          0
DHCPDISCOVER         1540
DHCPREQUEST          1482
DHCPDECLINE          2
DHCPRELEASE          310
DHCPINFORM           85

Message              Sent
BOOTREPLY            0
DHCPOFFER            1490
DHCPACK              1480
DHCPNAK              2
  • If DHCPDISCOVER is not incrementing: Client broadcasts are not reaching the Layer 3 SVI. Check that the VLAN exists in show vlan brief, the SVI is up/up, and the global service dhcp command has not been disabled (no service dhcp).
  • If DHCPDISCOVER increments but DHCPOFFER stays flat: The switch receives the request but cannot allocate an IP, almost always because the matching pool is exhausted or no pool matches the SVI subnet.

Step 2: Reclaim Exhausted Addresses by Clearing Conflicts and Stale Bindings

Repeated IP conflicts or short-lived guest devices can silently consume every available address in a subnet. Once you have resolved any static duplicate IP issues on the VLAN, flush the conflict table and expired or stale bindings to return those IPs to the active pool:

! Clear a single conflicted IP or all conflicted IPs (*)
Switch# clear ip dhcp conflict 192.168.10.25
Switch# clear ip dhcp conflict *

! Clear a specific stale lease or reset all dynamic bindings (*)
Switch# clear ip dhcp binding 192.168.10.21
Switch# clear ip dhcp binding *

Step 3: Run Real-Time DHCP Server Event Debugging

If clients still fail to obtain an address, enable DHCP server event debugging to watch allocation failures in real time. (If connected via SSH, run terminal monitor first to display console log messages in your session.)

Switch# debug ip dhcp server events
Switch# terminal monitor

Look for explicit diagnostic log lines when a client attempts to connect:
* DHCPD: there is no address pool for 192.168.30.1 — Indicates the SVI IP (192.168.30.1) has no matching network statement in any configured DHCP pool.
* DHCPD: pool VLAN10_USERS is empty — Confirms all usable addresses in the pool are currently leased or locked in the conflict table.

Immediately disable debugging once you capture the output:

Switch# undebug all

Key Takeaway: Checking show ip dhcp server statistics alongside debug ip dhcp server events quickly isolates whether a failure stems from Layer 2/SVI reachability, a missing subnet statement, or complete pool exhaustion caused by accumulated conflict entries.


Cisco IOS DHCP Verification Command Reference

The following reference table documents the official Cisco IOS and IOS XE command syntax, required execution modes, and output field specifications as defined in the Cisco IOS IP Addressing Services Command Reference.

Command SyntaxCommand ModePrimary Function & Key Output Fields
show ip dhcp pool [name]User EXEC (>) or Privileged EXEC (#)Displays pool subnet ranges and capacity counters.
• Utilization mark (high/low): Threshold percentages configured for SNMP/syslog pool utilization alerts.
• Current index: The next IP address the server will attempt to allocate.
• Leased/Excluded/Total: Breakdown of active leases, unavailable (excluded + conflicted) IPs, and total subnet capacity.
show ip dhcp binding [ip-address] [vrf vrf-name]User EXEC (>) or Privileged EXEC (#)Displays MAC-to-IP address lease records.
• Client-ID/Hardware address: Option 61 identifier or Layer 2 MAC address.
• Lease expiration: Date and time the lease expires, or Infinite for manual reservations.
• Type: Automatic (dynamic pool allocation) or Manual (static host binding).
show ip dhcp conflict [ip-address] [vrf vrf-name]User EXEC (>) or Privileged EXEC (#)Lists IP addresses withheld from allocation due to duplicate IP detection.
• Detection method: Ping (detected by switch prior to offer) or Gratuitous ARP (declined by client).
• Detection time: Timestamp when the conflict occurred.
show ip dhcp server statistics [type-number]User EXEC (>) or Privileged EXEC (#)Displays cumulative memory consumption, binding counts, and transmitted/received DHCP packet counters (DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, DHCPACK, DHCPNAK, DHCPDECLINE).
show ip dhcp database [url]Privileged EXEC (#)Displays the status of external DHCP binding database agents (FTP, TFTP, NVRAM, or flash) used to persist lease tables across switch reloads, including last read/write timestamps and transfer counters.

Key Takeaway: Use User EXEC or Privileged EXEC mode for read-only pool and binding verification, and verify show ip dhcp database on production switches to confirm lease bindings are backed up to flash or an external server across reboots.


Conclusion

Checking a DHCP pool on a Cisco switch comes down to correlating three core views: overall pool capacity (show ip dhcp pool), active client leases (show ip dhcp binding), and withheld addresses (show ip dhcp conflict and excluded-address configurations). By combining these verification commands with VRF filters and packet statistics (show ip dhcp server statistics), network administrators can accurately monitor subnet utilization, track endpoint MAC mappings, and resolve pool exhaustion before it impacts network connectivity.

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

Author

Comments

Write a Reply or Comment

Your email address will not be published.