Symptom

Last ACK received is not being updated after an ACK is received by SSM On-Prem. Router#show license status | begin Usage Reporting Usage Reporting: Last ACK received: <---------- Not updated Next ACK deadline: Nov 17 18:12:41 2024 GMT Reporting push interval: 0 (no reporting) Next ACK push check: Nov 18 17:39:46 2023 GMT Next report push: Last report push: Nov 17 13:59:22 2023 GMT Last report file write: If the device was previously registered but upgraded to an affected IOS-XE version,the Last ACK received will remain showing the old last ACK received date. Example: Router#show license status | begin Usage Reporting Usage Reporting: Last ACK received: Aug 20 11:10:01 2023 GMT <---------- Not updated Next ACK deadline: Nov 17 18:12:41 2024 GMT Reporting push interval: 0 (no reporting) Next ACK push check: Nov 18 17:39:46 2023 GMT Next report push: Last report push: Nov 17 13:59:22 2023 GMT Last report file write: Router#show license all | sec Smart Agent Smart Agent for Licensing: 5.1.30_rel/137 However from show logging and show license history messages we can see the ACK was received. Router#show logging | sec SIP *Nov 18 13:53:17.907: %SIP-5-LICENSING: SIP service is Up. License report acknowledged. Router#show license history message REQUEST: Nov 18 13:53:18 2023 GMT {"data":{"timestamp":1700304746060,"nonce":"7759951298143456120","poll_id":1887589975128958072,"action":"acknowledgements"}} RESPONSE: Nov 18 13:53:18 2023 GMT { "status": "COMPLETE", "message_code": "", "message": "", "timestamp": 1700269637713, "nonce": "7759951298143456120", "action": "acknowledgements", "poll_id": 1887589975128958072, "data": { "acknowledgements": [ { "sudi": { "udi_pid": "ISR4451-X/K9", "udi_serial_number": "XXXXXXXXXXX" }, "software_tag": "", "smart_license": "... Omitted for brevity

Conditions

Registered to SSM On-Prem Smart Agent 5.1.30 or lower Smart Agent 5.5.29 or lower Router#show license all | sec Smart Agent Smart Agent for Licensing: 5.1.30_rel/137

Workaround

Not available Fixed in IOS-XE 17.6.6 Fixed in IOS-XE 17.12.1

Further Problem Description