Streamlining Meraki EOL page

[rhbirkelund]

I'm working on something with the Meraki EOL page, but I'm having difficulty in getting a clean and consistent result with my script, due to the fact that some of the entries in the EoL page do not follow the same "formatting" as other entries.

E.g. the MX64 and MX64W are in the same row.Or the MV21 and MV71 cameras being different models with same EoL date, and being on the same row, in contrast to some other devices.

It would also be nice, if the entries would be specifc models, rather than just "MS220 series".

Also, perhaps move the country specific codes to a column itself?

It would also be nice, if the dates would be consistent aswell, instead of switching back and forth between e.g. "Jul" and "July".

[KarstenI]

After thinking about it, all the EOL information should be available via the API, with the results being clean JSON objects.

[rhbirkelund]

Are they, or is it just a suggestion? Because I'd love if it was already an endpoint. 🙂

[KarstenI]

Nothing more than a little daydream. At least I am not aware of something like this.

[rhbirkelund]

Fair enough. Must have been more of a fever dream then. 😂

[jimmyt234]

This may do something similar (haven't tried it, so can't verify): Francisco-1088/merakiLifecycleReport - Cisco Code Exchange

[rhbirkelund]

Thanks for the reference. It doesn't really seem to be maintained, since it's using old modules. I'll look into it though. 🙂

[PhilipDAth]

I just had an idea.  Cisco has an "EoX" API.  I wonder if you can look up Meraki part codes with that.

https://developer.cisco.com/docs/support-apis/#!eox/get-eox-by-dates 

[rhbirkelund]

Uuh.. I did just finish my modified version of the one that @jimmyt234 referenced, but I’ll take a look at the EoX api. 😄

[rhbirkelund]

Meh.

I got so far as to generating an access token, after registering my app.

But the EoX endpoint fails with "Developer Inactive", and this seems to be a known "issue", where one has to go through TAC to get that fixed according to Cisco Community.

The apix.cisco.com/hello, seems to work, so something must be okay, though.

But this should be the way to do it. I just can't check it. Assuming the "app" is registered in Cisco API Console

curl -L --request POST \
--url "https://id.cisco.com/oauth2/default/v1/token" \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data 'grant_type=client_credentials&client_id=[AwesomeClientId]&client_secret=[AwesomeClientSecret]'

which returns the access token to be used in;

curl --location 'https://apix.cisco.com/supporttools/eox/rest/5/EOXBySerialNumber/1/[serial]?responseencoding=json' --header 'Authorization: Bearer MyAwesomeAccessToken'