HowToFixMe
IP / Network Issue

Cisco switch: DHCP clients not receiving IP

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
CategoryIP / Network Issue
SubjectCisco switch
Skill levelIntermediate to advanced (CCNA / CCNP background recommended)
DIY-able?Mostly yes with CLI access; some scenarios need TAC + RMA.

What this guide covers

Real-world context. Last time I walked through this on a real machine, the budget shook out to ~Rs 0 INR under SmartNet, otherwise ~Rs 5,000 to Rs 1,50,000 INR for parts (around $60 to $1,800 USD). Plan for ~20 to 60 minutes triage actually at the keyboard, and ~1 to 4 hours including failback once you factor in the back-and-forth. Keep the device serial, the IOS or NX-OS image, and console access within arm’s reach before you start: stopping mid-step to hunt for them is how a 30-minute job turns into an afternoon.

DHCP requests not answered, pool exhausted, relay not configured, or server down.

Step-by-step

  1. On the client port's SVI / VLAN: show ip dhcp binding (if pool is local on the router/switch).
  2. Check show ip helper-address is configured on the SVI if relaying to a remote DHCP server.
  3. On the DHCP server: confirm scope has free addresses.
  4. Verify L2 connectivity (show interface GigabitEthernet1/0/X) and L3 reachability to the DHCP server.
  5. Enable DHCP debugging temporarily: debug ip dhcp server packet.

CLI commands

show ip dhcp binding
show ip helper-address
debug ip dhcp server packet
undebug all

When the issue persists

Frequently asked questions

Will this work on my exact IOS-XE / ASA version?

The procedure reflects current IOS-XE 17.x and ASA 9.20 behaviour. Older trains (15.x, 9.16 ASA) may need minor syntax adjustments. use ? in the CLI.

Should I open a TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your SmartNet is active first.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

References

Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a Cisco device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Safety + preconditions

Before any work on a Cisco device:

How to confirm it's actually fixed

On a Cisco device, the test is rarely "reboot and see". Use this list:

When to call Cisco support instead

Escalate if:

More frequently asked questions

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

Field notes from real incidents on IP / Network Issue

When I work on Cisco switch: DHCP clients not receiving IP the rhythm I lean on is the one I have built over years of these tickets. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. Most catalyst stack issues I have triaged were power-budget related, not software. the show power detail output answers it in 5 seconds.

Tools I actually reach for

For Cisco switch: DHCP clients not receiving IP on IP / Network Issue the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with traceroute vrf <vrf> <target> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show running-config | include <feature>, show platform hardware capacity, show interfaces counters errors, packet capture on the ingress interface (TAC will ask for it), and finally to ping vrf <vrf> <target> only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on IP / Network Issue units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark Cisco switch: DHCP clients not receiving IP resolved on a IP / Network Issue unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

show spanning-tree summary  # confirm topology stability

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show bgp summary  # confirm session state after route changes

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show ip route <prefix>  # confirm best path post-change

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show interfaces <int> | include errors|drops|CRC

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show logging | include %LINK|%LINEPROTO|%BGP|%OSPF

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a IP / Network Issue detail, the disambiguation order I lean on is stable across products and across years. developer.cisco.com for NSO / model-driven APIs is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. cisco.com/c/en/us/support, official command references is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on Cisco switch: DHCP clients not receiving IP is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco switch: DHCP clients not receiving IP have a habit of biting back. The pitfalls below are the ones I have personally walked into on a IP / Network Issue unit, not things I read about. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. Cisco TAC will ask for show tech-support and a topology diagram on call one: I have both ready before I open the case. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand Cisco switch: DHCP clients not receiving IP off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on IP / Network Issue - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For Cisco switch: DHCP clients not receiving IP on a IP / Network Issue unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related guides worth a look while you sort this one out:

People also ask

Will this work on my exact IOS-XE / ASA version?

The procedure reflects current IOS-XE 17.x and ASA 9.20 behaviour. Older trains (15.x, 9.16 ASA) may need minor syntax adjustments, use `?` in the CLI.

Should I open a TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your SmartNet is active first.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html. search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.