Migration to Meraki Managed Dashboard

Meraki dashboard migration

The Meraki dashboard is a centralized, web-based platform used to configure and monitor Cisco devices and services. Starting from release 26.1.1, you can migrate the Cisco IE35xx rugged series switch to cloud-managed mode. This migration enables you to manage and control your device through the Meraki cloud-based dashboard.

Key aspects of this migration behaviour and access include:

  • After migration, the switch operates entirely under the control of the Meraki dashboard.

  • Console access to the switch is unavailable after migration. To troubleshoot or configure the device, use the Meraki dashboard. You can access the LSP for the device by using the DNS name http://switch.meraki.com.

    If you cannot use the DNS name, you can access the local status page by entering the device's IP address in your browser. This approach helps if you set up the device on a network without Dynamic Host Configuration Protocol (DHCP) or before assigning its final IP address.

    You can use the IP address 1.1.1.100 from the client device to access the local status page.
To access this address, configure a device with these IP settings and browse to the address in a web browser.


    • IP address: 1.1.1.99


    • Subnet mask: 255.255.255.0

  • During migration, the flash memory and USB drives of the switch are formatted and reconfigured for the Meraki runtime environment. This process erases all previous configurations and the device must be reconfigured through the Meraki dashboard.

Supported switch models for cloud-managed mode

The supported switch models for migration to cloud managed mode are:

  • IE-3500-8T3S

  • IE-3500-8P3S

  • IE-3505-8T3S

  • IE-3505-8P3S

  • IE-3500-8T3X

  • IE-3500-8U3X

How to migrate to a Meraki managed dashboard

Follow these steps to migrate your device to Meraki dashboard.

Before you begin

  • Ensure that the device can Resolve DNS names .

  • Ensure that you have access to the Meraki dashboard.

  • Obtain the Meraki serial number before adding the device to the network. To register your device and retrieve the Meraki serial number, see the Register and migrate to Meraki dashboard section.

  • Ensure the device runs IOS-XE version 26.1.1 or later.

  • Ensure that the clock settings (date and time) are configured correctly before onboarding the device. Incorrect settings can cause onboarding or connectivity issues.

Procedure

Step 1

Validate device compatibility. See Validate device compatibility for more information.

Step 2

Register and migrate the device. See Register and migrate to Meraki dashboard for more information.

Resolve DNS names

Perform this task to verify that the device can resolve DNS names and that it has a routable IP address on the appropriate VLAN. You can also verify that the device routes traffic to external networks through the default gateway.

Procedure

Step 1

Use the ip name-server dns-server command to configure the device to use a DNS name server.

Example:

Device(config)# ip name-server 192.0.2.10
You can specify up to six DNS servers if needed.

Step 2

Configure a switch virtual interface (SVI) or routed interface with a routable IP address.

  1. Use the vlan vlan-id command to create the VLAN for cloud connectivity.

    Example:

    Device(config)# vlan 10        ! VLAN used for cloud connectivity

  2. Use the exit command to exit VLAN configuration mode.

    Example:

    Device(config-vlan)# exit

  3. Use the interface vlan vlan-id command to enter interface configuration mode for the VLAN.

    Example:

    Device(config)# interface vlan 10

    Use the same VLAN ID where the DHCP is present.

  4. Use the ip address dhcp command to assign an IP address through DHCP.

    Example:

    Device(config-if)# ip address dhcp

    The DHCP provides gateway and DNS information.

  5. Use the no shutdown command to enable the VLAN interface.

    Example:

    Device(config-if)# no shutdown

  6. Use the exit command to exit the interface configuration mode.

    Example:

    Device(config-if)# exit

  7. Use the ping meraki.com command to verify that the ping is successful to the Meraki dashboard.

    Example:

    Device# ping meraki.com
    Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 52.84.205.125, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Switch-2016#

Validate device compatibility

Follow this procedure to validate if your device is compatible for migration.

Procedure

Use the show cloud-mgmt compatibility command to verify if your device is compatible for migration.

Example:

Device# show cloud-mgmt compatibility
========================================================================================== 
Compatibility Check Status 
---------------------------------------------------------------------------------------------------------------------- 
Boot Mode INSTALL  - Compatible 
---------------------------------------------------------------------------------------------------------------------- 
Switch#  SKU                                Bootloader Version              Network Modules
----------------------------------------------------------------------------------------------
1        IE-3500-8T3S (M)   - Compatible    17_18_1r        - Compatible    N/A                          

Compatible NMs : 

----------------------------------------------------------------------------------------------------------------------

Note

 

If you attempt to migrate an incompatible device or a compatible device with an incompatible network module, the process fails and displays an error message.

Register and migrate to Meraki dashboard

Perform this procedure to register your device and migrate to cloud management mode.

Before you begin

Complete these steps before you initiate the migration process.

  • Back up your device configuration and any relevant local files, including any USB flash drives connected to the device. This is important because all file systems will be formatted once you initiate the migration process.

  • Upgrade to Cisco IOS XE 26.1.1 in install mode. For details about install mode upgrades, see the Release Notes for Cisco IE3500 Series Switches.

Procedure

Step 1

Use the configure terminal command to enter global configuration mode.

Example:

Device# configure terminal

Step 2

Use the service cloud-mgmt connect command to register and initiate migration of your device to cloud-mgmt mode.

The device contacts resources on the Meraki dashboard to register. Use the Meraki serial number to add each device to the dashboard.

Example:

Device(config)# service cloud-mgmt connect
        Starting to connect switch 1
        Successfully connect to Meraki Dashboard
        Switch 1 has been successfully registered
        Received MAC: AABBCCDDEEFF
        Meraki serial number: XXZZ-XXZZ-XXZZ
        Device Registration Status:

Step 3

Use the exit command to exit global configuration mode.

Example:

Device(config)# exit

Migrate to Cisco Catalyst Centre or CLI managed mode

Contact Meraki support to migrate your device back to Cisco Catalyst Centre or CLI-managed mode.

Consider these key aspects when migrating the device:

  • Ensure that the device is online and connected to the Meraki dashboard before beginning the process.

  • The migration process resets the device to its default factory settings and configurations.

  • Once the migration to Cisco Catalyst Centre or CLI managed mode is complete, install a Cisco TAC supported firmware version on the device before deploying them in production networks.

How the device behaves during migration

This section lists the events that occur on the device during migration.

  • The device prompts for input several times during the factory reset procedure. Wiping the flash takes 5 to 10 minutes.

  • The device reboots multiple times to enable 802.3bt mode before entering steady state.

  • When the migration is complete, the device is controlled by the Meraki dashboard.

  • Console access is disabled after the device reboots, which allows log events to be displayed.

  • The device boots up with default configuration and obtains its operational configuration from the Meraki dashboard.

Refer to the Configure your Dashboard Network documentation for more information and configuration best practices.