They are all running IOS XE 17.9.5. They were onboarded into Meraki Monitoring around May 2024 using the legacy monitoring onboarding process. They were onboarded at version 17.9.5.    Can I send you a sanitised copy of our configuration? If you're interested of course.  ... View more

Hey @Tony-Sydney-AU I must be the luckiest person in the world! It's happened to all 130 Catalyst switches I've migrated so far 😂 I should probably get some Lotto tickets for tomorrow night 😁 Yeah, the EEM script has failed to remove the VTY lines and AAA configuration every single time, requiring me to run through it with my mini script. It hasn't completed successfully on every C9300 and C9500 switch I've migrated so far. That's why I started thinking it was intentional.    Nah, I am not going to raise a case for this. It's no impact, and we have a quick and easy workaround for it like you said. So, we are just moving forwards, getting off legacy Cloud Monitoring and on to Cloud Management and moving on.    And completely understand the Meraki team only has finite resources and has to prioritise their workload, and with Cloud Monitoring going away in about two months, I understand it is not at the top of their list to troubleshoot weird issues. Especially issues that aren't disrupting services or causing outages.    I just wanted to check and see if there was a solution (now that I know it's an issue), and maybe it was an easy solution, or I was doing something wrong.    Thank you @Tony-Sydney-AU @FCU_JE for your input 😊       ... View more

I am getting the vibe from Meraki that they don't want anything to do with the legacy Cloud Monitoring service anymore. I've raised a couple of support cases, and the general response is "Yep, legacy cloud monitoring is broken. We are turning it off the 31st of March, please upgrade to Cloud Management"  Anyway, I fixed it myself by putting together a little command script that I copy and paste, and it manually goes through and cleans up all the left-over Meraki configuration.    Funny thing is, I actually thought the configuration that was left behind was intentionally left behind haha. I never thought it was an issue until a saw this thread.  ... View more

Hi @Tony-Sydney-AU  Do you know if this issue was ever resolved? Or do we need to open a support case if we are experiencing this issue as well? For us, the AAA configuration, and vty lines are being missed by the Meraki cleanup script. ... View more

Just did some testing, and yep, it does! Very good to know about that trick.   I'll be honest, I've just never tried looking for clients in other networks, just used it to find clients in the network I was looking at.    Thank you 😄  ... View more

Hey Jeroen,  Just double checking - Is this when onboarding switches into the new Meraki Cloud Managed mode? If so, would you mind sharing your aaa configuration? Would love to see how they are setup.  ... View more

Hey,    Not being ignorant at all - I am just as confused as you are, which is why I am asking here lol. It should make no difference; I agree with you.    But during testing, the Meraki Dashboard complained that the TACACS credentials I provided didn't work. Until I provided local credentials to complete the onboarding.    And as I am typing out this response, I think I just realised something else that may have actually broken it. So excuse me, I am going to pop away and do some more testing.  ... View more

Hi,    Yep, so I have seen that as well, and gone through it in detail; this is what I assume:    1. You should be able to use a TACACS account for onboarding.    2. If you do use a local account for onboarding, it can be changed or removed - As Meraki sets up its own local accounts for continued access, monitoring, and management.    But I cannot find anything specific stating that, and I want to confirm before proceeding with a wider rollout. As it will determine how much preparation we need to do before rolling it out.  ... View more

@alemabrahao wrote: Here is all the details that you have to know.     https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide I think you sent me the wrong link. That is for legacy cloud monitoring; I am referring to Enable Cloud Management for Catalyst Switches with Device Configuration - Cisco Meraki Documentation   And yes, I have gone through Enable Cloud Management for Catalyst document, and it mentions that "aaa authentication login default local and aaa authorization exec default local must be configured". But doesn't specify if the onboarding account needs to be a local or TACACS account, or if the account used for onboarding needs to stay around permanently or can be changed or removed.        ... View more

Introducing Cisco Meraki Cloud-First Wireless - Getting up to speed before I go to a meeting with a customer tomorrow. Easy to access, gave me the information I needed, to answer the customers questions.  ... View more