I knew it had something really simple 😅   Thanks for the quick answer ! ... View more

It seems like the postman collection is completely broken 😥   I think that I was using an old version of the collection (few weeks old maybe) because now that I have updated it (using postman.meraki.com, same as you) I see some very weird things: There is no description associated to each endpoint anymore you are right The parameters in the URL start with a colon (eg ":networkId") instead of behing put between two brackets like before : "{{networkId}}", so Postman is not able to interpret them as parameters anymore Headers seem to be empty, while they used to contain at least the "application/content" and the "X-Cisco-Meraki-API-Key" keys   Not sure to whom this should be reported to... ... View more

Strange indeed... The postman collection does shows the parameter, so I guess it's only missing in the Postman docs   ... View more

Hello Ritish,   There is an option to do that using the Dashboard API. Use the "Create a new network" endpoint and put the network id of the network you want to clone in the payload: def payload = [ name: xxx, type: xxx, timeZone : xxx, tags: xxx, copyFromNetworkId: network_id ]   ... View more

Have you tried disabling the Bonjour Forwarding feature ? I don't know if this could explain your issue (don't think so) but If all devices are in the same VLAN it shouldn't be required anyway. ... View more

Turns out that this is supposed to be a "one-time error" from Meraki. Their golden rule is that new API releases should not break the structure of existing API requests, which they have failed to achieve in this case.   The solution was "simply" to remove the encryptionMode attribute from the request. ... View more

That is exactly what my Meraki SE suggested to me: using the Webex Teams to follow closely what they release on the API sode.   Still, I'm a bit pissed off that they don't provide "retro-compatibility" when they modify their APIs, it should be a basic rule.   I will try your suggestion (removing the encryptionmode attribute) but I noticed that they have also: Added new attributes that seem to be mandatory Removed the possibility to set some existing attributes to "null"   If I find the right modifications in the payload I will share it in this thread.   PS : The Webex teams logs does show that they have changed the encryptionmode attribute: old objects: {'description': "The psk encryption mode for the SSID ('wpa', 'wep' or 'wpa-eap')"} new objects: {'description': "The psk encryption mode for the SSID ('wep' or 'wpa'). This param is only valid if the authMode is 'psk'"} ... View more

Since the API endpoint doesn't seem to exist, have you tried adapting your script to: Disable the email alert that is triggered by the port status change Disable the port Enable the port Enable the email alert again   Of course you'll need to get the network ID for each switch but that shouldn't be a big problem. ... View more

Hello Prashan,   That's a funny coincidence, I noticed the exact same issue earlier today. I spent a few hours scratching my head and switching between the Meraki dashboard and our Cisco ISE (which handles the RADIUS requests) and I finally figured out what was the issue.   In our case: all our ISE policies start with a "if Wireless_802.1X". This checks two things from the RADIUS request fields: NAS-Port-Type = Wireless-802.11 Service-Type = Framed Interestingly enough, it turns out that if you use the "Test" button the Meraki AP will not include the "Service-Type" information in its RADIUS request. Because of that the request does not pass the "if Wireless_802.1X" condition and is rejected.   You can see this behavior with a packet capture of the AP uplink port. As you can see below  only the NAS-Port-Type is sent:   However during a real user authentication, the AP correctly sends both information to the RADIUS server so the authentication is working fine.   So I would check whether you are also using the "Wireless_802.1X" condition on your RADIUS server or not. ... View more

Alright, here it is. A few comments: Just update everything that is between <> and the script should run fine We only have 3 organizations so I decided to hard code the org name and org ids in the script out of laziness ; now of course you can use an API endpoint to get this information and put it in an array instead of hardcoding it The scripts only reports SSID information that I cared about but of course you can update it to collect more/everything import json import requests import sys import csv # Define organizations orgs={'<orgName 1>':'<org Id 1>','<orgName 2>':'<org Id 2>','<orgName 3>':'<org Id 3>'} org_names=orgs.keys() # Define API URL and API key base_url='https://api.meraki.com/api/v0/' API_KEY = '<ApiKey>' with open('<filepath>', mode='w',newline='') as report_csv: report = csv.writer(report_csv, delimiter=',', quotechar='"', quoting=csv.QUOTE_MINIMAL) report.writerow(['Org name','Network name','SSID name','SSID Authmode','SSID Encryption mode','WPA mode','VLAN','RADIUS servers']) for org_name in org_names: #Get list of networks in each organization print("Cycling through organization " + org_name) session = requests.session() headers = {'X-Cisco-Meraki-API-Key': API_KEY, 'Content-Type': 'application/json'} networks = json.loads(session.get(base_url + 'organizations/' + orgs[org_name] + '/networks', headers=headers).text) #Get list of SSIDs in each network for net in networks: ssids=json.loads(session.get(base_url + 'networks/' + net['id'] + '/ssids', headers=headers).text) #Write csv file with various information for ssid in ssids: if "Unconfigured" in ssid['name']: break elif '8021x' in ssid['authMode'] and ssid['useVlanTagging']: row=[org_name,net['name'],ssid['name'],ssid['authMode'],ssid['encryptionMode'],ssid['wpaEncryptionMode'],ssid['defaultVlanId']] for index,radius in enumerate(ssid['radiusServers']): row.insert(7+index,radius['host']) report.writerow(row) elif '8021x' in ssid['authMode']: row=[org_name,net['name'],ssid['name'],ssid['authMode'],ssid['encryptionMode'],ssid['wpaEncryptionMode'],'No tagging'] for index,radius in enumerate(ssid['radiusServers']): row.insert(7+index,radius['host']) report.writerow(row) elif ssid['useVlanTagging']: report.writerow([org_name,net['name'],ssid['name'],ssid['authMode'],'','',ssid['defaultVlanId']]) else: report.writerow([org_name,net['name'],ssid['name'],ssid['authMode'],'','','No tagging']) report_csv.close   ... View more

I've written a small Python script for this exact same need. It goes through all our organizations and their attached networks and lists all SSIDs in a csv file. You can PM me if you want the script, it'll probably need some adjustments but that's not a lot of work.   The script is probably ugly so I prefer not to attach it to this thread, but it does the job. ... View more

Hi BBDave,   We ran into the same kind of discussions when we had to choose how we would use the dashboard. We decided not to use templates because once a network is attached to one there are not so many settings that can be overriden. In a way it is good since you are making sure all of your networks are configured in the same way but in the other hand you give up on some flexibility if you want to fine tune some settings that are specific to a site.   We prefer to create new networks by copying from an "empty" one which has all our settings, and then we are free to adjust them network by network. ... View more

I guess this is how we are going to configure it in the end if there is no "cleaner" way ! ... View more

This document is quite detailed, I had never seen it before. That being said it goes a bit quickly on how to configure thousands and thousands of access points :   "Repeat steps 1 through 7 for additional Meraki access points that will be used in the ISE deployment"   I really want to avoid having to manually configure a network device on the ISE everytime we deploy a new AP. ... View more