Migration from CLI-managed Catalyst Switches to Meraki-managed Mode
Attempting to migrate unsupported models, such as C9200CX may result in an unusable switch. Please review the list of supported models below before proceeding with the upgrade.Overview
With the public beta release of IOS XE 17.15.1, we are introducing cloud-native IOS XE, which brings several enhancements to your Cisco cloud-managed Catalyst switches. Notably, you will experience improved boot times, especially for stacks. Additionally, you can now access the CLI through the dashboard to run show commands for troubleshooting.
IOS XE 17.15.1 release comes with the capability to migrate the supported Catalyst 9000 switches (including the 9200L for the first time ever) from DNA management mode to Meraki Cloud management mode. This functionality migrates the switch or switch stack to become fully managed by Meraki Dashboard. During the migration process the switch's configuration, flash, USB-flash, and all storage will be formatted and reconfigured to the Meraki runtime.
This document gives you a step-by-step explanation on how to migrate your existing supported Catalyst switch to Cloud Management mode. For details on the cloud-native IOS XE architecture and software capabilities of this new release, please refer to the firmware release notes on the firmware upgrades page or the FAQ document.
Prerequisites
Supported Models
Migration is available for the following Catalyst 9000 models.
NOTE: ATTEMPTING TO CONVERT UNSUPPORTED MODELS SUCH AS C9200CX MAY RESULT IN A UNUSABLE SWITCH. PLEASE REVIEW THE LIST OF SUPPORTED MODELS BEFORE PROCEEDING WITH THE UPGRADE.
| Series | Models |
| C9200L series (New) | C9200L-24T-4X , C9200L-24P-4X, C9200L-48T-4X , C9200L-48P-4X , C9200L-48PL-4X , C9200L-24PXG-4X , C9200L-48PXG-4X , C9200L-24PXG-2Y , C9200L-48PXG-2Y , C9200L-24T-4G , C9200L-24P-4G , C9200L-48T-4G , C9200L-48P-4G , C9200L-48 PL-4G |
| C9300/X series | C9300-24T, C9300-24P, C9300-24U , C9300-24UX , C9300-48T , C9300-48P , C9300-48U , C9300-48UXM , C9300-48UN , C9300-24S, C9300-48S , C9300X-12Y, C9300X-24Y, C9300X-48HXN, C9300X-24HX, C9300X-48HX, C9300X-48TX, C9300L-24P-4X, C9300L-24T-4X, C9300L-24UXG-4X, C9300L-48P-4X, C9300L-48PF-4X, C9300L-48T-4X, C9300L-48UXG-4X |
Supported Firmware
For the migration to cloud management, switches are required to be on IOS-XE 17.15.1. The special firmware release can be downloaded from the software download page.
For C9300 and C9300X, cat9k_iosxe.17.15.01m1.SPA.bin is the release image. For C9200L, cat9k_lite_iosxe.17.15.01m1.SPA.bin is the release image.
Migration Steps from DNA Management Mode to Meraki Cloud Management Mode
To migrate to Meraki Cloud management mode, follow the steps below:
- Validate compatibility of the hardware and upgrade to the required minimum IOS-XE release
- Initiate Meraki registration of the Catalyst switch
- Claim the switch to a Meraki organization using the cloud ID
- Add the switch to the respective dashboard network for management
The following image shows the migration process from CLI-managed to cloud-native IOS XE:
The migration steps are explained in detail in the following sections:
Step 1: Validate Compatibility and Upgrade to the Minimum IOS-XE Release
To validate that your Catalyst switch has the hardware and software configuration compatible with the Meraki-managed mode, run the following command from the IOS-XE CLI.
show meraki compatibility
Switch#show meraki compatibility ================================================== Compatibility Check Status -------------------------------------------------- Boot Mode INSTALL - Compatible Stackwise Virtual Disabled - Compatible -------------------------------------------------- ------------------------------------------------------------------------------------------- Switch# SKU Bootloader Version Network Modules ------------------------------------------------------------------------------------------- 1 C9300-48U - Compatible 17.10.1r - Compatible C9300-NM-8X - Compatible ---------------------------------------------------------------------------------------------------------------------- Compatible SKUs: C9300-24P, C9300-24T, C9300-24U, C9300-24UX, C9300-48P, C9300-48T, C9300-48U, C9300-48UN, C9300-48UXM Compatible NMs : C3850-NM-2-40G, C3850-NM-4-10G, C3850-NM-8-10G, C9300-NM-2Q, C9300-NM-8X, MA-MOD-2X40G, MA-MOD-4X10G, MA-MOD-8X10G ----------------------------------------------------------------------------------------------------------------------
Note: Before attempting to migrate any switch and included network modules, run the Meraki compatibility check first. Ensure the compatibility check passes and that your switch is one of the supported models. Do not attempt to migrate any switches that are not in the supported models list. Failure to follow supported models list may result in an unusable switch. Please review the list of supported models before proceeding with the upgrade.
Step 2: Initiate Registration with the Cloud
Ensure that the Catalyst switch is able to connect to the internet and resolving dashboard.meraki.com.
To resolve DNS names and communicate with the Meraki Dashboard, the Catalyst switch will need the following configuration.
- A layer 3 interface, such as an SVI or routed interface, with an IP address that has connectivity to the internet.
- A next-hop or default gateway IP which the switch can use to send traffic to the internet.
- A DNS server which can resolve dashboard.meraki.com.
- "internet bound" vlan configured as http client source-interface
Example script while in global configuration mode:
vlan {vlan used for cloud connectivity}
exit
!
interface vlan {VLAN where DHCP is present}
ip address dhcp
no shutdown
exit
!
ip route 0.0.0.0 0.0.0.0 dhcp
ip http client source-interface {vlan-interface}
!
ip name-server 8.8.8.8
You can check whether the switch is configured correctly by pinging dashboard.meraki.com
Note:
- Do not use the OOB port (Gig0/0) management port on the rear of the switch for internet connectivity. Front facing ports only.
- SVIs only, no routed-port support at this time.
Once you have validated that the switch can reach the Meraki Dashboard, use the following command within the configure terminal to register the switch(es) unit or stack member with dashboard:
Single Member or Stack Active member:
Switch# configure terminal Switch(config)# service meraki connect
Single Member or Stack Active member:
During the registration process, the switch will communicate with the Meraki Dashboard to register itself and receive its Meraki ID or Cloud ID. Each switch, including switches in a stack will receive an individual Meraki ID. The Catalyst serial number and Meraki ID mapping, along with the registration status, will be displayed on the CLI terminal, as shown in the following image:
.png?revision=1)
You can also issue the show meraki connect command to view the status of the registration and its details as shown below. Once the output of “show meraki connect” indicates that the meraki tunnel config fetch has succeeded, the switch is ready to be claimed on the Meraki dashboard.
Switch# show meraki connect
Step 3: Claim the Switch to Meraki Dashboard Using Cloud ID
Once the output of “show meraki connect” indicates that the config fetch has succeeded, the switch is ready to be claimed on the Meraki dashboard. The cloud ID generated as part of the registration process above will be needed to claim the devices to your Meraki dashboard. Navigate to the Organization>Inventory page on the Meraki dashboard and claim the switch.
If you need information on creating a Meraki Dashboard account, refer to our documentation on Creating a Dashboard Account and Organization.
Step 4: Add the switch to the dashboard network
When you are ready to migrate the device to cloud-management mode, add the device to a dashboard network. Migration to management mode will not happen until the device has been added to a dashboard network.
When adding the device to dashboard network, a warning message appears to remind you that any existing configurations will be replaced by dashboard configurations for the assigned network. The warning message is shown in the following image:
.png?revision=1&size=bestfit&width=617&height=346)
After the device has been added to a dashboard network, migration to Meraki cloud management mode will be triggered, initiating a factory reset procedure and restricting the console to read-only mode.
The switch may take up to 15 minutes to factory reset, and reboot, and connect to the dashboard in Meraki-managed mode.
DO NOT power cycle the switches during the factory reset process. The console connection remains in read-only mode and can be used to monitor the process.
Once the migration has been successful, use the local status page to make basic configuration updates. For information on how to access and use the local status page please refer to our documentation on Using Cisco Meraki Device Local Status Page.
The migration process will erase all configuration and files stored locally, or on any attached USB devices. Be sure to back up all necessary data from the local or connected storage, prior to initiating the migration. It is recommended that USB storage devices be disconnected, as they will not be accessible in Meraki-managed mode.
During migration, the switch or switch stack may reboot one or more times to enable 802.3bt. Once the switch has rebooted console access will be restricted to read-only mode, only showing log events. The switch will boot up with default configurations for connecting to Meraki dashboard. Refer to our documentation on MS390 Deployment Best Practices for more information on how zero-touch deployment works and the best practice configurations.
Migrating to DNA management mode
To migrate your Catalyst switch(es) to DNA management mode, contact Meraki Support. To be migrated, a switch must be online and connected to the Meraki dashboard.
Migration will factory default the switch and all configuration.
When operating in the Meraki-managed mode, Catalyst switches use firmware customized for cloud connectivity.
Once the migration to DNA or CLI managed mode is complete, please be sure to install a supported IOS-XE software version on the switches before deploying them in production networks.