Meraki Cloud Monitor Catalyst Switches

A full walkthrough of getting a catalyst switch into the Meraki dashboard. I also talk about what you get with a DNA Essential license vs a DNA Advantage license.
Pre-Onboarding Checklist:
documentation.meraki.com/Clou...

[@jazzdrone1302]

Great demo Sal 👍

[@mikekline7708]

Great job as always Sal!

[@cardnyl]

Great Video and thank you for the breakdown of the on-Boarding process. If Possible, we need an Off-Boarding Process as well. Divesting Networking gear when a portion of your corporation is sold, reverting Cisco catalyst switches back to normal state when it is time to refresh for actual Meraki Switches (because, let's be honest, the enterprise license for Meraki is Drastically Cheaper than DNA Licenses...) I think this is as much needed as the on-boarding process. I am currently staring at the EEM script to Off-Board a Catalyst switch, like "This cannot just be it"

[@CiscoSal]

You should be erasing everything in that situation. Write erase reload. If you only need to remove the meraki portion then the eem script will do the trick.

[@Pixel_Runner]

Just for your reference, the Meraki onboarding application doesn't actually remove IOS - it actually installs a Meraki application in an application container and locks down the CLI (so it would work just like the MS390). Then the app in the app container then acts as an agent that communicates with the Meraki dashboard, updates config on the switch, and sends back assurance (Health) data to Meraki so you can see the data in dashboard.

[@CiscoSal]

Thank you for pointing that out! If I do a meraki managed 9300 ill make sure to go into detail how it gets converted into an ms390. Thanks again!

[@joearonow3560]

Quick point of clarification here - the standalone onboarding application is specific to cloud monitoring, which does not use any on-box container or lock down the CLI interface. The cloud management migration process, which is the process Sal refers to briefly at the start of the video that actually turns the switch into a full fledged "meraki switch" similar to the MS390, is totally separate and doesn't use the onboarding app.

[@abbeyggartee1891]

need step by step for configurating switch..let pretend I don't know anything about CLI...I'm lost

[@FINPJENN]

Great video, Sal! I’ll prob put a couple 9200L switches in Meraki to test, but what happens when their NWE and DNA licences expire? Will they carry on working in the Meraki Dashboard?

[@CiscoSal]

They will not work in the meraki dashboard without a DNA license. The switch will continue to operate without dna, but you will lose dna cli commands and meraki dashboard access.

[@sonnykapsengchanh7614]

I got error: invalid sudi, how to I fix this?

[@CiscoSal]

I would call into tac. That’s not very descriptive. We would have to trace the whole process and see where it got stuck