Summary: This note outlines the requirements and the general approach for converting a Cisco IOS-XE Catalyst switch to Meraki managed mode. This process integrates the Catalyst switch into the Meraki dashboard for cloud-based management, with console access becoming primarily read-only for troubleshooting.
Before initiating the conversion, ensure the following prerequisites are met:
- Supported Models: The migration is primarily available for specific Cisco Catalyst 9000 models (e.g., C9200L, C9300, C9300L, C9300X, C9350). Verify that your exact model is supported by consulting Cisco Meraki documentation.
- IOS-XE Version: The Catalyst switch must be running a compatible IOS-XE version, generally 17.10.x or newer (e.g., 17.15+ for enhanced features). Check the release notes for your specific IOS-XE version to confirm Meraki dashboard migration support.
- Install Mode: The IOS-XE must be operating in "install mode," not "bundle mode." Attempting migration in bundle mode will result in an error.
- Full Encryption IOS-XE: "Full encryption IOS-XE" is a mandatory requirement. "No Payload Encryption (NPE)" versions are not supported.
- Compatible Network Modules: Any network modules utilized by the switch must be compatible with the migration process. Incompatible modules will prevent migration.
- Meraki Dashboard Access and Licensing: An active Meraki account and access to the Meraki Dashboard are required. The existing Cisco DNA license will need to be converted to a Meraki MS Cloud license.
- Internet Connectivity: The Catalyst switch must have internet connectivity and be able to resolve
dashboard.meraki.com to initiate and maintain Meraki management.
- Data Backup: The migration process performs a factory reset, formatting the switch's configuration, flash, USB-flash, and all storage. It is essential to back up all necessary data before initiating the conversion. Disconnecting USB storage devices is also recommended as they will not be accessible in Meraki cloud operating mode.
The conversion process generally follows these steps:
-
Validate Compatibility and Upgrade IOS-XE:
- From the IOS-XE CLI, run the command
show meraki compatibility to confirm hardware and software compatibility.
- If necessary, upgrade the switch to the required minimum IOS-XE release in "install mode" and ensure it is a "full encryption IOS-XE" version.
-
Initiate Registration with the Cloud:
- Ensure the Catalyst switch has internet connectivity and can resolve
dashboard.meraki.com.
- Initiate Meraki registration from the switch. This process obtains the Meraki ID required for claiming the device.
-
Claim the Switch to a Meraki Organization:
- Use the obtained Meraki ID to claim the switch to your Meraki organization within the Meraki Dashboard.
-
Add the Switch to the Dashboard Network:
- Once claimed, add the switch to the appropriate network within your Meraki Dashboard for management. The Dashboard network's firmware version must meet the minimum requirement for the migrated Catalyst switch.
-
Migration to Meraki-managed Mode:
- After successful registration and claiming, the migration to Meraki-managed mode can be initiated using a command such as
service meraki start on the Catalyst switch.
- Configuration Wipe: Be aware that the migration will wipe all existing configurations and data from the switch.
- Console Access: Post-migration, console access will be restricted to primarily read-only for log events. All configuration and monitoring will be performed via the Meraki Dashboard or the Local Status Page.
- Firmware: Meraki-managed Catalyst switches utilize firmware customized for cloud connectivity.
- Stacking: A Meraki-managed Catalyst switch stack can consist of up to eight stacking-capable Cisco Catalyst 9300 Series switches linked via StackWise-480 ports. The stack must only contain Meraki-managed Catalyst switches.
- Reverting to IOS-XE/DNA Management: To revert a Meraki-managed switch back to DNA or CLI management, Meraki Support must be contacted. This process will also factory default the switch and erase all configurations, and a DNA license will be required.
- Support: For any issues during or after migration, contact the Meraki Support team.