For devices that manufacturers provide API support to fetch end of sale and end of life dates, we can have a job to periodically fetching the dates and populate end of sale/end of life fields of the devices. For Cisco devices, we can use Cisco Support APIs to fetch this data.


Cisco Support APIs onboarding

Every customer who wants to use the end of sale/end of life population job for CISCO devices will need to obtain an API key and client secret from Cisco. This requires those customers to have a valid Smart Net Total Care with Cisco to be able to obtain those keys.

The process for onboarding and setting up a user account with the API Developer role are documented at https://developer.cisco.com/docs/support-apis/#!user-onboarding-process.

And the process for registering an application is documented at: 

https://developer.cisco.com/docs/support-apis/#!application-registration/application-registration

If there are issues with onboarding, please raise it on the Cisco Community forums. If your account has the Smart Net Total Care API Developer role, and you still don't see the EOX API in your API Console, you may need to reach out to Cisco API Support.

The Cisco API console can be found here:

https://apiconsole.cisco.com/apps/register


 

Device's fields used for query

Device's HW vendor field is used to choose which manufacturer to fetch the data from.

For Cisco devices, Model and Serial number are used to query for the end of sale/end of life dates.


User Interface

  1. Cisco API keys settings – setup your Cisco client ID and secret.  This can be found in settings under “Cisco API”

Graphical user interface, application

Description automatically generated

 

 

 2. Ad-hoc population from Device menu


    3. New Job – you can create a job that can be run to update the Cisco API for all, or specific, Cisco devices

Graphical user interface, application

Description automatically generated

 

 4. Results from API call or job


 

Systems without Internet access

It's not possible to fetch end of sale dates from Cisco server without Internet access. However, users can export inventory as a csv file which can be used to import into Cisco Services. Then users can export a csv file from Cisco Services and import into the system to update end of life dates. 

 

Please note that Cisco Services does not include end of sale dates in the export file.

 

To export a csv file that can be used to import into Cisco Services please select “Export inventory as Cisco csv file” from Inventory menu.

 

 

Graphical user interface, application

Description automatically generated

 

 

Reporting

In the Reporting section, there is a new report “End of Sale/End of Life” that can be run to generate a report showing any devices that have eos/eol tag.  This report can also be setup to run as a job.