Cisco Bug: CSCvu65829 - tams_process_tamc_cmd error:TAM_ERROR_NO_SESSION
Jul 16, 2020
- Cisco 8000 Series Routers
Known Affected Releases
Symptom: The TAM Service Client APP command may get rejected with error TAM_ERROR_NO_SESSION because the APP cached session context might already have invalidated by TAM Service. The TAM Service Client APPs are, fpd_client, tam_sync, attestation, authentication and etc., Conditions: The TAM Service has preset max client APP sessions to serve at a time and oldest sessions will be freed without notifying client APP to accommodate new sessions when it reached maximum. The REST communication from x86 to secondary node APP uses the TAM service to get authenticated and repeated secondary node reboot causes this client APP to leak the session context because it wasn't freed properly. All other client APPs cached context are invalidated by TAM service once it reached the max sessions (it is 20 and increased to 50 later). So those client new commands will be rejected because the cached sessions were invalidated by TAM Service already.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases