Claimed MS225-48 switch

[Lazyllama]

I bought an Cisco MS225-48 secondhand and since It's pre-owned by a company, they already have it claimed on Meriki and therefor I get an error when trying to claim it on my Meriaki org. Is this something that can be resolved, or are they only for one specific user? I have no clue who the first owner of the switch was so contacting them isn't possible.

[TyShawn]

If you brought it from eBay you can contact the seller and let them know about the issue. From there you could file a claim with eBay to help resolve the issue. If you didn't use some kind of protected site to do this transaction you're out of luck unless the seller can release the switch.

To save you the time support will not be able to help in this case. If you were the original buyer sale could have helped you here, but since that isn't the case you are left with very few options. 

[DarrenOC]

Unless you can get the original owner to release from their dashboard then I’m afraid you’ve purchased an expensive doorstop.

[PhilipDAth]

Also note you will need to buy a licence for the MS224-48 to make it work (if and once you resolve the ownership issue).

[Lazyllama]

I'm in good contact with the seller and It's a protected transaction so no worries there. Is is there any way to make the switch work like a normal switch without the management? Seems like half the ports on the switch are disabled. Rest of them work like normal. I'm in no need to use the meriaki dashboard at all. Just thought 50$ for a 48P switch with 4 SFP+ ports was a pretty good deal. Thanks!

[DarrenOC]

Nope, you need to get the device registered to the cloud.  It simply won’t work any other way

[DarrenOC]

Even if you tried a factory reset on the device it’s simply going to keep on popping up in the owners dashboard and re-downloading its config from there.

[TyShawn]

TLDR = No

The focus of Meraki is a cloud based networking solution. Some vendors (including Cisco) does have a local control system, but Meraki is pure cloud control for the moment. 

[Ryan_Miles · Accepted solution]

Others have already given the answer. Just providing the official stance here as well for archival purposes as this question tends to arise often.

https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Cisco_Meraki_Devices_p...

[TyShawn]

@Ryan_Miles - It wouldn't hurt to pin a post on this topic as it comes up often enough that it could help curve repeat posts, unless the mods are using these posts to help with the forums count ;).

[Ryan_Miles]

Yeah I was already looking into if a pinned post would help. That's only effective if folks actually see them which depending on what forum they're in they may not or they may simply overlook any pinned posts regardless. 

[DarrenOC]

I don’t believe a pinned post would work as you’ve stated - it wouldn’t get read.

[Ryan_Miles]

Agreed. The doc link is probably the best reference and when this gets asked next time folks should just link to that instead of a long thread of everyone explaining what's already documented 😉

[Lazyllama]

Managed to get it working by blocking the device on UniFi and resetting it leaving it in a state without the set config. This makes it work like a normal switch. Is there any downside to using it like this? Don't think I will have much luck finding another 48P switch for the same price.

[DarrenOC]

Only downside is having to manage the device manually via the mgmt port.  It’ll continue to work but if it hits the cloud again then it’ll download its config from there and you’ll have to factory reset again.

Obvs also no support, warranty, entitlement to software upgrades