Meraki

CBurkhead · ‎Nov 25 2019

As an FYI, we are using the per-device licensing. So the first call is still works in that case and returns valid data.

CBurkhead · ‎Nov 25 2019

I would expect to see the MX68W in the license count too, if you have the license. I just ran my script to get the license and device counts for my organizations and it seems to be working fine. I do not have an MX68W in any of my organizations,but one does have an MX68CW license and that is being reported correctly.

CBurkhead · ‎Nov 14 2019

I wrote my own Python test code, which can be seen in the other thread that I mentioned in a previous post, using requests and the API endpoint. I did not have any issues, either.

CBurkhead · ‎Nov 14 2019

You might want to look at the following thread. You are not the only person having problems doing this. https://community.meraki.com/t5/Developers-APIs/Bug-with-create-organisation-network-API-Only-works-when-a-copy/m-p/66783#M2240

CBurkhead · ‎Nov 14 2019

Already have my application in. 🙂

CBurkhead · ‎Nov 6 2019

I can't speak to that code and what it is doing, but I am able to create a new network in an organization using the /organizations/{organizationId}/networks endpoint without specifying a network ID to copy from or a value for disableRemoteStatusPage. The basics of this code is the following: import requests import json header = {'X-Cisco-Meraki-API-Key': myAPIkey} header.update({'Content-Type':'application/json'}) orgId = '9876543210' url = 'https://api.meraki.com/api/v0/organizations/'+orgId+'/networks' payload = {'name':'Test Network','type':'appliance','timeZone':'US/Eastern'} response = requests.request('POST', url, data=json.dumps(payload), headers=header) This code returns a code of 201 and the network does get created. If I had to guess what the problem is for the supplied code, I would say that create_organization_network.copy_from_network_id needs some kind of value. If you don't want to supply a network ID, try assigning a value of None to it.

CBurkhead · ‎Nov 6 2019

That should not be an issue on my end. I already have this endpoint going through a function to pull all of the page data and concatenating it. Thanks for the information. It is good to know that the results could be affected by the backend processing.

CBurkhead · ‎Nov 5 2019

I have also never seen that structure before. Admittedly, I am still fairly new to Python, but I'd think that if it was something being used at all frequently, I'd have seen it at least once. I also spent some time on Google last night and I have yet to find a reference to this. @jdsilva if you find something, please point me in the right direction. At first glance it just looks like adding [] to the dictionary key value. But if that is all it is, then I don't see why you would not just use "includedEventTypes", as you said.

CBurkhead · ‎Nov 4 2019

Confirmed, this is now working. For anyone that does not want to dissect that Python code, the relevant information is the following: query = {'includedEventTypes[]':['failover_event','dhcp_lease'],'perPage':'25'} response = requests.request("GET", url, params=query, headers=header) For includedEventTypes or excludedEventTypes, you need to put the [] after the keyword as part of the key. The parameters are given as a list. Make sure you also specify the productType if you are querying a combined network. This is not necessary if the network contains only one type of device.

CBurkhead · ‎Nov 4 2019

Seems like all functionality for this endpoint beyond pulling all events is broken. Important safety tip, if you are grabbing all of the events, use the pageStartAt/pageEndAt data from each call to help determine how much data you want to pull. If you just grab it until there is no more you will end up with a huge amount of data. I think I stopped when I was initially looking at this when I was at 45 days back and 50,000+ records. Since there is no time period specified in the API call, you have to do it yourself.

CBurkhead · ‎Nov 4 2019

I am tending to see DHCP lease events and VPN events. All of those would be expected for the networks I am looking at. Have not been able to get past the 10 events. Have not tried asking for fewer than 10, but I bet I'd still get 10.

CBurkhead · ‎Nov 1 2019

OK, I have some more data. If you don't use params= in the requests line, and use data= instead, you will get the same information back regardless of whether you do a json.dumps for the query. It is still not giving me the events I am asking for and not giving me the number of entries per page I specify, but I am also not getting the error 400. I have also found that you don't need to specify the productType for a non-combined network if you do the json.dumps with params= or pass the query (with or without jason.dumps) using data=. Seems like that parameter really isn't required in this circumstance. @jdsilva are you seeing the same thing I am seeing? Do you just get the 10 most recent events for the network you are querying with no regard for the event(s) you asked for?

CBurkhead · ‎Oct 31 2019

A couple of notes, the ErrorCheck function that gets called is my internal function that converts the returned data to JSON and verifies there are no errors. It returns the data from the endpoint or a value of None. Also, I have had to modify this function a couple of times depending on the data that the endpoint is returning. It was originally made for getting client data, which was just lists of data. You might have to alter how the data is appended if you are getting a dictionary with lists in it or some other format. It does work as written for networks/{networkID}/clients.

CBurkhead · ‎Oct 31 2019

Here is the Python function for doing this. # This function takes the API URL and query string. It returns all of the JSON data from the API request that has # been broken up into pages of data. def GetPages(url,query): data = [] done = False while done == False: try: ret = requests.request('GET', url, headers=g_header, params=query) except requests.exceptions.ConnectionError: print('A connection error has occurred while getting the page information.\n') return None # Append the new data to the existing. data += ErrorCheck(ret) # Get the page URLs from the HTTP header of the API call and split it into the URLs. pages = ret.headers['Link'].split(',') # See if there is a page for the 'next' page of data. page = next((i for i in pages if 'rel=next' in i), None) if page != None: # Isolate the token and then add it to the new query. token = page.split('startingAfter=')[1] token = token.split('&')[0] query['startingAfter'] = token else: done = True return data The call to this would be something like: clientlist = GetPages(url,querystring) Where url is the full URL to the endpoint and querystring would be the parameters you want, like {'timespan':'30','perPage':'1000'}

CBurkhead · ‎Oct 31 2019

Well...I have good news and bad news. Good news first. I have gotten past the 400 error and am now getting data back from the endpoint using the includedEventTypes parameter. What needed to be done is the parameters sent to the endpoint needed to be dumped to JSON format, first. So, here is the updated line of code. BTW, this also works if you use data= instead of params=. response = requests.request("GET", url, params=json.dumps(query), headers=header) Now for the bad news. The data returned seems to totally ignore what ever event you specified for includedEventTypes. I was specifying failover_event and was getting DHCP and VPN events. I changed the event to client_connectivity and got the same events returned. Also, when specifying a perPage value, that is also ignored. I always got 10 events. They seem to be the 10 most recent events, regardless of the event type. We might be a bit closer to being able to use this endpoint without doing our own parsing, but I think it is still broken.

CBurkhead · ‎Oct 31 2019

That is the same error I have been seeing using a different endpoint (/networks/{networkId}/events) for the includedEventTypes parameter. No matter how I specify the data, I am told that that it must be an array. Hopefully, the answer for this problem will be the same for this other endpoint.

CBurkhead · ‎Oct 24 2019

There is no API call for this that I know of, but you can get a good idea if an AP is in repeater mode by checking the online status of the AP and seeing if it is offline. If it is not and the AP does not have a LAN IP, it is probably in repeater mode.

CBurkhead · ‎Oct 24 2019

Update: When I was trying this endpoint yesterday, before running into the issue with the includedEventTypes, I was getting an error 500. I was not sure why, but with the information from @TonyC, I know what was happening. It looks like the productType is required. If I specify only productType=appliance, I can pull the data from the event log. So, the following, works just fine. url = 'https://api.meraki.com/api/v0/networks/'+netId+'/events' query = {'productType':'appliance'} response = requests.request("GET", url, params=query, headers=header) You still have to do your own parsing if you are looking for particular events, but at least there is a method for getting the data.

CBurkhead · ‎Oct 24 2019

I added in the productType and I am still getting the error 400. Verified the URL that is being constructed in requests and it looks correct to me. It comes back as: https://n112.meraki.com/api/v0/networks/N_XXXXXXXXXXXXXXXXXX/events?productType=appliance&includedEventTypes=failover_event @jdsilva are you still getting the error?

CBurkhead · ‎Oct 23 2019

No worries. I was about the post the list I got, which had the information as the second entry. Guess we go back to "its broken" and wait for Meraki to address the problem. Love being on the bleeding edge of things. 🙂

CBurkhead · ‎Oct 23 2019

OK, thanks for the sanity check @jdsilva! I read the details of that parameter as a Python list, too. Makes sense given that you could be specifying multiple events to include. It seems broken to me as well. Hopefully, that will be remedied soon. Getting access to the "failover_event" information will allow me to start collecting data via the API for a customer that wants some special reporting for their store locations.

CBurkhead · ‎Oct 23 2019

I am beginning to look at this endpoint and I am running into a problem getting the event log information. I found the event type I wanted by looking at /networks/{networkId}/events/eventTypes, which is "failover_event" (Primary uplink status change). When I am pulling the data, I am getting an error 400 with the message that: "'includedEventTypes' must be an array" Here is the code snippet that I am using for testing: url = 'https://api.meraki.com/api/v0/networks/'+netId+'/events' query = {'includedEventTypes':'failover_event'} response = requests.request("GET", url, params=query, headers=header) It does not matter if I specify the "failover_event" as a string, make it a Python list (['failover_event']), or integrate it into the URL itself and change the code to: url = 'https://api.meraki.com/api/v0/networks/'+netId+'/events?includedEventTypes=failover_event' response = requests.request("GET", url, headers=header) I always get the error 400 and the same error message. any thoughts on how I can get around this and format the parameter correctly in Python?

CBurkhead · ‎Oct 14 2019

From what PagerDuty has said, we may be able to alter how the alerts are sent to PagerDuty from Meraki, but we would need to change the Javascript that the hook is written in. No one here has enough JS experience to want to try that, and we have better things to do than altering that code. Actually I have already written an HTTP server/event parser as an interface between N-Able/N-Central and PagerDuty. But, because we don't have the certificate for SSL on the server that runs it, I can't get the Meraki webhook to talk to it.

CBurkhead · ‎Oct 14 2019

We are in the process of doing some testing with Meraki webhooks and integrating with PagerDuty for alerts that get generated by our devices. We have the webhook setup and the alerts are getting through to PagerDuty. What we are seeing however, is that when the devices comes back online, the "back online" message is generating a new alert in PagerDuty instead of resolving the existing alert. PagerDuty support is telling us that the interface from Meraki to PagerDuty was written by Meraki. Has anyone done this integration and have you seen this problem? What, if anything, did you do to resolve it? Thanks!

CBurkhead · ‎Oct 8 2019

I am glad that you were able to solve the problem! I had a feeling that the double quotes around the vlans would help. I have found that when I am not sure about the format of the data based on the endpoint documentation, I use the GET for the information I want to modify and then look at the data in my debugger, or at least print it out. If I need a particular scenario, I will set it up on a device and then pull the data and look at it. This is how I saw that the vlans had to be a string. In your situation, looking at the data from the GET might have given you the insight you needed, if you already had an MX that had multiple vlans defined on a port, and not just 'all'. For debugging things like this, print() and the debugger in an IDE are your friends.

About CBurkhead

CBurkhead

Community Record

Badges