Cisco Customer Success - Video

Unified monitoring & management in the Meraki Cloud for IOS XE devices

Playback confirmation!

Do you want to resume playing from last left location?

Chapter 1 Thumbnail
00:09
Welcome, presenter introductions and session guidelines
Chapter 2 Thumbnail
02:20
Agenda, supported Catalyst models and benefits of Meraki cloud management
Chapter 3 Thumbnail
06:28
Meraki organization and network structure; configuration modes overview
Chapter 4 Thumbnail
08:37
Onboarding prerequisites and connection setup (dashboard and CLI)
Chapter 5 Thumbnail
12:18
Assurance dashboard: health score, Device 360 and Client 360
Chapter 6 Thumbnail
15:25
Application 360, topology, event logs, intelligent capture and reports
Chapter 7 Thumbnail
23:23
Meraki account setup, organizations and site networks
Chapter 8 Thumbnail
27:12
Demo: Onboard a Catalyst 9K via CLI, claim and add to network
Chapter 9 Thumbnail
32:08
Demo: Cloud vs device config modes, network-wide monitoring and captures
Chapter 10 Thumbnail
41:48
Demo: Switch and wireless monitoring; org reports, firmware/alerts; automation and AI workflows; wrap-up.

Transcript

Good morning and good afternoon, good evening, everyone. Thank you for joining today's session on unified monitoring and management in the Meraki Cloud for iOS XE devices. Thanks.00:09And I will be your moderator for the today.00:21So today we have two brilliant presenters, Satish Kumar Valachimmy and so Satish will be our demo specialist. Let me just give you some introduction about them. So he Satish has overall eleven years of experience in networking industry. He worked in routing.00:24And switching and wireless technology and now engages with customers for catalyst center.00:44He also holds ccie enterprise certification. Padmathi will be our presenter. He is a customer success specialist with eleven years of experience in networking, specializing in wireless and SD WAN technologies. He is dedicated to delivering seamless solutions and empowering customers to achieve their goals.00:51And next slide please. So before we actually jump, just before we actually jump into the session, let me just quickly tell you few things that will ensure that we have a good meeting, seamless meeting. So.01:09During today's session, you can ask any questions that you have about and one of our panelists will respond. You can post your questions in the chat in the chat or in Q and A and we can answer. So if you want to.01:27If you would like, you can raise your hand and one of our panelists will assist you. Once your question has been answered, we request you to please lower your hand. And for any unanswered questions, there will be a Q and A at the end of the session once the presentation is done.01:44So if you're having any audio issues, please use the chat panel and we can help you with that. And with that, over to you. Thank you. Good morning, everyone. So the topic that we'll be working on today is about unified dashboard. So to start.02:00Everything to give you a quick overview on the agenda that we'll be covering.02:20We'll start off with the dashboard overview of the terminologies and we look into the deployment modes and the onboarding procedures, followed by which we'll be covering the assurance capabilities and the AI automation capabilities. And with that moving on to the very 1st slide, so we'll start off with.02:24Why are we having the catalyst devices managed? What's the benefit of having them managed in the.02:44To start off with these are the list of devices, the switch catalyst switch models that are supported in the the Meraki dashboard, the C 9200 series, the 95 or the 9300 series and so forth.02:52That, yeah, this gives you the benefits of having this catalyst devices managed in Meraki is that it gives you a best in class cloud monitoring solution and it is scalable where it supports thousands of wireless devices for monitoring purposes.03:07There's NO additional cost you can start using them along or with the basic, the DNA license that exists in the catalyst already. And it gives you a single pane of glass for both the Meraki devices as well as the catalyst devices. This being on the cloud is giving a privilege to have it access from anywhere. You don't have to be mandatory connected.03:24To the VPN and so forth. And the flexibility to have it managed and to have it updated and backed up is there because we are having the catalyst devices now backed up in the cloud moving on to the switch and the controller models and the minimum supported versions.03:44So starting off from the 93, the C 9300 series, the 9293 9500 series and start the minimum recommended software version to be 1715 and seventeen.eighteen IOS XE seventeen.fifteen to seventeen.eighteen.04:01And the controller models that supported it's 9800 series and again the minimum is required software version to be 17 twelve.three or 17 fifteen.one and later on. When it comes to the scalability part of it, for now we say it is 20000 clients and 2000 access points.04:24What happens if the limit exceeds is that the dashboard might stop collecting data or would last updated data would be when the access point count is 2000. Once the count is brought back to 2000 again, the dashboard would start collecting data and populating it for the references or the troubleshooting purposes.04:43Moving on to the supported model APs, starting from 20 AP 2838 and 4800, it goes from, it goes to wi Fi six to wi Fi seven supported access points. Yeah. From there, quickly moving on to how the overall structure looks like.05:02So this is the overall structure of how the dashboard or the catalyst Meraki dashboard would look like. It is it is an organiz dashboard looks like an organization structure where the organization who holds the higher hierarchy, the higher part, and we have a networks coming under that. Networks are nothing but like.05:19Say e.g., if we pick an organization, it has a certain level of privilege like it has access to the inventory, it has access to the licensing inventory and each of their multiple sites for their, for a specific organization, if they have multiple sites.05:38They'd be termed as networks. So we call them a site A and site B, which is now as multiple networks. And there are certain level of privilege that you have on each of these organization levels and network levels. When I say privileges, their access.05:53The logins, the data that they'll be able to see can be classified or the privileges can be assigned based on whether it is in the organization level or on the network level. Quickly moving on to the deployment notes.06:09Prior to starting from 1750 or prior to iOS XE, iOS XE seventeen.15 it was cloud monitoring and cloud managed. Now it is all cloud managed only.06:28Under the cloud managed, we have two configuration modes, which is the device configuration mode and the cloud configuration mode. What's the difference in the device and the cloud configurations that when you go for cloud configuration mode, the configurations.06:43And all of that along with the backup of the changes or correction all are done from the dashboard level itself, which is from, which is from the cloud, which is the cloud config itself, but you won't be having any local access or you won't be able to do any changes specific to that device being on the device level.06:59Where in the device configuration mode, you have the privilege to do the configuration from the device level, any unique changes or specific changes to the device can be done here, but this will be clearly backed up on the cloud. This is how it will look like.07:15When you go for the, the configuration source on each of this type would be like the full config would be managed and done on the cloud level and would be synced and backed up in terms of cloud config mode, but in terms of device config, it will be done on the device level and would be adapted or synced to the cloud for the backup purposes.07:35The overall difference to quickly talk about is, when it comes to the cloud configuration mode, it's exclusively managed by the dashboard when the device config has the flexibility to do the device specific configurations. And here in terms of CLI, the cloud configuration will be read only CLI wherein the device config.07:57It will be read and write.08:17From the CLI support will be available, followed by which you see the list of devices that are supported, the catalyst switches and the catalyst controllers that are supported are mentioned here. There are certain pre onboarding requirements that we would have. The minimum starting from the minimum required software version.08:19And the platform or devices that are supported. The minimum software version as discussed is 1715 seventeen.15.three and later on. The primary device level configurations that we would require to have the devices onboarded here is that should be having basic internet reachability on the device level?08:37And we should be able to have the DNS reachability to do the resolution or to do the lookup part of it. Default gateway must be reachable and the NTP must be configured. Apart from that, if you have any radius server that was any radius authentication server, it will NO longer be.08:55In in case of onboarding part of it won't be accessible, you need to have a new model authentication server for the login purposes. Along with that to do the CLI part of it, we need a privilege privilege with the SSH access should be available basically.09:14Telemetry should be available. The steps that we would require to have the devices, whether we are onboarding through the dashboard or through the CLI would be simple, Upgrade the device to the recommended version.09:31If it's through the CLI, you run service Meraki Connect or if it's through the web UI, you'll have a button button to say connect to the Meraki, you will be establishing a connection. Then you'll get a cloud ID, which you will be able to claim and add the device.09:46To the required network from the inventory. Step one of what we do when we connect the device from the dashboard level is that as I mentioned, you see a button that says enable. Yeah, make sure that the sliding button is turned on and it is enabled.10:03And you see a button that says Meraki, click on the button, then the device would establish to catalyst.Meraki.com. Now this is where I said DNS should be configured as a primary sick to do the resolution part of it and certain ports such as TCP 443 should be allowed as well.10:19And once it is, it tries to establish the connection, you should be able to see the cloud ID from here, copy the cloud ID, copy and paste the cloud ID into the inventory to claim the device from there. And once the device is claimed by having the cloud ID pasted.10:37Then you can add the device to your required network if the network is already configured or what you can do is you can also have a network created and add the device in there. Now as a next step, once you add the device from there, yeah, before which.10:53We'll take a look at how we do it in the CLI based conversion part. Yeah, from the CLI, all that it would require is service Meraki Connect. That's the command to establish the connection. Then show Meraki Connect would show you the status of.11:10What's the tunnel status? Yeah, this is the show meraki connect output that you can see. This is going to show you the tunnel status and it is going to give you the cloud ID as well. Yeah. Using the cloud ID, you can claim the device in the inventory and add it to the network as we just described.11:27And post to which comes the part of where you choose which configuration mode you want, whether you want to have it to be cloud configuration or the device configuration, you get to choose from here and then enter the username and password to go to the next step from there to start of the config.11:43So that was about the configuration, initially the onboarding part of it and choosing what mode of configuration that you would prefer to have and and about the supported software versions and the devices. From there moving on to the next step is one of the very good feature that we'd like to discuss quickly on.12:00Is the assurance capability. This assurance capability would be an add on feature I would say because at a single glance this is going to show you a quick overview of how your network is performing. As you can see from the dashboard, this is giving you.12:18A graph as to how your overall network is behaving at a glance. It's giving you a points and showing you a percentage of out of hundred, how good is your network performing. And with that it is also giving you, you can see something that says points over there right under the score.12:34Of your network. Now this points is the difference. This is going to show you a difference in terms of value as to how your network is performing from yesterday to today. Sorry. Yes. So now this dashboard is again classified into three issue categories. Now this has.12:51This dashboard gets the overall score based on the client, the network, and the application performance. As you click on each of this, you will get to go into a complete three 60 degree view of it to, to get a more detail and a granular data.13:09Of each of these parameters be cloud, network devices or sorry, be client, network devices or application. To start off with, this is how the device three 60 degree page looks like. Once you click on the device under the assurance dashboard.13:25This is how the overall view of your device three 60 would look like. Now this is going to quickly give you on any specific device that you choose. This would give you an overall summary as to how your device is performing. It's going to show you the ports that are active, that are up.13:41In case what is the configuration mode that you have a source you choose for this device, whether it is clouds whether whether it is cloud or a device this will show you right next to the device status, whether it's online or offline, and also it's going to show you the routing that is done and any event that is generated for this specific device.13:56When you click on event logs, most of the detail will be covered in the demo part of it by Satish and also you have the tools under the tools, you'll be able to see if there's any kind of a capture in case this being an access point. If there's any kind of a capture that's taken for this AP would also be checked once you are under the device three 60.14:15From there moving on to client three 60, client three 60 again is similar to the device three 60 is going to give you a more detailed view of this specific client. Starting off from physically showing where the device is connected to which WLC.14:36Or which access point the device is connected to which SSID it is connected and what is the device MAC address, the VLAN status of it, and in case there's any firewall rules that the device the client the client device is bound to, all of this can be checked here along with the, in case any captures that you have run.14:51The store capture can also be viewed from here and again you have the option to choose for how long you'd like to see the data, whether it's for the last day or for the last 2 h reading to three months of time. Webex, once you move to the application three 60.15:09I've taken snapshot from one of the reference application, one of the application where I can explain more data on. So under the assurance dashboard, once you click on the application, you have the list of applications that you can choose from. I've chosen the Webex and yes, this is showing me.15:25Details of where or which site is using this application the most and again who are the client that are currently using this application in case there's any kind of an issue that's happening, how many clients are being impacted as you click on each of these details, this is gonna take you.15:41Little more deep and further and tell you which side the client is located, what time the issue did happen. Now this helps you in correlating and finding out whether the issue is happening on the device level or on the application level or on the SSID level. This makes it easier to find out where exactly.15:58The issue trigger comes from. Next is the topology view. Now to, this makes the job of any network is very easy to find out which level or which layer this device is connected to, where the capture has to be taken, a bit.16:14A pictorical representation of how your layer two, your network looks in the layer two link and the layer three is, is put up here. Event logs again, even logs again, you have the option to choose as you can see from the event log next to the event log there's a dropdown button.16:31You have the option to choose which device you would like to see the logs for, whether it's an access point or a or a WLC or a switch wherever you wanted to see from to which specific date or based on the you have the option to choose it based on the severity that you would like to see or if any specific event that you would like to see.16:49You have the option to apply the filter and check the events that has occurred. Along with that, you have the option to download this file in the CSV format so that you can use it for the later on troubleshooting purposes, the intelligent capture.17:09This is something that I just ex I explained when we were looking into the device three 60 and the client three 60 as well. Once you click on the tools, it takes you directly to one of the options which is the intelligent capture. This intelligent capture is a very good feature I would say because.17:28In moments like like a wireless issue where you need an instant capture to run Instead of waiting for the captures to set up at the same time run and mr. moment, you have the benefit of having the captures scheduled, you can set up the capture for a specific device.17:46In a specific interface for a specific duration of how long ever you want. This varies from five to thousand 200 s. You can set the captures for that long. You can have the captures scheduled and set for. And again, this gives you a privilege as to where you want the output to be stored, whether you want it.18:04To be in the cloud or you want to have it locally downloaded. It gives you the option to do that. What you see on the top, on the extreme right is the sample capture how it looks. You can define the port that you want. You can go specific up to the type of authentication that you have it specifies.18:21What type of port it uses and what are the protocol that it uses? You have the option to set here and schedule, and in case you wanted to make any changes to that again you can go back to the schedule captures, click on there and make the changes accordingly. Summary report.18:39This at a glance again is going to tell you if you based on whatever type of device that you choose, whether it is wireless, as you can see, the device tag that you choose, you can see the overall view or the usage for that specific client or device. It's going to show you.18:57If you've chosen a wireless, this is gonna tell you how many clients have connected, what is the amount of bandwidth that they've used, the total data that's uploaded and downloaded, what are the top clients by the usage is given here? So that in case you wanted to see any specific site, you feel like the utilization is going high.19:13Or any specific WLC you feel that the is being hit by any kind of a memory spike, you can come here, pull up the report and see the usage of it immediately, the compliance. For the SNMP purposes, it's gonna tell you.19:31What is the best of, you know, the SNMP access that you have, what is the privacy level that you have configured if this can be made any better? What is the dashboard SNMP version that you're running on, your authentication mode that you have set or or if this can be enhanced any further, all of this can be checked under the assurance compliance.19:48Alerts again. Alex again, you have the privilege to choose either the organization level or under the network level. This is going to tell you the alert trigger like in case any kind of a tunnel that's down or in kind in case any kind of a power failure that's happening.20:10You get to choose, and see what are the events that you'd like to see in specific active or if there's any, this issue was resolved, if I if I'd still like to go back and check, you have the option to choose whether it is active or the resolve issues, you can click on it and do apply the filters.20:27And this is going to show you what amount of critical issues that are currently happening in case any kind of application that's performing bad or any kind of a port failure, as I said, you can check from the alerts tab, and you can filter it either based on the network level.20:44Or on the organization level, the change log. This is one of the best feature I would say again because this is going to tell you the change log like as to what level this has happened on which network this has happened. When I say change.21:01This change can be anything that is done on the CLI level or through the API or on the dashboard level. You get to see at what time the changes has happened and what network level the changes on which network the changes happened. What was the previous value and what is the new value that changes has happened to or we made to.21:17In case it's specific to any kind of an SSID, again, it shows you which SSID the changes has happened as well. And again, to use this for references, you have the option to download as a CSV file, yeah, the firmware upgrade.21:36Former upgrade again, this is going to show you for the network levels, as you can see from here, you have three options, the overview, scheduled upgrades, and schedule changes. Under the overview, this is going to show you what is the device that you have in each of these network based on the network that you choose.21:56And it is going to tell you what is the current version that it is in and in case any kind of an upgrade that's available or all of that. Schedule upgrades is that you get to choose the network from here and go to the next step and schedule the upgrade whether it could be for the recommended version or it could be for any specific version that.22:13You have, you have the option to schedule it in the downtime, you have the option to choose it specific to the device family, whether it's switched or controller or you want to do it for the all the specific entire specific network. And again, you have the option to choose the firmware version that you want.22:33As you can see from the firmware type, it says any firmware which is gonna tell you, which is again going to give you multiple options based on your requirements as well. And again under the schedule changes, if you want to make any changes to the schedule, you can go back to the schedule changes.22:50You have the option to edit, you have the privilege to edit it from there and make the changes to the schedules that's already done. With that taking a look into the initial onboarding part of it and along with the assurance capability, I'll hand over to Satish so that we can see a deep demo on all of this for now.23:05Over to you Satish. Yeah, sure. Let me share my screen. Thank you but ok i hope everyone can see my screen. Okay, so if you're very new to the Meraki dashboard and if you would like to onboard your cat nine K on the Meraki dashboard, I'll just start from.23:23From the scratch. So the 1st and foremost thing that you do is create a Meraki account. If you log in, if you, if you try to access dashboard.Meraki.com, you will get into this page. You need to create a new account if you don't have any existing Meraki account. So while you create an account, you can choose in which region you're.23:42Meraki account should be hosted. You do have a different region. You can choose based upon where your network is available and what are the security violation that you have within your network. So once you selected your region and if you click next.24:03So you will be asked few details, your email ID, your name password, and the organization name. So when you create the account for the 1st time, you have to provide an organization name. It could be your company name.24:21And if you are creating another account with the same email address and a different organization name, so both the organization organization one and two will be part of your dashboard account. So how do you man monitor it? So once you log into the dashboard.Meraki.com, you will get into this particular page.24:38Which, you will see a dashboard called global overview. So if you go to the global overview page, you will see all the organization that is created by you or that are added to your email address. You'll see all this organization and the management type, you can see two types. One is dashboard.24:58So it's basically a Meraki dashboard organization that you create or you can also, if you have a catalyst center on your network, you can also add your catalyst center as one of the organization on your network in order to get the single pane of glass for your.25:18Catalyst center managed device and managed device. So in this particular example I have three organizations so I'll just click one of the organization Meraki enablement port three. So within this organization, I can create multiple network, network is.25:33Basically your location. So wherever your sites are located, you can create a multiple network based upon your requirement. I'll just give a summarize view of how my network is built. So basically I do have three branches, branch one and branch two and branch three. So if you see.25:52Branch one, you can see how what are the devices available in it. I do have one access point in it.26:12I have a wireless control 9800 also in branch one. In branch two and branch 3II have two switches each. In branch two I have these two switches in the cloud configuration mode which was explaining and in branch three, I have two switches in the device configuration mode. So.26:19I I'll talk about these two modes, how to onboard the devices. So before that, I'll just quickly show you a demo, how to onboard a cat nine K on your.26:39Meraki account or cloud account from the scratch. So, this is a recorded demo that I have. So I have my lab switch available. So before onboarding the switch into the cloud dashboard, I will just validate if I do have all the prerequisites completed. You need to have to.26:52Play new model command enabled on your devices and you need to have the local credential available on your device. If you have TACACS credential, you cannot use that credential to onboard the device on the cloud dashboard. You need to have at least one local credential which you need to use while claiming the device.27:12This is from the Meraki account. So, so this is fine and then I'll check the running configuration specifically for name server. I have my name server already configured and I'll validate the version, so I'm already running on 1715 four.27:32Which is compatible on onboarding the device on the cloud dashboard. So I'll validate the connectivity to the Meraki dashboard.Meraki.com and I'm able to ping the destination as well. So you can just try to ping these two URLs, I think if you can ping these two URLs.27:51Should be able the device can form a tunnel with the cloud Meraki cloud.28:11So after that, after onboarding the, before onboarding the devices into the cloud dashboard, if you wanted to validate if your device is compatible to onboard the devices on the cloud, execute a command called show Meraki compatibility. So that will tell you if your device is compatible or not for the cloud dashboard.28:18So I can see my the devices.28:38Compatible on the cloud for both cloud monitoring and cloud management. So then I'm good to onboard the devices on the cloud. So to onboard the device on the cloud, you need to go to the config mode and you just need to type this one command, service meraki connect.28:41So this is the one command that you need to do in order to automatically onboard the devices on the, cloud dashboard. So once you execute this command, you can see the switch one has registered and it is enabled and you will see some logs. It says that switch is trying to contact the cloud dashboard.28:58And the tunnel is up right now. So in order to validate it, if you do show Meraki Connect, you can see if the Meraki tunnel is up or not. So I can see the tunnel status is up. I can see two serial number one. One is the physical serial number that starts with FO. The other is.29:18Is the cloud ID. So the cloud ID is generated once you enter Meraki service Meraki Connect. So this cloud ID is very much important while you claim the devices from the cloud dashboard.29:37So I can see the tunnel statuses up and I can see this cloud ID. So just copy this cloud ID in a notepad. So this will be very helpful while you claim the devices. So now I'll go to the Meraki account that I created.29:52And under organization, go to the inventory tab. This is where you will claim any devices on the Meraki account, even the Meraki devices. So now you have an option of claim device. So all you need to do is copy this.30:10Cloud ID and enter here and click claim device. So then you will be able to see this device gets claimed on the cloud dashboard, your cloud dashboard. So in order to ok so before that, once you claim the device, you need to add the device into the respective net.30:29Work that you created. So you already created a network called CSS_lab. I wanted to add into this particular network.30:49So I'm choosing an existing network and this is where you will select whether you want to onboard the device on the cloud configuration mode or the device configuration mode. So I'll I'll tell you the exactly I'll show you a difference between two modes in my demo. As of now I'll just select the device config.30:56Integration mode and I'm providing my local credentials of the devices on the, on this particular dashboard. So this is very much important because your Meraki account should log into your devices, take SSH and get the telemetry information. So I'm adding this device to the network.31:16So within, three to 5 min, you will see the devices added into the network and you will be able to get the assurance capability from the cloud dashboard. Yeah, and the device configuration configuration source is showing us device.31:35So, with that, I'll just show you a demo. I I'll just show you the two different modes. So as I said, the branch two is on, is onboarded with two switches in the cloud mode and branch three is onboarded with two switches in the.31:52Device mode. I'll show you a difference. Let me go to the branch three 1st, which is onboarded in a device mode. So if you go to the switching and if you go to the switches.32:08You will see all the switches that are onboarded into this network and and also you can see what mode the switches is onboarded into it. So you can see the configuration source it shows.32:25Device mode. So, if it is showing us a device mode, you'll not be able to make any configuration from the dashboard itself. Yes, there is a way to do it but the thing is if you go to the switch, if you click the switch, you will have an option to configure the switch.32:44Yeah let me refresh this page. Yeah, so here you can see the switch details. I come into this assurance capability, but if you can see the configuration sources device. So if you go to the ports.33:04You can see what port is configured with what VLAN and all those stuffs, but you'll not be able to make any changes over here. But let's say if you wanted to make the changes, the only way to make the changes is go to the cloud CLI and launch a terminal.33:22So it will log into that switch. Yeah, so here I have made a ways if I log into the switch, it could directly go to the config mode. You can, but, but you in on in settings you can also make sure that users can log into the switch only with the username and password that is doable. So if you wanted to.33:38Do any configuration, you can do it from here.33:59But, whereas in the configuration process cloud so I'll go to the different network branch two where I have onboarded the switch in the cloud mode. I'll show you what is different on the cloud mode. So if you go to the switching and switches, the same tab, you can see two switches.34:03That are onboarded in the cloud mode over here. So now if you go to the switch here under the ports, remember you don't see the cloud CLA option. Instead, you have an option to check this mark this port.34:22And you have an option to edit it. So you can edit this port, you can make it as a trunk, you can make this configuration changes from the dashboard itself. So that's the difference between the device onboarded on the device mode and the device onboarded on the cloud mode. And one important thing is, let's say if you onboard the device in.34:37The device configuration mode, your existing configuration will be preserved. Whatever you have as a configuration that will be preserved.34:57But if you onboard this switch as a cloud mode, your config will be viped and it will be a brand new switch connected to the Meraki and you need to do all the configuration from the Meraki dashboard itself. So we recommend if your switch is already in the production or if it is a core switch.35:05A better onboard it in a device configuration mode, but if it is a greenfield environment or if it has an access switch where you can do the configuration, it's just like a access port or trunk port configuration, then you can onboard it in a cloud mode in order to get the full automation capabilities.35:23So let me again go to the branch three and I just wanted to cover one more thing in this. Let me click one of the switch.35:40Yeah.36:00So, so with this, you will be able to do all the troubleshooting, so before coming into the switch site troubleshooting, so I'll I'll just show you how to do a network wide troubleshooting, the device level troubleshooting, and then I'll talk about the organization level troubleshooting. So 1st into the device level troubleshooting.36:03So I.36:23I'll just open so all the clients connected to the particular network which is cloud monitored wireless. So even if there are like multiple switch onboarded, you'll see.36:27All the clients that are connected to all the switches within this network. So, here you can also see the usage of the client.36:44The device type of the client, the description and what switch it is connected to. So if you wanted to go back to the partici one last one month, you can click last one month, you can see the usage of the clients in this particular network for last one month of time. And also you can see what are all the applica.36:53That are used by the client overall all the clients, you can see the different application that that is mentioned over here. You can see all this application available. And within each and every application you can see what is its usage in terms of percentage also. But if you wanted to troubleshoot a particular client, you.37:13Just click the description of the client.37:33So that will take you to the client three 60 page, where you can see the complete information about that client for the last one day, you can, you can go to the last one week also. Let's say if a one if a particular client is complaining that they have some issues, you can click this dashboard and you can see what happened.37:35Open at that point of time for that particular client.37:55You can see also the usage of the client for the last up to last one month and what are the application that are used by the client. So remember if you wanted to get an application visibility or traffic visibility, the switch that you onboard on the Meraki dashboard should have an advantage like.37:59Licenses, but for the basic monitoring, the switch level monitoring or organization level monitoring, the DNA essential licenses should be enough.38:19So, and then I wanted to talk about the other functionality under the network wide. So, if you go to the network wide, if you wanted to see the topology of that particular network, you can click the topology, you can see the different topology of this network.38:28Let me go to the branch one and I can see the wireless controllers and the access point in the branch one. So the next tab that I wanted to explain is, the packet capture, intelligent packet capture. Once you onboard the device, your wireless or wired devices.38:47You should be able to do any packet capture from the Meraki dashboard itself.39:06So you can select what type what kind of devices that you want. So let me, if I'm selecting I wanted to do some kind of capture for my access point. So I can select access point in it and I can select whether I need to select the I capture for all the access point for the selected access point.39:11And you can select the wired capture as well as wireless capture and you can save it to the cloud and you can select the duration also by default it is 60 s. So if you start, you can start the capture now or you can also schedule the capture. Once the capture is done, it is going to be saved to the cloud itself, and if you.39:30You wanted to go and view the capture, so I have already scheduled a capture for us today. I'll show you how it looks.39:50So this is the capture that I have done and if you click this, you can see for the 1 min that I have selected what all the packets that capture packets that can be viewed over here. So you can view it from the.39:58Cloud dashboard itself. You don't need to download it and open it on your laptop with the Wireshark, all those things. You optionally you can also download it, but most of the basic filtering that you can do it from the dashboard itself.40:13So, and also you can get some event logs, let me go to the, another network. So if you wanted to see what are the events happening on my network, you can select what type of devices. So I wanted to view it for my catalyst switches that are onboarded.40:30So I can see all the events available. So, I has I have selected I need the events before this particular window, so I can see all the events, but it's very hard to go and each check each and every event. So you optionally you have a download, one is download, the other one is summarize this. If you.40:50Click summarize this, it is going to analyze all this event and it is going to tell you what are all the things that you need to look into this in order to take an action. So it tells there are some ports which is going up and down port flapping, the native VLAN mismatch.41:10And there are some configuration changes happen. So you can click summarization and you can see the important event that is happening on your network. So this is all about the network wide monitoring. I wanted to cover something on the device level monitoring also. So.41:28Let me go to the switching and switches. So let me cover the wired monitoring. So branch three is onboarded with two switches, which is in the device mode.41:48If you click the switch, so it will take to the switch three 60 page, where you can see the usage of the switch for the last 2 h, you can, you can click last month also you can you can see the detailed usage, the connectivity of the switch to the cloud dashboard, the.41:57Times that are connected to this switch for the last one month of time and its usage information. So you always click the settings icon, you can select whatever information that you need.42:17And if you wanted to see the port level configuration of the switch, you can see, click the port so you can see what are the access and trunk ports that are connected to it. And you can see this information in a graphical representation also.42:29As I said, you can also go to the cloud CLI and you can make any configuration changes of this switch. You don't need to be in a corporate network in order to do the changes. You can log into the cloud cloud CLI and you can make the configuration changes from here.42:45So let me refresh this page, yeah. Yeah, you can also see the health of the device information. So basically you can see if there are any power supply failure of the CPU.43:03Memory failure in this particular window.43:23So the power supply stack power PoE usage, so all those information can be monitored from here. So you can also see the event happened related to the switch. So instead of, so we have seen it under the network, it tells about the event happened on all the switches, but if you want to see for a specific switch, you can.43:27Can see the event log over here as well. And the very good tool here is the tool section here. So you can do the basic monitoring like can ping from the switch to a certain destination recycle the port Mac forwarding table, so you can do some basic troubleshooting from here.43:47As well.44:07So this is how about your device configuration mode switches. Similarly, if you wanted to monitor for your cloud configuration mode switches, you, you will get the similar option over here, so under switches, if you click the switch and you want the switch in the cloud mode, you, you get the similar option that I.44:09I mentioned for the device configuration mode.44:28Just that you might see more option under the tools because cloud mode has a better assurance capability than the device mode. So, this is all about wired troubleshooting. So in terms of wireless, so I have a wireless controller and branch one with one access point.44:33So I'm going to that branch one, and under wireless, you can click wireless list, you'll see all the wireless controller in it. So I have one wireless controller with one access point in it. So if you click this wireless controller.44:49Similarly you can see the summary of the device, the connectivity of the device, clients connected to the wireless controller, the access point connected for the last one day CPU memory utilization of the devices. You can see the port information, the port, historical usage, the layer two and layer three interface information.45:07Similarly, if you wanted to do any configuration changes for the wireless controller, you can launch the cloud CLA you can do. And if you wanted to monitor for your access point, you can come to the AP tab. So by default, once you onboarded the wireless controller, the AP will be onboarded on the same network. But if you want the AP to be in a different network.45:27You can click this edit option and you can change the AP to be in a different network. So let's say if there are 20 access access point in a wireless controller ten access point you can map it to the network A and ten in network B that's doable.45:46And if you click the access point, so that will take you the IAP three 60 kind of view where you can see more information related to the wireless. So, see in this particular page you can see.46:00The current clients connected to the CPs, the utilization of all the radios that are broadcasted by the SAP this AP and you can see the channel utilization, historical connectivity and the usage information of the CAP.46:16And you can also see the connection details where you can see for all the clients connected to this particular access point, how many of them are associated, authenticated and got an IP address. And you can also see the.46:33Performance of this API I I think I do have another dashboard where I can see a lot of clients connected to the wireless controller, I can go to this page. You can click here and you can go to the APs.46:49And let me click one of the AP, and here into the connection performance tab. So I can see the performance of the clients that are connected to this AP, the current client.47:05Clients connected to the AP yeah under the performance.47:25Yeah, the usage of the client, number of clients, the average signal quality, the average wireless latency, the channel utilization of this AP, the data rates. So you can monitor the AP related stuffs if you click that APs. Also similarly, you have an assurance dashboard, basically.47:32The assurance dashboard can provide you if there are any anomalies happening on your network. Your your Meraki dashboard will know what is the baseline of your network. Based on that, it can tell you if there are any any anomaly happening on your network. You can see how many successful connects.47:52So it's about 90 percentage and how long client takes to connect to the society, what is the utilization of the AP coverage of the AP. So all those monitoring information you can get here. Similarly, you can get the health score of your wired wireless devices as well. It can also.48:12See the application health also if there are any outages that happen related to that particular application. So this is all about the device level information that you can get once you onboard the device on the cloud dashboard. And some lastly I wanted to cover something on the organization level assurance. So.48:32If you go to the organization, the 1st fore foremost thing is I would say go to the summary report. So we have a very good reporting capability from the cloud dashboard. So you can either get the report for your complete organization or else you can select the network. So.48:52Let me select one single network.49:12Branch two switch. So I can get the usage of the network, the top devices client connected to the network, the top clients by usage, manufacturer by top client device manufacturer by usage, OS by usage, top of.49:15Application so I'll be able to get all this reporting functionality in this particular widget, so I have generated this report for last one day, but you can go up to one month as well. You can also select this export this report in the Excel sheet or you can also customize this report. If you don't want any information from here, you can also.49:35You move it from here. And also you can schedule this report, you can schedule this report like weekly or monthly basis and get this report via your email ID. So you can schedule this report with you can upload your image, you can add your email address in recipient and you can get this information on the email as well. So, so the next.49:55This thing that I wanted to talk about is the change job.50:15So if you wanted to see what are the changes that are happening on your network, you can see over here. So you can see the changes that are happening on your network. So if you wanted to go with particular network, I can select, like.50:20Branch.50:39Three and I can see the changes on the branch three only. So I can see the branch three changes as well. So I can see that I have made some changes in my name. I can see what is the old value and what is the new value. So you can see the change information on the organization.50:42Level on the network level as well. If you onboard multiple wireless controller on the cloud dashboard, you can go to the wireless controller page, so that will list you all the wireless controller that you onboarded on the cloud dashboard. And also you can.51:01Go to the firmware upgrade page. If you wanted to do perform any upgrades for your devices, the cat nine K that are onboarded on the cloud dashboard, you can do it from here so you can click schedule upgrades.51:20Let if I wanted to do any upgrade from my branch three devices, I can click branch three and schedule, it tells what is the current firmware and what are the target firmware available for that particular devices in the network. I can select the target network. It will tell you what are the things that you need to fix before an upgrade. It, you can value.51:35Updated.51:54And once you validated it, you can acknowledge and you can just click next. So you can also schedule the upgrades as well ok so and the last thing I wanted to cover is the alert section, so if you go to the alerts under the organization level.51:55Yeah, so alerts is available both on organization and the network as well. So in the organization you can also filter the alerts in terms of network as well. So you can let me select it for the larger window and.52:15Let me select all the alerts. If I wanted to view it only for my wireless, which is in the branch one, can select only the branch one, and I can see for the last six months of time what are the alerts that are generated on my wireless which is in the branch one. So it can categorize what are the critical alerts, what are the warning alert.52:32Alerts and what are the information alerts. So we can also configure alerts.52:52And get those alerts via email or webhook as well. So you can select what are the alerts that needs to be enabled over here. So, so I have, we, we have seen how to onboard the device, how to create an account with different organization, how to onboard the devices.52:58After onboarding the devices, what are all the assurance that capability that we can get from the network wide tab and the device wide tab and the organization wide tab. So from here I'll just hand over it to Lasha. So Lasha will cover.53:16What are all the automation and AA capabilities within cloud dashboard that you can leverage for your catalyst devices? Thank you Satish and for that presentation and the demo. I hope now.53:33All of our members have understood how to onboard the devices and what are all the capabilities that we can make use when we onboard is six devices on Meraki. So let me explain you some of the automation capabilities that are available.53:49On Meraki Cloud for iOS XE devices especially. Now, if you are new to Meraki, then there is a workflows which we call our Cisco workflows, which are hosted on cloud.54:08That is on Meraki Cloud, which will give you access to create workflows by just drag and drop the elements that is if you have worked within, you might observe that most of the automation that you do there, it's just you drag the boxes and drop there. So in a similar manner, we do have the workflows where.54:24Where you get to use all most of the Cisco APIs that are Meraki Catalyst Center, Snow.54:44I mean not SD WAN, ICE FMC, so in this way, whatever APIs that these products have, those are available as drag and drop elements, you can just drag and use those APIs for the products that you're using.54:52And similarly, you can use it for the device Meraki as well. And then there is this 3rd party drag and drops as well like snow ones, but if you like to create some change requests or want to know about some change requests or issue information, so whatever it might be, you can get information from snow also that.55:08Is from 3rd party as well and update them delete them. So in this way.55:28You can play around with the Cisco APIs and 3rd party ones as well. And also if you have the API keys for any of the llmiss, you can integrate LLM also, so there is an option to drag a element which is LLM. You just drag that box and.55:32If you, whatever API key you have, just create that, you just add it and you can integrate ELM as well. Now, all the workflows, I mean, there are several workflows on Meraki dashboard. So some of them are pre built, which is that Cisco has built them or it might.55:52Maybe some other person might have built and submitted to Cisco.56:12And upon reviewing it and going through rigorous testing, if it's useful for many customers, then Cisco will make it approved for everybody or community, so which is created by community. So in this way there are some prebuilt Cisco workflows which you can make use.56:16Or if you would like to make some changes in those pre built, what you need to do is you just need to I mean, so whenever if you want to use any of the workload that is available, you install it, you use it as it is. Or if you want to make any changes, you modify it, which is modified. And let's say if you want to create a very customer, so then.56:34You can just spin up a very new one.56:54From scratch and that will be your customer. So today, whatever we'll be viewing in the demo, that will be a customer one. So these are some key elements in the automation on Cisco workflows. So exceed and automation hub, so this is where you will get to see all the workflows that are.56:58Are provided by Cisco.57:18Partners or the community. So as mentioned, Cisco has created few workflows and then if And then there are people who have created and those workflows have been submitted and they have been approved and community ones as well. So in this way, whatever approved managed by Cisco are available in this exchange.57:21As the default, as the workflows, if you would like to use any one of them, you have to click on this install option.57:41And you use it. And then so these are all the validated designs that is as mentioned, Cisco has reviewed all of them and provided for the open source, and these are updated regularly and often.57:48If let's say if you have any idea, you can create your own workflow and if you feel that it can be helpful for other users, you can submit it and it, if it's really important, then it will be also approved.58:06Workspace. So here is like it's like GitHub workspace where you can view all the workflows that are created in your organization. You can see the status, owner and details that is if it's validated or executed when it's executed. So you can see all this information on the workspace.58:24And if you'd like to duplicate or edit or share any of the workspace that I mean any of the workflow that also can be done.58:42And you through this you will be managing your team that is, you will enable the network operations for daily or network devices to create the tasks Peter so this is where actually you create the workflow. So take.58:50Till now those are all the ways to manage a workflow, so but here it is where we actually created and executed. So you see right these are all the drag and drop boxes that I was telling. So you just these these will be available in this site, you just drag the box that you want and.59:10Place them here, drop them here. And then you can, there is a lot of user flexibility available here that is you want, if you want to create a Python script that is available, if you want to create a Json that is available creations, loops, serials. So in this way there is as much as user flexibility available here.59:31And as mentioned, these are, there are some out of box which are pre built. You can modify them or you can customize the whole workflow from the scratch. So.59:48AI driven dynamic workflows, which means now let's say you want to create a workflow, but you you can just you can just type that I want to create the specific workflow with all the information and AI assistant which is there on dashboard.01:00:05Can spin up a workflow for you and also can execute it for you. So it's just you tell AS system what you want to do and it will be able to help you. And then, as mentioned, it can execute also. So let's say you have already created a workflow. Now in our demo, I have already created a workflow. I just tell my AS.01:00:22Question to execute it. So then it will keep on asking me that is it will keep on confirming with me if I want to proceed with the next step. So it's it's not like agentless I mean it's not like humanless. There is a human in the loop to confirm whatever step it's going to take.01:00:42So, let me just go to the demo. So this is one of the lab. Now here in the top right, you will find AI assistant.01:01:01If you click on it, by default it will be a very small window, but I have selected the full screen. You can select docked floating window based on your requirement and here you can, so there are some pre built questions like you can just go if let's say you're trying to troubleshoot.01:01:19Then you can just go to this troubleshoot and.01:01:39Find if this information that you are looking for can be achieved through one of these questions. So in that way there are some already pre built questions which will be helpful for you in troubleshooting, I mean in the in your network management. And then.01:01:42This new, if you click on this button, you will be able to see all your history, all the chat that you have done with the AI assistant previously. So you'll be able to see the history of your AI assistant and you can click any one of them and continue the chat.01:02:00So now let me start a new chart, yeah.01:02:18So, let's see I want to understand what are the current issues in the network. I just say what are all the current issues in the network and it will be able, it will analyze all the issues that are there in the network and give you a.01:02:33Info, give you a report which is human readable instead of all the logs and everything. So it will just take some time. Meanwhile, yeah. So you, if you click on this thinking, you can also understand what it's actually doing in the background, like all the completed thinking and the implementation.01:02:50What is currently going on as well. So it will just take maybe few seconds to analyze and once it collects all the information that is required.01:03:09It will summarize and will give us the information yeah it is compiling the information so as you can see, there are several issues here.01:03:19So once it has retrieved all the issues information, it has generated this table kind of thing where you can just understand, ok, there are four types of issues, either that uplink degraded RF health issue, when packet loss VLAN mismatched, and then for each of the issue, it is also giving us the description.01:03:35And next steps also. So now it's up to us if you want to go to each of the impacted device and understand the issue in detail and follow the next steps that is given by assistant. So it will also give you the sources from which this information is retrieved.01:03:54So that if you want to check if this information is valid or not, you can go there and check it out. So next actions are also available. You just follow these next actions and if the issue is not resolved, then you can go to each of the device where it and understand the issue in detail.01:04:13So let me go to some of the other charts that I have had with the assistant. So as you can see I just asked what are the top five things to try today with the assistant and it has given me these information. So you can mo I can monitor I can ask what are the security events in my network troubleshooting, show me all the assist.01:04:31Session failures for wireless clients and sort by failure count, and I can also now if you are new to then it's a very cool thing which is you can view all the cases that you have opened regarding Meraki on the dashboard. So you can get that case summary also here, you just tell what is the status of the key.01:04:51Case and case number it will give the information. And you can also create the cases. And as mentioned, you can create the automated create the workflows and execute them. So it sees help me add a new firewall rule to block all outbound traffic to this IP address on all ports.01:05:11So once you see this, it will either spin up a new workflow or modify the workflow that is currently there. Yeah, and then if this is another chat where I mentioned in a table list all the recent configuration changes across my network and the dashboard account team that.01:05:31Need that change and highlight any changes that might impact security.01:05:51So now it is giving me the timestamp after which this change has occurred and who have made it made this change and what that change is actually about and if it's what the security impact that change has occurred, that change has created. So in this way.01:05:55That has given me this information. Now I want to go to workflows thing. I would like to show you what the workflow that we have created. So as of now, as you can see there are NO devices on this part.01:06:11So let me go to automation and workspace. Yeah, so we have created few workspace workflows here.01:06:28I'll go to this one, claim the catalyst switches in device configuration mode. And as you can see this is this is a customer. So what we have done here is so these device there are three, few devices which are already connected to internet, but are.01:06:46But needs to be up onboarded on Meraki. So what we have done is we have used some of the Meraki APIs APIs here, which so 1st one is get organization by name or ID. So the organization in which I want to onboard these devices is Cisco, so I'm just giving.01:07:05With this one and trying to get the organization ID of that organization name.01:07:25And once I get that, I'm trying to retrieve all the networks that are available in that organization because I want to onboard my devices in CSS lab network. So I'm trying to get all the networks that are available. So I just gave the organization ID that I got from the above element.01:07:30And then once I got all the networks, I passed those networks into a table, all those networks with their ID and the name. And from there I'm creating a for loop which will pass all the networks and find me the network where I.01:07:48Want to onboard my device. So what's happening here is, so you see this yes logic. So here it is trying to find.01:08:08If the the value in the read table from which parses, if it's, if that value is equal to CSS lab, then it needs to execute this Python script, which is actually the script where you will be onboarding the, which will be helping you onboard the device. So you see the.01:08:15This is the URL.01:08:35Which will claim the devices in a network with this network ID. So here again network ID also I have not given by manual I have not given manually. It will be taken from the above element, which is now we are pass passing the networks in the right so whenever the network.01:08:36Value matches CSS lab, that will be the network ID. So that will be saved in this network ID variable and that will be passed to this URL. And here I am mentioning all the serial numbers that I will be the serial numbers which is cloud ID of the devices and the details by device. So here.01:08:56I want to emphasize one thing here team. So I'm giving my name value, I mean username password enabled password. One thing here is in the documentation it is mentioned enabled password is optional, but if you have enabled, if you have enabled password on your device, it is mandatory or else.01:09:16You will be running into a warning when you onboard the device. The device will be onboarded, but once it is onboarded, you will be seeing a warning. And one more thing to onboard the device in the device configuration.01:09:36It is very important that you give the device mode as monitored. But if you want to onboard the same device in cloud, you can mention as managed. So it is very important that you see what is the device mode value that you're giving because if you onboard the device in managed.01:09:50When you want to onboard it and monitor, then there will be interruption because when you onboard the device in cloud config, the whole configuration will be erased. So it's very important that you need to mention that the device mode as monitored Monitored in the sense device configuration mode managed will be onboarded as cloud conf.01:10:09Configuration.01:10:29So in this way I have given all the other devices information also and API key. So the API key can be generated from the organization information. I will show it to you in a minute. So you just need to give the API key and there's some other head headers which are common for APIs and then.01:10:30You just run this request one. So once I have everything ready and then if by chance, if the, that if there is NO network called a CSS lab in this specific organization, then what I'm doing is I'm just setting the way.01:10:50Output workflow result to network not found and workflow errored and then completed. So once that is updated, that is output of the workflow is updated and just mentioning that this particular workflow has failed because we want the device to be onboarded, whereas it didn't.01:11:07Onboard. So now I will just execute it using the AI assistant, so you can execute it by clicking on this run, it will execute, but I want to show you using the AI assistant also.01:11:27So I'll just tell, execute this one. I'll just copy this name workflow. So once I see this, it will ask me about that workflow. It will.01:11:42Upon confirming with me. Yeah, this one, 1st one. So just like how you chat with you, it's a similar manner. Yeah, now you see claim the catalyst switches in device configuration mode. It is giving me the details about the workflow.01:12:02Get organization by name, everything is same, so it is asking me, do you confirm that you want to proceed with this workflow? Yes, I do want to do that. I just say yes and then again it is confirming with me that is so human is there in the loop.01:12:21At every step. So continue and now it will execute it. Please confirm that you want to execute workflow title with these parameters. As of now there are NO parameters. If you want, you can create parameters for your workflow as well.01:12:39Yes, whatever and then it will execute. So here also you can I'll just expand it a little more. Okay I'll yeah as you can see.01:12:56It has executed. From here only from here the AI system you can see the execution of each of the element. As you can see, get organization by name or ID, it is success 200, ok. And similarly, the other ones also will be executed successfully.01:13:12200 success. 200 success and now this is the main one where you will actually be executing the script to onboard the devices, 200 success. The workflow was executed successfully completing all required steps and proceeding the expected.01:13:30Outputs. So now what we can do is we can go to the inventory and check if the devices are onboarded or not.01:13:49So for that go to switching switches yeah so here you see initially we did not have any devices. Now we have three devices in.01:14:00Device configuration, so it will take some time for them to come online because maybe one to 2 min that's it. Once within one to 2 min they will be online. But but I want to show you one thing.01:14:15Yeah, here in the organizations. Oh, sorry. So in this organization settings you will be finding the API key. So by the.01:14:30You can only create two API keys team.01:14:50Systems. Just give me one moment. I think it should be my profile.01:15:02Yeah, so in my profile, it's not an organization team, my mistake, so it's an API my profile, go to this click person icon and click on my profile. And here in the API access, you can create your API key. It is very mandatory that you copy your API key because you.01:15:12After you create, I mean once you create the, once you click on create API key, you will be given an option to copy it. It's very mandatory that you copy it and then create it because once you create it, there's NO option that you, for you to again go back and.01:15:32And view the access key. I'm sorry API key, and then at the time you can only create two API keys. If you want to create a new one, you have to revoke it. And if you revoke it, if any of the scripts are using that specific API key will not be working anymore. So it's very mandatory that you.01:15:49Save the API key that you are using. And yeah, so that is the demo for AI and automation team. I'm sorry, let me just share my screen again. Sure.01:16:09So I'll let me just quickly go through the deck. So there is another session that is coming on Meraki, which is advanced features on dashboard for the iOS XE devices.01:16:29So these are some of the points that needs to be remembered when you onboard the device. So we need to ensure that all the onboarding prerequisites are met, that is all the NTP DNS.01:16:48Connection to the dashboard.com, everything should be ensured. Everything should be met, and then follow those streamlined onboarding workflow including device eligibility checks, secure TLS tunnel establishment, device cleaning and network assignment via the dashboard and.01:17:03Once onboarded, you can leverage the cloud monitoring features like real time topology, client tracking, switch status, troubleshooting tools, and former synchronization, and then you can utilize the automation and AI systems for telemetry for troubleshooting network management and workflows.01:17:23So for your next steps, please keep an eye out for a survey from us, so it will be from Cisco customer experience. It is quick and easy and we really appreciate it if you can take 2 min to provide feedback to improve our future ofference.01:17:43And with that, thank you and have a great rest of your day. Bye bye team. Thank you for joining.01:17:59

About this Video

Author : Cisco Customer Success

Uploaded : March 25, 2026

NetworkingMeraki
AI summary icon

AI summary

The recording shows how the Cisco Meraki Dashboard unifies monitoring and management for Cisco IOS XE Catalyst switches and 9800 Wireless Controllers. It walks through step-by-step onboarding (service meraki connect, Cloud ID claim, network assignment), compares Device Configuration and Cloud Configuration modes, and clarifies what is backed up or wiped. It demonstrates Assurance with Client, Device, and Application 360, Topology, Event Logs, Change Log, Alerts, Firmware Upgrades, and Intelligent Capture. It also showcases Cloud CLI plus AI-powered Workflows and Assistant that summarize issues and safely execute automated tasks with human-in-the-loop, including claiming devices via APIs. Scalability guidelines (2000 APs, 20000 clients) and licensing notes (DNA Essentials for monitoring, Advantage for traffic analytics) are covered.

  • Step-by-step onboarding and mode selection to preserve configurations or enable full cloud management.
  • Faster troubleshooting with 360 views, Topology, Intelligent Capture, and actionable logs, alerts, and reports.
  • Operational efficiency using AI Assistant and Workflows to claim devices and run verified changes, with clear scale and license guidance.