Cannot register C9300-48T for conversion to management

Solved
thomasthomsen
Kind of a big deal

Cannot register C9300-48T for conversion to management

I have a colleague that has run into a strange issue.

When trying to convert a C9300 to managed mode the switch gives this error on registration.

 

Switch#show meraki comp
Switch# SKU Bootloader Version
----------------------------------------------------------------------------------------------
1 C9300-48T - Compatible 17.12.1r - Compatible

 

 

Switch#service meraki register
% Health Check Warning: Switch 1 PowerSupply 0 State is No Input Power
Please use show environment power all exec CLI to get more details
% Are you sure you want to continue? [no]: yes
Starting to register switch 1
Converting catalyst.meraki.com to 158.115.128.76
Successfully connect to Meraki Dashboard
Error: Received failed respose from Meraki Dashboard!!!
(Message Response: HTTP/1.1 400 Bad Request
[{"mac":"<mac-address>","error":"Product type is not supported","status":"FAILURE"}]

 

 

My only thought was that it might be the NM module, but the NM module is a C9300-NM-8X, but as you can see it does not show up in the "show meraki comp" output.
Switch is running 17.12.4, and the config has been erased, so it does just have the basic config required for converting. have anyone else seen this issue ?

 

Thanks

Thomas

 

1 Accepted Solution

lol .. downgrading to 17.12.1 solved the problem.

wtf.

View solution in original post

6 Replies 6
thomasthomsen
Kind of a big deal

Just tried on another C9300-24T , without a NM but same IOS-XE 17.12.4, same error.

 

Could this be because the switch is running newer software 17.12.4 then the dashboard that runs C9300 switches as 17.12.3 as the latest ? - Just wondering.

Downgraded to 17.12.3 , same error. 😕

 

lol .. downgrading to 17.12.1 solved the problem.

wtf.

The migration doc mentions a specific IOS-XE version required

 

https://documentation.meraki.com/MS/Deployment_Guides/Getting_started%3A_Cisco_Catalyst_9300_Managem...

Ryan

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Arthamon
Getting noticed

I had ran into this same problem previously, with varying results from different firmware versions. @Ryan_Miles is accurate in that there is a very specific version that must be loaded.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels