Ever unboxed a brand-new, factory-sealed Cisco device only to find it’s already registered to another organization? Here’s the real-world breakdown of why this frustrating licensing nightmare happens and three solid ways to fix it, from a quick CLI command to the nuclear option.

“New” Cisco Gear, Old Problems: Un-haunting Your Smart Licensing

It’s 1 AM on a Saturday. We’re in the middle of a critical network cutover for our new prod-db-cluster. Everything is racked, stacked, and cabled. The final step is to light up the new Catalyst 9300 core switches. I plug in my console cable, power them on, and start running through our config template. Then I hit the licensing part. show license status… “Registration: REGISTERED – SPECIFIC LICENSE RESERVATION”. To some random company I’ve never heard of. On a device that was, I swear, sealed in a brand-new Cisco box an hour ago. My stomach just dropped. A “net new” purchase just derailed our entire maintenance window. If you’ve felt that pain, trust me, you’re not alone.

So, What’s Actually Happening Here?

Let’s get one thing straight: this isn’t usually a case of you getting used gear sold as new. More often than not, this is a ghost in the Cisco Smart Licensing machine. The root cause is typically tied to Cisco’s “Device-Led Conversion” (DLC) process. A device might have been used for a demo, a proof-of-concept, or was an internal unit at a distributor. It gets registered to some account, then returned to the supply chain. When it’s supposed to be wiped and reset for resale, that license registration token sometimes “sticks” in Cisco’s backend database, even if the device config itself is clean. So when your new device boots up and phones home to Cisco’s licensing portal, the portal sees its serial number and says, “Oh, I know you! You belong to ‘SomeCorp Demo Account’.” It then slaps that old registration right back onto your supposedly new hardware.

How to Exorcise the Licensing Ghost

You’re in the middle of a deployment and don’t have time for a lengthy support call. I get it. Here are the three ways I’ve personally dealt with this, ranging from a quick fix to a full reset.

Solution 1: The Quick and Dirty CLI Dance

This is my go-to first step. It’s the equivalent of a forced “log out, log back in” and solves the problem about 80% of the time. You’re essentially telling the device to forcibly de-register itself from whatever account it thinks it belongs to, and then you re-register it with a new token from your organization’s Smart Account.

First, get on the device’s command line:

switch# license smart deregister
switch# license smart register idtoken <YOUR_TOKEN_FROM_YOUR_SMART_ACCOUNT>

Pro Tip: Wait a good 5-10 minutes after running the deregister command before you try to register it again. Sometimes the backend needs a moment to catch up. If you do it too fast, you’ll often get an error and have to start over.

Solution 2: The “By The Book” TAC Case

If the CLI dance fails, or if you prefer to have an official paper trail, opening a Cisco TAC case is the “correct” way to fix this. It’s slower, but it ensures that Cisco cleans up the association on their end, which can prevent future headaches if the device is ever factory reset.

This is your best bet when the device stubbornly refuses to deregister. The TAC engineer can manually release the serial number from the old account in their backend systems, freeing it up for you to claim. You’ll need to provide:

• The device serial number (show version or show inventory)
• Your Sales Order (SO) number as proof of purchase
• Your Smart Account and Virtual Account domain names

Warning: This is not a fast process. It can take anywhere from a few hours to a day, depending on the TAC engineer’s workload and the complexity of the issue. Don’t rely on this if you’re in the middle of a late-night cutover.

Solution 3: The “Nuclear” Factory Reset

Okay, you’ve tried everything else. The device won’t deregister, and you can’t wait for TAC. There is a last resort, but use it with extreme caution. This command will completely wipe all licensing information, including any Specific License Reservation (SLR) or other entitlements on the device. It brings it back to a true factory-default licensing state.

switch# license smart factory reset

After running this and rebooting the device, it will be in a completely unregistered state. You can then proceed with the normal registration process using your Smart Account token. I’ve had to use this on stubborn devices that were part of a complex demo setup and just wouldn’t let go of their old identity.

CRITICAL WARNING: This is a destructive command for licensing. Do not run this on a production device that is correctly licensed. It will remove its entitlements and potentially cause an outage. Only use this on a “new” device during initial setup when all else has failed.

Final Thoughts

Running into a pre-registered device is incredibly frustrating, but it’s almost always fixable. Start with the quick CLI commands, escalate to TAC if you have the time and need it done “by the book,” and keep the factory reset in your back pocket for those true emergencies. This is one of those annoying “in the trenches” problems that you won’t find in a textbook, but now you know exactly how to handle it.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions