The Cloud Monitoring terminology has been deprecated. Everything is considered Cloud Managed now, but the key is where the Configuration resides which is either in the Cloud or on-device.  The reason for this change is because technically Cloud Monitoring was more than just monitoring. We provided the ability to bounce ports, take pcaps, upgrade firmware, etc. That's much more than just monitoring as were making changes to the device via cloud. Please refer to this documentation and Table 1 which gives a good breakdown of the different capabilities of each mode! https://documentation.meraki.com/Switching/Cloud_Management_with_IOS_XE ... View more

Cloud CLI only support read/write on Config Source: Device mode. On Config Source: Cloud mode CLI is only read therefore you would not be able to configure some of the more nuanced config in the Azure ExpressRoute documentation that was linked above. It appears to leverage QinQ which is today not supported in full Cloud Managed mode. ... View more

This is on the roadmap to bring back and you should expect to see more later this Calendar Year. ... View more

Hey Ksumann!   Thank you for your question! I would recommend directing this to the Workflows Community as the Workflow Product team monitors that forum more regularly. https://community.cisco.com/t5/cisco-workflows/bd-p/discussions-Cisco-Workflows ... View more

It is my understanding that VRF's across AutoVPN is supported in this initial release. I've personally have not had the opportunity to test this functionality out. I would recommend opening a support case at this time if something appears off. ... View more

Still waiting for the Product Team to open this up. Unsure if it's planned for 26.1.3 or it will be an Early Access menu option. Have a inquiry out and will report back. ... View more

It is located in the left hand menu after selecting an Access point where IP, Firmware, etc is all located.   ... View more

Hey Chewy!   Please post your Automation/Workflows related questions on the Cisco Workflows community!   https://community.cisco.com/t5/cisco-workflows/bd-p/discussions-Cisco-Workflows ... View more

Perfect, thanks for sharing that output.   I'll do some further testing on organizations with larger scale networks. Currently i've been developing the tool using my lab organizations which don't have more than 20ish networks so I haven't encountered this.   Thanks! -MK ... View more

I think the issue here is the prompt is a bit vague. Can you elaborate on what you mean by "What are the sites where the meraki network extends to"? There's no reference to a network that your looking for information about unless you excluded it purposefully.   Are you trying to determine if the network is a hub or spoke? If a spoke do you want to see which hubs your connected to?  From the below you can see how if you get a little more specific with what your asking you can get more valuable or intelligible information. The LLM is breaking down the natural language and then leveraging the MCP Server and it's available tools to run API calls, parsing the information received and finally spitting it back to the end user in what it thinks is the best response to the original prompt.   Original Prompt: For organization SEMA SE Lab can you tell me which hubs MK-Lab is using? LLM+MCP Response: I'll help you find which hubs the MK-Lab network is using in the SEMA SE Lab organization. Let me start by getting the organization details and then look for the MK-Lab network. Called get_organizations Great! I can see the SEMA SE Lab organization with ID "XXXXX". Now let me get the networks in this organization to find the MK-Lab network. Called get_networks   Perfect! I found the MK-Lab network with ID "L_XXXX". Now let me check the VPN site-to-site configuration for this network to see which hubs it's using. Called get_appliance_vpn_site_to_site   Now let me get the details of the hub network to see its name: Called get_network_details   Based on my analysis of the SEMA SE Lab organization, here's what I found regarding the hubs that MK-Lab is using: MK-Lab Network Hub Configuration Network: MK-Lab (I😧 L_XXXX) VPN Mode: Spoke Hub Network: MK-Lab-DC (I😧 N_XXXXX) Hub Details: Hub Name: MK-Lab-DC Hub ID: N_XXXXXX Product Types: Appliance Use Default Route: False Subnet Configuration: The MK-Lab network has 9 subnets configured, with 8 of them using VPN connectivity: 192.168.128.0/24 - Not using VPN (useVpn: false) 192.168.32.0/24 through 192.168.39.0/24 - All using VPN (useVpn: true) So to answer your question: MK-Lab is using MK-Lab-DC as its hub network in the SEMA SE Lab organization. This is a spoke-hub VPN configuration where MK-Lab acts as a spoke network connected to the MK-Lab-DC hub network. Thanks -MK ... View more

Hey there! If you're referring to this Meraki Magic than i'm the author and developed the tool more so to learn and experiment with MCP and it's capabilities. Happy to add more features and functionality if you can provide some insight into things you're interested in.    I know there are a couple of ecosystem partners working on MCP's for Meraki and I heard there would be an official Meraki MCP server in the future. A reason why there is a smaller list of tools available is because I developed this MCP using Claude and Cursor which limits MCP's to 40 tools.I therefore focused on the tools that I thought were useful, but you can enable/disable certain tools now so we can add more! Happy to help and advance the solution so please provide feedback!   Thanks -MK ... View more