Converting C9200CX-8P-2X2G to cloud managed-Meraki-Device

[StevenPPAA]

Hi everyone,

we're using and converted a bunch of Catalyst 9300 to cloud managed Meraki-Switches since a few years, they're working (most time) perfectly fine. We also use some 9200CX but in hybrid mode.

A few days ago I saw that the iOS 17.18.1 for C9200CX is supporting the full cloud managed mode. So I've tried it and failed. 🙂 

The upgrade was working, the pre-config for migration was working, pinging dashboard etc. was working and after claiming the switch on the dashboard it begins to migrating to the Meraki-FW. It was working like all the 9300 before it.

After adding the switch to a network it shows all the informations and it seems all fine. I tried to configure a port and it wouldn't let me (VLAN > 800). After a few tries it says the switch is limited to 512 VLANs but this was never a part of one of our running configs in CLI nor on the dashboard. I can't access via console (as normal in Meraki) but asks for a username/password. I think the switch sticks between catalyst and Meraki, so we called support and put it back on iOS 17.18.1. 

I factory reset the switch and put a completely fresh iOS on a completely erased switch...after pre-config I want to add it again to a network in Meraki...and it don't let me do it because the switch is limited to 512 VLANs and the migration didn't even start this try.

We deleted the switch from the inventory and want to try it tomorrow again, maybe there was some configs saved in the dashboard...

Is this part of the iOS as an ED release? Or a bug? Has anyone tried to migrate a C9200CX to cloud managed mode?

[alemabrahao]

Configuring the VLAN Database from the Local Status Page

Beginning with IOS XE 17.18.2, The VLANs that are active for a single switch can be modified from the local status page of that switch. This can be used to quickly reduce the number of VLANs below the limit so that a VLAN ID in the higher range (typically greater than 1000) can be quickly enabled on the switch. Use this if the management VLAN in your network is above 1000 for Catalyst 9300, or above 512 for Catalyst 9200. 

The local status page is not intended to be used for configuring switches that are currently connected to the cloud dashboard. Any changes made to the device may be overwritten by cloud dashboard config so it's important to ensure that the cloud dashboard configuration is correct. Use the LSP to get a switch online for the first time, or to troubleshoot connection issues. Otherwise the normal configuration of the VLAN database should be done from the dashboard.

Log into the local status page

Connect to the LSP via the management port on the back of the switch, or remotely using the management uplink IP address of the switch. For more information, refer to this article

Review the active VLANs

On the Connection tab, there is a VLAN Utilisation table. The table provides some useful information about the VLANs that are configured on the switch. In this example, the switch has already been configured with the minimal required VLANs via the cloud dashboard. 

1. The list of VLANs assigned to access ports, or allowed VLANs on trunks
2. The L3 Switched Virtual Interfaces (SVIs) enabled on the switch 
3. The management VLAN of the switch, used to reach the cloud dashboard
4. The list of active VLANs on the switch. This is the number limited to 512, or 1000, depending on the switch model.
   
   https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Design_and_Configure/C...

[StevenPPAA]

Thanks a lot! 

But how can I get access to  LSP on a C9200CX. It doesn't has an ethernet management port, just micro-usb port?

[alemabrahao]

You’ll need a micro‑USB to USB‑A cable.

[StevenPPAA]

Yep, then I have access to the console. Or can I access to the LSP aswell? LSP = WebUI?

[alemabrahao]

The cable is for accessing the console; you access the LSP via a web browser.

https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Troubleshooting_and_Su...

[GIdenJoe]

Oh really, I didn't know you had to prune all those vlans before joining it to dashboard.

Normally if they start out in vlan 1 you can then just use the vlan database function inside the vlan profiles on dashboard to limit the vlans.