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 a populating end of sale/end of life job for CISCO devices have to obtain api key and client secret from Cisco. Customers must have a valid Smart Net Total Care with Cisco to be able to obtain those keys.
You will also need to be able to access the below two URLs:
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.
- Cisco API keys settings – setup your Cisco client ID and secret. This can be found in settings under “Cisco API”
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
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.
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.