Well, support did not give me any commands.. but just put me on the right path.  1. your switch should already have aaa new-model in the config, otherwise it will not work. Then inspect your AAA commands and the AAA commands that the application will configure on the switch.  The application will configure new VTY Lines and add the authentication group MERAKI: line vty 32 33 access-class MERAKI_VTY_IN in access-class MERAKI_VTY_OUT out authorization exec MERAKI login authentication MERAKI rotary 50 transport input ssh   Then it will add some aaa to authenticate locally:  aaa authentication login MERAKI local aaa authorization exec default local aaa authorization exec MERAKI local   And if you have the aaa authorization config-commands then this config does not allow meraki-user to authorize, and therefore you must have a special rule to allow "meraki-user" to get privilege level 15. aaa authorization commands 0 default group tacacs+ local aaa authorization commands 1 default group tacacs+ local aaa authorization commands 15 default group tacacs+ local   In my case, it was an authorisation problem. In your case it seems the authentication is not working. Do you have the aaa new-model enabled already?   ... View more

I'll second Brandon's opinion. One more thing that I've observed over the time - the old Cisco phones did not like to be plugged into PoE and have also the external power adapter. Other than that, the wiring guys may buy a PoE tester, they're absolutely not cheap... but may identify problems without killing just another phone... ... View more

It is reporting as Repeater because it cannot obtain a lease, not vice-versa.  According to documentation:    The AP only converts to a repeater when one of the following is true: The AP cannot receive an ARP reply packet from the default gateway on the LAN which is usually a local firewall or router The AP is unable to obtain a valid IP address via DHCP   The most common problem: check the cabling.   ... View more

To be honest, I did not get the question but if you refer to cloud control as "What Cisco devices can you add in Meraki dashboard for monitoring" then they clearly said - Catalyst 9k switches - 9200, 9300 and 9500. ... View more

You should start on the documentation page. The switches should be configured in the traditional way and operational. So you should be familiar on how to configure them. Few pre-requisite must be met before being able to enable the switches for Meraki monitoring. Don't go with Meraki management yet, since this is not yet publicly supported. The process to add the switches to dashboard is straight forward without the need to execute CLI on the catalyst, the app will do everything, however if it will not work - the troubleshooting requires you again to interact with the CLI.  Good thing about catalyst is that they have console - so the client can connect them to console in case you need to access them remotely.   https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Overview_and_FAQ ... View more

the sunglasses are nice but I think smaller fonts and darker colors would be a better reward... ... View more

Do you think they teach Meraki now in the college?! 🤪 ... View more

Unfortunately, there are many more in the same boat, but this can't be done with Meraki MX.  So, the only way to do it is with a layer3 device in front of the MX which will do some routing and NAT. ... View more

New day has arrive but no lights in the end of the tunnel. The job from yesterday, todays return this beautiful information.... https://api.meraki.com/api/v1/networks/L_690XXXXXXXXXX097/devices/importStatus?jobId=6XXXXXX4 {'error': 'timed out', 'results': {'capabilitiesState': 'DIRECT_STARTED', 'configState': 'UNKNOWN', 'connectionState': 'CONNECTED', 'status': False}}     ... View more

Still not working to add the device for monitoring.  By checking the logs, everything seems to be correct and the application queries for an device import job id which does not seem to be promising.  { "results": { "connectionState": "NOT_CONNECTED", "capabilitiesState": "PENDING", "configState": "UNKNOWN" } }   Minutes later, I have queried the same endpoint and got this status, but the device still does not show in dashboard.   {'results': {'capabilitiesState': 'DIRECT_STARTED', 'configState': 'UNKNOWN', 'connectionState': 'CONNECTED'}}      Giving up for today. ... View more

Yes, I've seen your comments in the other thread and I went ahead and added an MS390 to the network to set the Unique Client Identifier, however, now I am stuck at the pre-check with " Device is not eligible for onboarding. Reason: Device SUDI was not found" on both switches, and I can't get out of it... ... View more

docs are saying 17.3.x - 17.7.x ... View more

This is what I have done, but I don't have very good experience with support on new features and now I have the same feeling. From very few posts here on community, I can see that each try is a "special" case that has to be troubleshooted individually, which is suggesting that the process is not even beta, but in alfa stage.  It is clearly a feature that many of us are interested in, so would be nice if we can see some fast fixes. ... View more

Yes, of course.  Check the developer hub, on the right side you have the examples for Python using the Meraki library or python requests library. https://developer.cisco.com/meraki/api-v1/#!update-network-wireless-ssid   ... View more

I experience the same behaviour with MR56 running 28.6. Two AP's connected to different switch models, the same behaviour, however, it does not happen too often. It could be once per week or more rare.  Did not dig further what exactly happens, but looking at the other thread, makes me want to dig dipper next time when it happens. ... View more

As far as I've been able to understand it, Meraki will only handle first entry in the role attribute, so if the Meraki role is not the first in the list, it will not work. I have asked our ADFS colleagues to send in the role attribute the memberOf group which only contains a specific string. ... View more

You might as well, think of redesigning the actual solution. The actual one might be outdated and was valid few years ago because this is what Cisco sold us... but things are changing meanwhile..   ... View more

and what is the problem to list one device and substract eid from the URL?   {'address': '', 'firmware': 'wired-14-53', 'url': 'https://n333.meraki.com/NetworkName/n/xxxxxdbd/manage/nodes/new_list/57239045832485'} {'address': '', 'firmware': 'switch-11-22', 'url': 'https://n333.meraki.com/NetworkName/n/xxxxxcbd/manage/nodes/new_list/457203458394437'} ... View more