- 7
- 1 038
Meraki Matt
United States
เข้าร่วมเมื่อ 4 มี.ค. 2024
Welcome to the Meraki Matt Channel, where we discuss all things relative to Meraki and the ecosystem(s) that may surround it. We will provides How-To's, and topics relative to integrations for the Meraki Networking portfolio and product platform(s)
Migrating C9300 with CMDS - UPDATED! (AIO-Part 1 and 2) abridged video
This is an abrigded video where we get our hands dirty immediately :)
This video condenses Part 1 and 2 of CMDS into 1 video and provides updates to the template dpeloyment section.
Documentation and links at the bottom of this desription.
(C)atalyst to (M)eraki (D)eployment (S)erver
This is an on-premise server platform that is designed to provide a seamless experience for migrating
Catalyst 9300 series switches to the Meraki platform with a Dialog based menu system.
The server is built upon Rocky Linux and is script based. It makes this a portable solution across
any hypervisor that will support Rocky linux, on multiple architectures.
The Server can be configured with the following capabilities:
(If in a Lab setting or for testing)
-An (Optional) NTP server to service the switches
-An (Optional) DHCP Server to service the switches
-An (Optional) Caching name server to service the switches (for DNS resolution)
-A TFTP server for switch config collection (mandatory)
-A Set of scripts to allow you to do the following:
-Harvest the switches (for analysis)
-Clean the File System on the switch (remove inactive files)
-Validate the Version of IOS-XE running on the switch platform (16.6.2 upgrade path to 16.12, oneshot to 17.09.03m3)
-Provide guidance on the version (s) needed to get to a supported version of IOS-XE for Meraki migration (minimum requirements and oneshot versions)
-Deploy these (IOS-XE) changes for you
-Deploy the upgrades on the switches
-Validate software configurations on the switches
-If there are any deltas in the configurations, provide guidance to put them into compliance
-The server will then deploy these changes for you (If needed)
-Validate hardware configurations on the switches and provide guidance for a successful upgrade
-Deploy the switches to be registered with the Meraki Cloud
-Provide API integration to claim the devices to the dashboard
-Migrate hostnames
-Provide Switch template configurations for the new deployment (assigning designated ports for wireless, cameras, etc) and deploy via API
-All of this being able to be scheduled (i.e. IOS-XE images can start at 1 A.M. without any intervention, short of you requesting it, with active and archive logging capabilities)
-Provide all logging/transaction history
-Configuration archival and download
-Provide documentation of all logging and successful registration with converted Serial Numbers
Please use this link to access Installation and Overview guide for CMDS:
docs.google.com/document/d/11V8D7SMiOxh83LpjK7glNaEX1MU6rLAe/edit?usp=sharing&ouid=113942710510622294220&rtpof=true&sd=true
GitHub REPO:
github.com/fumatchu/CMDS
Links of interest:
Deployment guide:
documentation.meraki.com/MS/Deployment_Guides/Getting_started%3A_Cisco_Catalyst_9300_Management_with_Meraki_Dashboard
LED Status Reference:
documentation.meraki.com/MS/MS_Installation_Guides/Catalyst_9300-M_Series_Installation_Guide#:~:text=Back%20Panel%20Components-,Inactive%20components:%20When%20operating%20in%20the%20Meraki%2Dmanaged%20mode%2C,the%20LED%20lights%20stop%20flashing.
(CTRL+F for "LED Indicators in the Meraki-managed mode")
www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/hardware/install/b_c9300_hig/Product-overview.html
(CTRL+F for "Figure 8. Switch Front Panel LEDs")
This video condenses Part 1 and 2 of CMDS into 1 video and provides updates to the template dpeloyment section.
Documentation and links at the bottom of this desription.
(C)atalyst to (M)eraki (D)eployment (S)erver
This is an on-premise server platform that is designed to provide a seamless experience for migrating
Catalyst 9300 series switches to the Meraki platform with a Dialog based menu system.
The server is built upon Rocky Linux and is script based. It makes this a portable solution across
any hypervisor that will support Rocky linux, on multiple architectures.
The Server can be configured with the following capabilities:
(If in a Lab setting or for testing)
-An (Optional) NTP server to service the switches
-An (Optional) DHCP Server to service the switches
-An (Optional) Caching name server to service the switches (for DNS resolution)
-A TFTP server for switch config collection (mandatory)
-A Set of scripts to allow you to do the following:
-Harvest the switches (for analysis)
-Clean the File System on the switch (remove inactive files)
-Validate the Version of IOS-XE running on the switch platform (16.6.2 upgrade path to 16.12, oneshot to 17.09.03m3)
-Provide guidance on the version (s) needed to get to a supported version of IOS-XE for Meraki migration (minimum requirements and oneshot versions)
-Deploy these (IOS-XE) changes for you
-Deploy the upgrades on the switches
-Validate software configurations on the switches
-If there are any deltas in the configurations, provide guidance to put them into compliance
-The server will then deploy these changes for you (If needed)
-Validate hardware configurations on the switches and provide guidance for a successful upgrade
-Deploy the switches to be registered with the Meraki Cloud
-Provide API integration to claim the devices to the dashboard
-Migrate hostnames
-Provide Switch template configurations for the new deployment (assigning designated ports for wireless, cameras, etc) and deploy via API
-All of this being able to be scheduled (i.e. IOS-XE images can start at 1 A.M. without any intervention, short of you requesting it, with active and archive logging capabilities)
-Provide all logging/transaction history
-Configuration archival and download
-Provide documentation of all logging and successful registration with converted Serial Numbers
Please use this link to access Installation and Overview guide for CMDS:
docs.google.com/document/d/11V8D7SMiOxh83LpjK7glNaEX1MU6rLAe/edit?usp=sharing&ouid=113942710510622294220&rtpof=true&sd=true
GitHub REPO:
github.com/fumatchu/CMDS
Links of interest:
Deployment guide:
documentation.meraki.com/MS/Deployment_Guides/Getting_started%3A_Cisco_Catalyst_9300_Management_with_Meraki_Dashboard
LED Status Reference:
documentation.meraki.com/MS/MS_Installation_Guides/Catalyst_9300-M_Series_Installation_Guide#:~:text=Back%20Panel%20Components-,Inactive%20components:%20When%20operating%20in%20the%20Meraki%2Dmanaged%20mode%2C,the%20LED%20lights%20stop%20flashing.
(CTRL+F for "LED Indicators in the Meraki-managed mode")
www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/hardware/install/b_c9300_hig/Product-overview.html
(CTRL+F for "Figure 8. Switch Front Panel LEDs")
มุมมอง: 41
วีดีโอ
Migrating C9300 Catalyst to Meraki with CMDS (Unabridged) (orchestrating and automating) Part 2
มุมมอง 73หลายเดือนก่อน
Please use this link to access Installation and Overview guide for CMDS: docs.google.com/document/d/11V8D7SMiOxh83LpjK7glNaEX1MU6rLAe/edit?usp=sharing&ouid=113942710510622294220&rtpof=true&sd=true GitHub REPO: github.com/fumatchu/CMDS This is part two of a two part video series. Part two is an in depth, step by stpe procedure to utilize CMDS and it's features to migrate the switches from IOS-XE...
Migrating C9300 Catalyst to Meraki with CMDS (orchestrating and automating) Part 1
มุมมอง 119หลายเดือนก่อน
Please use this link to access Installation and Overview guide for CMDS: docs.google.com/document/d/11V8D7SMiOxh83LpjK7glNaEX1MU6rLAe/edit?usp=sharing&ouid=113942710510622294220&rtpof=true&sd=true GitHub REPO: github.com/fumatchu/CMDS This is part one of a two part video series. Part one is an Overview and Step by Step deployment of the server This will provide you an Overview of CMDS (C)atalys...
Onboarding and migrating Catalyst C9300 switch into Meraki dashboard (Managed Mode)
มุมมอง 1973 หลายเดือนก่อน
This video provides a walk through of onboarding a Catalyst 9300 series switch into the Meraki dashboard for Managed Mode (Full Dashboard control) - We will go over documentation on how to deploy - We will check the current status of the running switch - We will run IOS-XE based Meraki registration commands - We will put this switch into inventory into the dashboard - We will run the migration ...
Configuring Meraki Catalyst Monitoring (Onboarding Catalyst switch)
มุมมอง 1243 หลายเดือนก่อน
This video will walk you through configuring the pre-requisites needed for onboarding a Cisco Catalyst 92/3/5 series switch into the Meraki dashboard. We will then download the Catalyst for onbaording application and integrate the Catalyst switch into the dashboard. -Configure the Catalyst for trunk communication -Configure L3 capabilities -Configure remaining pre-requisites -Onboard the switch...
Installing and configuring FreeRADIUS for 802.1x, MAC Auth/iPSK- Integrated with Meraki Dashboard
มุมมอง 1923 หลายเดือนก่อน
In this video, we will be installing FreeRADIUS on Rocky Linux and have it in operation in approx. 15 minutes. We will integrate into Meraki wireless via dashboard with 802.1x, MAC Auth and MAC auth with iPSK support. We will also test authentication for MAC auth and 802.1x. The FreeRADIUS server will be integrated into an Active Directory Environment with Group membership checking for auth. Gi...
Install Active Directory on Rocky Linux 9 (script)
มุมมอง 3043 หลายเดือนก่อน
This video will walk you through a step by step deployment of Samba Active Directory on Rocky Linux leveraging the mock build fetaure inside of Rocky. We will leverage an installation script that resides on Github to deploy the server with customer build in under 25 minutes, with a full featured installation of AD, Management Tools, and documentation to support the Administration process. GitHu...
Is there any way to access the CLI?
Hi! Currently, as of today, there is not a way to access the cli. You can plug a console cable into the switch, and see basic cli output, but it is not interactive, meaning you cannot login to the switch. However, you can still use the OOB management port and access the local (Meraki) web page of the switch, as you would a Meraki switch. So you still have local access to the switch in a catastrophic event where you still need to get local access to it. Hope that makes sense. Thank you for the question
I just wanted to take a moment to thank you for teaching me how to install domain control. Your guidance made the process so much easier to understand, and I really appreciate the time and effort you put into helping me Your expertise and patience have been invaluable, and I feel much more confident in managing domain settings now. If there's anything I can do to return the favor, please let me know. Thanks again for your support!
You are very welcome Sameer! I am happy that everything worked out! Good luck in the future!
great video
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!
Thanks
You are very welcome!
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?
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