Cisco Bug: CSCsz08931 - AAA Accounting stop Record not triggered when start is not sent for ssh
Jan 10, 2017
- Cisco Carrier Routing System
Known Affected Releases
Symptom: If the sending of the AAA accounting start record to the radius/tacacs fails because of the non-reachaility of the server then accounting stop record is not being triggered at all. Conditions: This happens in the following scenario 1) Configure a radius/tacacs server which is not started yet 2) Configure aaa start-stop accounting for exec from radius/tacacs 3) Bring up a ssh session to the router, wait for the start record attempt to fail 4) Start the radius/tacacs server configured Now when ssh session is exited the stop record is not triggered to the radius/tacacs configured.
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