Meraki

BrianC · ‎Apr 29 2019

I'm examining the snapshots I've taken from our Meraki deployments, and I've noticed that the response to the CDP/LLDP query can come back empty ("{}") one minute and full of data the next. I can spot this missing data (the sourceMac field is supposed to be present) and compensate, but does anyone know what makes the data go away?

BrianC · ‎Apr 11 2019

@writ_er_relo Either Cisco has to add a new string field, or you have to work around it. Here's what I did: const idMatches = allMatches(/"id":(\d+)/g, body); return JSON.parse(body).map((org, i) => ({ id: idMatches[i][1], name: org.name, })); ...where "allMatches" is a function that returns all matches for a regex on a string.

BrianC · ‎Apr 5 2019

You could add a second field id_str, which would avoid a breaking change. At the moment I'm pulling the id out with a regex, which has got me going for now.

BrianC · ‎Apr 3 2019

A bit surprising that the first API call I ran in Meraki gave me trouble. I requested my organizations from /organizations, and I got back something like this: [{"id":321786418483472292,"name":"sample"}] But in Node.js, this parses as: [{ id: 321786418483472300, name: 'sample' }] ...because the "id" is two digits longer than Number.MAX_SAFE_INTEGER, making it unparseable in Javascript. If you know you have a 64-bit integer, put it in JSON as a string, the way Twitter does.

Meraki

Community

About BrianC

BrianC

Community Record

CDP/LLDP data empty depending on when I ask

Re: API: Organization IDs are larger than MAX_SAFE_INTEGER

Re: API: Organization IDs are larger than MAX_SAFE_INTEGER

API: Organization IDs are larger than MAX_SAFE_INTEGER

API: Organization IDs are larger than MAX_SAFE_INTEGER