Meraki

ww · ‎May 10 2022

Life ain't easy on the phone 😆

RaphaelL · ‎May 10 2022

I'm using this endpoint daily without any issues. Have you tried to remove some of the filters ? Like OS

KarstenI · ‎May 9 2022

Let’s wait if any “official” joins this discussion. If not, they are likely equally confused as we are … 😂

PhilipDAth · ‎May 8 2022

If it works fine in Postman - you'll need to go back to AppGyver support. CORs errors happen when you attempt to access one domain while using another. For example, let's say you have google.com open in your browser, and then your browser has some javascript that tries to open api.meraki.com - that will cause a CORS error. api.meraki.com should be called by back end code only.

brc6985 · ‎May 5 2022

This is definitely an issue on Meraki's end. I have been experiencing the exact same problem for the past few years, on API versions 0 and 1. Sometimes increasing the timespan seems to do the trick, other times I have to paste the URL of the API call into a browser (while I'm logged into the Meraki dashboard) and try to refresh it a few times before I'll get any data back. Honestly Meraki's back end is a bit of a mess. They have straight up accidentally deleted our floor plans, and other configuration items, from their DB. The API is unreliable and inconsistent with returned data. Local device SNMP implementation is terrible (can't even get serial number or uptime from MRs). SNMP polling of the dashboard has timed out EVERY SINGLE ATTEMPT (sometimes after a few hundred results, sometimes after a few thousand, but still never managed to complete an SNMP walk on the dashboard). And I've seen loads of other problems with the group policies and device fingerprinting.... the list just goes on... Anyways, sorry to get off-topic, but it's just super frustrating having to deal with their unreliable infrastructure. I have not found any workaround for this specific issue of empty CDP/LLDP data, other to try increasing the timespan and retry the call. Good luck...

RaphaelL · ‎May 4 2022

Hi , I find it a bit odd that a dedicated endpoint for LldpCdp doesn't provide all the raw info while a SwitchPortStatuses endpoint does provide it. I understand that LldpCdp also have to support MXs which may not show the raw cdp/lldp packet but it would have been way easier for us to provide the same info from both endpoint. ( More info = the better ) getDeviceSwitchPortsStatuse on a MS355 ( irrelevant info was omited for simplicity ) [ { "portId":"1", "enabled":true, "status":"Connected", "isUplink":false, "errors":[ ], "warnings":[ ] "cdp":{ "platform":"Cisco ATA 187", "deviceId":"ATA08cc68e86e8d", "portId":"Port 1", "address":"10.92.133.234", "version":"ATA 9-2-3SR1-1", "capabilities":"Host, VoIP phone" } }, { "portId":"2", "enabled":true, "status":"Connected", "isUplink":false, "errors":[ ], "warnings":[ ] "cdp":{ "platform":"Cisco IP Phone 7945", "deviceId":"SEP2C3ECF778925", "portId":"Port 1", "address":"10.92.133.223", "version":"SCCP45.9-4-2SR3-1S", "capabilities":"Host, VoIP phone, Two-port MAC relay" } } ] getDeviceLldpCdp on a MS355 { "ports":{ "1":{ "cdp":{ "sourcePort":"1", "deviceId":"ATA08cc68e86e8d", "address":"10.92.133.234", "portId":"Port 1" } }, "2":{ "cdp":{ "sourcePort":"2", "deviceId":"SEP2C3ECF778925", "address":"10.92.133.223", "portId":"Port 1" } } }, "sourceMac":"f8:9e:28:ed:f2:03" } For CDP , seems to be missing 'platform' , 'version' and 'capabilities' Thanks !

dade80vr · ‎May 4 2022

works, thank you

RaphaelL · ‎May 3 2022

Yes there are multiple ways to do it. You can get the clients from a network and validate if they are connected to a switch. https://developer.cisco.com/meraki/api-latest/#!get-network-clients

AhmedJawad · ‎May 3 2022

thank you all for your replies.

FabrizioRollo · ‎May 2 2022

You could also try to get the responde as JSON # print json content print(response.json()) Look at the Response section of the guide: https://docs.python-requests.org/en/latest/user/quickstart/

Bruce · ‎May 2 2022

From my understanding (which may be out of dat now), Meraki use MaxMind for their Geo IP database. You can use tools on their site (the demo portal) to test the location of up to 25 addresses a day. I was always of the understanding that the Geo-blocking only works in the upstream (outbound) direction. So if you have traffic coming from a blocked country it will potentially hit the servers (firewall rules permitting), but any return traffic will be dropped. This prevents and TCP connections from establishing, but does mean you potentially see traffic from ‘blocked’ countries hitting your servers - e.g. TCP SYNs, UDP and ICMP traffic. You’d need to check this to be sure though.

RaphaelL · ‎Apr 28 2022

Like Miles mentionned , the only way ( that I'm aware ) is to retrieve the Template ID via : getOrganizationConfigTemplates ( https://developer.cisco.com/meraki/api-latest/#!get-organization-config-templates ) Once you have that ID , you can use it as a parameter for the next call : getOrganizationNetworks ( https://developer.cisco.com/meraki/api-v1/#!get-organization-networks ) Which would look like : GET /organizations/{organizationId}/networks?configTemplateId=XXXXXXXXXXX

jadamczyk · ‎Apr 28 2022

Thank you, I was using wrong URL in Postman! However, I still get errors when using over 1000 client IDs in Python SDK, and 502 error in some cases. Those are for other questions, though.

Cmccord1 · ‎Apr 27 2022

Thank you so much! I tried this originally however my code was missing the part: email,name,password = "", "", "" This makes since, and I really appreciate your response. TY I ran the code with success.

RaphaelL · ‎Apr 26 2022

In my snipet , all the pages are appended and returned as the variable ''results''. Works like a charm for our 1900 networks and 4800 switches

Scott3 · ‎Apr 26 2022

Hi no it was tertiary in some cases.

AutomationDude · ‎Apr 19 2022

Hey Jim, please check this out this course I made. I think it should have everything you need: https://go.boundlessdigital.com/meraki-api-with-python-course/registration

MarcP · ‎Apr 18 2022

We use 4 SSIDs everywhere... And on some APs even 5 SSIDs. So far, no problems. And got a good amount of devices within the locations/networks.

RaphaelL · ‎Apr 15 2022

It might have been added to the stack. But this switch has been stacked for more than 2 years.

JGill · ‎Apr 13 2022

V1 on the API call. Call's are working again, so assuming something on the backend got corrected.

GelC · ‎Apr 3 2022

Hi @PhilipDAth. Noted on this Thank you for you help.

Bruce · ‎Apr 2 2022

@RaphaelL Well done on the 250 posts, and glad you’re enjoying the Meraki experience.

John_on_API · ‎Apr 1 2022

Yes, when the features ships GA, it will become part of the public API spec, and then the following version of the Python SDK would be generated to include it.

rhbirkelund · ‎Apr 1 2022

I've updated the script a little. import meraki ## Assume MERAKI_API_ENV_KEY environment variable dashboard = meraki.DashboardAPI() OrgID = "xxx" # Get Network IDs in Org OrgNetworks = dashboard.organizations.getOrganizationNetworks(OrgID, total_pages='all') # Initialise NetworkSsids = [] NetworksWithOutdatedEncryption = [] for network in OrgNetworks: # Test if network contains wireless if "wireless" in network['productTypes']: # Get SSIDs in network NetworkSsids = dashboard.wireless.getNetworkWirelessSsids(network['id']) # Traverse through SSIDs for ssid in NetworkSsids: # Initialise temporary dictionary tempDict = { 'networkId': None, 'ssidNumber': [] } # Test if WPA1 is contained in the Encprytion mode if 'wpaEncryptionMode' in ssid.keys() and ssid['enabled']: if "WPA1" in ssid['wpaEncryptionMode']: # Store relevant parameters tempDict['networkId'] = network['id'] tempDict['ssidNumber'].append(ssid['number']) NetworksWithOutdatedEncryption.append(tempDict) else: continue # Update Encprytion standard for network in NetworksWithOutdatedEncryption: UpdateSsid(network)

MarcP · ‎Mar 31 2022

Maybe something to do with: https://community.meraki.com/t5/Wireless-LAN/api-meraki-com-SSL-Certificate-expiring/m-p/145126#M20266

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges