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 a local DHCP server, visibility into pool utilization, excluded IP ranges, and active client leases is critical for keeping networks online. Whether you are auditing available IP capacity on a branch office switch or diagnosing why new endpoints cannot obtain an IP address, Cisco IOS and IOS-XE provide dedicated verification commands to inspect every layer of a DHCP scope.

This article walks through the exact CLI templates to check your configured DHCP pools, how to audit active MAC-to-IP bindings and address conflicts, official command reference specifications, step-by-step troubleshooting for exhausted scopes, enterprise VRF and VLAN verification, and automated monitoring tools.

CLI Commands to Check DHCP Scope Range and Configuration

Use the following Cisco IOS and IOS-XE CLI commands in Privileged EXEC mode (enable) to inspect operational DHCP pool capacity, configured subnet ranges, default gateways, DNS servers, and excluded IP addresses.

! 1. View all DHCP scopes, IP ranges, and current utilization counts
Switch# show ip dhcp pool

! 2. View a specific DHCP scope by pool name
Switch# show ip dhcp pool <POOL_NAME>

! 3. View the exact DHCP scope configuration and excluded ranges in running-config
Switch# show running-config | section dhcp

! 4. View only the excluded IP address ranges
Switch# show running-config | include ip dhcp excluded-address

Template Output Reference

Switch# show ip dhcp pool DATA_VLAN10

Pool DATA_VLAN10 :
 Utilization mark (high/low)    : 100 / 0
 Subnet size (first/next)       : 0 / 0 
 Total addresses                : 254
 Leased addresses               : 142
 Excluded addresses             : 20
 Pending event                  : none
 1 subnet is currently in the pool :
 Current index        IP address range                    Leased/Excluded/Total
 192.168.10.163       192.168.10.1     - 192.168.10.254    142   / 20     / 254

Switch# show running-config | section dhcp
ip dhcp excluded-address 192.168.10.1 192.168.10.20
ip dhcp pool DATA_VLAN10
 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 1 12

Key Takeaway: Always run both show ip dhcp pool (for real-time utilization math) and show running-config | section dhcp (for scope options like DNS, gateway, and excluded IP boundaries), as operational pool output does not list configured DHCP options.


How to Check Active DHCP Leases, IP Bindings, and Conflicts

Once you have confirmed the overall scope boundaries using the CLI template above, the next step is inspecting which individual endpoints hold active leases and whether any IP addresses have been disabled due to network conflicts.

Step 1: View Active IP-to-MAC Address Bindings

Run show ip dhcp binding to list every active lease handed out by the switch, or append a specific IP (show ip dhcp binding 192.168.10.21) to check a single host.

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.9a12.34       Nov 19 2026 08:30 AM    Automatic
192.168.10.22       a4c3.f088.11b2          Nov 18 2026 06:15 PM    Automatic
192.168.10.50       0100.1b63.8445.e6       Infinite                Manual
  • IP address: The IPv4 address currently assigned to the endpoint.
  • Client-ID / Hardware address: If the client sent DHCP Option 61 (Client Identifier), Cisco IOS prepends the media type code 01 (Ethernet) to the 12-character MAC address, resulting in a 14-character string (0100.5056.9a12.34). If the client did not send Option 61, only the raw 12-character MAC address (a4c3.f088.11b2) appears.
  • Lease expiration: The exact timestamp when the lease expires unless renewed by the client.
  • Type: Automatic indicates a dynamic lease from the scope; Manual indicates a static reservation configured with the host and client-identifier or hardware-address pool commands.

Step 2: Check the DHCP Conflict Table

Before a Cisco switch assigns an IP address from a scope, it sends ICMP echo requests (pings) to the candidate IP. Meanwhile, the client checks the address via Gratuitous ARP after receipt. If a response is detected, the switch flags the IP as conflicted and removes it from rotation.

Switch# show ip dhcp conflict
IP address        Detection method   Detection time          VRF
192.168.10.25     Ping               Nov 16 2026 14:22:10
192.168.10.26     Gratuitous ARP     Nov 17 2026 03:11:04

Any IP listed here is counted inside the Excluded addresses total seen in show ip dhcp pool and will not be assigned to any host until an administrator manually clears the conflict.

Step 3: Audit Global DHCP Server Statistics

To verify that the switch is actively receiving client broadcasts and responding without memory errors, inspect the server packet counters:

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

Message              Received
BOOTREQUEST          0
DHCPDISCOVER         1240
DHCPREQUEST          2890
DHCPDECLINE          1
DHCPRELEASE          95
DHCPINFORM           412

Message              Sent
BOOTREPLY            0
DHCPOFFER            1240
DHCPACK              2888
DHCPNAK              2

Comparing DHCPDISCOVER (received) against DHCPOFFER (sent) confirms whether the switch is actively answering requests or dropping them due to an exhausted scope.

Key Takeaway: Monitoring show ip dhcp binding alongside show ip dhcp conflict provides complete visibility into both active endpoints and silent IP collisions that shrink your usable scope.


Cisco IOS and IOS-XE DHCP Verification Command Reference

For administrators looking for exact syntax definitions and field descriptions as standardized in the Cisco IOS IP Addressing Services Command Reference (applicable to Catalyst 9000, 3850, 3650, and 2960-X/XR series running IOS or IOS-XE), the following reference details the core verification commands.

Command Syntax and Modes

  • Command Mode: User EXEC (>) or Privileged EXEC (#)
  • Documentation Path: Cisco IOS IP Addressing Services Command Reference > DHCP Commands: show ip dhcp binding through show ip dhcp server statistics

1. show ip dhcp pool [name]

Displays DHCP address pool statistics and subnet allocation blocks.
* Syntax Parameter name: (Optional) Case-sensitive string identifying a specific configured pool. Omit to display all pools.
* Output Field Definitions:
* Utilization mark (high/low): High and low utilization threshold percentages configured for SNMP trap generation or pool scaling.
* Subnet size (first/next): Number of addresses automatically allocated in ODAP (On-Demand Address Pool) environments; 0 / 0 indicates a standard static local pool.
* Total addresses: Total assignable host IP addresses in the configured subnet (excluding network and broadcast addresses).
* Leased addresses: Number of IP addresses currently bound to active clients.
* Excluded addresses: Sum of administratively excluded addresses (ip dhcp excluded-address) plus addresses currently held in the DHCP conflict table.
* Pending event: Background database or pool resizing task status (none under normal operation).
* Current index: The next IP address in the sequential allocation pointer that the Cisco IOS DHCP server will attempt to ping and offer.

2. show ip dhcp binding [ip-address]

Displays address bindings created by the Cisco IOS DHCP server.
* Syntax Parameter ip-address: (Optional) Dotted-decimal IPv4 address of a specific client to query.

3. show ip dhcp conflict [ip-address]

Displays address conflicts logged by the Cisco IOS DHCP server when duplicate IP detection triggers.
* Syntax Parameter ip-address: (Optional) Dotted-decimal IPv4 address of a specific conflict entry.

4. show ip dhcp database [url]

Displays recent activity on the external DHCP database agent (such as TFTP, FTP, or NVRAM flash storage used to persist bindings across switch reloads).
* Syntax Parameter url: (Optional) Remote file URL or local flash path (flash:/dhcp-bindings.txt).
* Output Field Definitions:
* Type: Transfer protocol used by the database agent (flash, ftp, tftp, rcp).
* Write delay / Timeout: Configured delay and timeout values in seconds for syncing binding updates to persistent storage.
* Failures / Successes: Cumulative counts of database read/write operations.

Key Takeaway: Pay close attention to the Excluded addresses field definition in show ip dhcp pool—because Cisco IOS combines manual exclusions and detected IP conflicts into this single counter, a higher-than-expected number always warrants checking the conflict table.


Troubleshooting a Full or Non-Responding DHCP Scope

When clients fail to obtain an IP address (169.254.x.x APIPA) or the switch logs %DHCPD-4-PING_CONFLICT, follow this sequential troubleshooting workflow to restore DHCP service.

Step 1: Clear Conflicted IP Addresses to Reclaim Pool Space

When a switch restarts without a persistent DHCP database (ip dhcp database), it forgets previous bindings while connected endpoints still hold their old leases. As the switch attempts to hand out IPs starting from .1, pings succeed against live hosts, rapidly filling the conflict table and exhausting the scope until Leased addresses + Excluded addresses = Total addresses.

Verify the conflict table as covered above, confirm those IPs are not permanently assigned to static servers, and clear the conflicts in Privileged EXEC mode:

! Clear a single IP conflict
Switch# clear ip dhcp conflict 192.168.10.25

! Clear all IP conflicts to immediately return them to the active scope
Switch# clear ip dhcp conflict *

Step 2: Flush Stale or Orphaned DHCP Bindings

In high-turnover environments like guest Wi-Fi networks, a default 24-hour lease timer can lock up all available IPs even after mobile devices have left the building. Release stale leases immediately and shorten the lease timer in configuration mode:

! Clear a specific stale lease or all dynamic leases
Switch# clear ip dhcp binding 192.168.10.88
Switch# clear ip dhcp binding *

! Shorten the scope lease duration (e.g., 0 days, 4 hours, 0 minutes)
Switch# configure terminal
Switch(config)# ip dhcp pool GUEST_WIFI
Switch(config-dhcp)# lease 0 4 0
Switch(config-dhcp)# end

Step 3: Verify Global DHCP Service and Layer 3 VLAN SVI Status

If the pool has plenty of free addresses (Leased + Excluded < Total) and show ip dhcp server statistics shows 0 incoming DHCPDISCOVER packets, check three common configuration blockers:

  1. Global Service Directive: Verify no service dhcp is not present in the running configuration (show running-config | include service dhcp). By default, service dhcp is enabled and hidden from show run, so seeing no service dhcp means the server process is completely disabled. Re-enable it with service dhcp.
  2. SVI Interface State: Run show ip interface brief | include Vlan to confirm the switched virtual interface (interface Vlan<ID>) whose IP resides in the DHCP pool’s network range is up / up. If no physical access ports or trunks carrying that VLAN are active, the SVI stays down / down and cannot process DHCP traffic.
  3. DHCP Snooping Trust: If DHCP Snooping is active on the VLAN (show ip dhcp snooping), ensure internal switch-to-switch trunks are configured with ip dhcp snooping trust so DHCPOFFER packets are not dropped.

Key Takeaway: Over 80% of unexplained “scope full” outages on Cisco switches are caused by accumulated entries in show ip dhcp conflict after a switch reboot rather than actual concurrent client count.


Advanced Enterprise Scenarios: Checking Scopes per VLAN, VRF, Relay, and NX-OS

Enterprise networks rarely use a single flat DHCP pool. Below are answers to the most common questions when verifying complex Layer 3 switch architectures.

How do I check which DHCP scope is mapped to a specific VLAN?

Cisco IOS does not use an explicit vlan command inside ip dhcp pool. Instead, it automatically maps a VLAN to a DHCP scope by matching the IP address and subnet mask of interface Vlan<ID> to the network statement inside the DHCP pool. To check which pool serves a VLAN, run:

Switch# show ip interface brief | include Vlan
Vlan10                 192.168.10.1    YES NVRAM  up                    up
Vlan20                 10.20.0.1       YES NVRAM  up                    up

Then compare the SVI’s subnet (192.168.10.0/24) against show running-config | section ip dhcp pool to identify the matching scope.

How do I verify VRF-aware DHCP scopes and bindings?

When a Layer 3 switch segments routing tables using Virtual Routing and Forwarding (VRF), inspect VRF-specific bindings, conflicts, and pool configurations using the vrf keyword:

! View active DHCP leases inside a specific VRF
Switch# show ip dhcp vrf CORP_VRF binding

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

! Verify the VRF assignment inside the pool configuration
Switch# show running-config | section ip dhcp pool

How can I tell if a VLAN uses a local DHCP scope or a DHCP relay (ip helper-address)?

Check the SVI configuration for the target VLAN:

Switch# show running-config interface Vlan20
interface Vlan20
 ip address 10.20.0.1 255.255.255.0
 ip helper-address 10.100.1.50
end

If ip helper-address <server-ip> is configured under interface Vlan<ID> and there is no local ip dhcp pool with a network 10.20.0.0 255.255.255.0 statement, the switch is acting purely as a DHCP Relay Agent, forwarding client broadcasts as unicast packets to the external DHCP server (10.100.1.50).

How do I check DHCP configuration on a Cisco Nexus (NX-OS) switch?

Unlike Cisco Catalyst IOS/IOS-XE switches, Cisco Nexus switches running NX-OS are designed as data center core/aggregation switches and operate as DHCP relay agents rather than hosting local IOS-style DHCP server scopes. To verify DHCP relay settings and packet counters on NX-OS, run:

Nexus# show ip dhcp relay
Nexus# show running-config dhcp
Nexus# show ip dhcp relay statistics

Key Takeaway: Always inspect the interface Vlan<ID> block first on unfamiliar Layer 3 switches—it immediately reveals the subnet used to match a local pool, any VRF membership (vrf forwarding), or whether requests are relayed externally via ip helper-address.


Comparing IPAM and DHCP Scope Monitoring Tools for Cisco Switches

Relying solely on manual CLI commands makes it easy to miss a scope filling up until users lose connectivity. Third-party IP Address Management (IPAM) and network monitoring platforms poll Cisco switches via SNMP (CISCO-IETF-DHCP-SERVER-MIB) and CLI credentials to track scope utilization and send proactive alerts.

ToolCisco IOS DHCP Integration MethodScope Exhaustion AlertingConflict & Rogue DHCP DetectionBest Fit & Licensing Model
SolarWinds IP Address Manager (IPAM)Native SNMP MIB polling + automated CLI credential polling for IOS/IOS-XECustomizable threshold alerts (e.g., Warning at 80%, Critical at 90%) with automated email/webhook actionsCorrelates ARP/MAC tables with SNMP ping sweeps to flag IP conflicts and rogue DHCP serversMid-to-large enterprises needing unified Cisco, Microsoft, and ISC DHCP management (Commercial / Node-based)
ManageEngine OpUtilsSNMP polling + Switch Port Mapper integration for Cisco Catalyst switchesReal-time scope capacity gauges and threshold-based email/SMS/Syslog alertsBuilt-in Rogue Detection module and automated MAC-to-Switch-Port conflict trackingIT teams seeking cost-effective Cisco switch port + DHCP pool monitoring (Commercial / IP & Port tier)
Infoblox NIOS (Grid / IPAM)API/CLI synchronization or migration from local IOS pools to centralized GridEnterprise-grade predictive capacity forecasting and multi-tier alertingReal-time network discovery with automated quarantine via switch port controlLarge enterprises standardizing distributed branch DHCP into centralized DDI appliances (Commercial / Enterprise)
PRTG Network MonitorCustom SNMP sensors (1.3.6.1.4.1.9.10.102 Cisco DHCP Server MIB) + SSH script sensorsGranular channel limits per subnet with push, email, or Teams/Slack notificationsTracks free vs. leased counters and abnormal spikes in DHCPDECLINE packetsOrganizations wanting lightweight SNMP threshold alerting without full IPAM overhead (Commercial / Sensor-based)
phpIPAM / NetBox (with Custom Pollers)Python/Netmiko or Ansible scheduled scripts parsing show ip dhcp pool & bindingWebhook and email alerts via custom script thresholdsVisualizes documented vs. discovered IPs to highlight undocumented static collisionsDevOps and network automation teams preferring open-source infrastructure-as-code (Open Source / Self-hosted)

Key Takeaway: If you manage more than five Cisco switches acting as local branch DHCP servers, polling CISCO-IETF-DHCP-SERVER-MIB or running scheduled CLI checks through an IPAM tool prevents surprise pool exhaustion without requiring daily manual logins.


Conclusion

Checking a DHCP scope on a Cisco switch follows a clear progression: start with show ip dhcp pool and show running-config | section dhcp to verify capacity and scope options, drill into show ip dhcp binding and show ip dhcp conflict to audit active client leases and IP collisions, and verify SVI or VRF mappings when diagnosing multi-VLAN Layer 3 topologies. Combining these foundational Cisco IOS verification commands with persistent DHCP database storage or automated IPAM threshold alerts ensures your switch scopes remain healthy and responsive.

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

Author

Comments

Write a Reply or Comment

Your email address will not be published.