{"id":24574,"date":"2026-11-17T14:58:40","date_gmt":"2026-11-17T06:58:40","guid":{"rendered":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html"},"modified":"2026-11-17T14:58:40","modified_gmt":"2026-11-17T06:58:40","slug":"how-to-check-dhcp-pool-in-cisco-switch","status":"publish","type":"post","link":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html","title":{"rendered":"How to Check DHCP Pool in Cisco Switch"},"content":{"rendered":"<p>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 <code>show ip dhcp<\/code> 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.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_17 counter-hierarchy counter-decimal ez-toc-light-blue\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" style=\"display: none;\"><i class=\"ez-toc-glyphicon ez-toc-icon-toggle\"><\/i><\/a><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#CLI_Commands_to_Check_DHCP_Pool_Configuration_and_Utilization\" title=\"CLI Commands to Check DHCP Pool Configuration and Utilization\">CLI Commands to Check DHCP Pool Configuration and Utilization<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Example_Output_Template_and_Counter_Breakdown\" title=\"Example Output Template and Counter Breakdown\">Example Output Template and Counter Breakdown<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#How_to_Check_Active_DHCP_Leases_and_IP_Bindings\" title=\"How to Check Active DHCP Leases and IP Bindings\">How to Check Active DHCP Leases and IP Bindings<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_1_Display_the_Full_DHCP_Binding_Table\" title=\"Step 1: Display the Full DHCP Binding Table\">Step 1: Display the Full DHCP Binding Table<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_2_Interpret_the_Client-ID_vs_Hardware_Address_Format\" title=\"Step 2: Interpret the Client-ID vs. Hardware Address Format\">Step 2: Interpret the Client-ID vs. Hardware Address Format<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_3_Filter_Bindings_by_IP_or_MAC_Address\" title=\"Step 3: Filter Bindings by IP or MAC Address\">Step 3: Filter Bindings by IP or MAC Address<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#How_to_Inspect_Excluded_Addresses_and_DHCP_IP_Conflicts\" title=\"How to Inspect Excluded Addresses and DHCP IP Conflicts\">How to Inspect Excluded Addresses and DHCP IP Conflicts<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_1_Verify_Administratively_Excluded_IP_Ranges\" title=\"Step 1: Verify Administratively Excluded IP Ranges\">Step 1: Verify Administratively Excluded IP Ranges<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_2_Check_the_DHCP_Conflict_Log\" title=\"Step 2: Check the DHCP Conflict Log\">Step 2: Check the DHCP Conflict Log<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_3_Identify_the_Conflict_Detection_Method\" title=\"Step 3: Identify the Conflict Detection Method\">Step 3: Identify the Conflict Detection Method<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Verifying_DHCP_Pools_Across_Multiple_VLANs_and_VRFs\" title=\"Verifying DHCP Pools Across Multiple VLANs and VRFs\">Verifying DHCP Pools Across Multiple VLANs and VRFs<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#How_does_a_Cisco_Layer_3_switch_match_a_DHCP_pool_to_a_specific_VLAN\" title=\"How does a Cisco Layer 3 switch match a DHCP pool to a specific VLAN?\">How does a Cisco Layer 3 switch match a DHCP pool to a specific VLAN?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#How_do_I_check_DHCP_bindings_and_conflicts_for_a_specific_VRF\" title=\"How do I check DHCP bindings and conflicts for a specific VRF?\">How do I check DHCP bindings and conflicts for a specific VRF?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#How_do_I_tell_if_a_VLAN_is_using_a_local_switch_DHCP_pool_or_an_external_DHCP_server\" title=\"How do I tell if a VLAN is using a local switch DHCP pool or an external DHCP server?\">How do I tell if a VLAN is using a local switch DHCP pool or an external DHCP server?<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Troubleshooting_an_Exhausted_or_Non-Responding_DHCP_Pool\" title=\"Troubleshooting an Exhausted or Non-Responding DHCP Pool\">Troubleshooting an Exhausted or Non-Responding DHCP Pool<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_1_Audit_DHCP_Server_Packet_and_Memory_Statistics\" title=\"Step 1: Audit DHCP Server Packet and Memory Statistics\">Step 1: Audit DHCP Server Packet and Memory Statistics<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_2_Reclaim_Exhausted_Addresses_by_Clearing_Conflicts_and_Stale_Bindings\" title=\"Step 2: Reclaim Exhausted Addresses by Clearing Conflicts and Stale Bindings\">Step 2: Reclaim Exhausted Addresses by Clearing Conflicts and Stale Bindings<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Step_3_Run_Real-Time_DHCP_Server_Event_Debugging\" title=\"Step 3: Run Real-Time DHCP Server Event Debugging\">Step 3: Run Real-Time DHCP Server Event Debugging<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Cisco_IOS_DHCP_Verification_Command_Reference\" title=\"Cisco IOS DHCP Verification Command Reference\">Cisco IOS DHCP Verification Command Reference<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\/#Conclusion\" title=\"Conclusion\">Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"CLI_Commands_to_Check_DHCP_Pool_Configuration_and_Utilization\"><\/span>CLI Commands to Check DHCP Pool Configuration and Utilization<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>To immediately inspect the configured parameters and real-time capacity counters of all DHCP pools\u2014or a single named pool\u2014run the following commands in Privileged EXEC mode (<code>#<\/code>). Keep prose intervention minimal by copying and adapting the CLI templates below directly into your terminal session.<\/p>\n<pre><code class=\"language-ios\">! 1. View utilization counters and subnet ranges for all DHCP pools\nSwitch# show ip dhcp pool\n\n! 2. View utilization counters for a single specific DHCP pool\nSwitch# show ip dhcp pool &lt;POOL_NAME&gt;\n\n! 3. View the running configuration for all DHCP pools and global DHCP parameters\nSwitch# show running-config | section ip dhcp\n\n! 4. View only the network, gateway, DNS, and lease settings of a specific pool\nSwitch# show running-config | section ip dhcp pool &lt;POOL_NAME&gt;\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Example_Output_Template_and_Counter_Breakdown\"><\/span>Example Output Template and Counter Breakdown<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<pre><code class=\"language-text\">Switch# show ip dhcp pool VLAN10_USERS\n\nPool VLAN10_USERS :\n Utilization mark (high\/low)    : 100 \/ 0\n Subnet size (first\/next)       : 0 \/ 0 \n Total addresses                : 254\n Leased addresses               : 142\n Excluded addresses             : 12\n Pending event                  : none\n 1 subnet is currently in the pool :\n Current index        IP address range                    Leased\/Excluded\/Total\n 192.168.10.155       192.168.10.1     - 192.168.10.254    142   \/ 12     \/ 254\n<\/code><\/pre>\n<pre><code class=\"language-text\">Switch# show running-config | section ip dhcp pool VLAN10_USERS\nip dhcp pool VLAN10_USERS\n network 192.168.10.0 255.255.255.0\n default-router 192.168.10.1 \n dns-server 192.168.10.10 192.168.10.11 \n domain-name corp.example.com\n lease 0 8\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> Always compare <code>Total addresses<\/code> against the sum of <code>Leased addresses<\/code> and <code>Excluded addresses<\/code> in <code>show ip dhcp pool<\/code> to calculate how many usable IPs remain before the subnet reaches exhaustion.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"How_to_Check_Active_DHCP_Leases_and_IP_Bindings\"><\/span>How to Check Active DHCP Leases and IP Bindings<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>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&#8217;s DHCP binding database.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Display_the_Full_DHCP_Binding_Table\"><\/span>Step 1: Display the Full DHCP Binding Table<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>From Privileged EXEC mode, run the <code>show ip dhcp binding<\/code> command to list every active IP lease currently maintained by the switch:<\/p>\n<pre><code class=\"language-ios\">Switch# show ip dhcp binding\nBindings from all pools not associated with VRF:\nIP address          Client-ID\/              Lease expiration        Type\n                    Hardware address\/\n                    User name\n192.168.10.21       0100.5056.9a3b.1c       Nov 18 2026 02:14 PM    Automatic\n192.168.10.22       001b.6384.45e6          Nov 18 2026 03:40 PM    Automatic\n192.168.10.50       01a4.83e7.1120.9f       Infinite                Manual\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Interpret_the_Client-ID_vs_Hardware_Address_Format\"><\/span>Step 2: Interpret the Client-ID vs. Hardware Address Format<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Examine the second column carefully when matching a lease to a physical device:<br \/>\n* <strong>14-character hex string (starting with <code>01<\/code>):<\/strong> Indicates the client included a DHCP Option 61 Client-Identifier in its request. The leading <code>01<\/code> represents the Ethernet media type, and the remaining 12 hex characters (<code>0050.569a.3b1c<\/code>) represent the device&#8217;s actual MAC address.<br \/>\n* <strong>12-character hex string:<\/strong> Indicates the client did not send a Client-ID option, so the switch recorded the raw Layer 2 Hardware (MAC) address directly.<br \/>\n* <strong>Type (<code>Automatic<\/code> vs. <code>Manual<\/code>):<\/strong> <code>Automatic<\/code> indicates a dynamically leased IP with a finite expiration timestamp, whereas <code>Manual<\/code> indicates a static DHCP reservation (<code>host<\/code> statement) with an <code>Infinite<\/code> lease.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Filter_Bindings_by_IP_or_MAC_Address\"><\/span>Step 3: Filter Bindings by IP or MAC Address<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>On switches managing hundreds of endpoints, pipe the output or specify an IP address directly to isolate a single client:<\/p>\n<pre><code class=\"language-ios\">! Check the binding details for one specific IP address\nSwitch# show ip dhcp binding 192.168.10.21\n\n! Search for a lease using the last four hex digits of a client MAC address\nSwitch# show ip dhcp binding | include 3b.1c\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> 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 <code>01<\/code> Client-ID prefixes do not cause missed matches.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"How_to_Inspect_Excluded_Addresses_and_DHCP_IP_Conflicts\"><\/span>How to Inspect Excluded Addresses and DHCP IP Conflicts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In the <code>show ip dhcp pool<\/code> output covered earlier, the <code>Excluded addresses<\/code> 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.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Verify_Administratively_Excluded_IP_Ranges\"><\/span>Step 1: Verify Administratively Excluded IP Ranges<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Check the running configuration for <code>ip dhcp excluded-address<\/code> statements. These commands reserve static IP blocks (such as SVI gateways, printers, and servers) so the DHCP server never assigns them:<\/p>\n<pre><code class=\"language-ios\">Switch# show running-config | include excluded-address\nip dhcp excluded-address 192.168.10.1 192.168.10.10\nip dhcp excluded-address 192.168.10.250 192.168.10.254\n<\/code><\/pre>\n<p>In this example, 15 addresses (<code>1\u201310<\/code> and <code>250\u2013254<\/code>) are intentionally excluded by the administrator.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Check_the_DHCP_Conflict_Log\"><\/span>Step 2: Check the DHCP Conflict Log<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the <code>Excluded addresses<\/code> counter in <code>show ip dhcp pool<\/code> exceeds your configured static exclusions, inspect the DHCP conflict table:<\/p>\n<pre><code class=\"language-ios\">Switch# show ip dhcp conflict\nIP address        Detection method   Detection time          VRF\n192.168.10.25     Ping               Nov 16 2026 09:12 AM\n192.168.10.26     Gratuitous ARP     Nov 16 2026 11:45 AM\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Identify_the_Conflict_Detection_Method\"><\/span>Step 3: Identify the Conflict Detection Method<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>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:<br \/>\n* <strong>Ping:<\/strong> 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 <code>Ping<\/code> conflict.<br \/>\n* <strong>Gratuitous ARP:<\/strong> 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 <code>DHCPDECLINE<\/code> packet back to the switch, which logs a <code>Gratuitous ARP<\/code> conflict.<\/p>\n<p><strong>Key Takeaway:<\/strong> Any IP listed in <code>show ip dhcp conflict<\/code> 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.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Verifying_DHCP_Pools_Across_Multiple_VLANs_and_VRFs\"><\/span>Verifying DHCP Pools Across Multiple VLANs and VRFs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>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.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_does_a_Cisco_Layer_3_switch_match_a_DHCP_pool_to_a_specific_VLAN\"><\/span>How does a Cisco Layer 3 switch match a DHCP pool to a specific VLAN?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>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 (<code>interface Vlan&lt;ID&gt;<\/code>) against the <code>network<\/code> statement configured inside each <code>ip dhcp pool<\/code>. To verify which VLAN a pool serves, compare <code>show ip interface brief<\/code> against the pool&#8217;s network range:<\/p>\n<pre><code class=\"language-ios\">Switch# show ip interface Vlan10 | include Internet address\n  Internet address is 192.168.10.1\/24\n<\/code><\/pre>\n<p>Because <code>Vlan10<\/code> uses <code>192.168.10.1\/24<\/code>, any DHCP broadcast arriving on VLAN 10 is automatically served by the pool configured with <code>network 192.168.10.0 255.255.255.0<\/code>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_check_DHCP_bindings_and_conflicts_for_a_specific_VRF\"><\/span>How do I check DHCP bindings and conflicts for a specific VRF?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If your DHCP pools are segmented across VRFs, the standard <code>show ip dhcp binding<\/code> command only displays non-VRF (global routing table) leases. Append the <code>vrf<\/code> keyword to inspect leases or conflicts inside a specific VRF instance:<\/p>\n<pre><code class=\"language-ios\">! View active DHCP bindings inside a specific VRF\nSwitch# show ip dhcp binding vrf GUEST_VRF\n\n! View IP conflicts recorded inside a specific VRF\nSwitch# show ip dhcp conflict vrf GUEST_VRF\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_tell_if_a_VLAN_is_using_a_local_switch_DHCP_pool_or_an_external_DHCP_server\"><\/span>How do I tell if a VLAN is using a local switch DHCP pool or an external DHCP server?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Inspect the SVI configuration for a DHCP relay agent (<code>ip helper-address<\/code>). Run <code>show ip interface Vlan&lt;ID&gt; | include Helper<\/code> to check:<\/p>\n<pre><code class=\"language-ios\">Switch# show ip interface Vlan20 | include Helper\n  Helper address is 10.100.1.50\n<\/code><\/pre>\n<p>If a Helper address is present and no local <code>ip dhcp pool<\/code> matches that SVI&#8217;s subnet, the switch is relaying DHCP broadcasts to the external server rather than allocating addresses locally.<\/p>\n<p><strong>Key Takeaway:<\/strong> Always confirm that the SVI IP address falls within the exact subnet defined in the pool&#8217;s <code>network<\/code> statement, and use the <code>vrf &lt;VRF_NAME&gt;<\/code> flag whenever auditing multi-tenant Layer 3 switches.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Troubleshooting_an_Exhausted_or_Non-Responding_DHCP_Pool\"><\/span>Troubleshooting an Exhausted or Non-Responding DHCP Pool<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When endpoints fall back to APIPA addresses (<code>169.254.x.x<\/code>) despite an active DHCP configuration on the switch, follow this diagnostic sequence to identify bottlenecks and restore IP allocation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Audit_DHCP_Server_Packet_and_Memory_Statistics\"><\/span>Step 1: Audit DHCP Server Packet and Memory Statistics<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Verify whether client requests are actually reaching the switch CPU and whether the switch is attempting to respond by checking the global server statistics:<\/p>\n<pre><code class=\"language-ios\">Switch# show ip dhcp server statistics\nMemory usage         42912\nAddress pools        3\nDatabase agents      0\nAutomatic bindings   142\nManual bindings      1\nExpired bindings     8\nMalformed messages   0\nSecure arp entries   0\n\nMessage              Received\nBOOTREQUEST          0\nDHCPDISCOVER         1540\nDHCPREQUEST          1482\nDHCPDECLINE          2\nDHCPRELEASE          310\nDHCPINFORM           85\n\nMessage              Sent\nBOOTREPLY            0\nDHCPOFFER            1490\nDHCPACK              1480\nDHCPNAK              2\n<\/code><\/pre>\n<ul>\n<li><strong>If <code>DHCPDISCOVER<\/code> is not incrementing:<\/strong> Client broadcasts are not reaching the Layer 3 SVI. Check that the VLAN exists in <code>show vlan brief<\/code>, the SVI is <code>up\/up<\/code>, and the global <code>service dhcp<\/code> command has not been disabled (<code>no service dhcp<\/code>).<\/li>\n<li><strong>If <code>DHCPDISCOVER<\/code> increments but <code>DHCPOFFER<\/code> stays flat:<\/strong> 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.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Reclaim_Exhausted_Addresses_by_Clearing_Conflicts_and_Stale_Bindings\"><\/span>Step 2: Reclaim Exhausted Addresses by Clearing Conflicts and Stale Bindings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>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:<\/p>\n<pre><code class=\"language-ios\">! Clear a single conflicted IP or all conflicted IPs (*)\nSwitch# clear ip dhcp conflict 192.168.10.25\nSwitch# clear ip dhcp conflict *\n\n! Clear a specific stale lease or reset all dynamic bindings (*)\nSwitch# clear ip dhcp binding 192.168.10.21\nSwitch# clear ip dhcp binding *\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Run_Real-Time_DHCP_Server_Event_Debugging\"><\/span>Step 3: Run Real-Time DHCP Server Event Debugging<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>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 <code>terminal monitor<\/code> first to display console log messages in your session.)<\/p>\n<pre><code class=\"language-ios\">Switch# debug ip dhcp server events\nSwitch# terminal monitor\n<\/code><\/pre>\n<p>Look for explicit diagnostic log lines when a client attempts to connect:<br \/>\n* <code>DHCPD: there is no address pool for 192.168.30.1<\/code> \u2014 Indicates the SVI IP (<code>192.168.30.1<\/code>) has no matching <code>network<\/code> statement in any configured DHCP pool.<br \/>\n* <code>DHCPD: pool VLAN10_USERS is empty<\/code> \u2014 Confirms all usable addresses in the pool are currently leased or locked in the conflict table.<\/p>\n<p>Immediately disable debugging once you capture the output:<\/p>\n<pre><code class=\"language-ios\">Switch# undebug all\n<\/code><\/pre>\n<p><strong>Key Takeaway:<\/strong> Checking <code>show ip dhcp server statistics<\/code> alongside <code>debug ip dhcp server events<\/code> quickly isolates whether a failure stems from Layer 2\/SVI reachability, a missing subnet statement, or complete pool exhaustion caused by accumulated conflict entries.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Cisco_IOS_DHCP_Verification_Command_Reference\"><\/span>Cisco IOS DHCP Verification Command Reference<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>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 <em>Cisco IOS IP Addressing Services Command Reference<\/em>.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Command Syntax<\/th>\n<th style=\"text-align: left;\">Command Mode<\/th>\n<th style=\"text-align: left;\">Primary Function &amp; Key Output Fields<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>show ip dhcp pool [name]<\/code><\/td>\n<td style=\"text-align: left;\">User EXEC (<code>&gt;<\/code>) or Privileged EXEC (<code>#<\/code>)<\/td>\n<td style=\"text-align: left;\">Displays pool subnet ranges and capacity counters.<br \/>\u2022 <strong>Utilization mark (high\/low):<\/strong> Threshold percentages configured for SNMP\/syslog pool utilization alerts.<br \/>\u2022 <strong>Current index:<\/strong> The next IP address the server will attempt to allocate.<br \/>\u2022 <strong>Leased\/Excluded\/Total:<\/strong> Breakdown of active leases, unavailable (excluded + conflicted) IPs, and total subnet capacity.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>show ip dhcp binding [ip-address] [vrf vrf-name]<\/code><\/td>\n<td style=\"text-align: left;\">User EXEC (<code>&gt;<\/code>) or Privileged EXEC (<code>#<\/code>)<\/td>\n<td style=\"text-align: left;\">Displays MAC-to-IP address lease records.<br \/>\u2022 <strong>Client-ID\/Hardware address:<\/strong> Option 61 identifier or Layer 2 MAC address.<br \/>\u2022 <strong>Lease expiration:<\/strong> Date and time the lease expires, or <code>Infinite<\/code> for manual reservations.<br \/>\u2022 <strong>Type:<\/strong> <code>Automatic<\/code> (dynamic pool allocation) or <code>Manual<\/code> (static host binding).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>show ip dhcp conflict [ip-address] [vrf vrf-name]<\/code><\/td>\n<td style=\"text-align: left;\">User EXEC (<code>&gt;<\/code>) or Privileged EXEC (<code>#<\/code>)<\/td>\n<td style=\"text-align: left;\">Lists IP addresses withheld from allocation due to duplicate IP detection.<br \/>\u2022 <strong>Detection method:<\/strong> <code>Ping<\/code> (detected by switch prior to offer) or <code>Gratuitous ARP<\/code> (declined by client).<br \/>\u2022 <strong>Detection time:<\/strong> Timestamp when the conflict occurred.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>show ip dhcp server statistics [type-number]<\/code><\/td>\n<td style=\"text-align: left;\">User EXEC (<code>&gt;<\/code>) or Privileged EXEC (<code>#<\/code>)<\/td>\n<td style=\"text-align: left;\">Displays cumulative memory consumption, binding counts, and transmitted\/received DHCP packet counters (<code>DHCPDISCOVER<\/code>, <code>DHCPOFFER<\/code>, <code>DHCPREQUEST<\/code>, <code>DHCPACK<\/code>, <code>DHCPNAK<\/code>, <code>DHCPDECLINE<\/code>).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>show ip dhcp database [url]<\/code><\/td>\n<td style=\"text-align: left;\">Privileged EXEC (<code>#<\/code>)<\/td>\n<td style=\"text-align: left;\">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.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Key Takeaway:<\/strong> Use User EXEC or Privileged EXEC mode for read-only pool and binding verification, and verify <code>show ip dhcp database<\/code> on production switches to confirm lease bindings are backed up to flash or an external server across reboots.<\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Checking a DHCP pool on a Cisco switch comes down to correlating three core views: overall pool capacity (<code>show ip dhcp pool<\/code>), active client leases (<code>show ip dhcp binding<\/code>), and withheld addresses (<code>show ip dhcp conflict<\/code> and <code>excluded-address<\/code> configurations). By combining these verification commands with VRF filters and packet statistics (<code>show ip dhcp server statistics<\/code>), network administrators can accurately monitor subnet utilization, track endpoint MAC mappings, and resolve pool exhaustion before it impacts network connectivity.<\/p>\n<div class='sfsi_Sicons' style='width: 100%; display: inline-block; vertical-align: middle; text-align:left'><div style='margin:0px 8px 0px 0px; line-height: 24px'><span>Please follow and like us:<\/span><\/div><div class='sfsi_socialwpr'><div class='sf_fb_share sf_icon' style='text-align:left;vertical-align: middle;'><a href='https:\/\/www.facebook.com\/sharer\/sharer.php?u=https%3A%2F%2Fcciedump.spoto.net%2Fblog%2Fhow-to-check-dhcp-pool-in-cisco-switch_24574.html' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Facebook Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/fbshare_bck.png'  \/><\/a><\/div><div class='sf_twiter sf_icon' style='display: inline-block;vertical-align: middle;width: auto;margin-left: 7px;'>\r\n\t\t\t\t\t\t<a target='_blank' href='https:\/\/twitter.com\/intent\/tweet?text=How+to+Check+DHCP+Pool+in+Cisco+Switch+https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html'style='display:inline-block' >\r\n\t\t\t\t\t\t\t<img data-pin-nopin= true width='auto' class='sfsi_wicon' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/en_US_Tweet.svg' alt='Tweet' title='Tweet' >\r\n\t\t\t\t\t\t<\/a>\r\n\t\t\t\t\t<\/div><div class='sf_pinit sf_icon' style='text-align:left;vertical-align: middle;float:left;line-height: 33px;width:auto;margin: 0 -2px;'><a href='#'  onclick='sfsi_pinterest_modal_images(event,\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\",\"How to Check DHCP Pool in Cisco Switch\")' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Pin Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/share_icons\/Pinterest_Save\/en_US_save.svg'  \/><\/a><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>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&#8230; &raquo; <a class=\"read-more-link\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\">read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,608],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v18.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog\" \/>\n<meta property=\"og:description\" content=\"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... &raquo; read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\" \/>\n<meta property=\"og:site_name\" content=\"SPOTO Official Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T06:58:40+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"SPOTO \u7f16\u8f91\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\",\"name\":\"SPOTO Club\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"caption\":\"SPOTO Club\"},\"logo\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\"},\"description\":\"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205\",\"sameAs\":[\"https:\/\/cciedump.spoto.net\/\"]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/\",\"name\":\"SPOTO Official Blog\",\"description\":\"Focus on Online IT Training for 20+ Years\",\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\",\"name\":\"How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\"},\"datePublished\":\"2026-11-17T06:58:40+00:00\",\"dateModified\":\"2026-11-17T06:58:40+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cciedump.spoto.net\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Check DHCP Pool in Cisco Switch\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage\"},\"author\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\"},\"headline\":\"How to Check DHCP Pool in Cisco Switch\",\"datePublished\":\"2026-11-17T06:58:40+00:00\",\"dateModified\":\"2026-11-17T06:58:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage\"},\"wordCount\":1533,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"articleSection\":[\"CCNA Certification\",\"Cisco Certification\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\",\"name\":\"SPOTO \u7f16\u8f91\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"caption\":\"SPOTO \u7f16\u8f91\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html","og_locale":"en_US","og_type":"article","og_title":"How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog","og_description":"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... &raquo; read more","og_url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html","og_site_name":"SPOTO Official Blog","article_published_time":"2026-11-17T06:58:40+00:00","twitter_card":"summary_large_image","twitter_misc":{"Written by":"SPOTO \u7f16\u8f91","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Person","Organization"],"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638","name":"SPOTO Club","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","caption":"SPOTO Club"},"logo":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo"},"description":"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205","sameAs":["https:\/\/cciedump.spoto.net\/"]},{"@type":"WebSite","@id":"https:\/\/cciedump.spoto.net\/blog\/#website","url":"https:\/\/cciedump.spoto.net\/blog\/","name":"SPOTO Official Blog","description":"Focus on Online IT Training for 20+ Years","publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage","url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html","name":"How to Check DHCP Pool in Cisco Switch - SPOTO Official Blog","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#website"},"datePublished":"2026-11-17T06:58:40+00:00","dateModified":"2026-11-17T06:58:40+00:00","breadcrumb":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cciedump.spoto.net\/blog"},{"@type":"ListItem","position":2,"name":"How to Check DHCP Pool in Cisco Switch"}]},{"@type":"Article","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#article","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage"},"author":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1"},"headline":"How to Check DHCP Pool in Cisco Switch","datePublished":"2026-11-17T06:58:40+00:00","dateModified":"2026-11-17T06:58:40+00:00","mainEntityOfPage":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#webpage"},"wordCount":1533,"commentCount":0,"publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"articleSection":["CCNA Certification","Cisco Certification"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-dhcp-pool-in-cisco-switch_24574.html#respond"]}]},{"@type":"Person","@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1","name":"SPOTO \u7f16\u8f91","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","caption":"SPOTO \u7f16\u8f91"}}]}},"_links":{"self":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24574"}],"collection":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/comments?post=24574"}],"version-history":[{"count":0,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24574\/revisions"}],"wp:attachment":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/media?parent=24574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/categories?post=24574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/tags?post=24574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}