07-07-2024 04:18 PM
We use the EOX API for automatically checking the EoL status of the PIDs we use in the network we manage.
It works well for most PIDs, but 2 of the PIDs we use incorrectly report as invalid PIDs.
Does it mean we can't rely on the EOX API to always provide valid information? I'd hate to miss a critical lifecycle milestone because we're checking the wrong source.
Query:
Response:
{
"EOXRecord": [
{
"EOLProductID": "",
"ProductIDDescription": "",
"ProductBulletinNumber": "",
"LinkToProductBulletinURL": "",
"EOXExternalAnnouncementDate": {
"value": "",
"dateFormat": null
},
"EndOfSaleDate": {
"value": "",
"dateFormat": null
},
"EndOfSWMaintenanceReleases": {
"value": "",
"dateFormat": null
},
"EndOfRoutineFailureAnalysisDate": {
"value": "",
"dateFormat": null
},
"EndOfServiceContractRenewal": {
"value": "",
"dateFormat": null
},
"LastDateOfSupport": {
"value": "",
"dateFormat": null
},
"EndOfSvcAttachDate": {
"value": "",
"dateFormat": null
},
"UpdatedTimeStamp": {
"value": "",
"dateFormat": null
},
"EOXError": {
"ErrorID": "SSA_ERR_021_Pid",
"ErrorDescription": "Incorrect PID: [SNS-3695-K9, C9300X-NW-A-12]"
},
"EOXMigrationDetails": {
"PIDActiveFlag": "",
"MigrationInformation": "",
"MigrationOption": "",
"MigrationProductId": "",
"MigrationProductName": "",
"MigrationStrategy": "",
"MigrationProductInfoURL": ""
},
"EOXInputType": "ShowEOXByPids",
"EOXInputValue": ""
}
]
}
If I try the Webex EoLBot (CiscoEoL@webex.bot) with the same PIDs it works fine.
>You: SNS-3695-K9
>CiscoEoL 3/07/2024 4:46 PM •
here is the EoS/EoL data for SKU: SNS-3695-K9
End of Sale Date: 2023-08-17
Last Ship Date: 2023-11-15
Last Date of Support: 2028-08-31
Product Bulletin URL: https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/secure-network-server-3615-3655-3695-eol.html
Migration Product ID: SNS-3795-K9
Latest Migration PID: SNS-3795-K9
>You: C9300X-NW-A-12
>CiscoEoL 3/07/2024 5:07 PM •
SKU is VALID there is NO EoL data for it
C9300X-NW-A-12 ----- C9300 Network Advantage, 12-port license
07-08-2024 03:10 AM
@sam-turner you would need to report this to TAC, or via the API team for this, to flag an issue. Odd one, as you presume the webex bot is just a API as you are.
Hope this helps.
07-09-2024 02:07 AM
Thanks, yes I sent an email to the Support API team. They are looking into it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide