Configuring Meraki Catalyst Monitoring (Onboarding Catalyst switch)

[@aussietramp]

great video

[@MerakiMatt]

Thank you! I'll be working on more videos like this in the future to share with the community. If you are looking at Meraki migration with 9300's, check out the program I wrote that will migrate them all for you. Thanks for stopping by!

[@davenelson5496]

Adding 1 at a time seems straight forward. However, how would you migrate a stack? Do you do one at a time and then once all registered create the stack in the dashboard just like the MS platform? Or is there a different process for stacks. Also, how do you access the local status page, Using the dedicated Mgmt port on back or through a front port? Can you statically set the switch ip /vlan using the local status page?

[@MerakiMatt]

Hi Dave! Sorry for my delayed reply. I apologize. Since this is Monitoring, you will still have direct SSH access to the switch. So there is no local access page, per se'. It would still be the CLI access of the switch, or if you have ip http enabled on the switch (the Cat web GUI). With Cat monitoring, the Switch stack should be identified by the dashboard. The migration process would be the same. This is a note from the deployment doc: "Note: As Cisco stacks share the same IP address across all members, the single IP should be entered which will onboard the entire stack." documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide You could also turn on the Early Access for Autostacking.. That should allow the stack to be detected automatically. So adding the stack would be the same process, but again, you are using the Catalyst Monitoring Client to move it to the dashboard. Hope this makes sense and let me know if you have further questions! FYI, for Cat management, where you are erasing IOS-XE and installing Meraki code on 9300, the OOB management port would be the direct local web access page I believe you were referring to. Keep in mind that the OOB port will also provide DHCP for a client to connect to it locally, so just make sure that it is truly OOB, otherwise DHCP issues may arise on that network segment