HowToFixMe
Catalyst Switch Configuration

How to configure DHCP snooping on Cisco Catalyst 2960X

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

⚡ At a glance
SectionCatalyst Switch Configuration
SubjectHow to configure DHCP snooping on Cisco Catalyst 2960X
Skill levelIntermediate (CCNA / CCNP background recommended)
DIY-able?Yes if you have CLI access and a maintenance window.

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.

Enable DHCP snooping to stop rogue DHCP servers.

Step-by-step CLI commands

enable
configure terminal
ip dhcp snooping
ip dhcp snooping vlan 10,20,30
no ip dhcp snooping information option
interface GigabitEthernet1/0/24
 ip dhcp snooping trust
end

How to verify

show running-config
show vlan brief
show interface status

Common issues

| Issue | Fix |

|---|---|

| Command rejected | Check you're in the correct mode (# for privileged EXEC, (config)# for global config). |

| Configuration disappears after reload | Confirm write memory (or copy run start) was issued before reload. |

| Counters show drops | Check the related show command for the subsystem and inspect mismatched neighbour settings. |

Frequently asked questions

Will this configuration survive a reload?

Only after write memory (or copy running-config startup-config). On IOS-XE devices in install mode, the install commit is also required.

Is this safe to apply on a production network?

Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.

Where can I find the Cisco official documentation?

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

Which IOS / IOS-XE version does this apply to?

The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax, check ? in the CLI.

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 this device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the affected device fix goes cleanly:

How to confirm it's actually fixed

On this hardware, the test is rarely "reboot and see". Use this list:

Escalation guide

For this device, the right escalation depends on impact:

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.

Should I update firmware first or last?

Update firmware first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Will this void my warranty?

Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.

Field notes from real incidents on How to configure DHCP snooping on Cisco Catalyst 2960X

When I work on configure DHCP snooping on Cisco Catalyst 2960X the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Cisco bug search tool is the cheapest sanity check before a config change: search the symptom, sort by affected releases, decide. 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.

The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. 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 configure DHCP snooping on Cisco Catalyst 2960X on How to configure DHCP snooping on Cisco Catalyst 2960X the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with show platform hardware capacity because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show interfaces counters errors, packet capture on the ingress interface (TAC will ask for it), show tech-support (capture for TAC), ping vrf <vrf> <target>, and finally to show logging last 200 only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on How to configure DHCP snooping on Cisco Catalyst 2960X 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 configure DHCP snooping on Cisco Catalyst 2960X resolved on a How to configure DHCP snooping on Cisco Catalyst 2960X 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 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

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 spanning-tree summary  # confirm topology stability

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 How to configure DHCP snooping on Cisco Catalyst 2960X detail, the disambiguation order I lean on is stable across products and across years. Cisco TAC case knowledge base is where I start for the ground-truth view. cisco.com/c/en/us/td/docs/ios-xml for IOS XR 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 configure DHCP snooping on Cisco Catalyst 2960X is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on configure DHCP snooping on Cisco Catalyst 2960X have a habit of biting back. The pitfalls below are the ones I have personally walked into on a How to configure DHCP snooping on Cisco Catalyst 2960X unit, not things I read about. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide. Most catalyst stack issues I have triaged were power-budget related, not software: the show power detail output answers it in 5 seconds. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. 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 configure DHCP snooping on Cisco Catalyst 2960X off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on How to configure DHCP snooping on Cisco Catalyst 2960X - 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 configure DHCP snooping on Cisco Catalyst 2960X on a How to configure DHCP snooping on Cisco Catalyst 2960X 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 configuration survive a reload?

Only after `write memory` (or `copy running-config startup-config`). On IOS-XE devices in install mode, the install commit is also required.

Is this safe to apply on a production network?

Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.

Where can I find the Cisco official documentation?

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

Which IOS / IOS-XE version does this apply to?

The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax, check `?` in the CLI.